Well everyone is right (or something close anyway).
The s0C4 could be something like trying to write a logrec record
(possibly an error occurred during the format of the new record or...
it could just about be anything without basic info its hard to say).
Ed
On Oct 17, 2013, at 10:58 PM, Jon Perryman wrote:
John is completely correct that you need to look at a dump. It
could be almost anything. Most programs have an expectation about
the data they read (e.g. specific record layout and specific
lengths). If the program ignores the I/O error and assumes the data
is valid, then you could have any type of error. Capture a dump
from the abend and determine which product is abending. The
hardware seems to be reporting a valid error. The software doesn't
abend with unrecoverable I/O error. Instead, it seems to continue
happily using the bad data.
Jon Perryman.
________________________________
From: John McKown <[email protected]>
I do _not_ know why your are getting these types of abends after a
tape I/O
error. My _guess_, without any kind of dump available, is that the
program
code is reading beyond the I/O area.
On Thu, Oct 17, 2013 at 9:05 AM, suresh chacko
<[email protected]> wrote:
In my shop we were using lots of tape jobs which are of 3490 old
VTS kind.
Currently migrating to IBM7700 VTL.
We experience lots of batch jobs failures from 3490 VTS followed by
equipment check 0C4 -11 or 4. These jobs are reading dataset
written on
multiple logical volumes. What I noticed the 0C4-11 will be occurred
immediately after an equipment check on VTS drive causing I/O error.
----------------------------------------------------------------------
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
