|
View previous topic :: View next topic
|
| Author |
Message |
ojdiaz
New User
Joined: 19 Nov 2008
Posts: 98
Location: Spain
|
|
|
|
Hello
I have an interesting issue with Control-M under and IBM 390 mainframe and I want to avoid to use a dummy job for the following
I have a job that currently has 2 input conditions, they are both generated by two differents systems. One of them, let's name it CONDITION A, is generated early in the morning, around 1:00 am, the other, CONDITION B can be received at time, around 3:00 am or could be quite late, after 8:00 am.
We have an issue when the B CONDITION is late on its generation, and we need our job to be submited at a deadline, around 3:30 am, without any regards of this condition
By this reason, we need to submit this job in two different cases:
1.- Once both conditions has been generate by their other corresponding job, or
2.- Once a Time has come, the job should submit, without any regards of B Condition.
Is there a way to do this in Control-M wihtout creating a dummy job that gives this condition
Currently, the conditions for the job is like this:
| Code: |
===========================================================================
IN HI$$M012-HI$$PASB-JJ ODAT HI$$INM1-HI$$PASB-JJ ODAT
CONTROL
RESOURCE
TIME: FROM UNTIL PRIORITY DUE OUT SAC CONFIRM
TIME ZONE:
===========================================================================
|
|
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello and welcome to the forum,
One way to do what you want is to make the B file a gdg that is re-created every day. The first generation will always be an empty file. When the process that creates the actual data is run, it will be written as a +1.
When the job that reads both files executes, it will either get an eof-of-file immediately (only the empty generation is available) or it will read the data that was uploaded. |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
I can't see any way around your problem, if the definition has 2 IN-CONDITIONS, then both conditions need to be satisfied, hence you will need someting to post the B condition (dummy job), or you could remove the B condition and add a from time of 3:30am to your definition.
This means your job will not run until 3:30am even if the B job has run earlier.
Gerry |
|
| Back to top |
|
|
ojdiaz
New User
Joined: 19 Nov 2008
Posts: 98
Location: Spain
|
|
|
|
Thanks for your reply guys. I'm a bit confused about the GDG issue posted by Dick Scherrer, perhaps this is the wrong post? 
gcicchet:
Thanks, I think I'll have to go with teh dummy job after all, and let it post the condition B at that time, no matter if the other job as already being submited or not.
I guess I can't do a
CondA OR Submit time in the conditions area
Thanks anyway, I like this forum, I'll be coming back more often if I have issues or anwers that i might know
Best Regards
Oliver |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| I'm a bit confused about the GDG issue posted by Dick Scherrer, perhaps this is the wrong post? |
No, this is the correct post. . .
Many places use a gdg that the first generation is always an empty file so that processing is not disrupted and "special" or "dummy" jobs are not needed. There should be no problem with an empty file, but a missing file causes exception processing (which is usually more complicated and error prone). |
|
| Back to top |
|
|
ojdiaz
New User
Joined: 19 Nov 2008
Posts: 98
Location: Spain
|
|
|
|
| dick scherrer wrote: |
Hello,
| Quote: |
| I'm a bit confused about the GDG issue posted by Dick Scherrer, perhaps this is the wrong post? |
No, this is the correct post. . .
Many places use a gdg that the first generation is always an empty file so that processing is not disrupted and "special" or "dummy" jobs are not needed. There should be no problem with an empty file, but a missing file causes exception processing (which is usually more complicated and error prone). |
Oh! I understand now... I haven't think about it in that way. It might Work. Let me check if the condition is associated with a file, therefore it might be a valid solution. However, i think files are dated on this specific batch, i mean, they use ODATE as part of the file name
Thanks for your answer
Oliver |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
You're welcome - good luck 
d |
|
| Back to top |
|
|
|
|
