Supported IMS log records

Record

Description

Contents

Possible Usage

X'01'

Input message

This record represents the transaction input and associated information like the input TIME, USER’s ID, and DATA for the transaction to process.

Records the start time so that you can compare it with a subsequent 03 record and understand how long it took to process the transaction.

Determine how many transactions are coming from a specific origin to develop a normal transaction level for later variance analysis.

Look at the information the user has asked IMS to process, the “input payload”.

X'02'

Command log record

This record represents a condensed version of the command entered by the IMS user or program.

Analyze who is entering which IMS commands

X'03'

Output message

This record is the output result of IMS transaction with associated information like the TIME and USER to receive the output.

Match with the 01 record to know processing time for the transaction. Determine if SLAs were met.

Determine how many transactions are going out to a specific destination to develop a normal transaction level for later variance analysis.

Look at the information the user is getting back from IMS, the “results payload”.

X'06'

IMS event accounting record

IMS writes this record when major IMS system events occur, such as IMS starting or stopping.

Understand how often IMS was started or stopped and how long it was up. Can be used to gather availability trends.

X'07'

Program termination accounting record

This termination record contains the date and time of program termination and the resources it consumed while it ran.

Pair this with the 08 record to track program processing times. Determine if SLAs were met.

Track trends in which programs were used throughout a day, week, month or other time period.

Track trends in a program’s resource usage and flag any variances from normal.

X'08'

Program schedule record

This schedule record contains the date and time of program start and the region and schedule initiation type.

Gather a program’s start information to match up with a subsequent 07 record.

X'0A'

CPI-C program record

CPI Communications (CPI-C) driven application programs are defined only in APPC. This record contains information about when a CPI-C application was started or stopped

A CPI-C program is a specific type of IMS program. You may want to know it if you are using any of them, how long they ran and trends for their usage

X'10'

Security violation record

This record indicates that IMS detected a security violation, identifies the precise nature of the violation and specifies whether it is terminal or program-related.

Contains information about any security violations IMS detects so you can track trends and determine why the violation occurred.

X'14'

Switched-line disconnect

This record is written at disconnection of a dial line.

Know when a dial up connection to IMS ends. Pair with the corresponding 15 record to know the length of the connection. Not used much anymore as most IMS connections are no longer dial up.

X'15'

Switched-line connect

This record is written at connection of a dial line.

Know when a dial up connection to IMS starts. Not used much anymore as most IMS connections are no longer dial up.

X'16'

Sign-on/off record

This record is written at successful completion of a /SIGNON or /SIGNOFF command.

Track user activity by knowing when they signed onto IMS and when they left. Could be used to find users that signon and then go inactive without signing off. You may want to automatically disconnect these users after a defined time to free up the connection or close an inactive open connection as a security precaution.

X'18'

Extended checkpoint record

This record logs the details and checkpoint data for an extended checkpoint.

Use this record to get information captured by an extended checkpoint.

X’22’

IMSPLEX command

This record is written at successful completion of an IMSPLEX type 2 command.

Use to analyze which IMS commands are being entered to manage all the IMS instances in a group of IMS systems (an IMSPLEX).

X'30'

Message queue prefix changed record

This record logs changes made to the message queue record prefix.

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'31'

Message queue GU record

This record logs the details of a message that is taken (GET UNIQUE (GU)) from the message queue to be sent to its destination. The record is present for incoming messages that are processed by a program scheduled in a message processing region, or for outgoing messages that are sent to a network destination. In addition, the record is present for message switches.

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'32'

Message queue reject record

This record is produced when the IMS message queue rejects a message because an error occurred, presumably causing an application program abend.

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'33'

Message queue DRRN free record

This record always indicates that the message is no longer needed by IMS.

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'34'

Message queue cancel record

This record indicates that the message was canceled from the queue

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'35'

Message queue enqueue record

This record indicates that the message in the message queue has been placed on the queue for processing

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'36'

Message queue dequeue record

This record indicates that the destination received the message, and the message has been dequeued or deleted.

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'37'

Message queue syncpoint transfer record

This record indicates that the message transferred to its permanent destination and reflects that a successful commit occurred.

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'38'

Message queue syncpoint fail record

This record indicates that a syncpoint failure occurred and the message transfer will not occur.

These X’3x’ records contain details about the IMS message queues and the messages they contain. A customer would use these records to do detailed analysis of the IMS message queues and how they are used.

X'40'

Checkpoint record

This record is written when an IMS system checkpoint is taken. The sub-types contain detailed information about the checkpoint.

The customer would use the information in this record to do analysis of the system wide checkpoints that IMS is taking and the information that IMS writes out as part of that checkpoint action.

X'41'

Checkpoint batch record

This record indicates that a batch program has issued a checkpoint.

