TSO commands

This appendix describes the TSO commands and how you can use them in batch mode, using the event-generating batch program, EQQEVPGM. See EQQEVPGM - Issue commands in batch for an example of the JCL that you need for EQQEVPGM. Examples of these commands are provided for both online and batch invocation.

To invoke these as TSO commands from a system where a controller is not running, they must first be defined as authorized TSO commands on that system. Your system programmer can do this by adding the commands to the list defined by the NAMES keyword of the AUTHCMD statement in member IKJTSOxx of SYS1.PARMLIB. For more information about updating SYS1.PARMLIB, see HCL Workload Scheduler for Z: Planning and Installation.

Note: When EQQEVPGM is used to issue TSO commands, statement data must be in columns 1 through 72. Information in columns 73 through 80 is ignored. You can abbreviate keywords to their shortest unambiguous form. For example, you can shorten the AVAIL keyword to an ‘Aʼ.
If you plan to issue the TSO commands many times per day from a long-running non-TSO address space (for example, NetView®) it is recommended that you use an HCL Workload Automation for Z subroutine instead. If you plan to run PIF applications many times per day from a long-running non-TSO address space (for example, NetView®), it is recommended that you do not specify the EQQYPARM ddname. When you either do one of the following:
  • Issue the commands from TSO or as input to the EQQEVPGM program
  • Run a PIF application by specifying the EQQYPARM ddname
a TSO environment must be established each time and some of the resources remain allocated until the task ends, which might lead to a storage shortage if the commands are issued many times.

For detailed information about the subroutines, see Customization and Tuning.