|
If you do a new install of 57xx-TC1 it will set all those servers I mentioned to AUTOSTART(*YES) - that's the default. My specific concern was I had 5769-TC1 already installed on V4R1, those TCP servers were set to AUTOSTART(*NO), and after the system was up and running following the V4R2 upgrade I noticed those server jobs were running in QSYSWRK and the setting had been changed to AUTOSTART(*YES). Has anoyone else noticed this specific situation occur ? 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: bdietz@3x.com [SMTP:bdietz@3x.com] > Sent: Monday, July 27, 1998 5:29 PM > To: MIDRANGE-L@midrange.com > Subject: Re: V4R2 installed changed TCP server Autostart values > > I too have noticed this. My only thought was that on a 170 I > installed, > that was preloaded, did not have the TC1 product installed. I recall > seeing in the setup manual that IF you wanted that functionallity you > had > to install it. When I did nearly all of the TCPIP servers were > defaulted > to on. I guess that since you had to install TC1 you would then know > the > risk. > I think it is a bad idea however to change settings when installing a > new > release. Heck, they(IBM) even keep changes to > some subsystems we might modify after an upgrade to V4R2. > Bryan Dietz > 3X Corp. > > > > > Neil Palmer <npalmer@NxTrend.com> on 07/27/98 01:46:49 AM > > Please respond to MIDRANGE-L@midrange.com > > > > To: "'Midrange-L'" <MIDRANGE-L@midrange.com> > > cc: (bcc: Bryan Dietz/Columbus/3X Corp) > > > > Subject: V4R2 installed changed TCP server Autostart values > > > > > > > > I have complained to IBM about this behavious I observed after a V4R1 > to > V4R2 upgrade. > Has anyone else observed this ? > > After doing a release upgrade from V4R1 to V4R2 and looking through > WRKACTJOB I noticed several jobs running in QSYSWRK subsystem that > should not have been there. It appears that the release upgrade > ALTERED > the AUTOSTART settings for several TCP/IP servers from *NO to *YES. > The servers I noticed altered (I did have some already set to *YES so > it > may actually change others) were FTP, LPD, SNMP, POP, HTTP, REXEC ! > Changing these defaults during a releae upgrade is TOTALLY > unacceptable > behaviour from a security standpoint - especially for servers like > FTP > and REXEC. > ...Neil > > > Neil Palmer > +--- | 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.