Was the VSAM1 dataset successfully backed up after the last time it was
modified? If so, delete it, rebuild the catalog, and restore the backup to the
same volumes.
Can you do a LISTCAT of the individual dataset without error? If so, the
listing should contain enough information to support a DEFINE RECATALOG later.
If not, do you have access to the job that created the dataset originally (or
to the person/program)? If so, does that provide sufficient data for a DEFINE
RECATALOG? If you have sufficient data:
Perform a DELETE NOSCRATCH for the dataset. That will remove the catalog
entry.
Perform a REPRO MERGECAT for all the remaining datasets in the catalog.
The record with the error should not be accessed.
Fix all the aliases in the master catalog for the HLQs involved (including
VSAM1) to point to the new catalog
Perform a DEFINE RECATALOG for this dataset.
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of willie bunter
> Sent: Friday, September 16, 2016 10:36 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
>
> When I do the LISTCAT of the entire catalog it flags the dsn which was also
> flagged by the
> DIAGNOSE.
> The error message is
> IEC331I 028-002,LISTCAT ,STEP1 ,IGG0CLEG
> IEC331I SYS1.ICFCAT.UCATPROM
> IEC331I VSAM1.HARL.VVL000D.MASTERA.SNAP
> IEC332I GETO,GFL ,ICDV,ACD1
>
> The explanation is
> Permanent I/O error in catalog.
> Explanation: An I/O error processing the
> catalog occurred while processing an access
> method services command that requires
> modifying the catalog.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
