/16/16, retired mainframer <retired-mainfra...@q.com> wrote:
Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Friday, September 16, 2016, 3:08 PM
Was the VSAM1 dataset
successfully backed up after the last time it was
modified? If so,
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
>
&g
I looked at that option but the bad record(s) will be moved as well.
On Fri, 9/16/16, Mike Schwab <mike.a.sch...@gmail.com> wrote:
Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Friday, September 16
fra...@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.
s will not work.
>
>
> On Thu, 9/15/16, Gibney, Dave <gib...@wsu.edu> wrote:
>
> Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
> To: IBM-MAIN@LISTSERV.UA.EDU
> Received: Thursday, September 15, 2016, 3:25 PM
>
> Well, try to IMPORT the
>
, Dave <gib...@wsu.edu> wrote:
Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Thursday, September 15, 2016, 3:25 PM
Well, try to IMPORT the
back-up on a test system or different name and see what
happens.
> -Original
Message-
&g
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
&
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) an
TSERV.UA.EDU]
On
> Behalf Of willie bunter
> Sent: Wednesday, September 14, 2016 4:33
AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REASON: 3 - RECORD TYPE NOT
RECOGNIZED
>
> The
DIAGNOSE gives the same error and no change. I ran examine
(using the following
>
t; To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
>
> I would probably open an SR with IBM on DFSMS VSAM - any actions taken
> might require their assistance to recover. Better to have them look and help
> provide the right guidance.
>
> Liz
UA.EDU] On
> Behalf Of willie bunter
> Sent: Wednesday, September 14, 2016 4:33 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
>
> The DIAGNOSE gives the same error and no change. I ran examine (using the
> following parms) and " NO
SERV.UA.EDU
> Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
>
> The DIAGNOSE gives the same error and no change. I ran examine (using the
> following
> parms) and " NO ERRORS DETECTED"
>
> INDEXTEST DATATEST
> ITEST NODATATEST ERRORLIMIT(1000)
> NO
his subject.
Thanks.
On Tue, 9/13/16, retired mainframer <retired-mainfra...@q.com> wrote:
Subject: Re: REASON: 3 - RECORD TYPE NOT RECOGNIZED
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Tuesday, September 13, 2016, 1:01 PM
> -Original
Messag
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of willie bunter
> Sent: Tuesday, September 13, 2016 9:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: REASON: 3 - RECORD TYPE NOT RECOGNIZED
>
> Hi All,
>
'
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
15 matches
Mail list logo
