DFS616I SYSTEM LOG DATASET NOT CLOSED- LOG WRITE ERROR
or
or
or
or
Explanation
A permanent I/O error occurred on the last remaining IMS log data set. If dual logging is in effect for IMS batch, the error occurs when both of the log data sets are damaged. For IMS online, the error occurs when the last remaining OLDS has a permanent I/O error or does not have enough space to complete a checkpoint freeze. There are 5 forms of this message.
- An IMS online system is running.
- No blocks are written on the log at the time of abend.
- An invalid block number is detected in the log buffers.
The second form is issued when an IMS batch region terminates abnormally without successfully closing the batch log (SLDS), and the last log record sequence number written on the batch log is located in a log buffer.
- The OLDS is not opened when the OLDS Buffer Purge ESTAE routine (DFSFDLF0) receives control.
- DFSFDLF0 fails the GETMAIN request for its message area.
- DFSFDLF0 fails to locate the last log sequence number written on the OLDS in all OLDS buffers.
The fourth form is issued when an IMS online system terminates abnormally without successfully closing the OLDS, and the last log record sequence number written on the OLDS is located in a log buffer.
The fifth form is issued when an IMS online system terminates abnormally and successfully purges all OLDS buffers during the OLDS Buffer Purge ESTAE routine.
System action
For the first two forms of this message, IMS terminates abnormally. Otherwise, IMS continues processing.
Programmer response
For the first two forms, allocate new log data sets to replace the ones that have encountered I/O errors. It might be necessary to use the Log Recovery utility to create log data sets free from WRITE or CLOSE errors. When a sufficient number of log data sets are available, emergency restart IMS to continue processing. Otherwise, not action is required