Of course it does not matter to COBOL! But it might matter to one or more applications that might just happen to be written in COBOL!
No disrespect @Gil but this kind of answer drives me crazy. One thinks about a problem. It is a big and complex problem with multiple unknowns and tradeoffs. There are many ways one might at least partially solve it. One thinks at length about all the tradeoffs. One finally drills down on one particular approach ... but wait! There is one detail necessary for the solution to work that one does not know. So one posts on IBMMAIN "how can a COBOL program running as a started task but not APF-authorized determine how many widgets are in a bushel?" And someone immediately replies "why would you want to do that?" Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Thursday, May 14, 2020 9:57 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? On Thu, 14 May 2020 16:31:45 +0000, Farley, Peter x23353 wrote: >Thanks Lizette, I had forgotten about LISTDSI. The context here was a need >for an API callable from a batch COBOL program, but that could be done too, if >somewhat clumsily due to the requirement for LISTDSI to be executed in a TSO >environment. > >I sent my co-worker on a search at cbttape.org for something he could use. > Why? Where does this matter to COBOL? The VTOC-based approaches give at least an upper bound, which might suffice for capacity calculations. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
