POI Command Processors › OPSCMD Command Processor—Issue z/OS, JES, VM, and IMS Commands › Issue the OPSCMD from CLISTs

Issue the OPSCMD from CLISTs

In most cases, you issue OPSCMD from a CLIST to capture the output of system commands in variables so the CLIST can then act on that output. However, you can also direct the command output to a TSO terminal.

Note: If you are using OPSCMD from a CLIST and you turn on CLIST debugging options, you will probably receive a bogus first line of output (reflecting the command you entered), with all the correct output lines starting with the second line returned through the SYSOUTTRAP feature. If your CLIST uses debugging options, your code must allow for this extra output line. OPS/REXX TRACE options do not introduce extra lines into the external data queue.

Examples: Issue the OPSCMD from CLISTSs

The following OPSCMD examples show how to issue the same command with different abbreviations for OPSCMD:

• To execute a z/OS display command, issue one of the following commands:

  OPSCMD d a,l
  

  OC d a,l
  

• To execute a JES3 display command, issue the following command:

  OPSCMD *i a
  

• To execute a VM query command, issue the following command:

  OPSCMD #cp q n
  

• To execute a z/OS command, issue one of the following commands:

  OPSCMD COMMAND(d r,l)
  

  OPSCMD command(D r,l)