|
I just had this problem the other day and was stumped and forced to call IBM. They had me diddling with lots of things regarding user QUSER's user profile. We have many other AS/400's and the changes he was doing were not on our other boxes so I questioned him many times about the changes. What _I_ believe was the problem is that another person had to change QUSER's Max Storage limit to *NOMAX, then did some things, then changed it back. Now the problem was that QUSER owned some objects that essentially put it over the (now put back) limit. Now the Prestart jobs could not fire up. IBM had me make other changes but I believe the Max Storage thing was the problem. Once we changed it to *NOMAX, things appeared to fire up fine. We were also able to delete the "offending" object that were owned by QUSER and things were still fine. Hope this helps! ************************************************** Sannan Solberg (406)523-1392 Business/Programmer Analyst (406)523-1636 fax Washington Corporations ssolberg@washcorp.com > -----Original Message----- > From: Art Tostaine, Jr. [SMTP:atostain@crecomp.com] > Sent: Tuesday, May 05, 1998 1:00 PM > To: MIDRANGE-L@midrange.com > Subject: STRHOSTSVR Problem > > We have had problems connecting with Client Access for Win95/NT to a > new > Model 600. We get an error like the license system unavailable. Help > suggests STRHOSTSVR *ALL or use CWBPING to check on status of servers. > > CWBPING shows that all host servers are active. > > If we try to end and restart the servers, we get messages on QSYSOPR > that the prestart jobs did not start. > > Result is we cannot connect to this box at all. > > IBM suggested that we install the XW1 product, Client access for > windows > (we only had Client Access Base family) installed. We did this and > IPL'ed, still same result when starting jobs. I haven't been able to > try and connect with a PC as I won't be in the office until tomorrow. > Any ideas until then? > > -- > Art Tostaine, Jr. > Creative Computer Associates, Inc. > Parlin, NJ 08859 > > > +--- > | 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 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.