MVSFORUMS.com

[LaluMon]

Hello,

We are having a large number of VSAM datasets in one hlq, say,
PRSCRPB.****. Now we are getting away with PRSCRPB, and we need to rename all datasets with PRSCRPB to a new hlq, BJ22AO.***.

I used IDCAMS and ALTER & NEWNAME parameters. No problems with QSAM files. All qsams with PRSCRPB is renamed properly to BJ22AO.
But VSAMs are giving 'CATALOG Error'. Seems PRSCRPB is in one catalog and BJ22AO in another catalog. I have more than 1000 datasets to be renamed, every vsam has index and data too !

Is there a easy way to do the mass rename overcoming the catalog error?

Lalu!

[kolusu]

Lalumon,

Try this

[LaluMon]

Kolusu,

I dont think the solution is working for me! I gave:

ALTER PRSCRPB.DEV.OUTPUT.DTYR.**.* -
NEWNAME ( BJ22AO.DEV.OUTPUT.DTYR.**.* ) -
CATALOG (SYS1.CATALOG.VCAT031)

The catalog name is that of the prscrpb qualifier dataset.

I am getting IDC3203I error stating:

IDC3203I ITEM 'PRSCRPB.DEV.OUTPUT.DT' DOES NOT ADHERE TO RESTRICTIONS

and the job ends with RC=12.


When I used one particular dataset alone, (PRSCRPB.DEV.OUTPUT.DTYR.FINS.VSAM) using,


ALTER PRSCRPB.DEV.OUTPUT.DTYR.FINS.* -
NEWNAME ( BJ22AO.DEV.OUTPUT.DTYR.FINS.* ) -
CATALOG (SYS1.CATALOG.VCAT031)

I got RC=8 and the messages,
IDC2054I - INVALID AUTHORIZATION TO EXECUTE FUNCTION
IDC3009I - **VSAM CATALOG RETURN CODE IS 190 - REASON CODE IS IGG0CLFT - 2


If this error is due to RACF, I can get permissions soon ! But I dont want to be doing renaming each dataset individually. I want to rename a whole list of datasets (> 1000) with the pattern:

PRSCRPB.DEV.OUTPUT.DTYR.**

Hope there is an easier way to do this!

[bablack]

Lalu, I presume that you want the renamed datasets in the new catalog (for BJ220A0). The IDCAMS manual, under the NEWNAME parm of ALTER says
" You might not be able to rename a data set if you are changing the
high-level qualifiers of the data set's name and those qualifiers are
an alias name of a catalog. (The number of high-level qualifiers used
to form an alias can be one to four, depending on the multilevel alias
search level used at your installation.)

If you are changing a high-level qualifier, NEWNAME acts differently
depending on whether the data set being renamed is SMS-managed or
non-SMS-managed, and whether the data set has aliases or not. Figure 5
shows how NEWNAME resolves under different conditions. "

Then table 5 says, for SMS VSAM, you can't do it. For non-SMS VSAM, you can rename it but it will be in the wrong catalog, where it is probably not usable. Since you got errors, I presume these were SMS.

I think your only choice is to back up the clusters, delete them, then restore them with the new names.

BTW, the
IDC3009I - **VSAM CATALOG RETURN CODE IS 190 - REASON CODE IS IGG0CLFT - 2
error is a directed catalog error, you are not authorized to specify a catalog name.[/img]
_________________
Bruce A. Black
Senior Software Developer
Innovation Data Processing

[LaluMon]

Thanks Bablack for providing the information.

I wrote a small rexx, which will gather all the dataset names and produce jcls to define cluster and repro to the new qualifier.

It worked. Thanks kolusu too for trying to provide the solution.

LaluMon

[coolman]

Lalumon,
Was just going through the earlier posts...You said about cluster definitions, but were all the files that you had created clusters for had the same RECORDSIZE, KEY and other parameters..

Cheers,
Coolman.
________
buy herbalaire