ALTLIB command operands

ACTIVATE | ACT

indicates that you want to include the specified library level when searching for a REXX exec or CLIST.

DEACTIVATE | DEACT | DEA

indicates that you want to exclude the specified library level when searching for a REXX exec or CLIST.

DISPLAY | DISP | DIS

requests information about the search order the EXEC command processor currently uses to find a REXX exec or CLIST.

RESET | RES

resets the libraries searched to system-level REXX execs and CLISTs only.

USER

indicates that the user-level REXX execs and CLISTs are to be activated or deactivated. User-level REXX execs and CLISTs are those data sets concatenated to the ddname SYSUPROC for both CLISTs and REXX execs and the data sets concatenated to ddname SYSUEXEC for REXX execs only.

APPLICATION

indicates that the application-level REXX execs and CLISTs are to be activated or deactivated. Application-level execs and CLISTs are those data sets defined with the DATASET or FILE operands.

SYSTEM

indicates that the system-level REXX execs and CLISTs are to be activated or deactivated. System-level execs and CLISTs are the data sets that are concatenated to the ddname SYSPROC for both REXX execs and CLISTs or those data sets that are concatenated to the ddname SYSEXEC for REXX execs only.

ALL

indicates that you want to deactivate all library levels, user, application, and system, of REXX execs and CLISTs.

(EXEC)

indicates that you want to activate or deactivate REXX execs at the level you specify (user, application, or system).

(CLIST)

indicates that you want to activate or deactivate CLISTs at the level that you specify (user, application, or system).

(*)

indicates that you want to activate or deactivate REXX execs and CLISTs at the level you specify (user, application, or system).

DATASET(dsname) | DSNAME(dsname)

specifies a data set list to define an application-level library of REXX execs or CLISTs. When specifying DATASET or DSNAME:

The data sets must be cataloged partitioned data sets when you issue the ALTLIB command.
The maximum number of data sets you can list is fifteen. Use the FILE operand if you want to specify more than fifteen.
The data sets must all have the same record format (RECFM).
If the data sets have different block sizes, you can specify them in any order of block sizes.
Member names cannot be specified in the list of data sets.

FILE(ddname) | DDNAME(ddname) | LIBRARY(ddname)

specifies a ddname that defines an application-level library.

The ddname must be allocated before issuing the ALTLIB command.
The ddname must be allocated with the permanently allocated attribute to ensure that the system does not automatically deallocate the ddname when the allocation control limit is exceeded. Note that the data sets allocated in a LOGON procedure or by the ALLOCATE command are automatically allocated with this attribute, however, if you access dynamic allocation directly, using SVC 99, you need to specify this attribute. For more information about the permanently allocated attribute, seez/OS MVS Programming: Authorized Assembler Services Guide.
To avoid errors when the EXEC command runs, specify only cataloged partitioned data sets.

UNCOND | COND

UNCOND: activates the specified application-level library even if another application-level library of the same type, CLIST or REXX exec, is active within the current application. Up to eight application-level CLIST and REXX exec requests can be stacked. (See Stacking Application-Level library requests for an explanation of stacking.)
COND: activates the specified application-level library only if another application-level library of the same type, CLIST or REXX exec, is not active within the current application. If you issue the ALTLIB command with the COND keyword and there is already an application-level library in effect, a message is displayed and a non-zero return code is set.

QUIET

indicates that you want messages saved and not displayed at the terminal. Messages can be saved in the ISPF shared pool when QUIET is used and ISPF is active. Variable IKJADM1 contains the first message, variable IKJADM2 contains the second message, and so on. Variable IKJADM contains the number of messages returned for the invocation of ALTLIB according to these rules:

If you specify ALTLIB with QUIET, IKJADM is reset to the number of messages returned for that invocation of ALTLIB.
If you do not specify the QUIET operand, IKJADM is not reset. It equals the number of messages returned for the last invocation of ALTLIB with QUIET.
QUIET takes effect after TSO/E determines that the ALTLIB command is syntactically correct. If the command is not syntactically correct, then IKJADM equals 0 and a return code of 20 is returned indicating a syntax error.

QUIET saves up to 99 messages.

IKJADM1 echoes the command entered in IKJADM1. For example,

IKJADM = 4
IKJADM1= ALTLIB DISPLAY QUIET
IKJADM2= IKJ79322I Current search order (by DDNAME) is:
IKJADM3= IKJ79327I System-level EXEC       DDNAME=SYSEXEC
IKJADM4= IKJ79328I System-level CLIST      DDNAME=SYSPROC

REXX execs and CLISTs may use the variables IKJADM and IKJADM1 - IKJADM99 as in this example:

/* REXX */
ADDRESS TSO "ALTLIB DISPLAY QUIET"
ADDRESS ISPEXEC "VGET (IKJADM IKJADM1 IKJADM2 IKJADM3 IKJADM4) SHARED"
SAY 'IKJADM = 'IKJADM
SAY 'IKJADM1='IKJADM1
SAY 'IKJADM2='IKJADM2
SAY 'IKJADM3='IKJADM3
SAY 'IKJADM4='IKJADM4

If you use a program that invokes ALTLIB with the QUIET operand, you must take the following into consideration: ALTLIB declares IKJADM as a fixed binary integer, four bytes long. IKJADM1 - 99 are character format, 251 bytes long. If QUIET is in effect and you invoke ALTLIB from a program, messages are not displayed, but they are available to the program.

Note: Do not use the QUIET option of ALTLIB in the IPCS dialog. IPCS does not make ISPF services available to TSO/E commands that IPCS invokes.