All true, but that does not explain why TCP is starting twice as submitted by the IBM procedures. That is still causing some interesting problems.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 9/19/2012 7:02 AM, rob@xxxxxxxxx wrote:
Documented by IBM that this is what needs to be done.
What's new for IBM i 7.1
Save menu changes

When using some of the save menu options, TCP/IP is ended before ending
the subsystems. For more information see topic GO SAVE command menu

IBM's not updated the help on GO SAVE 21 to show this.


No, ENDSBS *ALL does NOT end all of tcp. Parts will keep running if you
don't end tcp first. This ain't your father's 400 - stuff changes.
"System ended to restricted condition" is misleading.

Go here
and select the telnet fixes also. Of course, be current on all cumes and
groups also.

Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 From: ankush agrawal <aankush39@xxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, Date: 09/18/2012 10:22 PM Subject: Re: TCP/IP starts twice in V7 Sent by: midrange-l-bounces@xxxxxxxxxxxx Hi Jim, "Client machine keeps crashing the Telnet Server." This is the issue with V7R1. After upgrading from V5R4 to V7R1, we also faced the same problem. I would suggest you to try this. ENDTCP before ENDSBS *ALL *IMMED If the Telnet server is not ended prior to the ending of subsystems, it might not automatically restart. To circumvent this and other potential problems it is suggested that prior to ENDSBS *ALL *IMMED these steps be taken: 1. ENDTCPSVR *ALL 2. ENDHOSTSVR *ALL 3. Allow the commands to complete and the servers to end. If issuing the commands from a CL program include a DLYJOB DLY(300) to allow the commands to complete. 4. ENDTCP Also, there are PTF's recommended by IBM. Thanks On Tue, Sep 18, 2012 at 3:38 PM, Paul Nelson <nelsonp@xxxxxxxxxxxxx> wrote:
> I ran into this one the other day. IBM first had me bounce the telnet
> server
> using the HMC, and then when I could get to QINTER, change the IPL
> attribute
> to not start TCP, and then change the boot program to start the
> first, and then issue the STRTCP command down at the end of the program,
> with a 2 minute delay. This is then followed by starting a couple of tcp
> servers needed for the application software.
> Mind you, this machine was upgraded in February. He told me TCP has been
> flaky since it was rewritten for V6R1, and it was dumb luck this hadn't
> happened previously.
> There are also a few ptf's that are not part of a package yet.
> Paul Nelson
> Cell 708-670-6978
> Office 512-392-2577
> nelsonp@xxxxxxxxxxxxx
> -----Original Message-----
> From:midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
> Sent: Tuesday, September 18, 2012 2:51 PM
> To: Midrange Systems Technical Discussion
> Subject: TCP/IP starts twice in V7
> Folks,
> This one has me stumped. Client machine keeps crashing the Telnet
> Server. IBM says the reason is TCP is starting twice. Nice, except
> there is not STRTCP command anywhere in the start up stream that we know
> of (I retrieved the cl source of the start up program to be sure) IPL
> attributes are set to start TCP.
> Any ideas?
> --
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
> --

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page