There are zaps available from IBMLink.
First, be sure module dmssvm5 is at the v3 r5 m22 level. See apar ow25040
below. Then apply the zap in apar pq19589 also below.
--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
Item OW25040
Item OW25040
APAR Identifier ...... OW25040 Last Changed..98/04/06
SVM MOD 22 REFRESH
Symptom ...... NF NEW FUNCTION Status ........... CLOSED UR1
Severity ................... 4 Date Closed ......... 97/08/19
Component .......... 5695DF119 Duplicate of ........
Reported Release ......... 1C0 Fixed Release ............ 999
Component Name DFSMS/MVS REUSE Special Notice
Current Target Date ..97/12/06 Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 1B0 : UW41096 available 97/09/29 (F709 )
Release 1C0 : UW41097 available 97/09/29 (F709 )
Release 1D0 : UW41098 available 97/09/29 (F709 )
Release 100 : UW41099 available 97/09/29 (F709 )
Parent APAR:
Child APAR list: OW28755
ERROR DESCRIPTION:
SVM modification level 22.
Symptoms for problems to be fixed in this level:
1) ABEND0C4 in SVMPROG when a LOAD_PROGRAM is done for a
module less than 9 bytes in size that gets loaded in the last
two words of a page in storage.
2) EZY2621E Server terminating: SVM does not support this
level of the FTP server. The problem only happens when
there are three or more TCP/IP images running.
Additional symptoms:
MSGEZY2658W EZY2658W Domain name unknown, GETHOSTBYNAME() error
LOCAL FIX:
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: IBM program products requiring SVM mod 22. *
****************************************************************
* PROBLEM DESCRIPTION: Upgrade to SVM mod level 22. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Item PQ19589
APAR Identifier ...... PQ19589 Last Changed..99/01/02
ADSM/MVS SERVER RECEIVES ANR5092E UNABLE TO INITIALIZE TCP/IP
DRIVER - ERROR CREATING ACCEPTOR, WHEN RUNNING ON OS/390 V2R6.
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 2 Date Closed ......... 98/10/29
Component .......... 565511901 Duplicate of ........
Reported Release ......... 310 Fixed Release ............ 999
Component Name ADSM MVS/VM SRV Special Notice
Current Target Date ..99/01/01 Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 310 : UQ23882 available 98/12/04 (F812 )
Parent APAR:
Child APAR list:
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.
LOCAL FIX:
The ZAP below is available for the current DFSMS SVM module for
ADSM/MVS levels of 3.1.1.3 and below:
//DSMLINK JOB (L798160,K9,021,68L),MVSSERVER,
// TIME=60,REGION=4M,
// MSGCLASS=H,USER=L798160
//* This ZAP will modify DMSSVM5 load module modification 22
//* to provide relief for TCP/IP V3.5 operation.
//* ZAP instructions:
//* 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
/*
The following APAR fix is available for ADSM/MVS 3.2.1.0.
This APAR fix only applies to the 3.1.2.0 level. At any lower
ADSM level the above ZAP will have to be used.
++APAR(AQ19589).
++VER(Z038) FMID(JDS3310) PRE(UQ20342).
++ZAP(ANRSVM5) DISTLIB(AANRLOAD).
NAME ANRSVM5 DMSSVM5
VER 01F258 00020302
REP 01F258 00020305
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: *
ADSM MVS V3 server
****************************************************************
* PROBLEM DESCRIPTION: *
ANR5092E unable to initialize TCP/IP driver. ADSM is unable
to initalize TCP/IP communication on OS/390 R6.
****************************************************************
* RECOMMENDATION: *
Apply PTF when available.
****************************************************************
Add 0305 to the table of support TCP images.
In <5D88BE4FFA43D211BB1B000092A72D95A6F6DE AT mail.va DOT gov>, on 07/12/99
at 10:38 AM, "Whitwell, Andy" <Andy.Whitwell AT MAIL.VA DOT GOV> said:
>Our site recently upgraded to OS/390 v3.6, Communications Server v2.6, and
>MVS TCP/IP v3.5. ADSM is at version 2, release 1, level 0.18/0.18. ADSM is
>no longer able to communicate using TCP/IP and issues an ANR5092E message.
>In the server option file IUCV is set to *NONE*, TCPNAME is set to the
>correct name, and TCPPORT is set to 1500 (as is MVS TCP/IP).
>Does anyone know of a patch, fix, or bailing wire and spit solution to
>getting this older version of ADSM talking to the newer MVS TCP/IP software?
>Thanks.
>Andy Whitwell
|
