Extended format (VSAM and non-VSAM)
Or
(Extended format VSAM) and (non-VSAM)
?
The former is redundant or overly wordy: why not just say "extended format
datasets"?
The latter, OTOH, seems implausible to me. Why would they do all non-VSAM
but only extended format VSAM?
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Seymour J Metz
Sent: Saturday, May 16, 2020 6:40 PM
To: [email protected]
Subject: Re: Is there any z/OS API to get byte file size for non-VSAM,
non-zFS, non-database files?
How do you parse "Restriction: This field is only valid for extended format
VSAM and non-VSAM data sets."?
Does that mean extended format VSAM and any format non-VSAM, or extended
format VSAM extended format non-VSAM?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Mike Hochee [[email protected]]
Sent: Saturday, May 16, 2020 1:31 AM
To: [email protected]
Subject: Re: Is there any z/OS API to get byte file size for non-VSAM,
non-zFS, non-database files?
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:[email protected]] On
Behalf Of Farley, Peter x23353
Sent: Thursday, May 14, 2020 11:55 AM
To: [email protected]
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 [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
