> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of willie bunter > Sent: Tuesday, September 13, 2016 9:01 AM > To: [email protected] > Subject: REASON: 3 - RECORD TYPE NOT RECOGNIZED > > Hi All, > > While running a DIAGNOSE on a USERCAT the following error was picked up: > > IDC21364I ERROR DETECTED BY DIAGNOSE: > ICFCAT ENTRY: 05:26:06.214 UTMOPB08: START TWRC MSGID(AFE7 (7) > RECORD: 05:26:06.214 UTMOPB08: START TWRC MSGID(AFE7 /F0 > OFFSET: X'0002' > REASON: 3 - RECORD TYPE NOT RECOGNIZED > IDC21365I ICFCAT RECORD DISPLAY: > RECORD: 05:26:06.214 UTMOPB08: START TWRC MSGID(AFE7 /F0 > > The programmer response (I hope I read it right) says > Use DELETE NOSCRATCH to remove the sphere or base record, if it exists. > > I have 2 questions: > Since the dsn is not listed in the job output after IDC21364i message I > assume that the dsn - > listed on side (cols 85 to 119) - > I assume that is the dsn in question. Please correct me if I am wrong. > > Is this problem serious or it can wait for action to be taken? The problem > was detected > about 10 days ago.
You have already waited ten days and not yet taken any action. Has there been any noticeable impact? If you run the DIAGNOSE again, do the results change? For better or worse? Were other activities that use the catalog running at the same time as your DIAGNOSE? When I was running EXAMINE jobs to confirm consistency between catalogs and VVDSs, I determined that some reported errors were transient and could be eliminated by executing the VERIFY command just prior to the EXAMINE. I don't know if the same issue could affect DIAGNOSE. If it is a permanent error, I would be more concerned with how it occurred and what to do to prevent it in the future. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
