|
Yep, I changed that one right away. Now the default is *FTP. Which we don't normally use. It's not that we let users use that command, I've personally taken down the tcp servers that way. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com "Jim Franz" <franz400@xxxxxxxxxx To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> om> cc: Sent by: Subject: Re: TCP/IP shutdown or crash midrange-l-bounces@m idrange.com 05/20/2004 11:23 AM Please respond to Midrange Systems Technical Discussion when net tech unplugs the network cable from switch or hub, it can cause major prob. I've had people ipl only because remotely I can't see exactly what's going on (they are on dumb terminal or ops console). Ending and restarting the interface would not do it at v5r2. On earlier releases i "think" setting ethernet line to infinitely retry could get past this. Never had ip shutdown or crash on it's own. Have had pgmr type ENDTCPSVR and press enter instead of F4 and that ends all tcp servers because default is *ALL.. jim ----- Original Message ----- From: <rob@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Thursday, May 20, 2004 11:08 AM Subject: Re: TCP/IP shutdown or crash > Only time we end tcp is while preparing to IPL. However, that is one way > of reducing the number of IFS locks when saving the IFS. > > Speaking as a customer who purchased an iSeries based paging system to > only have them blame their problems on one of the major paging companies, > I suggest that you modify your applications to handle tcp/ip 'exceptions'. > > Crashing unexpectedly? Not that I am aware of. Sounds like a call to IBM > for me. Perhaps they are having battles with MSF/SMTP and instead of > doing ENDTCPSVR *SMTP they choose ENDTCP instead? It's easier to get > permission to IPL than it is to ENDTCP. They are just as drastic here. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Urbanek, Marty" <Marty_Urbanek@xxxxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 05/20/2004 09:18 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx> > cc > > Subject > TCP/IP shutdown or crash > > > > > > > Do you ever have a need to shutdown TCP/IP but keep the rest of the system > up (including applications) and if so, why? > > Do you ever have TCP/IP crash? > > I have a customer that says sometimes they need to shutdown TCP/IP and > that > sometimes it crashes unexpectedly. This creates some "challenges" for one > of > our applications that is TCP/IP dependent. > > My stance has been that needing to shut TCP/IP down while keeping the rest > of the system up seems very unusual to me, and that having it "crash" is > unheard of and should be reported to IBM immediately. > > What do you guys think? > > FYI, I'm talking V5R2 here, not some old release. > > Anybody? > > Thanks, > -Marty > _______________________________________________ > 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.
midrange.com
