GENERATE options

You can use the OPTION parameter for the GENERATE action to control certain processing. This topic describes the available options for use with the GENERATE action.

Overview of GENERATE options

Table 1 provides an overview of the GENERATE options that are available. Each of the available options is described in more detail in GENERATE OPTION keywords.

Table 1. Overview of GENERATE options
OPTION	Abbreviation	Description
USS	–	Run only the GENERATE workflow stage that deploys the parts related to z/OS® UNIX System Services. This option requires a complete run of the GENERATE action prior to use.
NOUSS	–	Do not run the z/OS UNIX deploy stage in the GENERATE action.
SECEXITS	SEC	Perform configuration for security exits only. This option requires a complete run of the GENERATE action prior to use.
VALIDATE	VAL	Perform initial validation of RTEDEF parameters.
QUICKLOAD	QL	Load the read-only configuration members to the RK* data sets. The read-only members are those members that are not impacted by customization during configuration. This option requires a complete run of the GENERATE action prior to use.
QUICKCONFIG	QC	Update the configurable members for the runtime environment (for example, in the RKANPARU, RKANSAMU, and RKANCMDU libraries) without refreshing data from SMP/E target libraries. This option requires a complete run of the GENERATE action prior to use.
RELINK	LINK	Assemble and link edit modules for OMEGAMON for Networks (KN3) and OMEGAMON enhanced 3270 user interface (KOB). This option requires a complete run of the GENERATE action prior to use.
TRGCOPY	TRG	Make a copy of your SMP/E target libraries, from which you can create or update your runtime environments.
PREPARE	PREP	Prepare work data sets for your runtime environment. You can use this option to build the work data sets before other GENERATE action stages, in preparation of OMEGAMON installation or maintenance.

To specify more than one option, separate the values with a comma and no spaces. For example: OPTION USS,SECEXITS

Compatibility of GENERATE options

Some options are not compatible to run with other options during the same job. Table 2 indicates which options are compatible. Y in the table cell indicates that you can specify the two options together in the same job. N in the table cell indicates that you cannot specify the two options together in the same job.

Table 2. Compatibility of GENERATE options
	USS	NOUSS	SECEXITS	VALIDATE	QUICKLOAD	QUICKCONFIG	RELINK	TRGCOPY	PREPARE
USS	—	N	Y	N	Y	Y	Y	N	N
NOUSS	N	—	N	N	N	N	N	Y	N
SECEXITS	Y	N	—	N	Y	Y	Y	N	N
VALIDATE	N	N	N	—	N	N	N	N	N
QUICKLOAD	Y	N	Y	N	—	Y	Y	N	N
QUICKCONFIG	Y	N	Y	N	Y	—	Y	N	N
RELINK	Y	N	Y	N	Y	Y	—	N	N
TRGCOPY	N	Y	N	N	N	N	N	—	N
PREPARE	N	N	N	N	N	N	N	N	—

GENERATE OPTION keywords

USS | NOUSS

You can optionally control when to run the GENERATE workflow stage that deploys the parts related to z/OS UNIX. By default, the GENERATE action automatically performs any required z/OS UNIX configuration. However, there might be cases where you would want to skip this step (for reasons such as authorization issues), and perform this step at a later time. You can use the OPTION parameter to specify the NOUSS or USS value to control this processing, as follows:

NOUSS

When OPTION NOUSS is specified, the GENERATE action does not run the stage that deploys the parts related to z/OS UNIX. You can use this option on the initial run of the GENERATE action for a new runtime environment, as well an on subsequent runs.

USS

When OPTION USS is specified, the GENERATE action runs only the stage that deploys the parts related to z/OS UNIX; no other processing is performed (unless another OPTION value is also specified, such as SECEXITS). You cannot use this option on the initial run of the GENERATE action for a new runtime environment; it can only be used on subsequent runs.

Important:

You must perform a complete run of the GENERATE action before you can use OPTION USS.
If you have changed any parameters inside your RTEDEF members that impact z/OS UNIX configuration, do not use OPTION USS, because it will not capture your parameter changes. Instead, run action GENERATE with OPTION NOUSS (or without the option) to reconfigure the members related to z/OS UNIX. Then, you can use OPTION USS to move the updated members to z/OS UNIX.

