Duplicate Dataset



Ask about System customization & performance, Workload management, I/O device configuration etc.

Duplicate Dataset

Postby v1gnesh » Wed Feb 22, 2012 12:58 am

Hi!

I'm facing quite a peculiar situation. Please let me know what other information you need to help me figure out this problem.

There are these 3 datasets, ( HLQ changed throughout the post )
ABCDE.JHH.DUMP.PROD
ABCDE.JDH.DUMP.PROD
ABCDE.JHS.DUMP.PROD

First step of job deletes these dsn via IEFBR14 with disp=mod,delete,delete. These 3 datasets were created by the same job with disp=new,catlg,catlg in the second step. The job failed on E37 on the second step. When I reran job, first step ran OK ( meaning, the datasets were deleted ) but 2nd step failed because “duplicate dsn on Vols TST001, TST002, TST003 for ABCDE.JDH.DUMP.PROD. I deleted dsn via idcams and reran; it went fine.
//STEP1   EXEC PGM=IEFBR14             
//OUTFILE1 DD DSN=ABCDE.JHH.DUMP.PROD,
//             DISP=(MOD,DELETE,DELETE),
//             SPACE=(TRK,(1,0)),       
//             UNIT=DISK               
//OUTFILE2 DD DSN=ABCDE.JDH.DUMP.PROD,
//             DISP=(MOD,DELETE,DELETE),
//             SPACE=(TRK,(1,0)),       
//             UNIT=DISK               
//OUTFILE3 DD DSN=ABCDE.JHS.DUMP.PROD,
//             DISP=(MOD,DELETE,DELETE),
//             SPACE=(TRK,(1,0)),       
//             UNIT=DISK 


Step 2 uses CA-Easytrieve Plus and here's the info for the above-mentioned file creation.

//OUTFILE1 DD DSN=ABCDE.JHH.DUMP.PROD,           
//            DISP=(NEW,CATLG,CATLG),               
//            UNIT=SYSDA,                           
//            SPACE=(23300,(100,100),RLSE),         
//            DCB=(RECFM=FB,LRECL=233,BLKSIZE=23300)
//OUTFILE2 DD DSN=ABCDE.JDH.DUMP.PROD,           
//            DISP=(NEW,CATLG,CATLG),               
//            UNIT=SYSDA,                           
//            SPACE=(12680,(100,100),RLSE),         
//            DCB=(RECFM=FB,LRECL=634,BLKSIZE=12680)
//OUTFILE3 DD DSN=ABCDE.JHS.DUMP.PROD,           
//            DISP=(NEW,CATLG,CATLG),               
//            UNIT=SYSDA,                           
//            SPACE=(26700,(100,100),RLSE),         
//            DCB=(RECFM=FB,LRECL=89,BLKSIZE=26700)


How does the dataset exist, if the first step is meant for deleting them, and after the deletion step went fine.

Regards
v1gnesh
boyo
v1gnesh
 
Posts: 72
Joined: Wed Sep 28, 2011 8:24 pm
Has thanked: 1 time
Been thanked: 0 time

Re: Duplicate Dataset

 

Re: Duplicate Dataset

Postby BillyBoyo » Wed Feb 22, 2012 1:58 am

You are sending your datasets when writing them to a "pool" of DASD units which are "SYSDA'. That means any one of your files could go on any of a number of disks.

It is likely that on one (or more) of those disks you have some "uncataloged" datasets with the same name, which you have inadvertently created earlier.

Specifying CATLG when already cataloged is one way to create these. Deleting a dataset whilst specifying a volume that it is not on can/used to remove the catalog entry but not delete the dataset from the correct disk.

You have UNIT=SYSDA when creating, and UNIT=DISK when deleting. I don't know if that is giving you the problem, or if you have some stuff left over from earlier runs. If using IEFBR14 to delete, I'd not specify other parameters.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Duplicate Dataset

Postby NicC » Wed Feb 22, 2012 1:59 am

System Programming??? More like SMS.

Are you absolutely sure that the old datasets got deleted? You do not show any output to prove it to us. Also, they may be old, uncataloged, datasets from some failed delete on a previous day that just have not surfaced before now because you were allocating on different volumes. But you have gone and deleted the evidence so I do not think it possible to say what really happened.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: Duplicate Dataset

