IDMS 40xx abend codes - how to identify the module

book

Article ID: 220507

calendar_today

Updated On:

Products

CA IDMS

Issue/Introduction

There are some 40xx abend codes which indicate a problem loading an IDMS module.
These can occur in a CV, batch job, CICS, or some other front end such as TSO.

 

Environment

Release : Any supported release.
Component : CA IDMS/DB

Resolution

Some of these abend codes indicate that the problem was with a specific module, as follows:

4002 - any module
4004 - RHDCCSA
4008 - RHDCCODE
4009 - IDMSNLT
4010 - RHDCOPTF
4012 - IDMSUXIT
4013 - IDMSUTAB
4014 - RHDCTAPE

In the event of a 4002 abend, to identify the problematic module, check the log of whichever front-end is involved.
As an example, in CICS, a common reason for a 4002 abend is that RHDCSRTT could not be loaded:

IDMS DC999999L MODULE RHDCSRTT LOAD FAILED

Once the name of the module is identified, make sure it is available in the appropriate DDNAME concatenation for that front end (e.g. STEPLIB, CDMSLIB, DFHRPL).

Note:
These abend codes are documented but under the usual eight character style IDMS message code of ABNDxxxx.
To find them, search on ABNDxxxx. Example: ABND4002
The URL for these messages on the TechDocs message space is:
https://techdocs.broadcom.com/us/en/ca-mainframe-software/database-management/ca-idms-messages-19-0/19-0/ca-idms-abnd-codes/abndXXXX.html
where XXXX is the abend code.