Multiple JOB QUEUE!!

[cvapl]

Hi!
Our Client(XE, SP 15.1, DB2) needs to be able to assign Job Queues by User
or Environments. When we Promote the Versions from say DEV to CRP to PROD,
the Job Queue remains the same and therefore all UBE's Piles up in the same
Job Queue.Resulting in Delays.

Could we get Any suggestion/help on this!!


Thanks in Advance
Siva & Sachin
XE, SP 15.1, DB2)

 

[SPhillips]

To List:

I'm looking for the same type of solution that Savi is. This
problem really manifests it self at the end of the month for each
department.

Thanks in advance.

Steve Phillips
B7332, SP 11.3, DB2.

 

[MSiebenschuh]

The solution I came up with is what we call the Queue Director. Basically we
send all jobs to a bogus queue (QWAIT) then we have a daemon running on the
HP9000 that looks at the submitted jobs table for any job in QWAIT. It then
strips the version and the job and the environment. Looks it up in another
table where I assign jobs to SHORT, MEDIUM, or LONG queues and load balances
accordingly (i.e. we have 7 of each (SHORT, MEDIUM, LONG)it fills each of
them with a job to run and then fills as others become available.)This way
you don't hardcode anything into the version and you can change things on
the fly. All the queues are single threaded so you don't have to worry about
that whole issue and it works great. We did 2900 jobs the other day and no
one noticed the difference from another day where we only ran 1500. If this
sounds too extreme you might want to search the archives for multi-threaded
queues but there are some gotchas (not all jobs can run in multi-threaded
queues). Good luck.

Mark Siebenschuh
XE Financials/Base Distribution/HP9000/Oracle 8.0.5

 

[Bill_Feeney]

Mark,
Very innovative. When you re-submit the jobs do you then put the versions
and job and environment back on them?

Bill Feeney
JDE Technical Developer
B733.2, SP 13.1, Unix, Oracle 8.1.6




Bill Feeney
B733.2, SP 13.1, Unix, Oracle 8.1.6

 

[MSiebenschuh]

We don't resubmit them we just have the daemon change the record in the
submitted jobs table (f986110) from QWAIT to whatever queue the job is
supposed to be in. Since the job status is W it just moves on through like
it should.

Mark Siebenschuh
XE/Base/Oracle 8.0.5/HP9000