RE: Advanced Job Scheduler (IBM's product) -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Yes I think that will do the trick

thanks!

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Clay
Sent: Wednesday, March 06, 2013 10:21 AM
To: midrange-l@xxxxxxxxxxxx; midrange-l@xxxxxxxxxxxx
Subject: Re: Advanced Job Scheduler (IBM's product)

Upon review, you may need to use the STRGRPJS command instead, but the
theory is the same.

STRGRPJS JOB(NIGHTLY01 {grpName} 01) TIME(*IMMED)

IIRC, the group sequence has to be 01.

On 03/06/2013 11:07 AM, Robert Clay wrote:

If I understand this correctly, then you could...

1. Remove the dependency and place the NIGHTLY01 job in *HELD status.
That way, it stays on the job scheduler.

2. Then, add this as the last command for DAILYBACKUP:

SBMJOBJS JOB(NIGHTLY01 {grpName} {grpSeq}) TIME(*IMMED)
DATE(*CURRENT)

...where {grpName} and {grpSeq} are filled in with the
appropriate values or *NONE as appropriate.

3. Add a new final group job for the MONTHEND group that contains
this same command.

Now, both jobs submit NIGHTLY01 when they need to.

Would that work for your situation?

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.