|
Elvis, Ok the following: ENDTCPSVR *NETSERV ENDHOSTSVR *DATABASE ENDSBS QSERVER STRSBS QSERVER STRTCPSVR *NETSERV STRHOSTSVR *DATABASE And its doing the same as it did before. Only 3 servers are shown, the iSeries Netserver, the IxS and the one I did the mkdir for. Looks like it's time to call IBM. Thanks for the help, Charles > -----Original Message----- > From: Elvis Budimlic [mailto:ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx] > Sent: Tuesday, August 03, 2004 4:23 PM > To: 'Midrange Systems Technical Discussion' > Subject: RE: QNTC file system (mostly) empty > > > Charles > > Here is some info on jobs running under QSERVER (see bottom > of the page): > http://www-1.ibm.com/support/docview.wss?uid=nas10dac6572b7e1d > 0a98625689d006 > 4dd3b&rs=110 > Strange they list database server jobs there, as these usually run in > QUSRWRK. Oh well... > > All of the interfaces listed above would obviously be affected by > ending/restarting the QSERVER. > Reason I recommended it is that IBM also recommends it in a > lot of their > APARs related to Netserver. That is the only bulletproof way > to guarantee > you are not reconnecting to some old prestart job (i.e. > QZLSFILE) that's > gone awry. > Once you recycle QSERVER, STRHOSTSVR *NETSVR and still can't > find QNTC, I'd > say it's time to call IBM. > > Elvis > > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of > CWilt@xxxxxxxxxxxx > Sent: Tuesday, August 03, 2004 2:48 PM > To: midrange-l@xxxxxxxxxxxx > Subject: RE: QNTC file system (mostly) empty > > Elvis, > > Before I do a ENDSBS QSERVER, have you any experience with > what else this > would effect? > > I see the following jobs in QSERVER: > QPWFSERVSD > QPWFSERVSO > QSERVER > QZDASRVSD > QZLSSERVER > > > Thanks, > Charles > > > > > -----Original Message----- > > From: Elvis Budimlic [mailto:ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx] > > Sent: Tuesday, August 03, 2004 3:33 PM > > To: 'Midrange Systems Technical Discussion' > > Subject: RE: QNTC file system (mostly) empty > > > > > > Recycle QSERVER subsystem. > > > > -----Original Message----- > > From: midrange-l-bounces@xxxxxxxxxxxx > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of > > CWilt@xxxxxxxxxxxx > > Sent: Tuesday, August 03, 2004 2:00 PM > > To: midrange-l@xxxxxxxxxxxx > > Subject: QNTC file system (mostly) empty > > > > All, > > > > We've been using the QNTC file system without problems for > > quite awhile. > > Today when I went to access a PC through QNTC I got an error > > saying the file > > didn't exist. > > > > Doing a WRKLNK '/QNTC/*' only shows my IxS server and the > > iSeries Netserver > > itself. > > > > Doing the WRKLNK on my TEST partition shows all servers as expected, > > including the production Netserver and IxS. > > > > QNTC on the production system was working fine last week. We > > did do a full > > system backup and IPL this past weekend, but that has been > done before > > without problems. > > > > md '/qntc/servername' worked fine, but I can't do that for > everything. > > > > Both Production and Test Netserver configurations point to > > the same WINS > > servers. I've tried stopping and restarting Netserver on > > production without > > effect. > > > > > > Thoughts? > > > > Thanks in advance, > > Charles > > -- > > This is the Midrange Systems Technical Discussion > > (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > 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@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > 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@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > 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@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > 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.