Where can the explanations for the FILE905E GSSFILE return codes in the IDMS Tools products be found?
Article ID: 52602
Updated On:
Products
Issue/Introduction
Question:
Where and what are the reasons for the FILE905E GSSFILE return codes?
When executing DB/REORG, what is the meaning of the message "FILE905E-GSSFILE RETURNED
AN ERROR DURING OPEN INPUT WITH FILE VSAMEXT RETURN CODES ARE 008,080,160,028"?
Answer:
GSSFILE is a General Service File handling routine that is used in the Tools Batch products only; not in the online products. Therefore the FILE905E GSSFILE error can occur in various IDMS Tools batch products (DB/Reorg, Dictionary Migrator, DB/AUDIT, etc).
Depending upon the product that is running (DB/Reorg, Dictionary Migrator etc) the format of the error messages may vary slightly from product to product. However the messages section in the various Tools Users Guides will describe the reason and action code for the product in question.
For example in DB/Reorg the message is:
GSFL001E ERROR OCCURRED DURING < OPEN/READ/WRITE> OF FILE file-name.
GSSFILE RETURN CODE is n1,n2,n3,n4
In addition to the DB/Reorg User Guide these GSSFILE return codes are described in the other the relevant IDMS Tools User Guides.
A similar message in Dictionary Migrator is:
FILE905E GSSFILE RETURNED AN ERROR DURING file-function WITH file-name, RETURN CODES are n1,n2,n3,n4
Table 23 in the IDMS/DB Database Reorg Option User Manual documents the n4 Return Codes.
Table 24 in the IDMS/DB Database Reorg Option User Manual documents the n2 Return Codes.
- Here is a common GSSFILE OPEN error example and how to interupt its return codes:
FILE905E-GSSFILE RETURNED AN ERROR DURING OPEN INPUT WITH FILE VSAMEXT
RETURN CODES ARE 008,080,160,028
The 028 is n4 and in Table 23; it means a VSAM error has ocurred and n1, n2 and n3 must be examined for other errors.
Since n4 is a VSAM error, n3=160 contains the VSAM feedback byte error.
To locate the Return code for n3, check the IBM VSAM Message Manual for the 160 code.
160 VSAM code indicates the file was empty.
Therefore in this first example; it refers to the VSAMEXT file which is used within Dictionary Migrator. This file is created from the entities within the EXTRACT file. If the EXTRACT file is empty then no VSAM file will be written and a subsequent OPEN INPUT fails. - Here's another example of a common GSSFILE error:
FILE905E GSSFILE RETURNED AN ERROR DURING WRITE WITH FILE EXTRACT, RETURN
CODES ARE The GSSFILE return codes of 000,002,000,008 mean:
n2=2 Parm list override JCL
n4=8 Open error or file is not open.
In the second example with the return codes of 0,2,0,8; this can happen for a variety of reasons generally related to the JCL definition. Either incorrect DCB information
or DCB information that does not match the internal program definitions. - In this example GSSFILE RETURNED AN ERROR DURING OPEN WITH FILE ARCHIVE, RETURN CODE ARE 000,001,000,008
n2=1 JCL/label overrode parm list
n4=8 Open error or file is not open.
Here the problem is in the EXTRACT file where the DCB information changed.
References:
CA IDMS ADS Alive Option User Guide, Chapter 5 Messages and Severity Codes
CA IDMS/DB Audit Option User Guide, Chapter 6 Error Messages
CA IDMS/DB Database Analyzer Option User Guide, Chapter 5 Message Listing
CA IDMS/DB Database Enforcer Option User Guide, Chapter 5 Messages
CA IDMS/DB Database Extractor Option User Guide, Chapter 6 Messages
CA IDMS/DB Database Journal Option User Guide, Chapter 6 Processing Messages
CA IDMS/DB Database Reorg Option User Manual,Chapter 6 Message Text and Messages Return Codes
CA IDMS/DB Database SASO Option User Guide, Chapter 5 Message Text
CA IDMS/DC Transaction Server Sort Option User Guide, Chapter 6 Non-Standard Message Codes- Batch
CA IDMS Database Dictionary Migrator Option Guide, Chapter 6 Using CA IDMS Dictionary Migrator Reports
Environment
Component:
Feedback