Postby v1gnesh » Wed Feb 22, 2012 2:27 am

NicC wrote:System Programming??? More like SMS.

Are you absolutely sure that the old datasets got deleted? You do not show any output to prove it to us. Also, they may be old, uncataloged, datasets from some failed delete on a previous day that just have not surfaced before now because you were allocating on different volumes. But you have gone and deleted the evidence so I do not think it possible to say what really happened.


Sorry. Mods can please move this to the appropriate topic.
boyo
v1gnesh
 
Posts: 72
Joined: Wed Sep 28, 2011 8:24 pm
Has thanked: 1 time
Been thanked: 0 time

Re: Duplicate Dataset

Postby v1gnesh » Wed Feb 22, 2012 2:36 am

is it possible that in step2, NEW,CATLG,CATLG just uncatalogues the dataset while the job gets an E37-08 ?

EDIT : We recently replaced Mainview SRM with CA - Allocate. If that information is of any use.
boyo
v1gnesh
 
Posts: 72
Joined: Wed Sep 28, 2011 8:24 pm
Has thanked: 1 time
Been thanked: 0 time

Re: Duplicate Dataset

Postby BillyBoyo » Wed Feb 22, 2012 3:02 am

Very useful. It means we can tell you that asking here is not going to get you far, as we have no idea how it operated before, nor how CA - Allocate has been installed. The people who know these answers are at your site.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Duplicate Dataset

Postby v1gnesh » Wed Feb 22, 2012 3:07 am

NicC wrote:System Programming??? More like SMS.

Are you absolutely sure that the old datasets got deleted? You do not show any output to prove it to us. Also, they may be old, uncataloged, datasets from some failed delete on a previous day that just have not surfaced before now because you were allocating on different volumes. But you have gone and deleted the evidence so I do not think it possible to say what really happened.


The problem I have posted here is a client's issue. We're providing support, and we're unable to find out the root cause. So when you're saying "I" deleted, its actually the client. The client is a bit dodgy, in the sense that he doesn't want his JCL to be changed. Also, the person uses various DISP parameters for the same dataset in different jobs. So it is really difficult to find out the reason behind the uncatalogued dataset's presence. They haven't been having this problem this long (we recently had a data centre migration; which is why i mentioned that we migrated from Mainview SRM to CA Allocate).

I thought that - if and when the issue happened again, before i delete the datasets, i would give an 'i' in front of the dataset to obtain the creation/reference information. But since its deleted before i can get the information.. i can't do much.
boyo
v1gnesh
 
Posts: 72
Joined: Wed Sep 28, 2011 8:24 pm
Has thanked: 1 time
Been thanked: 0 time

Re: Duplicate Dataset

Postby v1gnesh » Wed Feb 22, 2012 7:07 am

BillyBoyo wrote:Very useful. It means we can tell you that asking here is not going to get you far, as we have no idea how it operated before, nor how CA - Allocate has been installed. The people who know these answers are at your site.


The replacement was 1 year back. The JCLs worked fine back then. The client claims its only after the DC migration that he's facing this problem.
boyo
v1gnesh
 
Posts: 72
Joined: Wed Sep 28, 2011 8:24 pm
Has thanked: 1 time
Been thanked: 0 time

Re: Duplicate Dataset

Postby v1gnesh » Wed Feb 22, 2012 7:09 am

v1gnesh wrote:is it possible that in step2, NEW,CATLG,CATLG just uncatalogues the dataset while the job gets an E37-08 (abnormal end) ?


Does anyone have an answer to this..?
boyo
v1gnesh
 
Posts: 72
Joined: Wed Sep 28, 2011 8:24 pm
Has thanked: 1 time
Been thanked: 0 time

Re: Duplicate Dataset

Postby jaggz » Wed Feb 22, 2012 9:34 am

Hi Vignesh,

Is your dasd shared in your environment ? Probably the dataset is uncatalogued in some volume(Mostly in Non-smsed Volume). Could you please post us your SYSPRINT messages ? So , that it will be good enough to diagnose your issue.

Jaggz
User avatar
jaggz
 
Posts: 356
Joined: Fri Jul 23, 2010 8:51 pm
Has thanked: 8 times
Been thanked: 4 times

Next

Return to System programming

 


  • Related topics
    Replies
    Views
    Last post