There is lots it could do! Make a decision on "strategy" based on the volume of input, for example. Do I process it all or cut off after 'n' records and do more on the next run? Do I read the file into an in-memory table and access records there, or do I load it into a VSAM file for direct access? Do I invoke an external sort or use an internal sort? Or a thousand other things.
It is wrong as @Shmuel points out to preclude questioning the necessity of doing something exactly as the OP suggests. It is equally wrong to assume there could be no good reason for doing it the OP's way. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard adam Sent: Thursday, May 14, 2020 11:52 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Is there any z/OS API to get byte file size for non-VSAM, non-zFS, non-database files? It is easy to say that a COBOL program needs to “know” this but it is nonsense since there is nothing a COBOL program can do with this info. If it turns out to really be necessary then a subroutine can be written (as it has been done for decades) to provide this information. If the question is simply to bitch about why z/OS does do this automatically via a call or something then the complaint is directed to the wrong group ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
