Message audit log

An FTM SWIFT message audit log is a database table in which data about messages is stored. There is a separate message audit log for each OU. Each message audit log provides structures to store the following data:
  • Message header (MQRFH2 header)
  • Message body
  • Context data, for example, the user ID of the message originator
There are two kinds of message audit logs:
non-partitioned
This is the default type of message audit log. This type of log is sufficient if, for each OU, there is a regular period during which all FTM SWIFT services are stopped, and during which you can archive and maintain the data in its message audit log.
partitioned
This type of audit log employs several partitions, at least one of which is inactive at any given time. This lets you archive and maintain the data in a message audit log while FTM SWIFT services are still running. For more information, see Partitioned message audit log.
Table 1 describes the fields of a message audit log.
Table 1. Fields of a message audit log
Field name Data type Mandatory (Field is always filled) Description
AM_LOG_GMT_TS TIME STAMP Yes Date and time, in Coordinated Universal Time (UTC), when the message was stored in the Audit Log.
AM_AUDIT_GMT_TS TIME STAMP Yes Date and time, in UTC, when the service requested that the message be stored in the Audit Log.
AM_CFG_GMT_TS TIME STAMP   Date and time, in UTC, when the configuration took place. For information about how to retrieve the configuration that was valid at a specific date and time, see View DNIV_A_OU_ou.
AM_USER_ID CHAR(100) Yes The user ID that originated the message.
AM_OU_NAME CHAR(8) Yes OU to which the message belongs.
AM_MQRFH2 CLOB (100M)   The IBM® Integration Bus MQRFH2 header of the message. For information about the message model and data formats, see The message interface.
AM_BODY_CCSID INTEGER   Character set identifier of the contents of the AM_BODY column. For a command or a response to a command, this is always 1208.
AM_BODY_ENCODING INTEGER   Numeric encoding of the contents of the AM_BODY column. For a command or a response to a command, this is the system default encoding (MQENC_NATIVE).
AM_BODY BLOB (100M)   One of the following:
  • For a message, the last folder that is both at the same hierarchical level as the headers and not an MQ header (that is, does not have a name that begins with the letters MQ). Usually, this is the message body, but if the message does not contain a body this is the last non-MQ header or, if the message does not contain any such headers, a null value.
  • For a command, the command as issued by the user.
  • For a response to a command, the response message or messages.
  • For messages disposed with the Data Integrity Checker Utility, the content of the disposed row. For the format see Audit log for Data Integrity Checker command dispose.
AM_MSG_ID CHAR(24) FOR BIT DATA   The message ID. This ID must be unique within an FTM SWIFT instance, and can be used to identify the information in this and other tables that corresponds to a particular message.

For FIN messages, possible values are described in Table 2.

For messages processed by the MSIF transfer service, the value is a hexadecimal representation of MQMD.MsgId.
AM_MSG_TYPE VARCHAR (254)   The message type. For SFD-related audit nodes with suffix Snffsm, the value is SwiftEnvelope. Messages disposed with the data integrity checker tool have the value table_name:row_id. For FIN IL messages, InterAct messages, and commands and responses to commands, this is always NULL.
AM_EXT_MSG_ID VARCHAR (50)   The message ID which is from an external system, for example, the Unique Message Reference (UMR) in MERVA ESA.
AM_MSG_GRP_ID VARCHAR (50)   The message group ID. This is used to correlate messages that belong together, for example, as an inbound message and its acknowledgment, or a request message and its corresponding response message. Use this field to identify messages that belong to the same unit of processing.

For FIN messages, possible values are described in Table 2.
AM_BUS_GRP_ID VARCHAR (50)   The business group ID. This ID correlates the messages that belong to the same business transaction.
AM_REPLY_TO_QMGR VARCHAR (48)   The queue manager used to pass back the reply message.
AM_REPLY_TO_Q VARCHAR (48)   The queue used to pass back the reply message.
AM_BROKER VARCHAR (254)   Name of the broker hosting the message flow that caused the audit record.
AM_MSG_FLOW VARCHAR (254)   Name of the message flow that caused the audit record.
AM_NODE VARCHAR (254)   Name of the node that caused the audit record. Possible values are described in Possible values in column AM_NODE.
AM_APPL_NAME VARCHAR (100)   Name of the application that inserted the message.
AM_ROWID ROWID Yes This column is maintained by DB2®. Use of this column requires comprehensive knowledge of the concept of DB2 ROWID columns.