|
Right, thanks. But once you are connected with Code/400 do you also find that you can end them with impunity? I suspect so. And if so, why are they persistent? jte -- John Earl johnearl@powertechgroup.com The Powertech Group www.powertechgroup.com Kent, Washington, USA +1 253-872-7788 ----- Original Message ----- From: Reeve Fritchman <reeve@ltl400.com> To: <midrange-l@midrange.com> Sent: Thursday, November 01, 2001 02:43 PM Subject: RE: QZRCSRVS > These bad daddies are used by CODE/400 as well... > > -----Original Message----- > From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On > Behalf Of John Earl > Sent: Thursday, November 01, 2001 4:40 PM > To: MIDRANGE-L@midrange.com > Subject: QZRCSRVS > > This is a multi-part message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > When one uses Client Access, a fair number of jobs named QZRCSRVS are > populated into QCMN or QUSRSYS (depending on what release your are on). > These jobs appear to be used by the central server and/or the signon server > for authentication. They also appear to be used only at startup time > because I have noticed that you can end these jobs without affecting signed > on users (at least it doesn't affect then signed on user in any way that I > can discern). > > But on a busy system, it is not unheard of to have 1000+ of these jobs > active at a time. This seems to be a nuisance at best and a terrible waste > of resources (if they are in fact unneeded) at worst. So here is a two part > question: > > 1) Do the QZRCSRVS jobs serve any useful purpose after Client Access has > authenticated and signed the user on. > > 2) Has anyone devised an efficient method of flushing old versions of these > jobs out of the system. > > > aTdHvAaNnKcSe > > jte > > > > -- > John Earl johnearl@powertechgroup.com > The Powertech Group www.powertechgroup.com > Kent, Washington, USA +1 253-872-7788 > > > -- > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
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.