Indicates that a batch program has issued a checkpoint.

X'42'

Log buffer control

This record is written when IMS has switched from one OLDS to another, or a checkpoint was taken, or a shutdown checkpoint was taken.

This record is written when IMS has switched from one OLDS to another, or a checkpoint was taken, or a shutdown checkpoint was taken.

X'45'

Checkpoint statistics record

This record is written to report checkpoint statistics. The sub-types contain detailed statistics about IMS buffer pools and other system areas.

Use this record to understand how IMS resources are being used over time. Statistics include information on buffers, storage pools, scheduling, and much more.

X'4C'

Program/database start/stop record

This record is written when an action that is related to a full-function database occurs. Actions can include backouts, write errors, program stops, database starts and stops, locks, and so on.

Actions against full function databases

X'50'

Full function database update

This record is written when an application program updates a full-function database.

This record is written when a full function database is updated. It has a number of subtype records that are used to show various parts of the update action.

Use this record to see the data that was inserted, changed or deleted. This record also contains information about the database such as VSAM or OSAM, database type (HDAM, HIDAM, HISAM, etc.), partitioned or not, share levels, and so on.

X'56'

External subsystem record

This record indicates the status of external subsystem connection and commit processing.

A type 56 record is written when any of the following events occurs:

• An event has occurred to change the status of a transaction that is executing in an IMS external subsystem.
• An event has occurred to change the status of a connection between IMS and the CCTL.
• An event has occurred during IMS sync point processing.

X'59'

Fast Path database update

This record is written when a Fast Path database is updated and when various events occur during Fast Path processing. The sub-type records contain the details such as the input message, output message, datasets opened, closed or changed and other information.

Provides details about changes made to Fast Path databases

X'67'

Trace record

X’C0’

BMC COPE for IMS Base System

This record is written by BMC COPE for IMS Base System at the time of an Online Log Data Set (OLDS) switch.

Type X'C001' contains information that BMC COPE for IMS Base System collects about IMS Transaction Activity.

X’DA’

BMC AMI Change Manager for IMS TM (formerly DELTA PLUS)

This record is written by the BMC AMI Change Manager for IMS TM (formerly DELTA PLUS) product.

BMC AMI Change Manager for IMS TM writes this log record to document the actions it has taken and the journals it created. Use this information to track the dynamic changes made by BMC AMI Change Manager for IMS TM.

X’DE’

BMC AMI Change Manager Virtual Terminal for IMS (formerly DELTA Plus Virtual Terminal)

This record is written by the BMC AMI Change Manager Virtual Terminal for IMS (Formerly DELTA Plus Virtual Terminal) product.

The BMC AMI Change Manager Virtual Terminal for IMS product writes these log records when doing checkpoints or to record significant events such as signons, forced signoffs, deletes. LTERM definitions, successful MODBLOCKS changes, etc. Use the information in this record to track actions by BMC DELTA PLUS VIRTUAL TERMINAL.

X'EA'

BMC AMI Extended Terminal Assist for IMS

This record is written by the BMC AMI Extended Terminal Assist for IMS product.

The BMC AMI Extended Terminal Assist for IMS product writes these log records when terminal sessions are created or deleted, when user session signon or sigonoff occurs, and when IMS checkpoints are taken.

X’EF’

BMC AMI Message Advisor for IMS

This record is written by the BMC AMI Message Advisor for IMS product.

The BMC Message Advisor Queue Protection Facility (QPF) writes these records when the QPF is activated, and the user wants to know what actions were taken by the product. Use this information to understand how often QPF may have been triggered and what it did.

X’F8’

BMC AMI Datastream for IMS

This record contains information about changes made to IMS database segments and includes the segment key.

Use this information to understand and analyze changes (inserts, updates, deletes and reads) of information in specified IMS segments. This record is created by BMC AMI Datastream for IMS to record those changes with the addition of the IMS segment key information to enable easy identification of the IMS segment that was changed.

X’F9’

BMC AMI Ops for IMS (formerly MainView for IMS)

This record is written by BMC AMI Ops (MainView) for IMS at the time the program is terminated.

Contains information MainView for IMS collects about an IMS program. For MainView customers, it may be easier to use this record to get things like program start/stop, program resource usage, zIIP/zAAP eligibility of the program, etc. than from multiple regular IMS log records.

X’FA’

BMC AMI Ops for IMS (formerly MainView for IMS)

This record is written by BMC AMI Ops (MainView) for IMS when transaction processing is complete.

Contains information MainView for IMS Offline collects using its unique Event Collector functionality.  This record contains things like transaction start/stop, transaction type, database access times plus very detailed and granular information not available in regular IMS log records. IMS normally only records database changes (inserts, updates, deletes), but this record adds information on what databases the user read, which could be important in security analysis.