Subject: | |
From: | |
Reply To: | |
Date: | Tue, 5 May 1998 16:38:35 +0200 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
another answer I got by an colleague ... Andreas Schmidt, CSC, Germany
What about if you use CHORUS.MAESTRO.CCC which is used to document BULK jobs from
individual
groups/accounts to the MAESTRO database, even wildcards can be used, i.e.
[log in to unmask]
This program is even able to check for duplicate entries (they will NOT be entered
again).
Andreas Schmidt
30.04.98 18:36
To: [log in to unmask]
cc: (bcc: Thomas Siebel/HI/CSC)
Subject: Re: MAESTRO HOW TO ? (Document link not converted)
No, Stephen, our MAESTRO version starts the ACTUAL JCL if it is time to start a
job (all conditions have met).
Changes done since the FINAL schedule has ran to activate today's production
schedule are reflected.
The real problem is that your job-file names are changing. In MAESTRO's ARRANGER
you have to define the JCL name once - and this file name should be kept.
Currently I do not have an idea how to deal with ... no other than re-writing your
program to force it to the MAESTRO known names ...
Best regards, Andreas Schmidt, CSC, Germany
[log in to unmask] on 30/04/98 05:14:59 PM
Please respond to [log in to unmask]
To: [log in to unmask]
cc: (bcc: Andreas Schmidt/HI/CSC)
Subject: MAESTRO HOW TO ?
As I remember, the auto job scheduler MAESTRO has to be compiled with
the current schedule and then set into play.
At that point, a snapshot is taken of each JCL and then compiled into
one working object.
These production JCL's are kept where the users can not alter them.
The problem; on a daily basis, files are downloaded across the country.
These files use the current date as their name (CD980430).
A program constructs the JCL with the right names to use today.
How then do you get MAESTRO to use this JCL that was just constructed by
my program ?
The real problem is, the JCL's are constructed and streamed in but
MAESTRO puts a priority 8 on all 'production' jobs (productions jobs are
those compiled in and MAESTRO is aware of).
If there are 50 jobs waiting, my files arrive late. MAESTRO must put a
pri "10" and move it to the top of the wait que but MAESTRO doesn't
recognize the job as a 'production' job since it was not compiled in.
?????????????????????
Stephen Johnson
|
|
|