This topic applies only on the z/OS operating system.

Customization Dialog variables

The Customization Dialog provides a means to save dialog variable values from one session to the next using the Customization Dialog save files. ISPF can save these variables from one session to the next; in addition, the Customization Dialog can save WebSphere® Application Server customization variables in data sets that can be reloaded during later customization sessions.

The WebSphere Application Server for z/OS® Customization Dialog uses ISPF variables to store customization values. Although it is possible to reenter these values every time you use the Customization Dialog, this process can be time-consuming and error-prone.

Customization Dialog save files

The Customization Dialog provides its own method for saving and reusing dialog variable values. From most task menus, you can type S on the command line to save the current dialog variables in a file, and type L on the command line to restore dialog variables from a previously-created save file. These files are ordinary z/OS sequential files (RECFM=VB, LRECL=255) with one variable-value pair per line.

Because values in save files are explicitly saved and restored, you are somewhat less likely to use them accidently when customizing a different cell than values stored in the ISPF profile. Also, you can use the save file name to identify the WebSphere Application Server for z/OS cell or node for which they are created, the WebSphere Application Server for z/OS version and release, and so on. You can use a Customization Dialog save file, together with the WebSphere Application Server for z/OS product files, to recreate the WebSphere Application Server for z/OS customization data sets (.CNTL and .DATA) at any time.

One save file that is particularly important is the security domain save file. You should save the security domain values during the creation of each WebSphere Application Server for z/OS security domain and import them whenever you create a new stand-alone application server or Network Deployment cell in that security domain. Within the dialog panels for cell creation, you can view the security domain settings but you can not change them. The panels have specific numbered options for saving the newly created security domain values and restoring them during cell creation so that you do not forget.

Once you have finishing setting customization variable values for a new stand-alone application server or Network Deployment cell, save the variable values before proceeding with customization. This allows you to more easily restart the customization process if you discover you have made an error during customization. You can also import the appropriate saved values when performing tasks, such as federating a stand-alone application server or creating a new managed node, on an existing Network Deployment cell.

The following are some cautions that you should take when working with Customization Dialog save files:
  • Customization Dialog save files might contain unencrypted passwords and other sensitive information. Make sure that access to the save files is restricted.
  • Save files created with the S command include the security domain variables as well. If you need to restore values from both a regular save file and a security domain save file, therefore, restore the security domain save file last.
  • Do not edit Customization Dialog save files directly—-instead, restore them in a Customization Dialog session, make the appropriate changes, and save the values again.
You can also use Customization Dialog save files to check for typing errors and similar problems by sorting the save file on the columns containing the dialog variable values. This can help detect typographic errors in product data set names and so on as well as detect ports or UNIX® UID/GID values that are accidently reused within a particular configuration.

The instructions for each configuration task provide guidance on restoring and saving Customization Dialog variable values.

ISPF variable pools

Variable pools are a feature of ISPF that allow the dialog variables for one application to reside separate from those for other applications. Whenever you start the dialog using the ISPSTART command, you can use the NEWAPPL option to assign a one to four character name to the application and its variable pool. Variable pool names must be one to four characters long, alphanumeric, and begin with an alphabetic letter. The default variable pool name for the WebSphere Application Server for z/OS Customization Dialog is BBO6.

When you exit ISPF normally, the current editor settings and dialog variable values for each variable pool are saved in a pair of members in the user ID's ISPPROF (ISPF profile) data set. The data set name of the ISPPROF data set is usually something like userid.ISPF.ISPPROF, but it can vary from installation to installation. When saving settings for application xxxx, the editor settings are saved in member xxxxEDIT and the variable settings are saved in member xxxxPROF.

You can use the APPL option when starting the WebSphere Application Server for z/OS Customization Dialog to specify the application name (variable pool) that you want to use:

EXEC 'was_hlq.SBBOCLIB(BBOWSTRT)' 'APPL(xxxx)'

Whenever you start the Customization Dialog for the first time with a particular application name, the product copyright page is displayed before the main menu appears. Each Customization Dialog task menu panel shows the application name in the upper right-hand corner, labelled "Appl:".

By using different application names, you can separate variable pools for different WebSphere Application Server for z/OS releases, target systems, or cells. Just be sure to specify the same APPL value whenever you start the Customization Dialog in order to work with a particular WebSphere Application Server for z/OS customization task. You should also use customization save files (described in the following section) to provide long-term, more easily documented backup of customization variable values.

To delete all information from an ISPF variable pool, delete the xxxxEDIT and xxxxPROF members from the ISPPROF data set.
Note: Ensure when you do this that the ISPF application that uses the variable pool is not active.

If an ISPF dialog such as the WebSphere Application Server for z/OS Customization Dialog terminates abnormally, the variable pool members in the ISPPROF data set will not be updated.




Related concepts
[z/OS] WebSphere Application Server for z/OS terminology
Related tasks
[z/OS] Using the Customization Dialog
Concept topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 9:31:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=cins_cdvariables
File name: cins_cdvariables.html