---------------------------- Top of message ---------------------------- >>--> 05-07-01 13:42 S.SHEPPARD (SHS) Unable to init TCP/IP dri There were major changes in OS/390 TCPIP at, I believe, Release 2.5. If you migrated from a release prior to that one, that's probably your problem. Not being the TCPIP expert, I'm not sure what the specific changes were. Sam Sheppard San Diego Data Processing Corp. (858)-581-9668 -----------------------------------------------------------------------` ---------------------------- Top of message ---------------------------- >>--> 05-07-01 13:36 ..NETMAIL () Unable to init TCP/IP dri Date: Mon, 7 May 2001 13:13:09 -0700 From: "Glass, Peter" <[EMAIL PROTECTED]> Subject: Unable to init TCP/IP driver in OS390 2.10 To: [EMAIL PROTECTED] _________________________________Top_of_Message_________________________________ We just upgraded our development MVS to OS390 2.10. Since then, ADSM generates this error: ANR5092E Unable to initialized TCP/IP driver - error creating acceptor socket. TCP/IP is up and running, and still under the same name that it's always had. We are running ADSM Version 3, Release 1, Level 2.50. Would this be a release incompatibility issue (we're aware that this release of ADSM is no longer supported), between ADSM and the new OS390? Any other ideas on what may cause this error? Thanks, in advance, Peter Glass Distributed Storage Management (DSM) Wells Fargo Services Company > * 612-667-0086 * 866-249-8568 > * [EMAIL PROTECTED] > -----------------------------------------------------------------------`
