The most common problem with VSAM is failing to specify the proper value
for indexed/nonindexed. It must match the actual cluster.
.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: Lizette Koehler <stars...@mindspring.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 08/28/2012 04:01 PM
Subject: Re: HELP - RECATALOGING VSAM COMPONENTS
Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Did you look up the IDC3009I message
6 Explanation: Either the primary VSAM volume record
(VVR) points to another catalog, or the primary VVR or
non-VSAM volume record (NVR) for the object being
recataloged was not found on the first volume serial
number specified. The primary VVR or NVR contains the
data set information needed to recatalog the object.
Possible causes of this error are:
o No VVR exists.
o A VVR exists, but it points to another catalog.
o Parameters were not specified as they were when
the cluster was originally defined. The parameters
are NAME, INDEXED, LINEAR, NONINDEXED, NUMBERED,
and VOLUMES.
Programmer Response:
If no VVR exists, then re-issue the DEFINE command,
without the RECATALOG parameter, for the ICF catalog.
If the VVR exists but points to a different catalog,
specify the correct catalog and re-issue the DEFINE
command with the RECATALOG parameter.
If the original values for parameters NAME, INDEXED,
LINEAR, NONINDEXED, NUMBERED, and VOLUMES were not
specified, specify the original values and re-issue
the DEFINE command with the RECATALOG parameter.
Have you tried adding LINEAR? Or is it the correct catalog (I tend to not
include a catalog)?
Lizette
-----Original Message-----
>From: John Dawes <jhn_da...@yahoo.com.au>
>Sent: Aug 28, 2012 3:54 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: HELP - RECATALOGING VSAM COMPONENTS
>
>G'Day,
>
>I restored a DB2 VSAM dsn (which was deleted in error) on to the volume
which it used to reside on. The restore was from a full volume dump. All
went well however it didn't catalog the CLUSTER & COMPONENT:
>
>2012.241 17:51:51 EXECUTION
BEGINS
>THE INPUT DUMP DATA SET BEING PROCESSED IS IN FULL VOLUME FORMAT AND WAS
CREATED BY DFSMSDSS VERSION 1
>RELEASE 13 MODIFICATION LEVEL 0 ON 2012.231
05:41:01
>DATA SET CLUSTER VDB2U.DSNDBC.PENDBD10.PENTS113.I0001.A001
COMPONENT
>VDB2U.DSNDBD.PENDBD10.PENTS113.I0001.A001 ALLOCATED, ON VOLUME(S):
SMP116
>THE FOLLOWING COMPONENTS FOR CLUSTER
VDB2U.DSNDBC.PENDBD10.PENTS113.I0001.A001 ON SMP116 MAY HAVE TO BE
>CATALOGED IN CATALOG
CHATT.UCAT
> COMPONENT
VDB2U.DSNDBD.PENDBD10.PENTS113.I0001.A001
>THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED FROM VOLUME
SMP116
> VDB2U.DSNDBC.PENDBD10.PENTS113.I0001.A001
VDB2U.DSNDBD.PENDBD10.PENTS113.I0
>2012.241 17:52:50 EXECUTION
ENDS
>2012.241 17:52:50 TASK COMPLETED WITH RETURN CODE
0000
>
>I tried the following to catalog the component:
>
> DEFINE CL (NAME(VDB2U.DSNDBD.PENDBD10.PENTS113.I0001.A001) -
> VOLUMES(SMP116) -
> RCTLG) -
> CATALOG('CHATT.UCAT')
>IDC3014I CATALOG ERROR
>IDC3009I ** VSAM CATALOG RETURN CODE IS 86 - REASON CODE IS IGG0CLEY-6
>IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
>
>IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12
>
>Could someone suggest something that I could try?
>
>Thanks.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
