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.

IMFEXEC MQI variables

The following list describes general properties for the IMFEXEC MQI variables:

  • Variable names consist of a:
    • Prefix name (for example, IMFMQI)
    • Structure name (for example, MD, DLH)
    • Field name (for example, MsgId or CorrelId in the message descriptor)

  • Each node of the variable name is delimited by an underscore (_)

  • Field-name variables whose corresponding possible values are constants, defined for them by IBM MQ, are populated with the constant name rather than the actual value. For example, in the case of a Dead Letter message, the variable IMFMQI_MD_FORMAT, which contains the format field from the message descriptor, is set to MQFMT_DEAD_LETTER_HEADER. Likewise, the variable IMFMQI_MD_VERSION, which contains the version of the message descriptor, is set to MQMD_VERSION_1 instead of x’1’. The following rules apply for variables set by BMC AMI Ops Automation for MQ:

    • If the value for a character field does not have a defined constant value, the actual value is used.

    • If the value for a numeric field that has a defined range does not have a defined constant, the actual numeric value converted to zoned decimal is used.

    • Variables for fields that are defined as hexadecimal fields (MQBYTExx in IBM MQ) are not converted and are set ‘as is.’

    • Variables that are created for flag fields in a IBM MQ structure may contain multiple constant values, delimited by blanks. For example, the variable for the message descriptor Report field, IMFMQI_MD_REPORT, can have several values. The resulting value might look like this: ‘MQRO_COA MQRO_COD’. Any other valid combination could be seen as well.

    • Variables that are created for IBM MQ fields where the value has more than one defined constant will contain both constants. For example, the variable IMFMQI_MD_PUTAPPLTYPE, which contains the PutApplType value from the message descriptor, would contain the value, ‘MQAT_OS390 MQAT_MVS’, if the message originated on an z/OS system. This result is because both constants contain the value ‘2’.

Related topic

BMC-AMI-Ops-Automation-for-MQ-IMFEXEC-statements


 

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