ACTIVATE | ACT

indicates that you want to include the specified libraries ahead of the standard search order.

DEACTIVATE | DEACT | DEA

indicates that you want to exclude the previously activated libraries from the top of the search order.

If previous activation requests have been done unconditionally, DEACTIVATE causes the last stacked request to become active again. See Stacking load module and program object library requests for more information about stacking library activation requests.

DATASET(dsname[,dsname, … ]) | DSNAME(dsname[,dsname, … ])

specifies the data set name of a load module library, or a list of data set names of load module libraries, to be activated. Up to 15 data set names can be specified.

The data sets must be cataloged partitioned data sets, and they must be of the same record format (RECFM = U).

For the load module or program object libraries to be activated, the system automatically creates a ddname of SYSnnnnn. The ddname remains allocated until you issue TSOLIB DEACTIVATE or TSOLIB RESET.

If you want to activate more than 15 data set names, use the FILE operand of TSOLIB.

For authorized commands and programs to be invoked from a library read Further considerations.

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

specifies a ddname that represents a load module library or a list of load module libraries. The ddname must be allocated before you issue the TSOLIB command. The ddname remains allocated even after a TSOLIB DEACTIVATE or RESET command is issued. Use the FREE command to deallocate the ddname when required.

For authorized commands and programs to be invoked from a library read Further considerations.

Using a ddname, compared to a dsname or a list of dsnames, allows for a greater number of libraries to be activated. Use the ALLOCATE command to associate up to 255 data sets with a ddname; then issue TSOLIB ACTIVATE FILE(ddname).

UNCOND | COND

controls the way TSOLIB is to treat an ACTIVATE request if previous requests have been performed.

UNCOND

(the default) indicates that the activation request is to be done unconditionally. Any active request is temporarily deactivated and stacked for later re-activation. See Stacking load module and program object library requests for more information about stacking library activation requests, and TSOLIB command examples.

Note that stacked ddnames remain allocated. See also the description about the DATASET and FILE operands.

COND

indicates that the activate request is to be successful if no other request is active. Otherwise, the activate request is unsuccessful, a message is displayed, and a non-zero return code is set.

RESET | RES

excludes all specified libraries, set with the ACTIVATE operand, back to the standard search order. The search order for library load modules is now the same as it was before any TSOLIB command was given.

DISPLAY | DISP | DIS

issues information about the currently active ddname that is in front of the standard search order and those still on the stack, which will become the active ones, one after the other, with each following TSOLIB DEACTIVATE command.

If other task libraries became active after TSOLIB activated a library, for example, ISPF was started with ISPLLIB, the DISPLAY operand issues information about the situation.

QUIET

indicates that you do not want messages from this invocation of the TSOLIB command displayed.

The QUIET operand is primarily intended for programs under ISPF that invoke the TSOLIB command. The programs need access to the messages that TSOLIB issues, but will not want to display them. Trapping of messages is not available, and &SYSOUTTRAP cannot be used in a program.

If ISPF is active, the messages are saved in ISPF shared pool variables:

• Variable IKJTSM contains the number of non-blank messages being returned from this invocation of the TSOLIB command with the QUIET operand.
• Variable IKJTSM1 contains the first message, IKJTSM2 the second message, and so on. Up to 99 messages are saved in variables IKJTSM1 through IKJTSM99.

  The variables contain the actual messages that TSOLIB would have displayed if invoked without the QUIET operand. The lengths of the messages are not restricted to 80 characters.

The ISPF shared pool variables are only set when needed. They are not blanked out when not needed.

QUIET does not take effect until after the content of the command buffer, holding this invocation of the TSOLIB command, is known to be syntactically correct. If the command parser finds an error, or needs to prompt for input, it will issue messages and obtain input from the terminal as necessary.

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

If you invoke the TSOLIB command without specifying an operand, TSOLIB will assume the ACTIVATE and DATASET operands and prompt you for the missing information. Note that prompting restricts you to a single data set name. You cannot enter a list of dsnames.

Entering only the significant characters can abbreviate operands. However, you might need to clarify reasons for the abbreviations shown.