On Wed, 30 Apr 2025 16:29:35 -0700, "Bob Polmanter"
<wably@...> wrote:
Hi Fernando,
Hi Bob,
Ok, I thin I too a first step to understand all this, but with a long
way to go.
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.
Got it, I thin I will have to learn how to pla with them.
Just in order to educate me, if I have a set of "personal DASDS",
should I have one catalog on each one, or just one catalog in one of
the DASD will be enough?
===========8<------------- very clear and educational text clipped
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)
/*
Still pursuing some education. :)
On that DASD, counting the "*.index" names, I have seven VSAM
datasets/clusters/????? with the "*.data" companion (what would be the
correct nomenclature?), no one of them cataloged. In the JCL above,
will it erase all datasets? (VSAM and nonVSAM) Should some kind of DSN
be coded somewhere?
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.
Ok, it seems that (at least) those VSAM datasets must go.
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.
Going after education.
For nonVSAM datasets, if I have DASD already populated, if I
uncatalog the datasets, is it possible to create a user catalog and
recatalog those datasets there? Or, if possible, may I create a
catalog and redirect those datasets to the new catalog? What would be
the easiest approach.
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).
Thank you Bob, I thin that this would be the easiest approach. I
will try this after reading a little about catalogs.
Regards,
Bob
Best regards.
Roxo
--
---------------- Non luctari, ludare -------------------+ WYSIWYG
Fernando M. Roxo da Motta <mvs@...> | Editor?
Except where explicitly stated I speak on my own behalf.| VI !!
PU5RXO | PX5Q6048 | I see text,
------------ Quis custodiet ipsos custodes?-------------+ I get text!
