S613: Tape label or positioning error at OPEN

What it means

A standard-labeled tape starts with a volume label, and each data set on it has header and trailer labels around the data. When a program opens a tape data set, OPEN positions the tape at the right file and reads the header labels, or writes new ones for output. If that fails, OPEN issues message IEC147I and ends the step with system completion code 613.

The return code after the dash tells you which part failed.

• 613-04 means an I/O error while positioning the tape, or an installation exit rejected the volume.
• 613-08 means an I/O error while reading a tape label.
• 613-0C means OPEN read a label that wasn't right. The wrong volume may be mounted, the tape may not have standard labels, or an earlier abend in the step may have left it at the wrong position.
• 613-10 and 613-14 mean an I/O error while writing a label, or while writing the tape mark after the header labels. On encrypting drives this can be a key manager failure, so check the system log as well.
• 613-24 means a tape library volume opened for output is file protected.
• 613-54 means the internal volume serial of a private tape library cartridge couldn't be read, or the volume was never initialized.
• 613-64 means a 3590 cartridge hasn't been formatted. 613-80 means a program tried to overwrite data on a WORM cartridge.

Many more return codes cover automated tape libraries and the tape configuration database. IEC147I in IBM's MVS System Messages lists them for your release.

Common causes

• The wrong tape was mounted, or the tape's labels don't match the LABEL parameter on the DD statement, for example an unlabeled tape read as SL (613-0C).
• An earlier abend in the same step left the tape part way through a file, so the next OPEN read data where it expected a label (613-0C).
• A worn or damaged tape, or a dirty or failing drive, caused an I/O error while positioning or reading labels (613-04, 613-08).
• A new tape was never initialized with a volume label before use (613-0C, or 613-54 in a tape library).
• On an encrypting drive, the drive couldn't get a key from the key manager while writing labels (613-10, 613-14).
• The cartridge is write protected, is WORM media, isn't formatted, or isn't supported by the drive (613-24, 613-64, 613-80, 613-84).

How to find the problem

1. Find IEC147I in the job log. It has the form IEC147I 613-rc,mod,jobname,stepname,ddname,dev,volser,dsname. Note the return code, the device number and the volume serial.
2. Look at the messages just before it in the job log and the system log. Mount messages and IEC705I tape-on messages show which drive and volume were used, and IOS000I shows a hardware error.
3. Check the DD statement's LABEL parameter (SL, NL, AL or BLP) and file sequence number against what's really on the tape. Your tape management system (DFSMSrmm, CA 1 or similar) shows what the volume should hold.
4. If the error follows the volume across drives, suspect the tape. If it stays with one drive, suspect the drive.

How to fix it

• For 613-0C, make sure the right volume is mounted and that LABEL matches the tape. If an earlier abend caused it, fix that error first and let the tape be unloaded and mounted again.
• For I/O errors, rerun on another drive. If the error repeats there, copy what you can from the tape and retire it.
• Initialize new tapes with a standard volume label before using them for labeled output.
• For 613-10 and 613-14 on encrypting drives, have the storage team check the key manager connection and the system log.
• For library and media codes such as 24, 54, 64 and 80, have the storage team check the cartridge and its library record before you rerun.

What it looks like

IEC147I 613-0C,IFG0195B,PAYRUN01,STEP030,TAPEIN,0B41,PR4417,PROD.PAYROLL.HIST
IEA995I SYMPTOM DUMP OUTPUT
  SYSTEM COMPLETION CODE=613  REASON CODE=0000000C
IEF450I PAYRUN01 STEP030 - ABEND=S613 U0000 REASON=0000000C

Technical reviewer: Albert Joseph, WND Software.

Last reviewed 2026-10-18 by the WND Software team. Written in our own words. For the full reference, check IBM’s z/OS documentation for your release.