baije01

Tech Tip: CA IDMS CV Batch Job Accessing Database Error-Status 0069

Discussion created by baije01 Employee on Dec 12, 2017
Latest reply on Dec 28, 2017 by Sushil Joseph

Problem

Batch Job Abends with the following messages in JES output. 

IDMS DC410003 DNS SEND/RECEIVE Failure Status is : 0069 
IDMS DC410006 DNS Processing error, Function is RECEIVE_AND_WAIT, Status is XMIT 
IDMS DTS: Abend on path's subsequent downstream node 
IDMS DTS: Logical connections to node disabled 
IDMS DTS: Physical connection to node disabled 

Cause:

  The batch job has started a database transaction in the IDMS CV and the Task running in the CV has been abended for a reason other than a database related error.

Any errors related to accessing the database will be returned to the issuing program as an error-status, but if that error-status is 0069 it means the Task running in CV on behalf of the batch program was abended for a non-database reason and the connection to the CV has been severed.

The reason for the disconnection will be described in the IDMS CV LOG. 

It could be caused by a number of different situations.

Most commonly the Task running in CV was abended for one of the following:

 

  1.  STALL abend.  The Task waited for a CV resource (storage, database resource, etc) longer than the STALL INTERVAL (INACTIVE INTERVAL parameter in SYSTEM      or TASK definition in the Sysgen).

       This produces a series of messages ending with DC001003.

       DC001003 Vnn Tnnnnnn TASK:taskcode PROG:pgmname STALLED WAITING FOR resource ID

 

  1.   Exceeding LIMITS abend.  If the DBA has defined LIMITS enforcement on key system resources a task can be abended for exceeding the specified Limit for the         specified resource type.

        This produces message DC244002 or DC244003.

        Example:

        DC244002 Vnn Tnnnnnn TASK:taskcode; LOCK RESOURCE LIMIT EXCEEDED

 

  1. A system program servicing a call from the batch program has abended with a program check abend.

       This would produce message DC027002.

       example:

 DC027002 Vnn Tnnnnnn SYSTEM MODULE PROGRAM CHECKED NEAR modulename AT OFFSET nnnn 

 

Resolution/Workaround:

 The DBA needs to look at messages on the IDMS LOG from the time period when the batch job got the 0069 error-status.

 This can be done via online Task OLP or by running the PRINT LOG utility for the relevant time period.

 The resolution will be different depending on the abend of the batch Task. 

 

Additional Information:

CA IDMS Messages - Home - CA IDMS Messages - CA Technologies Documentation 

Outcomes