Thank you for your answers.

We are using TCP/IP 3.4 (OS/390 2.5) and the server option: TCPName (ADSM server
level: 3.1.2.15).

We now get TCP/IP up before  ADSM is started

 Regards,

        Tomas Norberg
        Svenska Handelsbanken
        email: tono02 AT handelsbanken DOT se






Bob Labrie <labrie AT US.IBM DOT COM> on 99-03-07 14:47:01

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Tomas Norberg/TONO02/SHB)
Subject:  Re: Problem when TCP/IP is started after ADSMserver






Hi,  There was a problem using TCP/IP V3.1 when the ADSM server option
TCPName was not
           TCPIP.  If the TCP/IP started task was named TCPIP310, for
example, and the ADSM server
            option TCPNAME  was TCPIP310, ADSM would try establishing an
API with the image
            TCPIP310.  If it failed the first time ADSM would try
initializing the API with the default
             TCPName of TCPIP.  You'll see 7 or 8 ANR5092 messages until
they are suppressed.
              ADSM contiues to attempt establishing the TCP/IP API,  you
just don't see the error messages.
             The same logic  applies when using TCP/IP 3.2 &3.4 when using
the IUCVTCPIP parameter in
              the ADSM server option file.   The IUCVTCPIP keyword in the
ADSM server option file forces
              ADSM to use the TCP/IP 3.1 type interface when running on
TCP/IP V3.2 or V3.4 and should not
              be used unless you are unable to conduct TCP/IP sessions
without it.
Thanks, Bob La Brie ADSM Development



Nathan King <nathan.king AT USAA DOT COM> on 03/05/99 10:16:16 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Bob La Brie/Tucson/IBM)
Subject:  Re: Problem when TCP/IP is started after ADSMserver





We had the same problem our solution was to have automation key-in on the
full initialization of TCP-IP, then have ADSM start.

Nathan

        -----Original Message-----
        From:   Tomas Norberg [SMTP:tono02 AT HANDELSBANKEN DOT SE]
        Sent:   Friday, March 05, 1999 2:46 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Problem when TCP/IP is started after ADSMserver

        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