|
Hmmm, seems IBM only changed that around V3R7 (probably when they started getting reports of problems ?). On V3R1 & V3R2 the second last subsystem started is QCMN, and last QSERVER. On V3R7 & V4R1 is starts QSERVER second, after QSPL, and QCMN is started last. Neil Palmer AS/400~~~~~ NxTrend Technology - Canada ____________ ___ ~ Thornhill, Ontario, Canada |OOOOOOOOOO| ________ o|__||= Phone: (905) 731-9000 x238 |__________|_|______|_|______) Cell.: (416) 565-1682 x238 oo oo oo oo OOOo=o\ Fax: (905) 731-9202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ mailto:NPalmer@NxTrend.com AS/400 The Ultimate Business Server http://www.NxTrend.com > -----Original Message----- > From: ericadelong@pmsc.com [SMTP:ericadelong@pmsc.com] > Sent: Wednesday, April 01, 1998 6:30 PM > To: MIDRANGE-L@midrange.com > Subject: Re[4]: CA file transfer mode description. > > > That's just what I did...... The RTVd source QSYS/QSTRUP starts QCMN > followed by > QSERVER. Our version of startup (<lib>/STARTUP) extends this a bit by > then > starting SNADS and TCPSRV. > > ___________________ Reply Separator _______________________ > > That's the point. I BELIEVE that QSERVER must be started BEFORE you > start QCMN, otherwise some server jobs than need to run in QSERVER > will > attach to QCMN instead. > In my startup program I do STRSBS QSERVER several subsystems before I > hit STRSBS QCMN. > RTVCLSRC for IBM's QSTRUP program in QSYS and look at it. You will > see > QSERVER being started second (right after QSPL), well before QCMN > (which > is the last subsystem started). > +--- | 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-2025 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.