3 Replies Latest reply: Oct 4, 2012 1:30 AM by manjunath NameToUpdate RSS

schedule a job to run for next ODATE

latha NameToUpdate

hi ,

 

i have a requirement where i get a set of files from an external system at 5 different timings.

Say I have file1 coming @ 3am,        

                file2 coming @ 8:30 am,

                file3 comes @ 10 am,

                file4 comes @ 12 pm and

                file5 comes @3pm

 

Whevever a file comes in i need to run a set of 5 different jobs (based on the GP that i et from these systems)

There is no problem with 1st 2 files as the files come @ 3 am and 8:30 am.

So when a NDP runs, and AJF gets loaded @ 9 am and the runs for file1 and file 2 will be completed.

but as the file3, 4 &5 come after 9 am i wil 2 set of jobs in AJF waiting for GP.

 

will GP have any ODATE appended to it, so that the correct GP with correct odate is picked and only the relevant jobs for that ODATE run

and the other set which should actually run for the NEXT odate keep waiting?

 

If not i have though to make the job run for NEXT odate. Is there an option in controlm to schedule a job till next odate

 

Please help me with this scenario.

 

thanks,latha

  • 1. Re: schedule a job to run for next ODATE
    P-J Sporsen

    You can put the jobs on its own user daily and use ctmudly to order the jobs at 4pm for example. That way you will only have one job waiting for the 3 last jobs.

     

    /P-J

  • 2. Re: schedule a job to run for next ODATE
    Swati B

    Hello, I haven't got your whole problem, but as you asked "Is there an option in controlm to schedule a job till next odate?", so yes, you can do it by adding intended days in "MaxWait" parameter in "Execution" Tab. for ecample if you want to keep your jobs for 2 days in AJF, you select "maxwait =2", which will keep your jobs in AJF for two days (those are not completed).

    Hope this will be useful.

    can you make ur question simple ?

  • 3. Re: schedule a job to run for next ODATE
    manjunath NameToUpdate

    Hi Latha,

     

    Got your problem.

    First put your job stream in a scheduling group table and assign a userdaily to that scheduling group so that it will load @ 2 AM.

    Add maximum re-runs=5 for your cyclic stream to make the stream stop once it finishes 5 runs.

     

    I hope you know how to create/use ctmudly (userdaily).

     

    Let me know if it works for you.