Is TCPIP properly authorized to force its friends? That is a class A
command.
Regards,
Richard Schuh
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Imler, Steven J
Sent: Monday, August 25, 2008 5:15 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Restart of TCPIP function servers when TCPIP is
recycled
I thought it/TCPIP did do a FORCE when it finds a server already
logged on when it tries to "StartANewLife"?
JR (Steven) Imler
CA
Senior Sustaining Engineer
Tel: +1 703 708 3479
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Colin Allinson
Sent: Monday, August 25, 2008 08:09 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Restart of TCPIP function servers when TCPIP is
recycled
Over the weekend a LAN problem resulted in TCPIP getting hung up
on 3 of our systems and a recycle of TCPIP was necessary to resolve the
issue.
On 2 of the systems we had no issue but, on a 3rd, we had a
subsequent issue with NAMESRV needing a separate manual recycle of that
server.
When I look at the console of TCPIP startup I see :-
DTCIPI030W StartANewLife: Victim NAMESRV, reason "Restarting
you because TCP/IP has been restarted"
HCPLGA054E Already logged on disconnected
and, sure enough, NAMESRV was not restarted. I see the same for
all 3 systems but, I guess, NAMESRV survived without problems on the
other 2 but got hung up on this system.
This leads me to the following questions:-
- Should TCPIP force it's application servers before starting
them - and, if so, what might I have configured incorrectly?
- If not, what would be the best place to insert commands to
force these off when TCPIP is started to ensure a clean start up?
Colin Allinson
Amadeus Data Processing GmbH
