IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

TAPE VERIFY utility??


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
MrExtraordinare

New User


Joined: 11 Feb 2010
Posts: 4
Location: USA

PostPosted: Fri Dec 09, 2016 10:57 pm
Reply with quote

It's been so long since I've worked with IBM mainframe tapes. When I run a IEBGENER to copy a tape to DASD, I'm getting U0061 error. It seems that the input tape might be empty but am not for sure.

Isn't there a TAPE VERIFY utility that I can include in my JCL to verify whether if the tape has data or not? I thought there was a utility but my memory failed me.

Any info you could share would be appreciated or point me in the right direction because Google Search apparently failed me.

Thanks!
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 917
Location: The Universe

PostPosted: Sat Dec 10, 2016 12:00 am
Reply with quote

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.
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10872
Location: italy

PostPosted: Sat Dec 10, 2016 3:12 am
Reply with quote

BEWARE ... BEST EFFORT AT GUESSING

IIRC depending on the DFSORT configurations options
dfsort and friends can abend or issue a message with the same number as the abend

Quote:
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 ..

Quote:
ICE061A
I/O ERROR, DD ddname, DEV address, ECB completion code, CSW status bytes, SENSE sense bytes
Explanation

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.
Hardware-related error.

Back to top
View user's profile Send private message
don.leahy

Active Member


Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada

PostPosted: Sat Dec 10, 2016 9:12 pm
Reply with quote

Another guess: the abend could be coming from the tape management system that might be installed at your shop.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts REASON 00D70014 in load utility DB2 6
No new posts Deleting a Tape file JCL & VSAM 14
No new posts ISRSUPC search utility - using high l... TSO/ISPF 2
No new posts Any JCL or VSAM Utility to get number... JCL & VSAM 1
No new posts JCL and TAPE drives: how to maximize ... JCL & VSAM 9
Search our Forums:

Back to Top