JCL utility to know Vol serial for uncatalogued Dataset

itzphaniz · New User Joined: 02 Sep 2005 Posts: 39

All-

Is there a JCL utility by which one can know the Volser for uncatalogued dataset? If not utility, is there any other way??
FYI, These uncatalogued datasets can be viewed using tape management system[TMSDSN]

expat · Posted: Mon Mar 26, 2007 3:00 pm

ADRDSSU - also known as DFSMSdss or DFdss - take a look at the manual to see dataset search criteria for DASD based datasets.

itzphaniz · New User Joined: 02 Sep 2005 Posts: 39

Xpat-
Is ADRDSSU a separate utility? Do we have to pass any PARM parameters to it?

expat · Posted: Mon Mar 26, 2007 3:46 pm

Here's a link to the manual.

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2U230/3.2.2?DT=20040624151438

dick scherrer · Posted: Mon Mar 26, 2007 9:38 pm

Hello,

From your post it is not clear that these are dasd datasets - are they?

Many (actually, most) sites have "clean-up" jobs that run periodically to automatically delete dasd datasets that are not cataloged.

In addition for the volser(s), you will want to determine what caused the dataset to be on the dasd and not in the catalog and take steps to prevent this in the future.

expat · Posted: Tue Mar 27, 2007 12:20 pm

dick scherrer · Posted: Tue Mar 27, 2007 7:46 pm

Hi expat,

Yup, that's why i asked if the file(s) were dasd.

If they are tape datasets, and may be seen in the tape management invenrtoy, i am confused about the question.

Maybe we will get some clarifying information. . .

expat · Posted: Tue Mar 27, 2007 7:53 pm

Yeah, but don't hold your breath

itzphaniz · New User Joined: 02 Sep 2005 Posts: 39

>>If they are tape datasets, and may be seen in the tape management invenrtoy, i am confused about the question

They are tape datasets(only not DASD) and can be viewed using TMS.. They cannot be seen using 3.4 option!

expat · Posted: Wed Mar 28, 2007 12:26 pm

And what's the problem with that.

The tape management software retains the last dataset name allocated to the tape even though it is in scratch status, replacing with a new dataset name the next time the tape is written to.

dick scherrer · Posted: Wed Mar 28, 2007 7:24 pm

Hello,

That is because 3.4 is catalog-driven.

If these are "good" files that are uncataloged, you will need to use the tape management reporting to prepare whatever info you need for the datasets that are being kept, but are not in the catalog. You wouldn't need an entire inventory list, just the dataset names that you are interested in.

Are these good files or have they expired and the volumes are now in scratch status? Or said differently, what do you need to use the information for? If we know what your requirement is, we can offer better suggestions.

itzphaniz · New User Joined: 02 Sep 2005 Posts: 39

We actually need to copy these tape files to DASD. The problem is, for Tape files which are viewable using 3.4 we are able to copy to DASD[with out mentioning VOLSER], but when the tape is not catalogued, we need to specify the Volser for the copying to happen, else we were getting error.
I hope i'm clear. Please let me know if you still have any doubts?

dick scherrer · Posted: Thu Mar 29, 2007 7:38 pm

Hello,

You are quite clear

From my perspective, you have 2 choices you can do on your own:

1) re-catalog the files.
2) run the copy jobs and include the volser(s) in the DD statements.

Either way, you will have to "mention" the volser somewhere - if you may need to do this multiple times, i'd suggest re-cataloging. Some sites make it harder to use uncataloged tapes. If yours does this, you will be ahead to re-catalog them. Keep in mind that you can re-catalog them without actually having a DD statement that allocates a physical derive.

You might also check with your tape management people and see if they have a preference and/or a suggestion. They may already have a something in place to (re)catalog existing tapes.

expat · Posted: Thu Mar 29, 2007 7:44 pm

And look out for multi volume datasets

itzphaniz · New User Joined: 02 Sep 2005 Posts: 39

>>Keep in mind that you can re-catalog them without actually having a DD statement that allocates a physical derive.

Could u elaborate on this please?
I don't think our TMS people are aware of "Re-catloging" existing tapes.

expat · Posted: Fri Mar 30, 2007 12:34 pm

It's an IDCAMS function.

BEWARE If you recatalog the tape you will need to ensure that the TMS is checked to see if there is an explicit expiry date allocated to teh tape. You may recatalog it, but the TMS will still kill it off at expiry date.

Why are these tapes uncatalogued - sort that out and your problem will go away. Prevent the problem rather than solve it.

itzphaniz · New User Joined: 02 Sep 2005 Posts: 39

expat thanks for the suggestion. Could help me out with the JCL please for this IDCAMS function. I'll checout the expiry date for the tapes.

Thanks~

expat · Posted: Fri Mar 30, 2007 2:20 pm

The JCL is simple

itzphaniz · New User Joined: 02 Sep 2005 Posts: 39

Xpat-
from the manual wat i get is that even for re-cataloguing we need to spcify the volser. But that is main problem. We just submit a job from a web interface. Based on the dates and various parameters chosen, we get a filename.[Now this is dynamic, coz the selection of dates and parameters may vary]. So for a specific combo we may find the Volser and run the IDCAMS step. But for the many to many kinda of mapping like ours, this may not be useful.. I hope i'm clear

expat · Posted: Fri Mar 30, 2007 3:09 pm

Yes, it's clear. Change the JCL from the web submitted job to catalog the tape and your problem is solved.

As for specifying the volser, yes you have to. All the catalog is, is a pointer to the volume and device type on which a datset resides. The OS goes to the catalog and if it can not find the dsn entry then the job will fail with dataset not found.

dick scherrer · Posted: Fri Mar 30, 2007 11:11 pm

Hello,

You can do what you need with IEHPROGM.

dick scherrer · Posted: Fri Mar 30, 2007 11:15 pm

Hello,

One more thing - mentioned above - if your dataset spans multiple volumes, include all of the volsers.