SLIB verification using ISPF file tailoring

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)