Skip to Content
Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see DASD MANAGER PLUS for DB2 13.1.

SLIB changes

To change an SLIB, code the changes to your SLIB source.

Before you compile the SLIB, you should use JCL Generation to test the changes by using ISPF standard file tailoring. Testing the changes ensures that the SLIB is coded correctly and that no ISPF-related errors exist.

You must recompile an SLIB each time that you change its source. Sample JCL for the SLIB compiler is in member AJXCOMPS in the HLQ.BMCCNTL data set that BMC provides at installation. To customize the JCL to your shop’s standards, follow the directions provided in this member.

Error
Warning

BMC uses SMP/E to package and deliver the SLIB members. If you must make a change to an SLIB, consider copying the SLIB member or members to be changed into a separate library. You can then make your changes to the SLIB members in that library without the risk of applying SMP/E maintenance that overlays your changes. Note that PTFs or GA releases that BMC distributes might change the SLIB source. You will need to determine whether the SLIB source was changed. If the SLIB source was changed, you will need to copy the new version of the SLIB source to your separate library, and reapply any changes that you made.

SLIB verification using ISPF file tailoring

The runtime unit first attempts to process compiled SLIBs. If the runtime unit cannot process a compiled SLIB, the unit reverts to standard ISPF file tailoring.

Warning

Important

If standard file tailoring is required, the SLIB that is being processed must exist in the ISPSLIB data set.

Any of the following criteria force the runtime unit to use standard ISPF file tailoring for an SLIB:

  • A compiled SLIB cannot be loaded from either STEPLIB or ISPLLIB.

    Remove or rename the compiled version of the SLIB in the STEPLIB or ISPLLIB.

    Removing the compiled version forces the runtime unit to process the uncompiled SLIB, using standard ISPF file tailoring.

  • The first four bytes of the compiled SLIB contain binary zeros.

    Insert a new line 1 in the SLIB. Beginning in column 1, enter:

    )CM NO-COMPILE.

    Then compile the SLIB.

    The compiler recognizes this SLIB as non-compilable and builds a load module with binary zeros in the first four bytes. The binary zeros force the runtime unit to process this SLIB by using standard ISPF file tailoring.

  • The ddname, $USESTFT, is allocated as DUMMY to either the TSO session or the batch job that is being executed.

    Add the ddname $USESTFT to the JCL stream for batch jobs, or allocate it to your TSO session with the TSO ALLOC command.

    This option forces all SLIBs to be processed by standard ISPF file tailoring.

    For example, in Batch Execution JCL Generation, add the following JCL:

    //$USESTFT DD DUMMY

    The option remains in effect for the duration of the batch job. In foreground processing, issue the following command before entering the product:

    TSO ALLOC FI($USESTFT) DA(’NULLFILE’) SHR

    The option remains in effect until you log off or you issue the following command:

    TSO FREE FI($USESTFT)

Compilation of changed SLIBs

BMC strongly recommends that you process all SLIBs as compiled SLIBs, because the runtime performance can be adversely affected by processing non-compiled SLIBs.

Warning

Important

Before you test the compiled SLIB, turn off or remove any options that you used, such as $USESTFT and )CM NO-COMPILE.

You can use the report that the runtime unit generates to verify that you are running with compiled SLIBs and that the compile date on the SLIB is what you expect. For more information about the runtime report, see Generating-the-SLIB-report.

After you successfully test the SLIB using standard file tailoring, compile the SLIB into your production HLQ.UBMCLINK library.

Related topic

Using-the-Skeleton-Library-compiler

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

DASD MANAGER PLUS for DB2 12.1