|
View previous topic :: View next topic
|
| Author |
Message |
yogesh suryawanshi
New User
Joined: 04 Mar 2013
Posts: 16
Location: India
|
|
|
|
Hi,
In one of my job I have below GDG base and its generations...
H2552PS.G.T3S1101.S52T3110.H2552T3O
H2552PS.G.T3S1101.S52T3110.H2552T3O.FEB2010
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0006V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0007V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0008V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0009V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0010V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0011V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0012V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0013V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0014V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0015V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0016V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0017V00
H2552PS.G.T3S1101.S52T3110.H2552T3O.FEB2010 is not part of GDG generation since it was created manually for adhoc business purpose on 7/10/2013.
My job ran on 7/16 which takes 0th generation of the GDG and send as attachment to the email from job itself. Instead of taking 0th generation G0017V00 it picked up the file H2552PS.G.T3S1101.S52T3110.H2552T3O.FEB2010 .
Can someone please let me know what could have caused job to pick the wrong file ..I believe job should have picked current generation of the GDG not the adhoc file. |
|
| Back to top |
|
 |
bvarun.
New User
Joined: 05 Jul 2013
Posts: 34
Location: India
|
|
|
|
Seems weird.
please post your jcl which you have used. it will be easy to comprehend your scenario.
Then we will ponder, Why and how it happened. |
|
| Back to top |
|
|
yogesh suryawanshi
New User
Joined: 04 Mar 2013
Posts: 16
Location: India
|
|
|
|
%XMITIP abc@XXX.COM +
CC (abc@XXX.COM +
abc@XXX.COM) +
MSGDD SYSUT2 +
FROM FLASH-MIS-REPT@some.stuff +
SUBJECT 'A Report' +
SENSITIVITY COM +
Format txt +
FILENAME ( 'A Report.txt' ) +
FILE ('H2552PS.G.T3S1101.S52T3110.H2552T3O(0)')
I have this control card which picks current generation and send as attachment to the email. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Well, it was unwise to name your 10 July dataset in such a manner, and you've no been tripped up by it.
You could investigate whether it was the Control Card which did it (which I'd guess) or the JCL, but basically, rename the ad hoc dataset and make sure your procedures and standards for datasetnames don't allow such a thing again. |
|
| Back to top |
|
|
bvarun.
New User
Joined: 05 Jul 2013
Posts: 34
Location: India
|
|
|
|
As of now,
Better copy current gen into a PS file and refer that PS file name in XMIT step if you cannot rename '10 July dataset'.
Any reason why '10 July dataset ' is named in such a way like gdg base name.
From my metlife experience, 'H2552PS' is a production qualifier. if you have prod access , confirm with assosciates before renaming it. |
|
| Back to top |
|
|
yogesh suryawanshi
New User
Joined: 04 Mar 2013
Posts: 16
Location: India
|
|
|
|
I understood that the dataset name for adhoc file has caused the problem.
But can you please explain why would JCL pick it as current generation ? I am asking because
1. It is not part of GDG ..
2. Job created current genration on 7/16
H2552PS.G.T3S1101.S52T3110.H2552T3O.G0017V00 before emailing step runs? So it should have been picked up? |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Quote: |
| But can you please explain why would JCL pick it as current generation ? |
You haven't even determined that it is the JCL doing it.
Use an IEFBR14 step, DISP=OLD, generation (0) and look at the message out and show us which dataset is referenced. |
|
| Back to top |
|
|
yogesh suryawanshi
New User
Joined: 04 Mar 2013
Posts: 16
Location: India
|
|
|
|
Please see below after running IEFBR14 as you said:
********************************* TOP OF DATA *********************************
ICH70001I H2506AA LAST ACCESS AT 02:43:46 ON MONDAY, JULY 22, 2013
IEF236I ALLOC. FOR H2506AAA DELDSN
IEF237I JES2 ALLOCATED TO SYSPRINT
IEF237I JES2 ALLOCATED TO AMSDUMP
IEF237I DMY ALLOCATED TO SYSIN
IGD103I SMS ALLOCATED TO DDNAME DD01
IEF142I H2506AAA DELDSN - STEP WAS EXECUTED - COND CODE 0000
IEF285I H2506AA.H2506AAA.JOB30092.D0000101.? SYSOUT
IEF285I H2506AA.H2506AAA.JOB30092.D0000102.? SYSOUT
IGD104I H2552PS.G.T3S1101.S52T3110.H2552T3O.G0017V00 RETAINED, DDNAME=DD01 IEF373I STEP/DELDSN /START 2013203.0243
IEF032I STEP/DELDSN /STOP 2013203.0243
CPU: 0 HR 00 MIN 00.00 SEC SRB: 0 HR 00 MIN 00.00 SEC
VIRT: 4K SYS: 380K EXT: 4K SYS: 12700K
IEF375I JOB/H2506AAA/START 2013203.0243
IEF033I JOB/H2506AAA/STOP 2013203.0243 |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
please show all output as requested earlier.
This file H2552PS.G.T3S1101.S52T3110.H2552T3O.FEB2010 is not part of a GDG and the only way it will get picked up is for you to specify this fully qualified name.
Gerry |
|
| Back to top |
|
|
yogesh suryawanshi
New User
Joined: 04 Mar 2013
Posts: 16
Location: India
|
|
|
|
| I said JCL picked up because I had checked no of Generations present for the GDG Base in Fileaid. It is showing 12 . So I am saying the adhoc file created on 7/10 is not part of GDG. |
|
| Back to top |
|
|
bvarun.
New User
Joined: 05 Jul 2013
Posts: 34
Location: India
|
|
|
|
Jcl refers the current generation of GDG in this format 'H2552PS.G.T3S1101.S52T3110.H2552T3O(0),
Whereas, does XMIT step refer in the same way ?
This is where i nitpick....
As this is bizarre that MF folks rarely see it. Better way of identifying now is to create a sample JCL with GDG bsae and run it to get the whole perspective.
Solution i can concur is
i) rename H2552PS.G.T3S1101.S52T3110.H2552T3O.FEB2010 (see the impacts if so).
ii) copy into PS if its not too big and use it |
|
| Back to top |
|
|
yogesh suryawanshi
New User
Joined: 04 Mar 2013
Posts: 16
Location: India
|
|
|
|
Hi BV...
Thank you...I have already fixed the problem..by renaming the adhoc file.
But just trying to understand what it is that causing such problem... |
|
| Back to top |
|
|
bvarun.
New User
Joined: 05 Jul 2013
Posts: 34
Location: India
|
|
|
|
So Did you find out the root....!
You can share with us if any. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Quote: |
| FILE ('H2552PS.G.T3S1101.S52T3110.H2552T3O(0)') |
Now that we know what the JCL does (behaves as expected) we know for certain that it is the above from the Control Card.
Whoever wrote the code originally didn't think of someone specifying a file with exactly the same HLQs as a GDG, and therefore the F-before-G file was included as the (0).
Yes, it is a bug. No-one should ever have discovered it, as they should have thought first "do I know what happens with a dataset named like this" and then know that simply asking themselves the question means it is a bad idea to name it so. |
|
| Back to top |
|
|
yogesh suryawanshi
New User
Joined: 04 Mar 2013
Posts: 16
Location: India
|
|
|
|
Thanks Bill...
That makes sense...I will share this with my entire IT collegues ... |
|
| Back to top |
|
|
yogesh suryawanshi
New User
Joined: 04 Mar 2013
Posts: 16
Location: India
|
|
|
|
| Its bug in Rexx code XMITIP which is used for emailing... |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
instead of specifying the dataset name in the control cards, you may want to use FILEDD ddname instead of FILE data-set-name.
Gerry |
|
| Back to top |
|
|
|
|
