CDC Guide for z/OS

Back Next

ERROR_LOG Parameter

Controls how the IMS log-based ECCR behaves when it encounters an IMS log that is marked as

in error

in the RECON data set or is otherwise unavailable.

ERROR_LOG={ABEND|SKIP|WAIT|WTOR|No response}

ABEND: When the IMS ECCR encounters a log that is marked as
in error
, it ends and issues a WTO message to the system operator console. The ECCR also issues messages that report the start and stop times of the log in error. The ECCR ends in a manner that enables you to restart it after resolving the log in error.
SKIP: The IMS ECCR skips any log that is marked as
in error
. The ECCR issues messages that indicate which logs have been skipped, including their names and start and stop times.
Use this option carefully. The ECCR might miss changes, which can invalidate the target data.
WAIT: When the IMS ECCR encounters a IMS log that is marked as
in error
, it issues informational messages that indicate the status of the log. Then, the ECCR sleeps. Periodically, the ECCR becomes active, based on the NO_DATA_WAIT2 value, to check the log status. After you resolve the log in error, the ECCR continues processing. Optionally, you can change the status of the log in IMS or remove the log from the RECON data set. If you do so, ensure that no changes are lost.
WTOR: Stops the IMS ECCR from continuing and issues a WTOR that asks for which option to use.
No response: The IMS ECCR waits on continuing basis. The ECCR issues messages that identify the log that is in error and the reason for the error.

Default is ABEND.

Typically, a IMS log is marked as

in error

when some type of media error occurs, such as an x37 abend, while data is being written to the log.

After a log has been ignored or skipped, you cannot try to process it again. You must rematerialize the target data.