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


  • Subject: Re: V4R1 and QPASRVP
  • From: Jeff Carey <jeffreycarey@xxxxxxx>
  • Date: Thu, 12 Feb 1998 08:38:17 -0600
  • Organization: Trase Miller Solutions

Actually, I had heard that the job in question only handles initiating
and terminating the passthru session - that once it is started, the
passthru job no longer has anything to do with QPASRVP until ENDPASTHR. 
So is QPASRVP is ended, no one can STRPASTHR or ENDPASTHR, but all
current PASSTHR jobs should be ok.  Is this not the case? 

mcrump@ballfoster.com 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.
> 
> +---
> | 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
> +---
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.