Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
How to catalog forgotten VSAM dataset
|
Hi all,
First of all, I am a complete NOOB related to an enormous list of things, at the top of the list are VSAM datasets a catalogs :( Long time ago I have installed KICS V1R5M0 in a DASD of an old installation of Tk? This virtual DASD got forgotten in a corner of my desktop system (Linux Xubuntu 22.04). Now I decided to connect this virtual DASD to my Tk5. There is no catalog in that DASD, at the time I just cataloged to the "default" catalog. (Is it the master?) 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. 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 Any simple example (for a NOOB) would be very much appreciated. 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? TIA 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! |
|
There should be a user catalog where they were created.? Export creates a backup with info to catalog in new catalog.? Import reads the backup and creates the catalog and dataset. On Wed, Apr 30, 2025 at 12:06?PM Fernando M. Roxo da Motta via <mvs=[email protected]> wrote:
--
Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? |
|
On Wed, 30 Apr 2025 13:13:45 -0500, "Mike Schwab via groups.io"
<Mike.A.Schwab@...> wrote: There should be a user catalog where they were created. ExportHi Mike, 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. Are those datasets named 'Z9999...' catalogs? If so, there is no such thin on that DASD. Thank you for your attention.
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! |
|
Hi Fernando,
?
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.
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.
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.
?
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) ? ?? ? ?? /* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
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
? |
|
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. Got it, I thin I will have to learn how to pla with them.Yes.? These Z9 datasets are either a master catalog, or a user 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 Still pursuing some education. :)That is correct.? Those VSAM datasets do not belong to your current 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? Ok, it seems that (at least) those VSAM datasets must go.When you originally created that dasd volume long ago, if you had 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. Thank you Bob, I thin that this would be the easiest approach. I will try this after reading a little about catalogs. 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! |
|
Hi Fernando,
?
You asked:
It's your choice.? These days it is pretty common to have one user catalog on each volume.? However, keep in mind that this is for production systems, with lots of batch jobs and many TSO users.? The user catalogs help keep the master catalog from being swamped.? In my own TK5 system, I do not do this.? Remember that for most of us, our TKx systems are single user systems - its just us.? There is no need to have a pile of user catalogs scattered all over.? Unless you just want to.
?
Also, please be aware that if you do create a user catalog on just one of the dasd out of many, then if you want to bring one of those dasd to another system, you will need to bring the dasd containing the user catalog as well, even if you dont really want or need that volume brought over.? That's one reason that putting a user catalog on each volume is not a bad idea.
?
You can name a user catalog whatever you want within the rules of dataset names, but a common practice is to name it as "CATALOG.volser", where volser is the name of your dasd volume.? That way, you just know the name of the user catalog, and you dont have to try to remember all of the different names.
The JCL that I provided should remove them all (all VSAM only).? You do not need to specify any names.
The proper nomenclature is "data component" and "index component".
Yes.? But it does get a little complicated.? Its easier if a batch job does the uncataloging and re-cataloging, because you can specify the catalog name to be used in the IDCAMS control statements, or, you can use IDCAMS with a STEPCAT DD to point to the user catalog (to uncatalog from), and another step with a STEPCAT DD to point to the new usercatalog to catalog them there.??
If you try to catalog them in TSO, using RFE or ISPF, the existing TSO user catalog is in the mix and so it complicates things.? When you previously cataloged datasets with RFE using "C", the catalog entries are most probably in the TSO user catalog.? If you want to get them in the user catalog that you create, you would need to uncatalog them from the TSO user catalog (use RFE again), and recatalog them to your new user catalog using a batch job with STEPCAT. ?
Keep in mind that if you put these datasets in a user catalog that you create, the system will not be able to locate any of these datasets by default, that is by just specifying DSN=file.dsn,DISP=SHR.? The system doesnt know what catalog to search and it will only look in the master catalog unless you direct it to the user catalog.? You direct it with a JOBCAT or STEPCAT DD statement naming the user catalog.? In every job that references those datasets.
?
To help mitigate the need for using JOBCAT/STEPCAT all the time, you can add ALIAS entries to the master catalog to automatically direct the system to search your user catalog.? You can set an alias for example to say that all datasets that begin with KICKS15 in the first qualifier to use the user catalog.? Then just be sure you name each dataset that way.? Of course, you can add additional aliases with other names pointing to the same user catalog or a different user catalog.? This helps cut down on the need for JOBCAT/STEPCAT.? Alias is described in the Access Method Services manual.
?
Regards,
Bob |
to navigate to use esc to dismiss