Where you receive output from a command issued by OPSCMD depends on how you issued OPSCMD:
|
If OPSCMD is issued from… |
The command output… |
|---|---|
|
A TSO terminal |
Is displayed on the terminal |
|
A CLIST |
Goes into CLIST variables if SYSOUTTRAP is active |
|
An OPS/REXX program (through an ADDRESS TSO instruction) |
Goes to the OPS/REXX external data queue |
OPSCMD internally determines when it has received the last line of command output. If you do not receive all of the output you expect, specify the WAIT keyword with OPSCMD or increase the specified wait time.
OPSCMD receives z/OS or JES2 command output only if the CA OPS/MVS address space is active. If CA OPS/MVS is not running, the system command you specified executes, but OPSCMD generates a non-zero return code and issues the following message:
COMMAND OUTPUT RETRIEVAL NOT OPERATIONAL
You can always receive VM command output if z/OS runs under VM, even if the CA OPS/MVS address space is not running. The CA OPS/MVS product can retrieve up to 4 KB of output from VM, the maximum amount of contiguous real storage that VM can obtain from z/OS. If a VM command produces more than 4 KB of output, OPSCMD returns the first 4 KB of output and this message:
VM COMMAND OUTPUT BUFFER OVERFLOW
z/OS and JES2 commands can return up to 2000 lines of output. You can increase this value either by using the OPSPRM REXX function to alter the OCMAXMSG parameter value, or by using the MAXCMDOUT keyword.
You receive the following error message if the CA OPS/MVS address space is active but a command issued through OPSCMD produces no output:
{MVS | VM | IMS} COMMAND GENERATED NO OUTPUT
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |