ADSM-L

Problem when TCP/IP is started after ADSMserver

1999-03-05 03:46:29
Subject: Problem when TCP/IP is started after ADSMserver
From: Tomas Norberg <tono02 AT HANDELSBANKEN DOT SE>
Date: Fri, 5 Mar 1999 09:46:29 +0100
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
<Prev in Thread] Current Thread [Next in Thread>