Sleeper Scheduling Question

[tpayne]

We need to schedule some reports to be run on the 7th and also on the 21st
of each month.
I can't see any way to do this in Sleeper other than defining each job
twice, to be run on a specific date and once a month.
Does anyone have any better solutions, given that we are looking at 2
reports x 20 sales areas = 40 reports. Defining these twice means adding 80
jobs to Sleeper not 40!
PS: We have to run each sales area as a separate job since the reports are
being emailed.
----------------------------------------------------------
Tony Payne - Senior Systems Analyst
Selmer-UMI Inc.
Elkhart, Indiana 46516
Work: (219) 522 1675 ext. 451
Email: [email protected]
(Running JDE A73 cum 10 on V4R3M0)




Tony Payne - Senior Systems Analyst
Selmer-UMI
Elkhart, Indiana 46516

 

[G_Smith]

Tony,
One attempt at grouping might be to put the 40 reports on a combination of
%Menus. It would take 2 at the least since you can get 23 options on each
menu with the 24th option of the first %menu being the 2nd %menu. But you
might want to leave some room for expansion so build more than just 2 menus
say by logical groupings and then link them together.

Anyway the first %Menu would have to be scheduled still to run monthly on
the 7th and then a second scheduled monthly run on the 21st but it would at
least allow less maintenance in sleeper. Anyway the "Program to Run" is
J81900 and the "Form" is the "%MENU name" and the "Version" is always
"ZJDE0001" and this will run each option of the %menu and if the 24th option
is another %menu then it will continue through the options of that %menu, so
on. If any %menu option cancels the remainder of the options continue
unless an error occurs that halts the job for a response that will cancel
the entire job. But a simple Dream Writer records not found will not keep
the rest of the options from being processed. It has the same short comings
as the rest of sleeper in that there are no interdependencies within the job
stream other than they process as one "job" (J81900) with multiple steps.
(I did modify the Sleeper submit program, J95BATCH, to submit %Menus with
the job name of an "@" in place of the "%" with the rest of the %menu name.
This allowed us to identify the

%Menu being initially submitted. Of course if the program to run wasn't
J81900 then I changed the first character to a "Z" to identify other
programs running from sleeper as well.)

Should you have any other questions you can contact me directly.



George Smith
World A7.3, Cum10 - V4R5
Walco International, Inc.

 

[SallyWhite]

Tony,

This is easy if you set up % menus to define the 40 reports (2 % menus, 20 reports each), and then create 4 Sleeper jobs, two for the 7th and the other two for the 21st of the month. The frequency code is M. Sleeper will bump the date by one month for the next submission.


Regards,
Sally White
15+ yrs JDE Financials programming
V4R5/A7.3c10; OW Xe

 

[tpayne]

Thanks Sally,
I had pretty much come to the same conclusion, but I dislike using the
%menus (jobstreams) as it's so tedious changing them if you have to insert
items, especially if you have more than 23 jobs in the stream. As this is
only 20 it is probably simpler than creating a CL program to do the same.
Thinking about it, a program that read a %menu into a subfile, allowed you
to change the subfile, adding / deleting / changing the sequence of the
jobs, and which then rebuilt the %menu for you would be a REALLY nice
feature, rather than having to go through each option of the menu at a time.
Might look at this if I ever get the time...
Tony



Tony Payne - Senior Systems Analyst
Selmer-UMI
Elkhart, Indiana 46516

 

[tpayne]

Thanks George.
I think this is the way we are going.
Tony



Tony Payne - Senior Systems Analyst
Selmer-UMI
Elkhart, Indiana 46516

 

[nanda_raote]

Of course the other way to get greatly improved flexibility and useability is to invest in a job scheduler (such as Robot) to replace Sleeper altogether.

Regards
Nanda
A7.3.11 v4r5