Hi Fernando,
?
? I created the DASD using 'dasdload' and have never created a
catalog, user or otherwise, in that DASD. ? ?I have only (blindly)
followed the instructions to install from a XMI, and everything got
cataloged at the time. ? Where? ? I don't know. ?As said, I am a
complete NOOB.
If you didn't create a catalog, and I am sure you did not, then these datasets were cataloged either in the master catalog of that old TKx system, or in the TSO user catalog, depending on how that system was set up.
? Are those datasets named 'Z9999...' catalogs? ? ?If so, there is no
such thin on that DASD.
Yes.? These Z9 datasets are either a master catalog, or a user catalog, or a VSAM space.? A space is used to contain one or more VSAM cluster datasets.? One or more of these Z9 datasets could be present on any volume.
? When I open the content of that DASD in RFE DSLIST all the
datasets are uncatalogued. ? I can use the "C" selection code to
catalog the datasets. ? Except for the VSAM datasets, I succeed to
catalog all non VSAM datasets.
This is pretty normal.? It is easy to catalog non-VSAM datasets as you have seen.? But for the most part, VSAM datasets are cataloged using IDCAMS when they are created, or imported (bringing a VSAM file over from other system).
?
You can't recatalog VSAM datasets that are "orphaned" on a dasd volume.? Orphaned meaning, a VSAM cluster that exists on the volume but is not a member of any catalog on the active system.? This would occur in a situation like yours, where you bring a volume over from some other system.
?
This is because VSAM datasets do not contain the information contained in the catalog record. For example the characteristics of the dataset, the CI size, the key position, and any number of other parameters are in the catalog record.? Without the catalog, VSAM has no way to know what characteristics this orphaned VSAM dataset has.? It wont let you catalog it for that reason.
?
? I am not allowed, by the system, to do anything to those VSAM
datasets. ? So, if possible, I would like to as for a set of JCL
examples that would allow me to:
? 1- ?Catalog those uncatalogued ones
? 2- ?Delete a VSAM dataset
?
That is correct.? Those VSAM datasets do not belong to your current system so you cant do anything with them.? You cannot catalog them.? And deleting them can be done, but sometimes can be a challenge.
?
The JCL to delete abandoned orphaned VSAM datasets on a volume that you brought from an outside system is here:
?
//HERC01D ?JOB 1,DELETEVOL,CLASS=A ? ? ? ? ? ? ? ? ?
//* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
//* USE THIS JOB TO REMOVE ALL VSAM CLUSTERS, SPACES, ETC FROM A ? ? ?
//* VOLUME THAT YOU ARE BRINGING INTO THE SYSTEM. ?THAT IS, NONE ? ? ?
//* OF THE VSAM ENTITIES ON THE VOLUME ARE IN THE MASTER CATALOG AND ?
//* SO THEY CANT BE DELETED THE CONVENTIONAL WAY. ?THIS JOB WILL ? ? ?
//* GET RID OF ALL VSAM ON THE VOLUME AND NOT AFFECT ANY ENTRIES WITH?
//* THE SAME NAMES IN THE MASTER CATALOG OR ON OTHER VOLUMES. ? ? ? ??
//* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
//STEP1? ? EXEC PGM=IDCAMS ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
//DD1 ? ? DD VOL=SER=123456, ? ? ? ? ? ? ? ? ? ? ?? <= your volume serial name here and below
// ? ? ? ? ? ?UNIT=SYSDA, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
// ? ? ? ? ? ?DISP=SHR ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
//SYSPRINT DD SYSOUT=* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
//SYSIN ? ?DD * ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
?ALTER SYS1.VMASTCAT ?FILE(DD1) ? ? ? REMOVEVOLUMES(123456) ? ?? ? ??
/* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
?
? BTW, would it be easier if I have created a catalog on that DASD?
Would it be possible to create it now, or does it have to be done
on a empty DASD? ? Any direction on the subject?
When you originally created that dasd volume long ago, if you had created a VSAM user catalog on that same volume, and then as you installed KICKS, if you had used STEPCAT DD or other means to cause those VSAM datasets that were created as part of the install to be cataloged into that user catalog, then you would be good to go.? Because then, you could mount that volume on your current system and use IDCAMS to issue an IMPORT CONNECT to cause that user catalog to be recognized by your current master catalog and become part of your system.? Then you could access everything and control everything on that volume.
?
You could create a user catalog on that volume now, but it wont do you any good, because the VSAM datasets are already created (as a part of the KICKS install), so they would not be cataloged in your new user catalog, and as previously stated, you can't catalog previously orphaned VSAM datasets.
?
As I see it, you have two options:
1. completely reinstall KICKS on a new volume, this time creating a user catalog on that volume (first, before KICKS) and directing the install JCL to catalog new datasets into it (either using JOBCAT/STEPCAT DDs, or IDCAMS steps in the JCL to designate the catalog to be used).
2. if you can bring up your old system you were using when the VSAM datasets were created, you could EXPORT those VSAM datasets to a tape or sequential dataset, and IMPORT them onto your new system.? One at a time.? Hopefully there is not too many of them.? I don't have JCL for export and import handy, sorry, but they are documented in the Access Method Services manual.? I personally have found export and import to be moody and difficult to use (to get everything just so, so they will work correctly).
?
There is a third option potentially where you could import connect your old master or TSO catalog into your current system, but it is complicated and in the end you still have to use export/import.? But it would only be useful if you cannot bring up the old system any longer or you dont have it.? I think option 1 would be the easiest.
?
Regards,
Bob
?
