MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » May 2014

Re: AJS (Advance Job Scheduler) issue



fixed

I'll be the one to disagree.
AJS's job is to submit on a schedule and monitor completion.
Included in that scheduling is what to do if system unavailable (options to submit upon resumption or not).
It's my choice to put the jobq on hold, for whatever reason.
We have many jobs that run repeatedly during the day & eve.

Why should AJS make it's own decision (by design) not to submit, when the scheduler is running and the time arrives?
It has no application knowledge to know if that is a good idea or not.

To me, it's a design flaw.

Jim Franz

----- Original Message ----- From: <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, May 21, 2014 1:40 PM
Subject: Re: AJS (Advance Job Scheduler) issue


I don't even use AJS but I tend to agree with them on this one.
Why would you want to queue up multiple jobs?
Let's suppose the job queue was on hold and not just this one job. Would
you expect that to stop it from queing up more?
I'm hoping someone held that job for a reason. Why should they have to
keep holding more and more? Suppose your AJS entry submitted it every 5
minutes? Might drive a lad bonkers holding them.
IBM clearly put on the entry "Dude, I'm not submitting this job anymore
until the other one is released from the job queue."



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 05/21/2014 01:21 PM
Subject: AJS (Advance Job Scheduler) issue
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Did you know, that if a job submitted from AJS, is put on hold in the jobq
before it becomes active, AJS will not submit any future jobs for this
job.
AJS job status is *JOBQ as opposed to normal *READY status.
Held job in jobq needed to be cancelled before any new jobs could be
submitted.

I did not expect this behavior, but WAD per IBM development..
I think I will be submitting a DCR request, scheduled job still should
run.

Any thoughts from the group?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact