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



So you're running production work in QPGMR then? You cannot 'share' job queues between systems. You can attempt to assign a job queue to multiple subsystems but only one will get it (first in wins).

FYI I strongly discourage changing the existing job queue to multi-threaded unless you know the system VERY VERY well. This is a "land mine".

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 7/15/2013 11:35 AM, Hoteltravelfundotcom wrote:

Jim - i am using QPGMR but it's sharing the job q. That's why I didn't even
think about the first time.

And it happened again because it didn't sink in. It's very possible the
vendor package wants it setup this way. I dont understand how the other
outside consultants manage.


On Mon, Jul 15, 2013 at 11:33 AM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:

Yes I can't make this change on my own. There must be a reason for the
single thread. Let's say I run my jobs in QSPL or even QINTER ( Qinter was
suggested to me by a consultant. For over the weelkend it would be fine).
I think they are still sharing the same que. So you have a situation where
testing is impossible.


On Mon, Jul 15, 2013 at 11:29 AM, Jerry Draper <midrangel@xxxxxxxxxxxxx>wrote:

Use nomax jobq qsysnomax if you want a job to run immediately without
hanging up users who are submitting to a single threaded jobq.

J


On 7/15/2013 8:24 AM, Hoteltravelfundotcom wrote:
What do you think of a shop which has only 1 jobs que? SHouldn't there
be a
test system
for a programmer? This has happened twice now. I have a long running
RPG program, working over the weekend, it didn't sink in the first time.
so then its still running and causes some jobs to not run. Consequently
subsystems
did not come up. I don't recall in many years either a system that shuts
down every night and comes back up.
It is frustrating. Am I wrong in thinking that they should have more
than 1
jobq, that is, that other jobs can run at the same time that there
should
be a test system? Is it possible for a newcomer to not make these
mistakes?
I suppose I am to blame that it happened again. BUt I really
have trouble acclimating to this type of environment, and not sure what
can
be done.


--
Jerome Draper, Trilobyte Software Systems, since 1976
iSeries, Network, and Connectivity Specialists -- iSeries, LAN/WAN/VPN
Representing WinTronix, Synapse, Netopia, HiT, and others .....
(415) 457-3431; www.trilosoft.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.




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.