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



Thanks everyone for that little lesson.

I printed the log and found that yesterday subsystem CMPSBSD started before QPGMR. So everything submitted to JOBQ QPGMR was being run in CMPSBSD. This subsystem was occupied, now I know why my job never got going. Today, I notice that QPGMR started first, so everything is back to normal. I wonder what controls that subsystem starting order?



-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de
Wintermute, Sharon
Envoyé : jeudi 28 mai 2009 16:35
À : Midrange Systems Technical Discussion
Objet : RE: JOBQ/SBS question



When a jobq is defined within two subsystems, the first
subsystem that starts will "attach" the jobq to itself.
IIRC, if you end that subsystem the second subsystem will
"pick up" the jobq and attach it.

We do this for programmer access a lot.


Sharon Wintermute


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

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

Follow-Ups:
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.