Re: Unable to init TCP/IP driver in OS390 2.10
2001-05-08 17:31:21
Subject: |
Re: Unable to init TCP/IP driver in OS390 2.10 |
From: |
Bill Colwell <bcolwell AT DRAPER DOT COM> |
Date: |
Tue, 8 May 2001 17:30:42 -0400 |
Peter - I found this in IBMLink. If the displacements aren't exact
you can refit the zap.
Item PQ39436
APAR Identifier ...... PQ39436 Last Changed..01/02/07
ANR5092E AFTER UPGRADE TO OS/390 2.10 ADSM 3.1.2.40
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 2 Date Closed ......... 00/07/24
Component .......... 565511901 Duplicate of ........
Reported Release ......... 310 Fixed Release ............ 999
Component Name ADSM MVS/VM SER Special Notice
Current Target Date ..01/03/04 Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 310 : UQ49134 available 01/01/13 (F101 )
Parent APAR:
Child APAR list: PQ40811 PQ40812
ERROR DESCRIPTION:
Customer running 3.1.2.40 of adsm. After Upgrade to 2.10 of
OS/390, experiencing error message:
ANR5092E Unable to initialize TCPIP drivers
---
ADSM not recognizing this new level of TCPIP being reported
as x'0510'
LOCAL FIX:
//SVMZAP JOB MSGLEVEL=(1,1),MSGCLASS=H,CLASS=A,REGION=4M
//*
//*-------------------------------------------------------------
//* To preserve the current version of the ANRSVM5 module,
//* please make a copy of the current module prior to applying
//* this ZAP.
//*
//* NOTE: This ZAP is for the ANRSVM5 module for 3.1.2.4 server
//*
//*-------------------------------------------------------------
//* Purpose of this ZAP:
//* Modify ANRSVM5 to recognize TCP/IP level of OS/390 2.10
//*-------------------------------------------------------------
//*
//STEP1 EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=A
//* vvvvvvvvvvvv---> Replace with your library
//SYSLIB DD DSN=ADSM.LINKLIB,DISP=SHR
//SYSIN DD *
*
NAME ANRSVM5 DMSSVM5
VER 01F42C 0308FFFF
REP 01F42C 03080510
/*
/
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: *
All users of Tivoli Storage Manager for MVS and the TCP/IP
communications method.
****************************************************************
* PROBLEM DESCRIPTION: *
TCP/IP level for OS/390 2.10 is not recognized by Tivoli Storage
Manager for MVS. Server unable to complete TCP/IP
communications method initialization.
****************************************************************
* RECOMMENDATION: *
Apply PTF that contains fix for this problem when available.
****************************************************************
TCP/IP level for OS/390 2.10 is not recognized by Tivoli Storage
Manager for MVS. Server unable to complete TCP/IP
communications method initialization.
PROBLEM CONCLUSION:
Tivoli Storage Manager for MVS was modified to recognize the
TCP/IP level for OS/390 2.10.
In <A7BF798B0884D411A1AB00508BDF0B3E0305C9BE AT msgmsp17.wellsfargo DOT com>,
on 05/08/01
at 05:30 PM, "Glass, Peter" <Peter.K.Glass AT WELLSFARGO DOT COM> said:
>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
>> * peter.k.glass AT wellsfargo DOT com
>>
--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
=========================================================================
|
|
|