Re: Running Batch jobs in QINTER

[JOberholtzer@xxxxxxxxxxxx]

With respect to those who advocate messing with the QINTER job queue, and
other techniques,  changing the job queue QINTER can have affects you may
not have thought about.  What about TFRJOB and jobs that may have routing
changes in them?  Communications with SNA can be a problem as well, no
issue if everything is TCP/IP, but we are all not there yet.  Messing with
the queues and other attributes of the QINTER subsystem will work but each
have a real problem associated with them.

In my experience, the workstation entry is where an on line job will gain
access to an interactive subsystem in most circumstances so removing the
job queue QINTER from the subsystem QINTER will accomplish the immediate
goal, but at what cost?

The only real way to control a job when it enters the subsystem, is to
provide a routing program that will control how the job will run.  Because
there is intelligence built in, you could even override changes in
priority, and other job attributes that could be set by the users in ways
you would not prefer them to.

It is easy, fast, and recoverable, and far easier to document, to make the
routing program handle the situation.

Jim Oberholtzer
Senior Technical Architect
Computech Resources, Inc.
Phone:  262/785-8111

IBM /I-B-M/
Once upon a time, the computer company most hackers loved to hate; today,
the one they are most puzzled to find themselves liking.
From:  www.tuxedo.org