Skip to Content
Information
Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

General coding conventions for IMFEXEC commands

IMFEXEC statements provide automation services not available in a REXX EXEC or with a TSO command procedure.

The command syntax is the keyword IMFEXEC, followed by the command and any necessary parameters; for example:

'IMFEXEC command [parameters]'

CLIST example:

IMFEXEC command [parameters]

Valid delimiters for the command are blank characters. IMFEXEC keywords must be coded in uppercase.

Each IMFEXEC command statement description includes a table describing the parameters for the command. The table uses the format:

Parameter

Function

Notes

1

2

3

 The numbers in this table correspond to the following descriptions:

  • A short parameter identifier
  • If the parameter has uppercase letters, this identifier must be coded exactly as shown.
  • If parts of the identifier are shown in bold, this parameter can be abbreviated, using the bold letters.
  • Positional parameters are not associated with a specific identifier. In these cases, this column contains an alias that describes the parameter.
  • The function of the parameter
  • Notes about the parameter

Typically, these notes describe any length, value, range, or string limitations.

This section contains the following topics: 

Related topic

Using-the-IMFEXEC-statements

 

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

BMC AMI Ops Automation 8.3