Skip to Content

REXX EXEC considerations

If you have the IBM REXX Compiler installed at your site, BMC AMI Ops Automation supports tokenized REXX EXECs with the following considerations:

  • The EXEC Management application does not display documentation ( DOC ) fields for tokenized REXX EXECs in its display fields.
    All comments are removed from the REXX EXEC by the compiler.
  • The tokenized REXX EXECs must be stored in a SYSPROC library concatenation.

Related topic

Using-advanced-techniques-with-BMC-AMI-Ops-Automation-EXECs

The IBM REXX Compiler can generate either a tokenized REXX executable or a load module REXX executable. BMC AMI OpsA does not support the load module REXX executable.

You can expect significant performance gains when you use tokenized REXX EXECs over interpreted EXECs. These gains, however, depend on the number of external calls (such as IMFEXEC commands) or subroutines that are used.

Wherever possible, REXX functions and subroutines should be built into the parent REXX EXEC. This configuration is much more efficient because it eliminates the function or subroutine load time.

After a REXX EXEC has been analyzed for performance and optimized, subroutines that are called many times by using IMFEXEC SELECT EXEC can be copied internally to the parent and called by using REXX CALL.

BBSAMP member AOXCPUST contains the tokenized version of AOXCPUSI.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.3.01