CMD Type(MVS) — Issue MVS command with response

Default is 1. You may specify from 0 through 9999. A Multi Line WTO (MLWTO) is counted as one line (even though it may be composed of many lines, as in some VTAM command responses).

When you specify COUNT(0) with the IMFEXEC CMD ‘MVS_command’ in an EXEC, it means that this EXEC is not expecting a response from the MVS command that is issued. BMC recommends using this specification instead of using the IMFEXEC CMD (without response) command.

Valid values are 0 to 99999 seconds.

The default value is 0 seconds, which means the command is executed with no delay. In addition, the DELAY|DLY parameter includes the following conditions:

• You can use either DELAY and DLY.
• You cannot specify response WTOs for delayed commands.  COUNT(0) is enforced for all delayed requests.
• A non-zero delay request will fail when you specify any parameters that request command response.
• You cannot specify a delay with the RESPONSE, WAIT, ALL, STEM and ENDMSG parameters.
• The delay request is no longer valid after an IPL or bouncing the PAS.

Specify an interval to wait from 1 to 9999 seconds.

ALLWAIT allows CMD processing to continue waiting in intervals (specified in seconds) until no responses are received within an interval of that length. If at least one response is received in that interval, processing continues for an additional interval.

This processing is repeated until no responses are received within an interval, which may result in added wait time. Therefore small intervals of 1-5 are recommended:

ALLWAIT is only valid when ALL is specified.

Use this parameter if the command must be issued from a specific MVS console name.

When the COUNT(parameter ) has a setting greater than zero (0) such as when the default of 1 is used, the NAME parameter must specify a currently inactive or undefined MVS console name; this console name must not be in use by any other jobs. BMC AMI OpsA requires exclusive control of the MVS console to read the command responses.

If the COUNT(0) (which means that responses are not required), the NAME( ) parameter can specify any MVS console name, active or inactive or undefined, and even specify consoles that are currently owned by BMC AMI OpsA or another program.

When you specify COUNT(0), the NAME keyword can specify a BMC AMI OpsA response console name such as ssid0001, ssid0002, and so on.

To use the same console name as an earlier IMFEXEC CMD command that was issued in the same EXEC, specify the variable name IMFCNAME. Refer to Example 4.

When command responses are expected, one of the following things can happen (depending on the state of the console of the console name you specified):

• An active console identified to BMC AMI OpsA will be used.
• When the command ends, the console is deactivated.

The NAME and CONSOLE parameters cannot be used together.

Specify a stem root name for the REXX stem variable. In addition:

• The maximum length of the value that you can specify is 8 characters.
• The value must conform to standard REXX variable naming rules.
• Compound REXX stem variables are not supported.

Note: This parameter is valid only for REXX EXECs. It does not work in CLISTs.

If the stem name provided ends in a period (.), BMC AMI OpsA processing ignores the period. For example, specifying STEM(MYVAR.) produces the same result as specifying STEM(MYVAR).

Using this parameter overrides the creation of LINEn variables in the LOCAL variable pool. The REXX stem variable is only defined as a TSO variable.

If you want to use the variables as LOCAL variables, you must first use IMFEXEC VPUT to move these variables to the LOCAL pool.

These REXX stem variables conform to all TSO/E REXX coding standards for stem variables.

Use the ENDMSG parameter when you know a specific message ID is available and indicates the end of the WTO

Only single line WTOs and the major line of multi-line WTOs are inspected for the ENDMSG() parameter. The minor lines of MLWTOs are not inspected.

If none of the WTOs have a message ID that match the ENDMSG parameter, the IMFEXEC CMD ends based on other parameters such as LINES() or WAIT(). The command performs as if the ENDMSG parameter had not been specified.

If the RESPONSE() parameter is specified, you can specify ENDMSG() and specify words that are not in specified with the RESPONSE parameter. This means the ending message ID does not have to be one of the WTOs that are returned in the LINEnnnn variables.

No reply has been received; WAIT time has expired.

Check whether the response WTOs have inadvertently been suppressed.

The SYSLOG MPF Flags have an indicator showing whether the WTO has been suppressed by a subsystem (for example, by an BMC AMI OpsA Rule).  In the following example syslog, the MPF flags are 000A0294.  The x'04' bit in the fourth byte indicates the WTO was suppressed.

These MPF flags are described in the HCLREQFL field in SYS1.AMODGEN(IHAHCLOG) and also in the IBM MVS publication z/OS MVS Planning: Operations section titled "SYSLOG MPF flags".