Paul Schuster wrote on 11/24/2022 11:13 PM:
TRKCALC knows everything.
Second best, I dug up this exec from the 1990s that should get it right:
/* Rexx */
Parse Arg kl dl .
"XPROC 2 KL DL DEBUG"
If dl = "" Then Do
Say "Usage: BLK3390 keylen datalen [DEBUG]"
Exit 2
End
c = 10
If kl = 0
TRKCALC knows everything.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
i was just getting ready to say this same thing.
The 3390 reference shows that for a 3120 byte block, only 15 blocks fit on
a track, with a 16% space waste.
Your best bet is to use TRKCALC...
https://www.ibm.com/docs/en/zos/2.4.0?topic=instructions-performing-track-calculations-trkcalc-macro
Subtracting the logical blocksize from either of those capacity numbers
as you describe will not give correct results for blocks per track. The
only accurate way to determine how many blocks will fit on a 3390 track
is to use the formulas from the 3390 Reference Summary (mentioned in
previous
You're missing an allowance for an inter-block gap.
On Thu, 24 Nov 2022 at 16:14, John Gateley wrote:
> The reason for asking the question about bytes on a track is that I am
> writing programs to report on all disk datasets.
> The first program looks at all on-line disk packs and extracts all
The reason for asking the question about bytes on a track is that I am writing
programs to report on all disk datasets.
The first program looks at all on-line disk packs and extracts all format 1, 3,
8 and 9 DSCBs while also providing a summary of space available/used on each
disk (similar to
