MDACC (32-byte bit string)

Accounting token.

This is part of the identity context of the message. For more information about message context, see Overview; also see the WebSphere MQ Application Programming Guide.

MDACC allows an application to cause work done as a result of the message to be appropriately charged. The queue manager treats this information as a string of bits and does not check its content.

When the queue manager generates this information, it is set as follows:

• The first byte of the field is set to the length of the accounting information present in the bytes that follow; this length is in the range zero through 30, and is stored in the first byte as a binary integer.

• The second and subsequent bytes (as specified by the length field) are set to the accounting information appropriate to the environment.

  • On z/OS the accounting information is set to:

    • For z/OS batch, the accounting information from the JES JOB card or from a JES ACCT statement in the EXEC card (comma separators are changed to X'FF'). This information is truncated, if necessary, to 31 bytes.

    • For TSO, the user's account number.

    • For CICS, the LU 6.2 unit of work identifier (UEPUOWDS) (26 bytes).

    • For IMS, the 8-character PSB name concatenated with the 16-character IMS recovery token.

  • On i5/OS, the accounting information is set to the accounting code for the job.

  • On HP OpenVMS, Compaq NonStop Kernel, and UNIX systems, the accounting information is set to the numeric user identifier, in ASCII characters.

  • On OS/2, the accounting information is set to the ASCII character '1'.

  • On Windows, the accounting information is set to a Windows NT security identifier (SID) in a compressed format. The SID uniquely identifies the user identifier stored in the MDUID field. When the SID is stored in the MDACC field, the 6-byte Identifier Authority (located in the third and subsequent bytes of the SID) is omitted. For example, if the Windows NT SID is 28 bytes long, 22 bytes of SID information are stored in the MDACC field.

• The last byte is set to the accounting-token type, one of the following values:

  ATTCIC

  CICS LUOW identifier.

  ATTDOS

  PC DOS default accounting token.

  ATTWNT

  Windows security identifier.

  ATTOS2

  OS/2 default accounting token.

  ATT400

  i5/OS accounting token.

  ATTUNX

  UNIX systems numeric identifier.

  ATTUSR

  User-defined accounting token.

  ATTUNK

  Unknown accounting-token type.

  The accounting-token type is set to an explicit value only in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. In other environments, the accounting-token type is set to the value ATTUNK. In these environments the MDPAT field can be used to deduce the type of accounting token received.

• All other bytes are set to binary zero.

For the MQPUT and MQPUT1 calls, this is an input/output field if PMSETI or PMSETA is specified in the PMO parameter. If neither PMSETI nor PMSETA is specified, this field is ignored on input and is an output-only field. For more information on message context, see the WebSphere MQ Application Programming Guide.

After the successful completion of an MQPUT or MQPUT1 call, this field contains the MDACC that was transmitted with the message. If the message has no context, the field is entirely binary zero.

This is an output field for the MQGET call.

This field is not subject to any translation based on the character set of the queue manager--the field is treated as a string of bits, and not as a string of characters.

The queue manager does nothing with the information in this field. The application must interpret the information if it wants to use the information for accounting purposes.

The following special value may be used for the MDACC field:

ACNONE

No accounting token is specified.

The value is binary zero for the length of the field.

The length of this field is given by LNACCT. The initial value of this field is ACNONE.