Hi Miklos - Have you looked up the message and the recommended response? System Programmer Response: Investigate what is delaying initialization based on the value for nnnnnnn. If this is the name of a peer irlm, then that member is not sending the required XCF messages to the new member joining. This may be due to XCF messaging problems, processing problems such as DXR167E, or lack of XCF EVENTS. If the new joining member had failed prior, make sure that each existing member has issued the msgDXR137I recovery message. If 'nnnnnnn' is NOEVENT, then the problem is most likely restricted to the new joining member, and only a dump of this member and XCFAS is likely to be needed. Check the lock structure and XCF group names to ensure that the names specified for this IRLM match the names usedby all group members. You can use XCF commands to display the current members in the XCF group to see if this IRLM joined successfully. If necessary, take dumps to assist in failure analysis. Since this message can be issued because of missing interaction with other members, you may need dumps of peer SYSPLEX IRLM members, along with XCFAS If ' nnnnnnn ' is a peer irlm, then take dumps of that member and the joining member. If you wish to get the new member to successfully join, you must terminate any peer member whose name appears for 'nnnnnnn' before attempting to start the new member.
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
