View previous topic :: View next topic
|
Author |
Message |
abin
Active User
Joined: 14 Aug 2006 Posts: 198
|
|
|
|
hi All,
Please look into the below problem and shed some lights.
I have following step in my jcl.
//SORTIN DD DSN=GDG.TEST.INPUT(+1),
// DISP=SHR
//SORTOUT DD DSN=GDG.TEST.OUTPUT(+1),
// DISP=(NEW,CATLG,DELETE),
// UNIT=TAPE,VOL=(,,,99),
//DCB=MDLDSCB,RECFM=FB,LRECL=5000,BLKSIZE=0,BUFNO=28)
I am getting a JCL error in the above step.
Error and explanation is as follows.
**********************************************
IEF287I &1 NOT CATLGD 7
The data set to be cataloged was not opened and the
following information was not provided on the DD
statement or via the retrieved source (VOL=REF or
passed data set):
Density For dual density tape requests only
Recording mode For requests where compaction
information is required
***********************************************
A very peculair thing is, this happens only in sort steps. |
|
Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006 Posts: 3156 Location: Tucson AZ
|
|
|
|
You were expecting no output, just trying to catalog an empty generation? |
|
Back to top |
|
|
abin
Active User
Joined: 14 Aug 2006 Posts: 198
|
|
|
|
Hi Will,
This is the first run of this job and GDG.TEST.INPUT(+1) is created in aprevious step. And no way it will be empty.
I have tried the same JCL in testing and it worked. But then I was using DASD instead of Tape.
Thanks,
Abin |
|
Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006 Posts: 3156 Location: Tucson AZ
|
|
|
|
It would help very much if you would share the full content of the actual error message...... |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
It will also help if you post the actual (production) jcl/control statement(s), not an edited piece of the jcl. I'm not positive, but i do believe the jcl posted will cause a jcl error. . .
On your production system has the GDG base been defined for:
?
I'd question why a "TEST" dataset is being created in your first production run |
|
Back to top |
|
|
abin
Active User
Joined: 14 Aug 2006 Posts: 198
|
|
|
|
Hi will,
I'll sent the JCl once I get to my office. Sorry to say this.Its night here and i'm out of office
GDG.TEST.OUTPUT is not a test GDG I just have put it there actuall name is different. And that ds created in a previous step using an existing ds. |
|
Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006 Posts: 3156 Location: Tucson AZ
|
|
|
|
Looking forward to it..... |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Regardless of the node name (i.e. TEST) whatever you used has to have a GDG definition in production. Has one been defined??
Your problem is not with the dataset created in the previous step - it is with the new dataset in the problem step.
As Bill said
Quote: |
Looking forward to it..... |
|
|
Back to top |
|
|
abin
Active User
Joined: 14 Aug 2006 Posts: 198
|
|
|
|
Hi,
It was problem with GDG base as will said. Its fine now. I feels like fish out of water
Thanks for support guys. |
|
Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006 Posts: 3156 Location: Tucson AZ
|
|
|
|
Ah, shucks.....'fess up now, what was the problem? |
|
Back to top |
|
|
abin
Active User
Joined: 14 Aug 2006 Posts: 198
|
|
|
|
no IDEA WILL IT WORKED TODAY
I'M CHECKIN ON IT |
|
Back to top |
|
|
|