IMS SYSGEN dates

The Log control record also contains the IMS SYSGEN dates as of the most recent IMS restart or online change. The SYSGEN date is recorded with each CM IMS TM request to IMS. An IMS element added through CM IMS TM is considered active if the SYSGEN date that was current at the time of the update matches the current SYSGEN date. During IMS restart, CM IMS TM reapplies active elements to IMS.

Related topic

BMC-AMI-Change-Manager-for-IMS-TM-log-and-history-files

The following table provides additional information about SYSGEN dates:

SYSGEN

Used for

Date defined as assembly date of

Comments

DB

databases, programs, transactions, and route codes

CSECT DFSISMB0 in module DFSSMB00 (in the MODBLKS data set)

The current DB SYSGEN date may change after an IMS online change (/MODIFY PREPARE and /MODIFY COMMIT commands). A change in the DB SYSGEN date is reflected in the Log control record with the next CM IMS TM request or restart of the IMS control region.

DC

LTERMs, subpools, and nodes

CSECT DFSICLL0 in the IMS nucleus


Important

Because SYSGEN dates contain only dates and no times, multiple online changes for MODBLKS on the same day could cause unpredictable results. The specific problem that will occur depends upon the elements on the Log when CM IMS TM attempts to determine which elements are active or inactive.

If you perform one MODBLKS gen and then back it off, no problem will occur.


 

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