Overriding POF values in SLIBs

One of the primary advantages of using POFs is that you can customize your JCL without having to modify your SLIBs. Nonetheless, you might need to modify your SLIBs from time to time.

SLIB variables (or ISPF variables) are used in the SLIBs. Some of these SLIB variables correspond to the parameters in the POF. Note, however, that the names of the SLIB variables differ from the names of the POF keywords.

For example, if you specify the data set prefix for local primary copies (see Specifying the prefix for a copy data set), the name of the primary copy data set resolves to the following name without modifications to the SLIB:

Related topics

Setting-options-and-authorizations

Specifying the prefix for a copy data set

Using-the-Skeleton-Library-compiler

For data sets that are not dynamically allocated, JCL Generation appends the ddname to the prefix to create the name of the data set.

Specifying the prefix for a copy data set

------------ JCL GENERATION DATA SET OPTIONS FOR LOCAL PRIMARY COPY UPDATE ----
COMMAND ===>

Type data and press Enter. Press PF3 or END to return to the main panel.

  Enter Data Set Prefix below:
   . . &SSID..IC.T.ICPY.&DB..&TS
  Unit Name . . . . . . . . . . . SYSDA    (SYSDA, TAPE, etc)
  Primary Space . . . . . . . . . 10       (Cylinders)
  Secondary Space . . . . . . . . 2        (Cylinders)
  Tape EXPDT. . . . . . . . . . .          (Blank or YYDDD or YYYY/DDD)
  Tape RETPD. . . . . . . . . . .          (Blank or 0 - 9999 days)
  SMS Data Class. . . . . . . . .          (Blank or Data Class)
  SMS Storage Class . . . . . . .          (Blank or Storage Class)
  SMS Management Class . . . . .          (Blank or Management Class)

  Threshold Value . . . . . . . . 0        (Cylinders, 0 means no Threshold)
  Alternate Unit Name . . . . . .          (SYSDA, TAPE, etc)
  Alternate SMS Data Class. . . .          (Blank or Data Class Name)
  Alternate SMS Storage Class . .          (Blank or Storage Class Name)
  Alternate SMS Management Class           (Blank or Management Class Name)

Now, assume that your site’s DBA decides that users should not have the ability to change the data set prefix from the options panels. The DBA can override the value in the SLIB. By specifying the value for the copy data set in the AJX#DSNS SLIB (see below), the DBA can uphold your site’s naming standards.

Changing the SLIB variable for the copy data set in AJX#DSNS

)CM-------------------------------------------------------------------
)CM-------------------------------------------------------------------
)SEL &AJXC1PRF ^= &Z

)SET SYSC1PR = &AJXC1PRF <- Resolved values from ISPF profile
)ENDSEL
)SEL &AJXC1PRF = &Z
)SEL &AJXSYCOP ^= &Z
)SET SYSC1PR = &AJXSYCOP
)ENDSEL
)SEL &AJXSYCOP = &Z
)SET SYSC1PR = &AJXHLQ..&AJXDB..&AJXTS
)ENDSEL
)ENDSEL
)SEL &AJXC2PRF ^= &Z
)SET SYSC2PR = &AJXC2PRF
)ENDSEL
)SEL &AJXC2PRF = &Z
)SEL &AJXSYCOP ^= &Z
)SET SYSC2PR = &AJXSYCOP
)ENDSEL
)SEL &AJXSYCOP = &Z
)SET SYSC2PR = &AJXHLQ..&AJXDB..&AJXTS
)ENDSEL
)ENDSEL
)SET SYSC1PR = user.shop.standards.&AJXDB..&AJXTS <- Override with SLIB variables
and fixed values

After changing an SLIB variable, the DBA should use JCL Generation to test the changes. If the SLIB is coded correctly, the DBA must then recompile the SLIB. The DBA can use the SLIB compiler tool that is supplied with the Administrative products to compile the SLIB.

For more information about testing the changes or using the SLIB compiler, see Using-the-Skeleton-Library-compiler.

Overriding POF values in SLIBs

On this page