CA MIM Resource Sharing CA RS 1402 Service List

Transcription

1 CA MIM Resource Sharing CA RS 1402 Service List Release Service Description Hiper 11.9 RO65928 U0051 RC7 ABEND DURING VCF INITIALIZATION **HIPER** RO67045 MIM0100A MSG CAUSES FATAL SD23 ABEND The CA RS 1402 service count for this release is 2

2 CA MIM Resource Sharing CA RS 1402 Service List Release Service Description Hiper 11.8 NO-SRVC CA RS 1402 Contains No Service For This Release of This Product. The CA RS 1402 service count for this release is 0

3 CA MIM Resource Sharing 3 CA RS 1402 Service List for CBTDB90 FMID Service Description Hiper CBTDB90 RO65928 U0051 RC7 ABEND DURING VCF INITIALIZATION **HIPER** RO67045 MIM0100A MSG CAUSES FATAL SD23 ABEND The CA RS 1402 service count for this FMID is 2

4 CA MIM Resource Sharing CA RS PTF RO65928 Details Release Service Details 11.9 RO65928 RO65928 M.C.S. ENTRIES = ++PTF (RO65928) U0051 RC7 ABEND DURING VCF INITIALIZATION PROBLEM DESCRIPTION: A U0051 RC=07 (reserve not held when expected) or MIMplex hang can occur during MIM VCF initialization if the MIMplex is undergoing a VCF migration. If the U0051 RC=07 is experienced, the initializing system will force VCF recovery and the MIMplex will recover. In the reported case, a more preferred master joined a currently executing MIMplex, causing an automatic migration. During the migration event, another system was attempting to join the MIMplex and experienced the U0051 RC=07. The problem affects MIMplexes running with MIMINIT COMMUNICATION=CTCONLY or MIMINIT COMMUNICATION=XCF. SYMPTOMS: There are two possible scenarios: (1) The initializing system is in a 'PRE-PENDING' state (U0051 RC=07). (2) The initializing system is in a 'PENDING' state (MIMplex hang). In scenario (1), the system experiencing the U0051 RC=07 will externalize the following messages during initialization: MIM0209E ABEND U0051 in Virtual Control File Director MIM0368I VCF recovery INITIATED - VCF SUBTASK ABEND The following messages may also be observed: DUMP TITLE=MIM 0000; ABEND U0051 Reason= at MIMDRVFD.MIMDRVFD+8180; Issuer=MIM External systems will issue: MIM0395I VCF recovery INITIATED by system <system name> In scenario (2), after VCF synchronization completes, the following messages will be observed... Master System: MIM0061W System <system name> in file VCF - possibly inoperative Client Systems: MIM0200W VCF ACCESS DELAYED - MASTER=<system name> In scenario (1), VCF recovery will complete and global operations will resume. In scenario (2), VCF recovery will be entered continuously, but the MIMplex will never recover. IMPACT: Depending on the scenario, VCF recovery may re-stabilize the MIMplex. If the MIMplex does not recover, a restart of MIM on all systems is required. Integrity exposures may occur if MIM terminates. CIRCUMVENTION: Avoid starting MIM if the MIMplex is currently undergoing a VCF Migration. PRODUCT(S) AFFECTED: CA MULTI-IMAGE MANAGER Release 11.8 CA MULTI-IMAGE MANAGER Release 11.9 CA MULTI-IMAGE MANAGER Release 12.0 Star Problem(s): MIM 230 Copyright (C) 2014 CA. All rights reserved. R00066-BTD119-SP1 DESC(U0051 RC7 ABEND DURING VCF INITIALIZATION). ++VER (Z038) FMID (CBTDB90) SUP ( RO43637 TR43637 TR65928 )

5 CA MIM Resource Sharing CA RS PTF RO67045 Details Release Service Details 11.9 RO67045 RO67045 M.C.S. ENTRIES = ++PTF (RO67045) MIM0100A MSG CAUSES FATAL SD23 ABEND PROBLEM DESCRIPTION: When MIM is operating on a DASD or XES control file configuration, Control File lockout situations may occur if MIM is unable to access the Control File for an extended period of time. MIM issues the MIM0100A WTOR when lockouts occur to prompt the operator for action. MIM may abend fatally when issuing this WTOR. In MIM r11.9 the abend does not occur every time, as it depends on the storage mapping of an internal control block. SYMPTOMS: A Control File lockout situation may or may not surface the MIM0100A. MIM may abend with a SD23 abend either before or after issuing the MIM0100A WTOR. IMPACT: Integrity exposures may arise from MIM going down. CIRCUMVENTION: This problem has different circumventions for r11.9 and r12.0. At MIM release level 11.9: Update your MIMMSGs definition either by restarting MIM or dynamically by using the MSGTABLE command to **include** a definition for the MIM0100A message if one does not already exist. At MIM release level 12.0: Update your MIMMSGs definition either by restarting MIM or dynamically by using the MSGTABLE command to **remove** the definition for the MIM0100A message if one exists. PRODUCT(S) AFFECTED: CA MULTI-IMAGE MANAGER Release 11.9 CA MULTI-IMAGE MANAGER Release 12.0 Star Problem(s): MIM 239 Copyright (C) 2014 CA. All rights reserved. R00067-BTD119-SP1 DESC(MIM0100A MSG CAUSES FATAL SD23 ABEND). ++VER (Z038) FMID (CBTDB90) PRE ( RO50262 ) SUP ( RO43424 RO46179 TR43424 TR46179 TR67045 )