---------------------------- Top of message ----------------------------
>>--> 03-11-99  09:59  S.SHEPPARD     (SHS)    Re: TCPIP error OS/390 2.
>>--> 03-11-99  09:59  S.SHEPPARD     (SHS)    Re: TCPIP error OS/390 2.

Problem is with the SVM code.  Following is the text of APAR PQ19589
which talks about the incompatibility introduced in TCPIP 3.5 (OS/390
2.6):

ERROR DESCRIPTION:
OS/390 V2R6 ships a new level of TCP/IP, 3.5. When ADSM
initializes he checks the level of TCP/IP. The current ADSM
servers do not recognize TCP/IP 3.5. This results in the
ANR5092E Unable to initialize TCP/IP driver - error creating
acceptor. The SVM code that does this check needs to be
modified to recognize this new level of TCP/IP. Since ADSM will
now be incorporating this SVM code into the ADSM product this
needs to be fixed in this new ADSM/SVM code.

They also supplied a zap. Don't know if it will work with ADSM v2, since
I believe it is out of service.

//*  ZAP dependencies:
//*     This ZAP applies only to SVM V2 R5 M22
//*  ZAP completion codes:
//*     AMASPZAP should complete with return code 0
//*
//STEP1 EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=H
//SYSLIB DD DSN=ADSM.LINKLIB,DISP=SHR
//SYSIN DD *
 NAME DMSSVM5 DMSSVM5
 VER 01F258 00020302
 REP 01F258 00020305

Sam Sheppard
shs AT sddpc.sannet DOT gov
San Diego Data Processing Corp.
-----------------------------------------------------------------------`
---------------------------- Top of message ----------------------------
---------------------------- Top of message ----------------------------
>>--> 03-11-99  09:13  ..NETMAIL     (001)     Re: TCPIP error OS/390 2.
>>--> 03-11-99  09:13  ..NETMAIL     (001)     Re: TCPIP error OS/390 2.
Date: Thu, 11 Mar 1999 11:48:16 -0500
From: "Jeff T" <tothj AT FAATCRL.TC.FAA DOT GOV>
Subject: Re: TCPIP error OS/390 2.6
To: <ADSM-L AT VM.MARIST DOT EDU>

>ANR5092E Unable to initialize TCP/IP driver