For our interfaced GL Tranasactions - I need to run GL165Report & GL165Update every single day with a different Run Group each day!

For my Patient Refund interface - I just need to run AP520Update Once a week (on Friday) but the BatchNumber is required (due to our setup) and changes every week!

Question: Do I have to actually go in and set up 730 jobs for GL (Report / Update mode) and 52 AP jobs?! Is there an easier way...

Oh man... :bonk: :bonk: :cof:

One solution (not a very good one, admittedly) is that an employee updates the job parameters each day/week. Same job, just different parameters each time. Yeah, it's ugly, but it works.

Just my 2-cents'-worth

Short answer: Yes, there is a way to do this without having to manually create each job before every run. But it certainly isn't an easy thing to do. Long answer...

You could possibly get VERY creative and do some heavy scripting to do the GL165 submits. You'd have to use tools like the jobload and wtsubmit, plus plenty of scripted parameter definition, editing and error checking. You could do a rngdbdump to get the day's run group and then build a job definition file to load with jobload then submit it with wtsubmit. The jobload would hold the parameters (report only, update, etc.). It works, but it isn't easy. You could probably do the same thing for your AP520 but it may not be worth it.

-GW

Coincidentally, just today I did something similar for a client. They needed to clone two 4-step jobs 70+ times with variable parameters. I had them set up one copy and wrote a 4GL routine to use the 900-LOAD-JOB and 900-CREATE-JOB to create the clones.

I've scripted this kind of thing often using jobdump, jobload, wtsubmit and the conservative application of 'sed' commands, and if you only have a few instances - as in your case - scripts work beautifully. But if you have LOTS of jobs that require this kind of thing then I STRONGLY recommend using a third party scheduler, like TWS, that can handle those parameter changes for you automagically.

How about a LawsonTalk project to create a template program based on Ragu's idea, which can be used to do automated job submissions?

It it's good enough, it could made available here and people could be urged to donate a small amount to LawsonTalk to defray expenses.

Ragu, would it be possible for you to post the code from that program?

I have no problem giving up some dough!

We are going live in ...ohh.....2 weeks!

:brr: