How the utilities build options
This section describes how the utilities build options.
For information about how the Image Copy function builds options, see Global options modules—Prefix Resolution/Update function.
At execution time, each utility follows an iterative process to determine which options values you want to use for a particular database. Each succeeding step replaces keyword values that were determined in the previous step:
- Each utility builds an initial parameter table from the internally coded default values.
Each utility searches for customization modules, as shown in the following table.
Product
First searches for
Then searches for
Online Reorg function (with limited prefix resolution and update support for logical relationships; for limitations, see Limitations-of-the-various-functions-of-BMC-AMI-Online-Reorg-for-IMS-solutions)
FRF$GLBL
NA
Reorg function
FRF$GLBL
NA
Unload function
ULPPARMS
ULP@imsi
Reload function
LDPPARMS
LDP@imsi
Index Build function
SIUPARMS
SIU@imsi
Prefix Resolution/Update function
PRPPARMS
PRP@imsi
Each utility merges the values coded in the modules it finds first to replace values in the parameter table.
- The Unload function and the Reload function search the PDX for a PDX customization member that is associated with this DBD and IMSID. If the functions cannot find a PDX customization member, they search the PDX named in the JCL or the global options table for a PDX customization member named DFLT. If the DFLT member exists, it was created with an earlier release of a BMC utility.
- Each utility uses the DBD name, DBRC, and IMSID values coded on the PARM parameter in the EXEC statement to add to or replace the values in the parameter table.
- Each utility uses any values coded in the PLUSIN control statement data set to add to or replace the keywords built in the previous steps.
The result of these steps is the options table that the utility uses during database processing. The global options are not modified.
With the Online Reorg function and the Reorg function, you can combine the global options module and commands for specifying keywords for maximum efficiency.
With the Unload function and the Reload function, you can combine the global options module, the PDX options member, and command methods for specifying options for maximum efficiency. You can use the xxxPARMS options module to specify the values you want to use for most of the databases at your site. For particular keywords you want to use only on a single IMS system (for example, a test system), you can use the xxx@imsi options module. For databases that need different values from those you specified in the xxxPARMS or xxx@imsi modules, you can create a PDX options member for those DBDs. For jobs that require different values from those you usually use for the database, you can specify the values in the PLUSIN data set.
With the Index Build function, you can combine the global options module and command methods for specifying options for maximum efficiency. You can use the SIUPARMS options module to specify the values you want to use for most of the databases at your site. For particular keywords you want to use only on a single IMS system (for example, a test system), you can use the SIU@imsi options module. For jobs that require different values from those you usually use for the database, you can specify the values in the PLUSIN data set.
The Options in Effect report lists the user-controlled options in effect for the current run.
The following figure shows how the options are built.
Related topic