CA IDMS fetch errors EW4009I IEW4005I CSV031I
Article ID: 123487
Updated On:
Products
IDMS
IDMS - Database
IDMS - ADS
Issue/Introduction
A CV log may show the following errors
IEW4009I FETCH FAILED FOR MODULE HTA711T FROM DDNAME V0002 BECAUSE OF AN I/O ERROR.
IEW4005I FETCH FOR MODULE HTA711T FROM DDNAME V0002 FAILED BECAUSE IEWFETCH ISSUED RC 0F AND REASON 40
CSV031I LIBRARY ACCESS FAILED FOR MODULE HTA711T , RETURN CODE 24, REASON CODE 26080021, DDNAME V0002
Reports on the PDF named in these errors may show that the disk pack where it resides has plenty of room. What do these errors mean, and how can this be resolved?
IEW4009I FETCH FAILED FOR MODULE HTA711T FROM DDNAME V0002 BECAUSE OF AN I/O ERROR.
IEW4005I FETCH FOR MODULE HTA711T FROM DDNAME V0002 FAILED BECAUSE IEWFETCH ISSUED RC 0F AND REASON 40
CSV031I LIBRARY ACCESS FAILED FOR MODULE HTA711T , RETURN CODE 24, REASON CODE 26080021, DDNAME V0002
Reports on the PDF named in these errors may show that the disk pack where it resides has plenty of room. What do these errors mean, and how can this be resolved?
Environment
This error can occur in any mainframe environment running CA IDMS.
Resolution
The errors indicated here are IBM errors; they are not produced by CA IDMS. IDMS does not physically read the loadlib; a DML statement triggers a request for the read by MVS. According to the IBM message manuals, the return codes being reported here (0F / 40) indicate a permanent error on a real (not virtual) dataset (https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieam800/kk4005i.htm).
There are several things worth researching here, which could be causing or contributing to this error:
1- DCMT VARY LOADLIB V0002 OFF, the back ON. If your loadlib has gone into a new extent while the CV is up, this series of VARY commands is mandatory to make the contents once more readable.
2- Copy the load module named in the error message to the first library in the CDMSLIB concatenation and issue a DCMT V PRO NCI, then try re-executing.
3- Cycle the CV & try again.
4- These errors can be caused by insufficient region. Ensure that your startup JCL specifies REGION=0M (if it doesn't already) & try again.
5- Possible problems with the loadlib that could cause this are
a- multiple extents (esp if one is added while the CV is up - see above),
b- a bad file. You can check the MVS Log for any messages relative to this loadlib; to see if there are any that give information about what physical problem could be causing the error.
6- You can move the dataset to another DASD and try again; this type message could mean that the disk pack may be corrupt.
7- The problem can be caused by a scheduling problem that caused loadlib compress jobs to run while the IDMS regions were up. That may also be a possibility you want to research.
If none of the above resolve the problem, IBM support should be involved to get assistance in determining the dataset or disk problem that is causing these errors. .
There are several things worth researching here, which could be causing or contributing to this error:
1- DCMT VARY LOADLIB V0002 OFF, the back ON. If your loadlib has gone into a new extent while the CV is up, this series of VARY commands is mandatory to make the contents once more readable.
2- Copy the load module named in the error message to the first library in the CDMSLIB concatenation and issue a DCMT V PRO NCI, then try re-executing.
3- Cycle the CV & try again.
4- These errors can be caused by insufficient region. Ensure that your startup JCL specifies REGION=0M (if it doesn't already) & try again.
5- Possible problems with the loadlib that could cause this are
a- multiple extents (esp if one is added while the CV is up - see above),
b- a bad file. You can check the MVS Log for any messages relative to this loadlib; to see if there are any that give information about what physical problem could be causing the error.
6- You can move the dataset to another DASD and try again; this type message could mean that the disk pack may be corrupt.
7- The problem can be caused by a scheduling problem that caused loadlib compress jobs to run while the IDMS regions were up. That may also be a possibility you want to research.
If none of the above resolve the problem, IBM support should be involved to get assistance in determining the dataset or disk problem that is causing these errors. .
Additional Information
Details about the CA IDMS DCMT commands to vary the loadlib can be found here:
https://docops.ca.com/ca-idms-ref/19/en/ca-idms...
https://docops.ca.com/ca-idms-ref/19/en/ca-idms...
Feedback
Yes
No
Powered by
