ISPF

A default configuration load module ISPCFIG is shipped with ISPF. It is used if you choose to make no customizations for your installation. If you do want to create your own configuration table, use msys for Setup to create instances of ISPF Configuration Table load modules or package them as SMP/E installable usermods.

The following tasks are required to modify the configurations settings, create a configuration table keyword file, build a configuration table load module or package it as an SMP/E usermod.

  1. Set the ISPF Policy An ISPF specific policy is available to let you define properties of the msys for Setup ISPF data sets. Among other parameters the high level qualifier to be used for these data sets can be defined here.
  2. Customize ISPF allows you to modify ISPF configuration settings for improved performance and usability and specify that you want to create an ISPF Configuration Table load module or package it as an SMP/E installable usermod. The ISPF Customization dialogs allow you to set two types of values: system-wide values and user-specific values. System-wide values are values that are used for all users and are re-read for the Configuration Table at the beginning of each ISPF session. User-specific values are used as initial values when a new profile is created.
  3. Perform Update to build the ISPF Configuration keyword file from the data specified in the customization dialogs and convert it to an ISPF Configuration Table load module and optionally specify to have it packaged as an SMP/E installable usermod. Note that the keyword file, load module or usermod built during this step is created in msys for Setup ISPF staging data sets. See Set the ISPF Policy for specifying the allocation parameters for these data sets.
  4. Commit Updates to copy the ISPF Configuration table load module or usermod from the staging data sets to the output data sets that you specified in the customization dialog. The load module must be placed in the standard MVS search sequence or allocated to ISPLLIB for ISPF to use the values specified.

If, for some reason you have to Undo Updates, the ISPF Configuration Table keyword file, load module, and usermods will be deleted from both the staging data sets and the output data sets.