BMC Software, Inc., Confidential and Proprietary Information
4-14 Administrative Products for DB2 Installation Guide
Compiling SLIBs
Compiling SLIBs
Summary: The Administrative Products share a common component called JCL
Generation. This component generates the JCL that is needed to execute all
the batch functions that use ISPF file tailoring. You may need to change
members of the BMC Software product skeleton library (SLIB) to generate
environment-specific JCL. This section describes the steps you must perform
to edit, test, and compile the SLIB.
Step 1 Edit the appropriate SLIB members in HLQ.SLIB to change the way the JCL
is generated.
Note: Any customizations that you have made to the SLIB members for a
previous release will not be included in your current installation.
Step 2 Use JCLGEN to test the changes to the SLIB. For more information, refer to
the ALTER and CHANGE MANAGER for DB2 User Guide, the CATALOG
MANAGER for DB2 User Guide, and the DASD MANAGER PLUS for DB2
User Guide.
Step 3 Compile the SLIB members that you edited. For more information, refer to
the ALTER and CHANGE MANAGER for DB2 User Guide, the CATALOG
MANAGER for DB2 User Guide, and the DASD MANAGER PLUS for DB2
User Guide. For a sample compile JCL, refer to the HLQ.CNTL member
AJXCOMPS.
Generating JCL Region Statements
The EXEC REGION parameter is set by default to REGION=0M in the
AJX#USRV member that resides in the SLIB. If you do not change the
IBM-supplied default limits in the IEALIMIT or IEFUSI exit routine
modules, this parameter requests that the job step get all of the available
storage above and below the 16 MB line.
If the IBM defaults have been changed, you should also change the
REGION=0M parameter in the AJX#USRV member by finding the variable
REGION and changing 0M. After you edit the member, compile it.
