TSO subcommand — run a TSO/E command

Use the TSO subcommand to:

Invoke a TSO/E command whose name is identical to an IPCS subcommand. See the description of the tsocmd parameter for information concerning authorized TSO/E commands.
Invoke a CLIST or REXX exec containing TSO/E commands whose names are identical to IPCS subcommands.
Enter TSO/E mode.

Invoke a TSO/E Command
Use the TSO subcommand to enter TSO/E commands whose names are identical to IPCS subcommands except when invoking ISPF.
For example, to request the display of status for all batch jobs whose job name begins with your TSO/E userid, enter:
```
tso status
```
If you do not precede the STATUS command with TSO, the system does not interpret the command as a TSO/E command. Note, however, that the system does not allow TSO/E commands, when invoked by IPCS, to request ISPF services. For example, using the TSO/E ALTLIB command with the QUIET option causes ALTLIB to use ISPF services, which the system does not permit.

ISPF under IPCS

Do not invoke the ISPF command with the TSO prefix. Instead, invoke ISPF by entering ISPF on the command line. If you enter TSO ISPF, you may obtain unpredictable results.

If TSO/E Release 2 or later is installed, you can enter installation-defined authorized commands and authorized TSO/E commands, such as TRANSMIT and RECEIVE (as determined by your installation). Otherwise, such commands end abnormally.
Invoke a CLIST or REXX Exec Containing TSO/E Commands
You can use the TSO subcommand to invoke a CLIST or REXX exec containing TSO/E commands. You can do this in any of the three IPCS processing modes. A CLIST or REXX exec invoked with the TSO subcommand can contain any or all of the following:
- TSO/E commands whose names are identical to IPCS subcommands. Using the TSO subcommand ensures that the TSO/E command is invoked instead of an IPCS subcommand of the same name.
- Any TSO/E command. Any TSO/E command can be included in a CLIST invoked using the TSO subcommand.
- TSO/E authorized commands in conjunction with a TSO/E function such as SYSOUTTRAP. While in the IPCS dialog, the SYSOUTTRAP will not trap the output from the authorized command correctly unless you use the TSO subcommand to invoke the CLIST. However, such a CLIST can be invoked successfully in batch or line mode without using the TSO subcommand.
- IPCS subcommands. To run IPCS subcommands from within a CLIST invoked using the TSO subcommand, use the BLSGSCMD dialog program to invoke the IPCS subcommands.
- ISPF commands. Invoke a CLIST containing ISPF commands from within IPCS dialog or in IPCS batch mode if ISPF is active in batch.
Restriction: You can define and use up to 10 global variables in CLISTs invoked through the IPCS dialog, if CLIST BLSCLIBD started the IPCS dialog. IPCS does not restrict the number of global variables you can define when the IPCS dialog is started using other approved methods. If CLIST BLSCLIBD started the IPCS dialog, and if you require more than 10 global variables, create your own copy of CLIST BLSCALTL and add more global variables. Modify CLIST BLSCLIBD to point to your copy of BLSCALTL rather than to SYS1.SBLSCLI0(BLSCALTL). For information about defining and using global variables, see z/OS TSO/E CLISTs.
Enter TSO/E Mode
In line mode or batch mode IPCS, you can enter the TSO subcommand without a command or CLIST or REXX exec invocation to suspend IPCS subcommand processing and enter TSO/E mode. Then, commands entered in TSO/E mode are processed as TSO/E commands until END is entered to resume IPCS processing. When the END subcommand is entered, the highest return code from the TSO/E command processing is returned.

Syntax

   TSO   [ [ [%]clistnm | [%]rexxnm | tsocmd ] [operands] ]

Parameters
clistnm

Specifies the name of the CLIST to be run. If the CLIST name is the same as the name of a TSO/E or IPCS command, a % must precede the name.

rexxnm

Specifies the name of the REXX exec to be run. If the REXX exec name is the same as the name of a TSO/E or IPCS command, a % must precede the name.

tsocmd

Specifies the name of a TSO/E command to be run. If TSO/E Release 2 is installed, tsocmd may specify the name of an installation-defined authorized command or an authorized TSO/E command, such as TRANSMIT or RECEIVE (as determined by your installation). See z/OS TSO/E Customization for more information.

operands

Specifies the operands of the TSO/E command or CLIST to be run.

Return Codes

Code	Explanation
12	Severe, an error condition or user request forced early ending of subcommand processing.
16	Ending error, an error condition from a called service routine forced an early end to the processing.
any	The return code is generated by the TSO/E command.

Example 1: Display the status of all batch jobs.
- Action
```
COMMAND ===> tso status
```
- Result
  This example requests the display of status for all batch jobs whose job name begins with your TSO/E user ID. If you do not preceded the command name, STATUS, with TSO, the IPCS STATUS subcommand are processed.
Example 2: Send a data set to a node and user ID.
- Action
```
COMMAND ===> tso transmit nodeb.user2 da('sys1.parmlib')
or
COMMAND ===> transmit nodeb.user2 da('sys1.parmlib')
```
- Result
  These commands request that a copy of a data set (SYS1.PARMLIB) be sent to a specified node and user (nodeb.user2). It is not necessary to precede the command name (TRANSMIT) with TSO because there is no IPCS subcommand with the name TRANSMIT. IPCS processes both of the commands in this example as TSO/E commands.