Journal Entry Types
Entries in the journal consist of one or more formatted print lines per event. Some events, such as hexadecimal dumps of control blocks, contain a variable number of lines, while others contain only one line. The first three bytes of each line, starting at position 2, indicate the line type.
The following table explains the DELTA IMS Journal’s line types and their definitions.
DELTA IMS Journal Facility Entry Line Types
Line Type | Description |
|---|---|
100 | Variable text data. $DLAJNL is used to output a string of useful information. The first three characters of text zzz relate to the CSECT (DLAXzzzX) that issued the $DLAJNL. |
200 | The current DB and DC SYSGEN dates. This line is issued during initialization and after /MODIFY COMMIT. |
300 | A record read from the DELTA Log. This entry can contain any of the following (as appropriate to the type of region): the IMS SYSGEN date, action, type of element, element name, spare mask/new name, and possible old element name in parentheses. Immediately following this line, the DELTA Log record is dumped as the LGRDSECT and DLSREC data areas. Records that show the status of IMS elements before DELTA IMS update are not written to the Journal. |
310 | A DELTA IMS X'02' log record encountered during /ERE. This line contains the action, type of element, element name, and spare mask/new name. Immediately following this line, the ITXDSECT and DLSREC data areas are dumped. |
320 | A DELTA IMS update received from BMCLINK. This line contains the action, type of element, element name, and spare mask/new name. Immediately following this line, the ITXDSECT and DLSREC data areas are dumped. |
400 | A message indicating the success of processing an update; a record for the update itself is written to the Journal in a preceding 300, 310, or 320 entry. Usually, this entry is simply the word Applied followed by a dump of the IMS control block updated. If no control block follows, it is unlikely that an update actually took place. |
410 | A BMCxxxx message that resulted from processing the preceding 300, 310, or 320 entry. Usually, this entry is simply the word Failed followed by the BMC Software message number. However, in some cases an error may have occurred or an update may have been made. If an update was made, the potentially updated control block is dumped on the lines that immediately follow this message. |
500 | A data area in dump format. Either the area name (such as DSECT name) or the area address appears. The offset into the area is given on subsequent lines (line type 510). The dumped area is otherwise produced in standard hexadecimal and character format. |
600 | Certain DELTA IMS messages issued from the IMS control region. |