Expected UNDO END log record not found on log stream llll for
job step stepname.
Explanation
At the completion of undo logging for a job step, CICS VR writes an UNDO
END log record to the undo log stream indicating whether the job step completed
successfully or abended. However, CICS VR did not find an UNDO END log record
on log stream llll for job step stepname.
An UNDO END log record might not have been written if undo logging failed
during execution of the specified job step.
System action
Batch backout processing continues.
User response
If you ran CICS VR batch backout to remove updates made by a batch job step
that encountered an undo logging error:
- If the CICS VR_UNDOLOG_CONTROL parameter was set to ENABLE SYNC during
execution of the specified batch job, any logging error would have caused
CICS VR to cancel the batch job. Also, the updates would have been synchronized
to ensure consistency between the actual VSAM updates and the updates recorded
on the log stream. Therefore, as long as no other steps or applications made
updates to the data sets after the specified batch job step was canceled,
CICS VR batch backout processing should have placed the VSAM spheres back to
the state that they existed prior to execution of the specified batch job
or batch job step. No further action is required.
- If the CICS VR_UNDOLOG_CONTROL parameter was not set to ENABLE SYNC during
execution of the specified batch job, updates might have been made to VSAM
spheres by the specified job step after the logging error occurred that are
not reflected on the undo log stream. Therefore, batch backout processing
might not have placed the VSAM spheres back to the exact state that they existed
prior to execution of the specified batch job or batch job step. Examine
the VSAM data sets for accuracy prior to performing any further updates against
them.
If you did not run CICS VR batch backout to remove updates made by
a batch job step that encountered an undo logging error, the undo log stream
might be corrupted and required log records might no longer appear on the
log stream. Examine the VSAM data sets for accuracy prior to performing any
further updates against them.