How to catalog an uncataloged dataset

trgk03 · New User Joined: 20 Jan 2006 Posts: 12 Location: kochi

Hi All,

How can i catalog an uncataloged dataset ? One of the GDG has been uncataloged and we want it back.
Is there any utility/job for this ? Request for help on this.

Regards
S D

murmohk1 · Posted: Tue Nov 27, 2007 3:53 pm

S D,

If you know the volume, you can do it from 3.2 screen.

gcicchet · Posted: Wed Nov 28, 2007 7:58 am

Hi Murali,
you are making the assumption that the dataset is on disk and is still available, that would not work too well if the dataset is on tape/cart
and would also need to know the label number.

Gerry

murmohk1 · Posted: Wed Nov 28, 2007 8:51 am

Gerry,

expat · Posted: Thu Nov 29, 2007 12:55 am

gcicchet · Posted: Thu Nov 29, 2007 4:37 am

Hi,

I don't understand waht you mean by "Only in the case of a multi dataset volume though".

I still can't see how you would catalog a tape/cart via 3.2

Gerry

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1592

You can try IEFBR14 w/DISP=(OLD,CATLG) and VOL=SER=xxxxxx and UNIT=SYSDA.

If it's a tape code UNIT=(TAPE,,DEFER). Check w/librarian if you use a TMS.

PS UNIT names may differ in your shop.

expat · Posted: Thu Nov 29, 2007 11:49 pm

You only need to know the label number for a multi dataset volume, i.e. a tape that has more than one dataset catalogued to it, because if one tape has only one dataset then the default is label 1.

However, it might be nice if the OP came back to us at some stage.

trgk03 · New User Joined: 20 Jan 2006 Posts: 12 Location: kochi

I got the JCL to catalog an uncataloged dataset and it works;;

//SRA4621C JOB (DUPB0000000,NM),
// 'CATALOG DATASET',
// MSGCLASS=J,
// CLASS=Y,
// USER=USERNAME
//*
//**************JOB OVERVIEW********************
//* PURPOSE: CATALOG AN UNCATALOGED DATASET
//*
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE NVSAM -
(NAME(XXX.YYY.B.DAILY.ABC.G3045V00) -
VOLUMES(PX3821) -
DEVT(3490))
/*

dinesh_deadman · New User Joined: 10 Aug 2007 Posts: 32 Location: Chicago

Hello:

I am trying to catalog an uncataloged data set that was created in the prior job (JOB A) - it is a flat file. Here is how it was defined.

//DATA DD DISP=(NEW,CATLG,DELETE),
// DSN=XXXDASD.YY.XXXXXXX.D126,
// UNIT=(SYSDA,01),VOL=REF=DEV.XXXXXXX.DISK,
// SPACE=(CYL,(20,10),RLSE)

This is just an fyi, infact in the same job 5 other files were also created and all with the same definition.

Once the job (prior one - JOB A) ended, I checked to see the output in the spool and there I found that this specific file wasn't cataloged. Here is the message.

IEF287I XXXDASD.YY.XXXXXXX.D126 NOT CATLGD 2

As some people have already suggested in this post, I tried 3.2 and also IDCAMS. Nothing seems to work.

Strangely, when I try to check in 3.4, it does appear but when I browse it, it fails and throws an error message - DATASET NOT FOUND.

Can somebody help me here please?

Dinesh

Robert Sample · Posted: Thu Oct 29, 2009 12:12 am

The NOT CATLGD 2 message means the data set was not cataloged because there is an identical entry already in the catalog. In ISPF 3.4, you can put a slash (/) beside the data set name, then use option 11 to uncatalog it. You can then go to the volume the data set was created on in your job (the job output will give you the volume serial) and catalog that data set by putting a slash then using option 10.

dick scherrer · Posted: Thu Oct 29, 2009 12:36 am

Hello,

Before getting too frisky mucking about with catalog entries, you need to make sure of what you have.

What is the content of the already cataloged dataset? Is it still valuable?

Once you decide what is to be done and correct the current situation, you also need to correct the process to delete the dataset in a timely manner (i.e. before the next cycle is run). Many processes do "housekeeping" at the beginning and/or the end of a run to make sure this does not happen.

dinesh_deadman · New User Joined: 10 Aug 2007 Posts: 32 Location: Chicago

Hello:

Robert Sample -> I tried to see what datasets are on that specific Volume, and it appears that this one isn't there.

Dick Scherrer -> The data in this dataset isn't all that important and more over it is in test region.

Thanks to you both for providing the potential solutions.

I renamed the output dataset in JOB A and reran that step alone and the new one that's created looks good.

Thanks again.

Dinesh

Robert Sample · Posted: Thu Oct 29, 2009 1:17 am

Are the data sets under SMS control? If so, you have to check the job output to see what specific volume was used for that run since SMS will ignore your volume specification and use any volume in the storage pool that it considers a candidate volume. Looking on the one volume you think it is on may be incorrect if SMS is involved.