Re: Dividing jobs to diffrent job queue depending of job type -- MIDRANGE-L

Well, when you factor in the potential harm that can come from messing with the job submission mechanism on the AS/400 plus the requirement that the solution is completely documented and understood so that it can be supported if the author is not available and the effort involved in every PTF and upgrade it seems simpler to me. A few hours of search and replace.

I know that I would find it confusing if I submitted a job to a job queue and it popped up somewhere else, simply because i used the wrong name.

It also places the decision making at the source, where it truly belongs.

But maybe I'm overthinking the whole thing.

Albert

----- Original Message -----
From: "Charles Wilt" <charles.wilt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: Re: Dividing jobs to diffrent job queue depending of job type
Date: Thu, 6 Aug 2009 13:17:41 -0400

Unless the existing SBMJOB is buried in 100's or 1,000's of programs.

Changing them to use XSBMJOB doesn't fit my definition of "simple".

Charles

2009/8/6 Albert York <albertyork@xxxxxxxxx>:

The simplist solution to me would be to create a special version
of the SBMJOB command (ie XSBMJOB) and use that.

Albert

----- Original Message -----
From: "Charles Wilt" <charles.wilt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: Re: Dividing jobs to diffrent job queue depending of job type
Date: Thu, 6 Aug 2009 12:50:46 -0400

Crispin,

My only concern there is that as I understand it, routing steps factor
in when the job is started.

So it seems possible that the job could wait in the wrong queue for a
while, then get moved to the correct queue to wait some more.

Charles

2009/8/6 Crispin Bates <cbates@xxxxxxxxxxx>:

In the past I have used subsystem routing to do this. The initial routing
step checks the request data. If it's a query, the job is resubmitted to
another queue. That could be easily expanded to check a file

for the program

found in the request data. That file would also contain the new jobq...

----- Original Message -----
From: "Charles Wilt" <charles.wilt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, August 06, 2009 10:59 AM
Subject: Re: Dividing jobs to diffrent job queue depending of job type

Vern,

I'd be concerned that it'd be possible that the job could start before
it gets moved. Unless you default to placing the jobs on a queue that
is not attached to a SBS.

Charles

On Thu, Aug 6, 2009 at 10:45 AM, Vern Hamberg<vhamberg@xxxxxxxxxxx> wrote:

Tomek

Search in google for "job notification exit" and you will find something
at IBM - it lets you name a data queue to which messages will be placed
when jobs hit various stages in their running. One of these is being put
on a job queue. You would have a never-ending-program to wait on that
data queue, then, when a job i put on a job queue, you can change that
job to go to a different job queue. You would need some kind of control
file or hard-coded set of IF or SELECT to decide which way to go.

HTH - that was just a quick thought
Vern

Tomasz Skorża wrote:

Good morning/evening

I would like to ask if you know any solution how we can divide and send
jobs to other job queues depend of type of job (not depend of user
profile).
I.e.
1 - every long_time_consuming reports which is not important is going to
queue - SNAIL :-)
2 - report which have to be done ASAP - to queue - RABBIT
3 - any other batch jobs to queue QBATCH

I thinking about some exit point which will be recognize called
jobs/program and using some rules will change default QBATCH to other.
Is it possible?

Regards

Tomek

__________ Informacja programu ESET NOD32 Antivirus, wersja

bazy sygnatur

wirusow 4312 (20090806) __________

Wiadomosc zostala sprawdzona przez program ESET NOD32 Antivirus.

http://www.eset.pl lub http://www.eset.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.

--
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.

--
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.