AFAIK, the abend for directory exhaustion is NOT x37. It is rather B14
or so.
BTW: yes, I know there are several x37 abends. That's why I used
lowercase 'x'.
BTW2: I even experienced F37 abend in the past. It was related to huge
(at the time) Jaguar J1A tapes and good compression and ...problems in
RMM. AFAIK I put over 6TB (terabytes) of uncompressed data on 300GB cart.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 24.10.2020 o 16:55, Joel C. Ewing pisze:
I'm not assuming any abend code outside the x37 family, just asking
which one.
x37 is not an actual abend code but a generic reference to family of
abend codes (A37, B37, D37, E37) relating to various out-of-space
conditions. For a PDS, you get a distinct E37 abend rather than a B37
or D37 when a space failure occurs when attempting to add a directory
entry.
Yes, the underlying root cause for a space failure in the directory is
different for a PDS vs a PDSE, and the problem resolution for a PDSE is
the same whether the no-free-block failure is for a directory-block or a
data-block; yet there are legitimate arguments for preserving an abend
distinction between the case where no member could be created vs the
possible creation of a member with incomplete data. The latter case is
potentially more dangerous, as an incomplete member is more likely to be
successfully read by a subsequent process and produce additional
incorrect results that must be resolved. Or does PDSE logic design
somehow preclude reading a PDSE member when an out-of-space condition
has prevented a proper close and writing of all data blocks during the
member creation?
JC Ewing
On 10/23/20 9:03 AM, R.S. wrote:
Why do you assume there is/should be other abend than x37?
Any request for new place in the dataset could end with such an abend.
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237,
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
01.01.2020 r. wynosi 169.401.468 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169.401.468 as at 1 January 2020.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
