POI Command Processors › OPSREPLY Command Processor—Compare WTOR Messages › Considerations for Issuing OPSREPLY

Considerations for Issuing OPSREPLY

Keep this information in mind when issuing the OPSREPLY command processor:

• The OPSREPLY command processor internally calls the OPSCMD command processor to issue the z/OS reply command when:
  • You specify one or more OPSCMD command processor keywords in the text of the OPSREPLY command processor.
  • You specify a cross-system keyword (for example, SYSNAME or SYSPLEX) in the text of the OPSREPLY command processor.
  • OPSREPLY works across systems that are part of the same sysplex.

  The internal call to OPSCMD provides these benefits:

  • It enables OPSREPLY to take advantage of the cross-system capabilities of OPSCMD
  • It permits users to specify the CMDRESP(destination,REPLY) keyword of OPSCMD to obtain the response to the reply command that will be issued. Variable output is also available; for example, you can specify CMDRESP(REXX,REPLY) to specify the generation of a series of REXX stem variables to hold the output.
• CA OPS/MVS converts the values of all keywords, including reply text, to uppercase characters.
• In a JES3 environment, local WTOR messages appear on the global ORE chain as foreign OREs. Specifying the SYSPLEX or SYSNAME keyword can cause these OREs to be selected. When the reply must be routed to the local processor, the REPLY command is prefixed with the following:

  *T sysname
  

• Whenever you specify an OPSCMD command processor keyword in the text of the OPSREPLY command processor, OPSREPLY links to OPSOSCMD. For a description of the OPSCMD command processor, see OPSCMD Command Processor in this chapter.
• In coded automation procedures, such as CLISTs or OPS/REXX programs, always specify the complete text of the OPSREPLY command processor and its keywords and operands. Doing so avoids syntax ambiguity in the future as we add new command processors to the CA OPS/MVS product.

  If you are invoking the OPSREPLY command processor online, as you would during an interactive TSO session, you can use the shortest unique abbreviations. Be aware that the shortest unique abbreviation of a command processor, keyword, or operand can change from release to release.