Anticipated Modifications

When an installation needs to change its LU configuration regularly, parmlib members can be pre-coded with the changes. For example, if an installation needs two system-level production LUs during third shift, LU Z096AP02 can be changed every evening from a user-level LU to a system-level production LU. The installation can code two parmlib members— one to change the LU to system level and one to change it back to user level.

Parmlib member APPCPM3S changes LU Z096AP02 to a system-level LU and member APPCPM1S changes it back to a user-level LU. When the installation wants LU Z096AP02 to be system level for third shift, the operator issues SET APPC=3S. When the installation wants LU Z096AP02 to be user level again, the operator issues SET APPC=1S.

Figure 1. APPCPM3S

  LUADD
    ACBNAME(Z096AP02)
    SCHED(XYZ)
    BASE
    NQN
    TPDATA(SYS1.XYZTP)
    TPLEVEL(SYSTEM)
    PSTIMER(3600)
    USERVAR(scheduler-supplied value)
    ALTLU(scheduler-supplied value)

Figure 2. APPCPM1S

  LUADD
    ACBNAME(Z096AP02)
    SCHED(XYZ)
    BASE
    NQN
    TPDATA(SYS1.XYZTP)
    TPLEVEL(USER)
    PSTIMER(3600)
    USERVAR(scheduler-supplied value)
    ALTLU(scheduler-supplied value)

Note that during third shift, there is no one parmlib member that reflects the configuration. Rather, the configuration is a combination of two parmlib members, APPCPM1A and APPCPM3S.