SECEXITS

You can perform configuration processing for security exits separately from the rest of the of GENERATE workflow. By default, the GENERATE action automatically performs the required configuration tasks for security exits, which includes rebuilding and relinking the security exits. By performing these tasks separately, you can save valuable CPU cycles.

When OPTION SECEXITS is specified, the GENERATE action performs configuration for security exits only; no other processing is performed (unless another OPTION value is also specified, such as USS). You cannot use this option on the initial run of the GENERATE action for a new runtime environment; it can only be used on subsequent runs.

Important: You must perform a complete run of the GENERATE action before you can use the SECEXITS option.

For more information about creating your security exits library, see Setting up security exits in your runtime environment.

VALIDATE

You can verify that all parameters specified in the RTEDEF data set have correct values and that you are not missing anything. This option helps you to prepare for running the full GENERATE action. OPTION VALIDATE will re-create interim and work libraries and will perform validation steps to ensure that your configuration is correct. You cannot use the VALIDATE option with any other OPTION value. After running the GENERATE action with OPTION VALIDATE, you can find the validation report using the $VALRPT DD statement.

Attention: If you previously used PARMGEN for configuration, be aware that using the GENERATE action with OPTION VALIDATE will re-create the WCONFIG data set, which will invalidate the PARMGEN configuration. This means that if you migrate a runtime environment from PARMGEN to Configuration Manager using the MIGRATE action, and then perform the GENERATE action with OPTION VALIDATE, you can no longer use the PARMGEN configuration.

QUICKLOAD

Using OPTION QUICKLOAD, you can load the read-only configuration members to the RK* data sets. The read-only members are those members that are not impacted by customization during configuration.

OPTION QUICKLOAD is compatible with the USS and SECEXITS options, but is not compatible with the VALIDATE and NOUSS options. This option requires a complete run of the GENERATE action prior to use.

QUICKCONFIG

With this option, you can quickly reconfigure your products without reloading the read-only runtime members or refreshing data from SMP/E target libraries. Using this option can improve performance, with the most impact experienced when using a full runtime environment (RTE_TYPE parameter is set to FULL).

When OPTION QUICKCONFIG is specified, the GENERATE action updates the configurable members for the runtime environment (for example, in the RKANPARU, RKANSAMU, and RKANCMDU libraries) without refreshing data from SMP/E target libraries. The read-only members, which are members that are not impacted by customization during configuration, are not loaded to the RK* data sets.

More specifically, running the GENERATE action with OPTION QUICKCONFIG performs the following actions:

Validates parameters
Allocates missing data sets
Updates configurable members for the runtime environment (for example, in the RKANPARU, RKANSAMU, and RKANCMDU libraries)
Updates started tasks, VTAM list, and VTAM node
Updates z/OS UNIX-related members, but does not deploy them to the z/OS UNIX directories or files. To deploy prepared members to z/OS UNIX files or directories, you must combine the QUICKCONFIG option with the USS option.

Running the GENERATE action with OPTION QUICKCONFIG does not perform the following actions:

Refresh data from SMP/E target libraries
Update read-only modules from SMP/E target libraries
Update z/OS UNIX files or directories
Perform any assembly or linking operations related to security exits or other load modules

You cannot use the QUICKCONFIG option with the VALIDATE option or the NOUSS option. The QUICKCONFIG option requires a complete run of the GENERATE action prior to use.

RELINK

Use OPTION RELINK to assemble and link elements into the SYSLMOD RKANMOD* load library when a relink of IBM Z OMEGAMON AI for Networks (KN3) or OMEGAMON Enhanced 3270 User Interface (KOB) modules is required, such as when applying maintenance.

Note: If you are familiar with PARMGEN, the RELINK option performs the same function as the PARMGEN KCIJPLNK job (Run post-SMP/E RKANMODU ASM/LINK steps).

Tip: You can customize the binder program that is used by specifying the program name in parameter GBL_UTIL_BINDER.

When using the GENERATE action with OPTION RELINK, the details differ depending on the environment where the action runs, as follows:

On a local system (the configuration system in a remote deployment scenario)

You can run the GENERATE action with OPTION RELINK on a local system to assemble and link elements.

