Hi Peter, 

I came across a similar use case a couple times over the past year or so. 
Shifting priorities have prevented me from doing much with it, but while at the 
most recent SHARE in Fort Worth, I asked one of the DFSMS architects about it. 
She encouraged me to check out the CSI, specifically, fields UDATASIZ and 
COMUDSIZ. They appeared to satisfy my use case, although as others have 
mentioned there are a few restrictions especially for UDATASIZ. 

HTH, 
Mike  

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Farley, Peter x23353
Sent: Thursday, May 14, 2020 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Is there any z/OS API to get byte file size for non-VSAM, non-zFS, 
non-database files?

Caution! This message was sent from outside your organization.

This question came to me from a co-worker: Is there any API to get the byte 
file size of a non-VSAM, non-zFS, non-database file in z/OS?  I.E., byte file 
size for plain sequential files?

I am aware of the "old way" of reading the VTOC of a volume to get the various 
DSCB's that total up disk extents, but that gets complicated quickly for 
multi-volume files, and was never guaranteed to be accurate as to the actual 
byte count of data in the file except in the RECFM=FS/FBS case anyway.

There is always the performance-killing option of just reading the whole file 
and totaling up the length of every record (or block depending on how you 
structure the reads), but no one would call that an API.

As far as I know there is no such API in z/OS, and this is what I told my 
co-worker, but am I wrong?  Is there an alternative of which I am not aware?

TIA for your input.

Peter
--



This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

----------------------------------------------------------------------
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

Reply via email to