V4R1 and QPASRVPV4R1 and QPASRVP

Michael wrote:

> One of the changes with V4R1 seems to be a job QPASRVP.
> This job is the target pass-through server job that is used by
> pass-thru and terminal emulation.  Prior to this pass-thru and
> terminal emulation were handled by individual jobs.  No big deal.
>
> However, it seems that for a given system there may be only
> 1 QPASRVP job.  The system value QPASTHRSVR allows you
> to control this but I haven't seen any effect on changing this.
>
> My problem with this stems from CA/400 (imagine that).  On
> occasion we will have a user who locks up or can't signon.
> They typically will reboot on their own.  Sometimes this works
> and sometimes it doesn't.  Our operators (unknown to me at
> the time - although I can't argue against it) typically then would
> end all jobs associated with the client access 'session'.
>
> Unfortunately, even though there may only be one QPASRVP
> job you will see it associated with each CA/400 device that
> has evoked terminal emulation.  What happens?  An operator
> ending jobs on an individuals PC will end the QPASRVP job
> and ALL PASS-THRU (INCLUDING PC TERMINAL
> EMULATION ) PROCESSES ON THE SYSTEM DIE.  You
> can recover but it is a little bit too late.
>
> Currently, I have stressed to everyone the importance of
> not ending jobs unless they really have to and to never end
> the QPASRVP job.  Problem is everyone (including me)
> does not have a perfect memory and I am really worried about
> the continued impact on the 'stability' of the system.
>
> 1.)  I am assuming that this is the way it should be and
> that other people on V4R1 are in the same boat.
>
> 2.) You can tell the system to start up to 100 of these jobs
> but for the life of me I can't seem to get anymore than
> one to work.
>
> 3.) Operationally, doesn't this seem to be a design flaw?
>
> 4.) What way do you have the system stop people from
> ending 1 specific job?
>
> Michael Crump
> Technical Project Leader
> Ball-Foster Glass Container Corp.

Michael,
Let me explain the V4R1 passthrough design:

QPASRVP is the PRIMARY passthrough server job, which passes requests
off to multiple QPASRVS secondary jobs.  The system value QPASTHRSVR
controls the number of *secondary* server jobs.  There will only be
one QPASRVP job per system.

As you stated, the problem is that WRKCFGSTS for a particular
device/mode will show the QPASRVP job as a *placeholder*, but this is
confusing to people, who may actually end the QPASRVP job, with bad
results.

The Passthrough developers are looking at this situation figuring out
the best way to address it.

Sorry for the problem.
Marty Keech

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---