DC201006 ?ABRT ABRU' and 'ABRT CKUR' abends.
Article ID: 36839
Updated On:
Products
Issue/Introduction
Question:
We get a fair amount of DC201006 ‘ABRT ABRU' and 'ABRT CKUR' abends. The System Tasks and Operator Commands documents the CKUR but not the ABRU. What's the difference?
Answer:
Regarding the documentation of aborts ABRU and CKUR; we've documented
them in the CA IDMS Messages and Codes Guide, Volume 1, Chapter 2 CA IDMS
ABND Codes.
Here's the text:
ABNDABRU
ABRU
Reason:
An external request unit executing under the active DC/UCF task has abended. The abend may have been caused when the request unit exceeded the maximum time allowed between database requests, or it may have been caused by other factors, as described in the system log. If the abend condition was detected by the check-user, look around-time, or external-wait mechanism, or by the code in the IDMSREL<x> routine (teleprocessing-monitor programs only), the system writes a snap dump to the log file, if requested during system generation.
Refer to the CA IDMS System Generation Guide for a description of these abend detection mechanisms and of the SYSTEM statement ABRU SNAP/NOSNAP parameter.
Module:
IDMSSERV or IDMSTASK
=====================================================================
ABNDCKUR
CKUR
Reason:
RHDCCKUR has detected that a batch to CV job with an open run unit is no longer running. The run unit is aborted. This can happen if the batch job abended or ended without issuing a finish.
Module:
RHDCCKUR
====================================================================
There’s a Knowledge base article on CKUR:
TEC584940 Batch program ends successfully but abends in the CA IDMS CV with abort code CKUR.
Additional Information:
CA IDMS Messages and Codes Guide, Volume 1, Chapter 2 CA IDMS ABND Codes.
CA IDMS Systems Tasks and Operator Commands, Chapter 4, section, “DCMT DISPLAY CENTRAL VERSION Command Usage”; subsection” CV-Status ABRT Values “.
Environment
Component:
Feedback
