U1304 abend in the CA Dispatch external ARCHIVE or EXTRACT subtask

Document ID : KB000016616
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

The CA Dispatch external ARCHIVE or external EXTRACT subtask received a USER COMPLETION CODE=1304 followed by the task coming down with ABEND=S000 U1399 REASON=00000000. Messages seen in the logs when this error occurs would look similar to the following:

 

USER COMPLETION CODE=1304 

TIME=09.58.51 SEQ=19330 CPU=0000 ASID=00DE 

PSW AT TIME OF ERROR 078D1000 8000930C ILC 2 INTC 0D 

ACTIVE LOAD MODULE ADDRESS=00008B68 OFFSET=000007A4 

NAME=XTDSBALI 

DATA AT PSW 00009306 - 00181610 0A0D4900 CAAA4780 

 0: 80000000 1: 80000518 

 2: 0000D52C 3: 0000D760 

 4: 00AE8AB0 5: 33C00130 

 6: 00006760 7: 00FC9700 

 8: 0000CE30 9: 80020408 

 A: 0000BE48 B: 0000D018 

 C: 80008B68 D: 000067D0 

 E: 8002087E F: 0000D6E0 

END OF SYMPTOM DUMP 

STC43074 CADS DC980034 External Extract Background Has Abended 

STC43074 *IEF450I CADSXTEX CADSXTEX - ABEND=S000 U1399 REASON=00000000

Question:

What caused the U1304 abend to be received in the external subtask? 

Environment:
z/OS
Answer:

These U1304 abends typically occur when the external archive or external extract subtasks of CA Dispatch lose their communication link with/to the CA Dispatch MAIN region.

 You can identify and confirm this communication link loss as being the cause of the problem via the existence of the following message(s) appearing in the logs prior to the U1304 abend occurring:

 

DC980041 - ARBGDB - 0069 STATUS - CV NOT PRESENT, TASK ABENDING 

or

DC980042 - ARBGEXDB - 0069 STATUS - CV NOT PRESENT, TASK ABENDING 

 

The cause of the communication disconnect may have been the result of some kind of contention problem between the external subtask and the main CA Dispatch region. Or, contention with a CA Dispatch batch utility job running at a time when the ARCHIVE or EXTRACT subtasks of CA Dispatch needed to be stopped first, before running the utility job. 

 

It may have also been the result of a problem in the MAIN CA Dispatch region itself. For example, if someone brought the MAIN region DOWN, issued a CANCEL command, or if it abended. 

 

If you receive one of these U1304 abends, check the MAIN CA Dispatch regions logs and see if there were any problems with the MAIN CA Dispatch region around the time the external subtask abended. You will likely find that the MAIN region was brought down.  

 

In any case, the appropriate resolution to the U1304 abend would be to RESTART the external subtask. Depending on what you find in the MAIN CA Dispatch regions logs, you might also want to consider recycling the MAIN region before restarting the external tasks. 

 

Additional Information:

Please refer to the CA Dispatch Message Guide regarding the DC980041 and DC980042 messages.