---------------------------- Top of message ----------------------------
>>--> 03-05-99  07:50  S.SHEPPARD     (SHS)    Problem when TCP/IP is st
>>--> 03-05-99  07:50  S.SHEPPARD     (SHS)    Problem when TCP/IP is st

We found that starting at the 3.1.2.1 level of the MVS server that ADSM
would never connect if it was started before TCP/IP.  Also, ADSM would
need to be restarted if the TCP/IP address space was dropped and then
restarted.  I asked the question in connection with an ETR I opened a
while back.  Level 2 asked for an SVCDUMP for that particular abend
(0C4 in ANRSVM5) which hasn't reoccurred and didn't have any response
to the TCP/IP question.  Our solution was to insure ADSM starts after
TCP/IP.
Sam Sheppard
San Diego Data Processing Corp.
shs AT sddpc.sannet DOT gov
-----------------------------------------------------------------------`
---------------------------- Top of message ----------------------------
---------------------------- Top of message ----------------------------
>>--> 03-05-99  01:03  ..NETMAIL     ()     Problem when TCP/IP is st
>>--> 03-05-99  01:03  ..NETMAIL     ()     Problem when TCP/IP is st
Date: Fri, 5 Mar 1999 09:46:29 +0100
From: "Tomas Norberg" <tono02 AT HANDELSBANKEN DOT SE>
Subject: Problem when TCP/IP is started after ADSMserver
To: <ADSM-L AT VM.MARIST DOT EDU>
_________________________________Top_of_Message_________________________________

When  ADSM is started before TCP/IP, on our MVS-system, we get:

03/05/1999 03:59:24 ANR5092E Unable to initialize TCP/IP driver - error creating
 acceptor socket.
03/05/1999 03:59:24 ANR5092E Unable to initialize TCP/IP driver - error creating
 acceptor socket.
03/05/1999 04:00:24 ANR5092E Unable to initialize TCP/IP driver - error creating
 acceptor socket.
03/05/1999 04:00:24 ANR5092E Unable to initialize TCP/IP driver - error creating
 acceptor socket.
03/05/1999 04:01:24 ANR5092E Unable to initialize TCP/IP driver - error creating
 acceptor socket.
03/05/1999 04:01:24 ANR5092E Unable to initialize TCP/IP driver - error creating
 acceptor socket.
03/05/1999 04:02:24 ANR5092E Unable to initialize TCP/IP driver - error creating
 acceptor socket.
03/05/1999 04:02:24 ANR5092E Unable to initialize TCP/IP driver - error creating
 acceptor socket.

When TCP/IP is up we have to restart ADSM to get the TCP/IP driver initialized.


Does anyone know how we can change the number of times ADSM try to initialize
TCP/IP driver?

ADSM server level: 3.1.2.15

Regards,

Tomas Norberg
Svenska Handelsbanken
email: tono02 AT handelsbanken DOT se

-----------------------------------------------------------------------`
=========================================================================