Recently, I had a file transfer issue between z/VSE and z/OS because VSE
support block lengths of 32768 (true 32k) while z/OS only supports 32760
(32k-8).
Does anybody know (historically) why z/OS does not support a true 32K
block? z/VSE has supported it since "way back" in the DOS days.
Tony Thigpen
Bill Woodger wrote on 12/16/2016 07:01 AM:
32760 is the maximum blocksize. You have an LRECL of 32760, which is not at
least four bytes less than the maximum blocksize.
The RC for the message goes up steps of four, and is already busted. Other RC
values have multiple items. Some are not even inclusive, and probably can't be.
I think it is unrealistic to expect a separate RC for each possible combination
of something which is invalid.
You didn't get a 20, so something was more twisted than would be normal for
this type of error.
34 looks like a catch-all "you've done something 'illogical', you'd best fix it". You
could experiment and perhaps find other illogical things which cause a 34. The message-text could
perhaps have a main part which is more explicit, and the individual items listed as a
"possible explanations" without the implication that all possible causes are covered.
It is like trying to document the exact results of "undefined behaviour", and
keeping it up-to-date with each change to the software.
Now, what happens if you change your LRECL to 32752 at most? Does it "work"
(keeping your 32767 for BLKSIZE) and does it give you 32760 for the actual BLKSIZE, or
does it fail, and how?
With a V rather than VB, you can get to LRECL 32756.
So, you've broken three limits (BLKSIZE, LRECL for V, LRECL for VB), and you want a
specific RC and message for that, plus, implicitly, additional RCs and specific messages
for assorted combinations? I don't think anyone would find that worth the effort, or
possible for all "illogical combinations of parameters" possible.
----------------------------------------------------------------------
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
