The 237-04 is due to the count of blocks actually read not matching the
number that was in the trailer label. The error likely happened at the
time the tape dataset was created. Possibilities:
The tape drive said it wrote a block but it lied (I haven't seen this in a
very long time).
Tape was overwritten (accidentally or deliberately)
The tape was created on a non-zOS system and the trailer label contents
weren't correct.
If you BLP (bypass label processing), then the system won't compare the
number of blocks actually read to the number in the trailer label (because
it bypasses label processing).
Successfully reading the tape using BLP means that all of the data blocks
on the tape were read successfully. But blocks that were supposed to be
written to the tape but weren't were not read. Of course, I'm only
guessing that the block count in the trailer label is larger than the count
of blocks actually read.
Tom
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"R.S."
<[EMAIL PROTECTED]
LTIBANK.COM.PL> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> S237-04 and tapes
10/25/2006 12:38
PM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
I observed an abend S237-04, when reading dataset from tape (using
IEBGENER).
The manual says it is due to discrepancy between # of blocks read and
the value written to EOF label.
The manual also suggests it can be hardware error.
Well... The drive looks OK - only one tape is affected, the media looks
OK (i.e. can be read using BLP).
Q: What component to suspect ?
drive ?
system ?
application ?
Any clue ?
Regards
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
