Jorge The <unsatisfactory people> who manage the IBM web site have removed a "Techdoc" which - I have every confidence - used to explain this problem. The Techdoc was referenced in the following post:
http://bama.ua.edu/cgi-bin/wa?A2=ind0912&L=ibm-main&T=0&F=&S=&P=54471 A possible useful explanation may be being provided here: <quote> EZZ0154I CONFIGURATION: UNABLE TO OPEN MESSAGE CATALOG ″ cfmsg.cat″ - errmsg rc/rsn Explanation: The configuration component was unable to open the configuration message catalog ″cfmsg.cat″ in the message catalog directory. The default location for the message catalog is set by the NLSPATH environment variable to be ″NLSPATH=/usr/lib/nls/msg/%L/%N&#8243;. errmsg describes the Return Code. rc is the decimal Return Code returned by catopen(). Return Codes are listed and described in the z/OS UNIX System Services Messages and Codes. rsn is the hexadecimal reason code returned by catopen(). Reason Codes are listed and described in the z/OS UNIX System Services Messages and Codes. System action: The configuration component will use the internal default messages instead of the messages from the external message catalog. Operator response: If you want to use the external message catalog, contact the system programmer to correct the error. If the default messages are acceptable, no action is necessary. System programmer response: Install the current level of the Configuration message catalog then restart TCPIP to gain access to the message catalog. If the problem persists, contact the IBM software support center. Module: EZACFMMN Procedure Name: main </quote> Chris Mason On Fri, 1 Jul 2011 12:01:56 -0500, Chris Mason <chrisma...@belgacom.net> wrote: >Jorge > >I've just spotted this but I have time only for a quick message: > >http://publib.boulder.ibm.com/infocenter/ieduasst/stgv1r0/topic/com.ibm.iea. co >mmserv_v1/commserv/1.9z/appl/FTP_Other.pdf > >Chris Mason > >On Fri, 1 Jul 2011 07:07:10 -0500, Jorge Garcia <jgarc...@mapfre.com> >wrote: > >>Hello: >> >> Last Saturday we've upgrade our production lpar to z/OS 1.10. Since last >>saturday when we enter the netstat home command we received this output: >> >>EZZ2350I MVS TCP/IP NETSTAT CS V1R10 TCPIP Name: TCPIP >>EZZ2698I -- reserved for future use -- >>EZZ2699I -- reserved for future use -- >>EZZ2700I Home address list: >>*** >>EZZ2701I Address Link Flg >>EZZ2701I Address Link Flg >>EZZ2701I Address Link Flg >>EZZ2701I Address Link Flg >> >> >>All fields are empty. In our development LPAR works fine in z/OS 1.10. >> >>We've revised: >> >>1 .- The RESOLVER config: This is our RESOLVER proc: >> >>//RESOLVER PROC PARMS='CTRACE(CTIRES00)' >>//EZBREINI EXEC PGM=EZBREINI,REGION=0M,TIME=1440,PARM=&PARMS >>//SETUP DD DSN=SYS2.TCPIP.TCPPARMS(RESOLC&SYSCLONE),DISP=SHR >> >>2 .- Content of RESOLCVR >> >>DOMAINORIGIN ES.MAPFRE.NET >>SEARCH ES.MAPFRE.NET >>SEARCH DES000.MAPFRE.NET >>SEARCH DES007.MAPFRE.NET >> >>These are our business DNS. We can entered a ping to the first IP in HOME >>PROFILE. >> >>3 .- Our etc/hosts has the correct IP (the same than HOME in PROFILE) >> >>4 .- We are searching too the netmsg.cat in /usr/lpp/tcpip.... because >>appears in some links. This file is identical between our production lpar and >>development lpar >> >>5.- In production lpar we enter the comand D TCPIP,TCPIP,NETSTAT,CON the >>system respond: >> >>D TCPIP,TCPIP,NETSTAT,CON >>EZZ2500I NETSTAT CS V1R10 TCPIP 211 >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >>-- RESERVED FOR FUTURE USE -- >> >>6 .- In development lpar we enter the same command: >> >>ro vdes,D TCPIP,TCPIP,NETSTAT,CON >>EZZ2500I NETSTAT CS V1R10 TCPIP 711 >>USER ID CONN LOCAL SOCKET FOREIGN SOCKET STATE >>BPXOINIT 00000043 0.0.0.0..10007 0.0.0.0..0 LISTEN >>CICSAD01 0000E54C 10.255.224.212..4113 0.0.0.0..0 LISTEN >>CICSAD02 0000E54E 10.255.224.212..4114 0.0.0.0..0 LISTEN >>CICSAT01 0000E4E2 10.255.224.212..3221 0.0.0.0..0 LISTEN >>CICSAT02 0000E4D2 10.255.224.212..3222 0.0.0.0..0 LISTEN >>CICSTD01 0000E548 10.255.224.212..4111 0.0.0.0..0 LISTEN >>CICSTD02 0000E549 10.255.224.212..4112 0.0.0.0..0 LISTEN >>CICSTI01 0000E4CA 10.255.224.212..4121 0.0.0.0..0 LISTEN >>CICSTI02 0000E4CC 10.255.224.212..4122 0.0.0.0..0 LISTEN >>CICSTN01 0000E4C8 10.255.224.212..4151 0.0.0.0..0 LISTEN >> >>7 .- We haven't change the profile in the upgrade to z/OS 1.10 in both lpar. >> >>8 .- When the DB2 master starts, it appears the message: >>23.29.37 STC06383 DSNL512I %DSNR DSNLILNR TCP/IP 985 >> 985 GETHOSTBYADDR(10.255.224.222) FAILED WITH >> 985 RETURN CODE=1 AND REASON CODE=00000000 >> >> 10.255.224.222 is he first IP in HOME profile. Could be connect both >>messages (netstat and gethostbyaddr)? >> >>The z/OS communication server works fine in both lpar, except the problems >>above. >> >>Regards >> >>Jorge García Juanino ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
