I usually do not use the CATALOG parm, but since this is your job, here is what 
I might code: 


DEFINE CL (NAME(VDB2U.DSNDBD.PENDBD10.PENTS113.I0001.A001)  -      
    VOLUMES(SMP116)  -  
     LINEAR    -                                               
     RCTLG)         -                                                  
     CATALOG('CHATT.UCAT')   



Lizette

-----Original Message-----
>From: John Dawes <[email protected]>
>Sent: Aug 28, 2012 4:31 PM
>To: [email protected]
>Subject: Re: HELP - RECATALOGING VSAM COMPONENTS
>
>Lizette,
> 
>Would you have an example using LINEAR?  
>
>
>________________________________
>From: Lizette Koehler <[email protected]>
>To: [email protected] 
>Sent: Tuesday, 28 August 2012 7:24 PM
>Subject: Re: HELP - RECATALOGING VSAM COMPONENTS
>
>John,
>
>I have not done this but I would catalog the DB2 Cluster Name with LINEAR in 
>the IDCAMS control cards.
>
>Lizette
>
>-----Original Message-----
>>From: John Dawes <[email protected]>
>>Sent: Aug 28, 2012 4:18 PM
>>To: [email protected]
>>Subject: Re: HELP - RECATALOGING VSAM COMPONENTS
>>
>>The cluster and the data component have a different names.  Do I need to 
>>recatalog the cluster too? 
>>
>>
>>
>>________________________________
>>From: Skip Robinson <[email protected]>
>>To: [email protected] 
>>Sent: Tuesday, 28 August 2012 7:13 PM
>>Subject: Re: HELP - RECATALOGING VSAM COMPONENTS
>>
>>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
>>[email protected]
>>
>>
>>
>>From:  Lizette Koehler <[email protected]>
>>To:    [email protected]
>>Date:  08/28/2012 04:01 PM
>>Subject:        Re: HELP - RECATALOGING VSAM COMPONENTS
>>Sent by:        IBM Mainframe Discussion List <[email protected]>
>>
>>
>>
>>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 <[email protected]>
>>>Sent: Aug 28, 2012 3:54 PM
>>>To: [email protected]
>>>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 [email protected] with the message: INFO IBM-MAIN

Reply via email to