|
Roger, The only other thing I can think of is the parameters of the prestart job. Here is what ours is, don't know if these are best settings but you might want to look at yours. Subsystem description: QSYSWRK Status: ACTIVE Program . . . . . . . . . . . . . . . . . . . . : QNPSERVS Library . . . . . . . . . . . . . . . . . . . : QIWS User profile . . . . . . . . . . . . . . . . . . : QUSER Job . . . . . . . . . . . . . . . . . . . . . . : QNPSERVS Job description . . . . . . . . . . . . . . . . : *USRPRF Library . . . . . . . . . . . . . . . . . . . : Start jobs . . . . . . . . . . . . . . . . . . . : *NO Initial number of jobs . . . . . . . . . . . . . : 1 Threshold . . . . . . . . . . . . . . . . . . . : 1 Additional number of jobs . . . . . . . . . . . : 2 Maximum number of jobs . . . . . . . . . . . . . : *NOMAX Maximum number of uses . . . . . . . . . . . . . : 200 Wait for job . . . . . . . . . . . . . . . . . . : *YES Pool identifier . . . . . . . . . . . . . . . . : 1 Other than that, I don't have any ideas. Scott > -----Original Message----- > From: Roger Vicker, CCP [SMTP:rvicker@vicker.com] > Sent: Wednesday, February 02, 2000 8:37 PM > To: MIDRANGE-L@midrange.com > Subject: Re: CA/400 Prestart job ending by itself (QNPSERVR) > > Scott, > > After trying the increase to max storage for QUSER it still ends by > itself. It > seems that after a few clients use the network print and then when they > all > disconnect is when QNPSERVR decides to shutdown completely. I hope to > convince > the corporate system manager to upgrade to V4R4 sometime in the next two > months. > > Roger Vicker, CCP > > Scott Mildenberger wrote: > > > I checked the storage used by quser on 3 of our machines and the values > were > > 3868, 5180, and 16344. The smallest was our development box which > doesn't > > have a lot of users and the largest was one of our heavily used > production > > boxes that typically has 150 users signed on, it also doesn't get IPL'd > very > > often but was last done in late December. If this is your problem then > the > > change you made should improve the situation but you could still bump > into > > it. > > > > -- > *** Vicker Programming and Service *** Have bits will byte *** > www.vicker.com *** > > The quest continues! ;-) > > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@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 subscribe to this list send email to MIDRANGE-L-SUB@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 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.