RE: Running a program interactively or in batch

Let's agree to disagree on this one, however I would imagine you perhaps do more operations work than I do.

It's never bitten me so I wouldn't be afraid of it especially if you're just doing a quick process test.

Regards,

Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com


-----Original Message-----
Yes I did see "test" and it makes it worse since you really don't know the outcome. I'd be careful sending jobs that are not clearly defined into the realm where it could freeze up the system. It happens, and I get several calls a year because something like this happens.

There are nearly 60 different routing entries in QUSRWRK using a multitude of classes that start with execution priorities of 7 (yes less than the console) and run up to 50. If you're lucky you get the default which runs at priority 50, then again depending on the job description you use that could be almost any one of them.

QSYSWRK was set up by IBM for specific reasons. So was QUSRWRK. Let's let them have those reasons and think about putting our jobs where they belong. Additionally it does not eliminate thread blocking it simply forces the threads to all run in *BASE which of course has limits just like all the other pools do. So the desired outcome is still not achieved.

--
Jim Oberholtzer
Agile Technology Architects