FS 90 reading VSAM sequentialy

[josep11477]

I am sequentialy reading a VSAM file in COBOL Set for AIX.
When arriving to the end of file I get a FS 90. I do not know what does it mean. Can anybody help me, please?

 

[TonyJollans]

Hi josep11477,

I think status code of 90 is more likely the result of trying to read past the end of the file. Is it possible you're missing EOF (status code 1x) somehow?

Enjoy,
Tony

--------------------------------------------------------------------------------------------
We want to help you; help us to do it by reading this: Before you ask a question.

 

[Crox]

http://publibz.boulder.ibm.com/cgi-....1?SHELF=IGY3SH10&DT=20020920180651#TBLKEYVAL

1. For multithreading only: A CLOSE of a VSAM or QSAM file was attempted on a thread that did not open the file. 2. Without multithreading: For VSAM only: See the information on VSAM return codes in the Enterprise COBOL Programming Guide.

 

[josep11477]

Thanks both, but I still have the problem. I am going to explain it. In AIX VSAM are created by COBOL with a binary file with some attributes of the file. Problem appears when you need to manipulate a file with SyncSort (like DFSORT in Mainframe). After the SyncSort step, if you need to process the output file in a COBOL program, you have to generate this binary file ".namefile.DDMEA", so that COBOL can open it. As this file contains attributes you cannot copy from another one you have (what I have been doing until now).
There is a problem with an attributed which tells the COBOL program the size of the file it is going to read. My problem is that COBOL thinks that there are still records to read based on the information in this binary file (copied from another). Question:

¿Does anybody work with this binary files ".namefile.DDMEA"?
¿Does anybody knows what can I do to generate this binary file from a file? ¿Is there any command to do so?

 

[Crox]

perhaps you can work around by making a sequential file and let syncsort work on it. What is it you want to do with syncsort instead of COBOL.

 

[Truusvlugindewind]

Yes, like Crox says, or embed sort into COBOL using the SORT verb and let COBOL do the I/O.
This insures that you have no "strange" files on your disk.

[offtopic]
Micro Focus and ACUcorp both use their own filesystem on an AIX (and other unices). Works great! I do not have the impression that IBM is paying a lot of attention to their COBOL compilers outside of the mainframe.
[/offtopic]

 

[josep11477]

Thanks about comments.
I agree about IBM not interested in their COBOL compilers in AIX. However, I am working in a migration project and it would be a great effort to us to implement SORT inside COBOL programs.
About a sequential file (not VSAM). It would be great if there were a sequential file in AIX. It seems stupid but I haven't found any file system with a typical sequential file. Line Sequential doesn't support COMP or binary items. STL filesystem generates some header bytes in the seq files. And VSAM has this .namefile.DDMEA that causes problems... There is still the SFS server (ENCINA) but is not recommneded for batch programs.

Thanks again