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. I ran several DIAGNOSE and the same dsn and attributes are displayed. I ran several EXAMINEs and NO ERRORS DETECTED. The parms I used for the EXAMINE are : ITEST NODATATEST ERRORLIMIT(1000) NOITEST DATATEST ERRORLIMIT(1000) INDEXTEST DATATEST I continue looking. -------------------------------------------- On Thu, 9/15/16, retired mainframer <retired-mainfra...@q.com> wrote: Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, September 15, 2016, 3:01 PM Told by whom? Since the error message says an I/O error occurred, it seems the offending record would be unreadable to any process. What happens if you LISTCAT the entire catalog? Do it in batch since TSO automatically changes the command if you don't specify an ENTRIES or LEVEL operand. (This will also give you a list of all the HLQs you will need for the MERGECAT.) If it comes back clean, then DIAGNOSE may be reporting a problem in a currently unused area. In that case, MERGECAT might not have any problem at all. If there is an error message, it might give more detail than DIAGNOSE did. If the daily EXPORT runs OK, it should be impossible for IMPORT to build a bad record. If anything is wrong with the exported data, I would expect IMPORT to either discard the offending record with a suitable info diagnostic (preferable) or abort the entire effort. EXAMINE is concerned with BCS/VVDS consistency. I don't think it cares that much about catalog structure. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, September 15, 2016 10:07 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED > > I was told that EXPORT/IMPORT would not fix the problem because it would export the > bad records only REPOR MERGECAT would work. > > I ran a LISTCAT on the dataset (as flagged by the DIAGNOSE) and it came clean. This > leads me to believe that it may not be the offending dsn. The dsn is on the volumes (3) > > The catalog is backed up via IDCAMS EXPORT daily successfully. > > I plan to run a VERIFY/EXAMINE (as recommended) and see what comes out. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