On a remote environment with a different z/OS level

You can run the GENERATE action with OPTION RELINK on a target system that is at a different z/OS level than the configuration system. You do not need to run all the steps in the remote deployment scenario (GENERATE action, PACKAGE action, transfer data sets, DEPLOY action).

Using the RELINK option requires the SMP/E library TKANMODS to be present on the target system. The TKANMODS library is not part of the full runtime environment, and it is not created by the BLDREMDS action. In other words, you must have an SMP/E environment present to ensure consistency. As a result, you must run Configuration Manager from the same SMP/E libraries.

You can rerun the GENERATE action with OPTION RELINK as needed.

When you use the RELINK option to relink modules on a remote environment at a different z/OS level, you might have different settings in the libraries set by parameters GBL_DSN_SYS1_MACLIB and GBL_DSN_CEE_SCEELKED than what you would have on your local system. If there are significant differences in the contents of those libraries, which control how modules are being assembled and linked, then you should run the GENERATE action with OPTION RELINK on the target system.

On a remote environment with the same z/OS level

You can run the GENERATE action with OPTION RELINK on a target system that is at the same z/OS level as the configuration system. In this environment, there is not an SMP/E environment on the target system, and only the minimal set of libraries is transferred to perform the DEPLOY action.

You can run the following series of steps:

GENERATE action with OPTION RELINK
PACKAGE action
Transfer of data sets
DEPLOY action

This implementation saves CPU cycles on the GENERATE step.

For a full runtime environment

In a full runtime environment, you must run the GENERATE action with OPTION QUICKLOAD,RELINK to achieve the correct relinking results. (This requirement is due to a dependency on the RKANSAM data set).

TRGCOPY

Use OPTION TRGCOPY to make a copy of your SMP/E target libraries, from which you can create or update your runtime environments. You can abbreviate this keyword to TRG. For more information, see Using SMP/E target library copies.

PREPARE

Use OPTION PREPARE to prepare intermediate work libraries for your runtime environment. You can use this option to build the work data sets before other GENERATE action workflow stages, in preparation of OMEGAMON installation or maintenance. You might find this option useful if you have to perform other related tasks that require the work data sets ahead of time or in parallel, such as preparing members for Db2 binds or copying started task members to PROCLIB libraries.

With this option, you can run the GENERATE action with OPTION PREPARE initially to create the work data sets, and then, when you are ready, run the GENERATE option again (without the PREPARE option) to complete the additional workflow stages. You cannot use the PREPARE option with any other OPTION value.

Important: If you use the PREPARE option to create the work data sets, you must be at the same Configuration Manager maintenance level when you run subsequent GENERATE action jobs without the PREPARE option.

More specifically, running the GENERATE action with OPTION PREPARE performs the following actions:

Validates parameter values
Performs parsing steps
Allocates and refreshes the interim staging (IK*) and work (WK*) libraries. These libraries will be copied to the runtime (RK*) libraries later.
Allocates and refreshes PROCLIB, VTAMLST, and VTAMLIB libraries. These libraries contain started tasks, VTAM lists, and VTAM nodes.
Important: Data sets specified in parameters GBL_DSN_SYS1_PROCLIB, GBL_DSN_SYS1_VTAMLIB, and GBL_DSN_SYS1_VTAMLST will be impacted.
Updates the global user library specified in parameter GBL_USER_JCL, which contains global parameters.
Important: Any changes to the following RTEDEF members will impact your existing runtime environment: VAR$GLOB, VAR$lpar, and SYS@lpar
Creates a checkpoint. At the end of the job, the GENERATE action with OPTION PREPARE creates member $PREPARE in the WKANPARU library and populates it with the checkpoint creation date and time, as follows:
```
******************* Top of Data ******************
* Checkpoint created by userID on yyyy-mm-dd hh:mm:ss
****************** Bottom of Data ****************
```
If the checkpoint is detected, subsequent GENERATE action jobs (without the PREPARE option) bypass the workflow stages performed by the PREPARE option and resume processing with the remaining workflow stages. The GENERATE action then deletes the $PREPARE member at the end of the job.
Note: The checkpoint is not removed if any of the following options are used: USS, SECEXITS, RELINK, QUICKLOAD