View previous topic :: View next topic |
Author |
Message |
pvrajesh31 Beginner

Joined: 10 Aug 2004 Posts: 31 Topics: 11
|
Posted: Thu Oct 06, 2005 4:13 am Post subject: Error in renaming a VSAM dataset |
|
|
Hi,
I want to rename VSAM dataset.
I am using IDCAMS utility and following syntax to rename the VSAM datasets
//REPLACE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
ALTER OLD.DATASET.VSAM1 -
NEWNAME(NEW.DATASET.VSAM1)
ALTER OLD.DATASET.VSAM1.DATA -
NEWNAME(NEW.DATASET.VSAM1.DATA)
ALTER OLD.DATASET.VSAM1.INDEX -
NEWNAME(NEW.DATASET.VSAM1.INDEX)
But i am getting the following error.
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLE6-122
IDC0532I **ENTRY OLD.DATASET.VSAM1 NOT ALTERED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8
Is there any way to overcome this ?
Thanks in advance. _________________ Rajesh |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12380 Topics: 75 Location: San Jose
|
|
Back to top |
|
 |
pvrajesh31 Beginner

Joined: 10 Aug 2004 Posts: 31 Topics: 11
|
Posted: Thu Oct 06, 2005 5:16 am Post subject: |
|
|
Hi Kolusu,
Thanks for ur prompt reply.
In the link i could get the reason for the error but no solution for this.
It says 'The ALTER NEWNAME is not allowed for VSAM
data set when the new name resolves to a different
catalog than the current one.'
But is there any way that we can specify or control the volume into which new name resolves. Is there any syntax for this ? _________________ Rajesh |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12380 Topics: 75 Location: San Jose
|
|
Back to top |
|
 |
warp5 Intermediate

Joined: 02 Dec 2002 Posts: 429 Topics: 18 Location: Germany
|
Posted: Fri Oct 07, 2005 2:05 am Post subject: |
|
|
If you need to rename the dataset to a different high level qualifier(HLQ) and this is in a different catalog then you must copy the dataset, for example with adrdssu. This might be required anyway because the different HLQ's might also be using different disk pools along with the different catalogs. |
|
Back to top |
|
 |
|
|