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



JOBQ's are actually "run-time attached" to only one subsystem at a time.
When the subsystem starts, it'll try to acquire each of the JOBQ's in
its job queue entries. If one is busy (already acquired by another
subsystem), it'll log a message and proceed to acquire the others.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Thursday, May 28, 2009 9:23 AM
To: Midrange Systems Technical Discussion
Subject: JOBQ/SBS question

I don't know much about this subject. All of a sudden my compiles are
getting jammed in JOBQ. Usually they are submitted to QPGMR in QGPL and
run in the subsystem named QPGMR.

My job is stuck in the JOBQ QPGMR. If I do WRKJOBQ QPGM* I see that this
JOBQ is attached to subsystem CMPSBSD.

But if I do WRKSBS and use options 5 then 6, I see that the JOBQ QPGMR
is attached to both subsystems CMPSBSD and QPGMR.

Why isn't my job going to subsystem QPGMR which is idling instead of
apparently waiting to go to CMPSBSD?

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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.