In addition to the similarities listed above, there are several important differences between OPS/REXX and standard REXX. These include:
if OPSINFO("SMFID") == "SYSA" then call EXTSUB1 else call EXTSUB2
Clearly, the EXTSUB1 subroutine is called only when the code executes on SYSA. Nevertheless, OPS/REXX requires the EXTSUB1 subroutine (or load module) to be available on every system. In TSO/E REXX, external subroutines are resolved only when they are called during execution.
In CA OPS/MVS, you can use the OPSWXTRN keyword of the OPTIONS instruction to indicate to OPS/REXX which external subroutines, built-in functions, and load modules are not absolutely required to be present prior to execution. The presence of the OPSWXTRN keyword in an OPTIONS instruction allows programs containing this OPTIONS instruction to be used by both OPS/REXX and TSO/E REXX, so the portability of REXX code that uses this instruction is unaffected. For more information, see OPTIONS Instruction in this chapter.
Note: For more information see the OPS/REXX DATE function in the Command and Function Reference.
Copyright © 2014 CA.
All rights reserved.
|
|