getting dataset not found error on step03 in which i am creating version 1 for a gdg.can anyone tell me the reason and resolution for this.
//STEP01 EXEC PGM=IDCAMS
//AMSDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE GDG (NAME(DEEP07.GDGS.JCL) -
LIMIT(3) -
NOEMPTY -
SCRATCH)
/*
//************THIS STEP IS TO CREATE A MODEL DATASET *******
//STEP02 EXEC PGM=IEFBR14
//SYSPRINT DD SYSOUT=*
//MODEL1 DD DSN=DEEP08.GDGS.JCL,
// DISP=(NEW,KEEP,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)
//SYSPRINT DD SYSOUT=*
//STEP03 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD *
DEEPAK
HANUJ
NAVEEN
/*
//SYSUT2 DD DSN=DEEP07.GDGS.JCL(+1),
// DISP=(NEW,CATLG,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE),
// DCB=(MODEL.DCB,RECFM=FB,LRECL=80,BLKSIZE=3200)
//
getting dataset not found error
-
- Posts: 14
- Joined: Tue Jan 15, 2008 5:28 pm
- Skillset: cobol,jcl,db2
- Referer: internet
- MrSpock
- Global moderator
- Posts: 809
- Joined: Wed Jun 06, 2007 9:37 pm
- Skillset: REXX, JCL, DFSORT, Syncsort, Axway MFT, Connect:Direct, FTP, SFTP
- Referer: ibmmainframes.com
- Location: Raleigh NC USA
- Contact:
Re: getting dataset not found error
First of all, cataloging a Generation Dataset using the +1 Relative generation will create a new GENERATION, not a new VERSION.
I have absolutely no idea what the purpose of the job with STEP02 is.
With the GDG base defined, your STEP03 code worked fine for me. I'd make the following changes to it:
//STEP03 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD *
DEEPAK
HANUJ
NAVEEN
/*
//SYSUT2 DD DSN=DEEP07.GDGS.JCL(+1),
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE
You don't need the output DCB information for a copy process. And, if your system is running SMS, you don't use a MODEL.
I'd suggest that you have your Storage Management team look at your code and suggest any changes as per your site's standards.
I have absolutely no idea what the purpose of the job with STEP02 is.
With the GDG base defined, your STEP03 code worked fine for me. I'd make the following changes to it:
//STEP03 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD *
DEEPAK
HANUJ
NAVEEN
/*
//SYSUT2 DD DSN=DEEP07.GDGS.JCL(+1),
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE
You don't need the output DCB information for a copy process. And, if your system is running SMS, you don't use a MODEL.
I'd suggest that you have your Storage Management team look at your code and suggest any changes as per your site's standards.
-
- Posts: 14
- Joined: Tue Jan 15, 2008 5:28 pm
- Skillset: cobol,jcl,db2
- Referer: internet
Re: getting dataset not found error
thanks for the solution and sorry for the mistake that i wrote a new generation as a new version.
-
- Posts: 14
- Joined: Tue Jan 15, 2008 5:28 pm
- Skillset: cobol,jcl,db2
- Referer: internet
Re: getting dataset not found error
can u plz sepecifically tell some possible reasons for the same as i am still getting the same error
-
- Posts: 110
- Joined: Thu Dec 27, 2007 5:18 pm
- Skillset: Known little stuffs to answer a few queries!!
- Referer: Google
- Contact:
Re: getting dataset not found error
rawatdewan,
DId you implement MrSpock suggestions?
I ran the below steps from your JCL and it ran fine. I do NOT understand what are you looking for.
Check the following points.
1. Make sure that the SYSIN card for IDCAMS starts from column 2 or later. Do NOT start the SYSIN card from column 1.
2. As MrSpock said, remove the DCB parameter from the SYSUT2 of IEBGENER.
3. May I know for what purpose you have STEP02? Remove it, as it is useless to this topic.
If you still get the JCL error then, review it line by line. Let me know if you have any question.
Arun.
DId you implement MrSpock suggestions?
I ran the below steps from your JCL and it ran fine. I do NOT understand what are you looking for.
Code: Select all
//STEP01 EXEC PGM=IDCAMS
//AMSDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE GDG (NAME(KNM884U.ARUN.GDGS) -
LIMIT(3) -
NOEMPTY -
SCRATCH)
/*
//STEP03 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD *
DEEPAK
HANUJ
NAVEEN
/*
//SYSUT2 DD DSN=KNM884U.ARUN.GDGS(+1),
// DISP=(NEW,CATLG,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE)
Check the following points.
1. Make sure that the SYSIN card for IDCAMS starts from column 2 or later. Do NOT start the SYSIN card from column 1.
2. As MrSpock said, remove the DCB parameter from the SYSUT2 of IEBGENER.
3. May I know for what purpose you have STEP02? Remove it, as it is useless to this topic.
If you still get the JCL error then, review it line by line. Let me know if you have any question.
Arun.
- MrSpock
- Global moderator
- Posts: 809
- Joined: Wed Jun 06, 2007 9:37 pm
- Skillset: REXX, JCL, DFSORT, Syncsort, Axway MFT, Connect:Direct, FTP, SFTP
- Referer: ibmmainframes.com
- Location: Raleigh NC USA
- Contact:
Re: getting dataset not found error
Obviously, you can't define a GDG base, and then attempt to use that GDG all in the same job. For the purposes of your example, I'm assuming that the GDG definition is one process, then the subsequent creation of a new generation is a separate process.
-
- Posts: 14
- Joined: Tue Jan 15, 2008 5:28 pm
- Skillset: cobol,jcl,db2
- Referer: internet
Re: getting dataset not found error
Actually i coded step02 for creating a model dataset as i read it somewhere that it needs to be created and passed to the step in which a new generation of the gdg is going to be created.
-
- Similar Topics
- Replies
- Views
- Last post
-
-
Recatalog Error:Moving a dataset entry from one cat to other
by gselvasridharan » Fri Apr 07, 2023 1:33 pm » in VSAM/SMS - 3
- 4956
-
by gselvasridharan
View the latest post
Mon Apr 10, 2023 12:58 pm
-
-
- 12
- 3938
-
by RalphEagle
View the latest post
Fri Jul 30, 2021 1:00 pm
-
- 2
- 2752
-
by willy jensen
View the latest post
Sat Mar 04, 2023 12:41 pm
-
- 3
- 2719
-
by sergeyken
View the latest post
Sat Nov 16, 2024 11:05 pm
-
- 1
- 1266
-
by sergeyken
View the latest post
Wed Feb 07, 2024 11:48 pm