IEC149I: 813 abend, tape label data set name mismatch

What it means

A tape with standard labels has a header label in front of each data set on it. The header label records the data set name. When a program opens a tape data set, z/OS reads that label and compares the name in it with the name in the job file control block (JFCB), which comes from the DSN on the DD statement. If they don't match, z/OS writes IEC149I and ends the step with abend 813 and return code 04.

A standard tape label only has room for 17 characters of the data set name. It stores the last 17 characters, and that is what gets compared. So two names that end in the same 17 characters look the same to this check, and a name that differs only in its first qualifiers still matches.

The message gives the abend and return code, the module that called the routine that issued it, the job name, step name and DD name, the device number, the volume serial and the data set name from the JCL. At the end, after LBL=, it shows the data set name actually found in the tape label. That last field usually tells you straight away what went wrong.

The step ends unless a DCB abend exit ignores or recovers the error. IEF450I follows with ABEND=S813 and REASON=00000004.

Common causes

• The DD statement names the wrong volume serial, so z/OS mounted a tape that holds a different data set.
• The DSN on the DD statement is misspelled or uses the wrong generation or date qualifier.
• LABEL=(n) points at the wrong file on a multifile tape, so the header found belongs to another data set.
• The first file on the tape was never written. The tape holds only a volume label and a dummy header, for example a scratch tape given by mistake.
• A program changed the JFCB before the open and put the wrong name in it.

How to find the problem

1. In SDSF, open JESYSMSG and find IEC149I. Compare the data set name from the JCL with the name after LBL=. Remember that only the last 17 characters count.
2. Check the volume serial in the message against the volume your catalog or tape management system holds for that data set, with LISTCAT ENTRIES('PROD.PAYROLL.ARCHIVE') VOLUME.
3. If the DD statement codes VOL=SER or LABEL, check both against the catalog or tape inventory.
4. If LBL= doesn't show a real data set name, the tape may have no data set written on it. Ask operations whether it is a scratch tape.

How to fix it

• Correct the DSN, the volume serial or the LABEL file number on the DD statement.
• For a cataloged data set, remove VOL=SER from the DD statement and let the catalog supply the right volume.
• If the tape is empty, find the job that should have written it and rerun that job first.
• If a program builds the JFCB itself, check the code that sets the data set name.

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