Re: job queues

[DrFranken <midrange@xxxxxxxxxxxx>]

As always YMMV because we don't know the complete setup of the system.

However this was the traditional use for the QPGMR subsystem. Run 
developer sessions there, developer compiles there, developer job queues 
for testing also were in there.  While many shops have moved away from 
this in a simple one or two man development shop this is a good setup.

What is virtually always bad is having developers running test jobs in 
the same job queues and subsystems as production and your situation is a 
very good example why this is true!

        - Larry "DrFranken" Bolhuis

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

On 7/15/2013 11: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.