Joined: 30 Nov 2013 Posts: 646 Location: The Universe
In order for anyone to evaluate this issue we need to see the job in its entirety. We do not need to see the job statement and you can mask out anything that's proprietary or confidential. We may need the JES2 JOB LOG data set for the failing job, with anything that is proprietary or confidential masked out.
I've been in this trade for more than 40 years. In all that time I've never heard of a U0061 ABEND in IEBGENER.
If, as you suspect, there is nothing on the tape you will most likely see some obscure Sx13 ABEND.
I am not aware of any "tape verify" utility as such. I am aware of a utility in CBT to analyze standard tape labels that could serve the purpose of a "tape verify" utility, and I can suggest other ideas after seeing the failing JCL, but that's about it.
IIRC depending on the DFSORT configurations options
dfsort and friends can abend or issue a message with the same number as the abend
For unsuccessful completion with ABEND in effect, DFSORT issues a user abend with the appropriate code as specified by the ABCODE installation option (either the error message number or a number between 1 and 99).
in this case - most probably - ICEGENER was substituted for IEBGENER
and the ICE0061A ( equivalent to the U0061 abend ) means that ..
I/O ERROR, DD ddname, DEV address, ECB completion code, CSW status bytes, SENSE sense bytes
Critical. This message was issued for one of the following reasons:
The job control statements incorrectly specified record length or blocking information for the data set located on the device indicated by the DEV field in the message.
A permanent error occurred during an I/O operation on the indicated device.
The most likely causes include:
The output data set of a merge, copy, or ICEGENER application is the same as one of the input data sets.
An output data set is the same as another output data set.