mmm error occurred during system termination processing. reason code=aa...aa, maintenance code1=bb...bb, maintenance code2=cc...cc, mapping identifier=dd...dd

mmm: MCF identifier

aa...aa: Reason code

00000006: An XMAP2/W log file error occurred.

00000007: The physical map is corrupted.

00000012: The XMAP2/W module cannot be activated.

00000014: A system call error occurred in XMAP2/W.

00000015: The XMAP2/W server went down.

00000016: A client cannot be connected since the resources of the XMAP2/W server have become full.

00000019: A shared memory allocation error occurred in XMAP2/W.

00000020: The version of XMAP2/W and that of XMAP2/W/560 do not match.

00000022: A memory allocation error occurred in XMAP2/W.

00000025: A mapping service has not been activated.

00000033: A mapping service identifier has not been defined.

bb...bb: Maintenance code 1

cc...cc: Maintenance code 2

dd...dd: Mapping identifier

S: Continues processing.

O: Contact the OpenTP1 administrator.

Countermeasure: Apply one of the following countermeasures according to the reason code.

00000006: Check the log file attribute of XMAP2/W, then re-execute.

00000007: Correct the physical map, then re-execute.

00000012: Verify the incorporation of XMAP2/W, then re-execute.

00000014: Reactivate the system.

00000015: Check whether the XMAP2/W server has been activated, then re-execute.

00000016: Increase the capacity of the XMAP2/W server or reduce the number of clients. Then, re-execute.

00000019: Reactivate the system.

00000020: Verify the versions of XMAP2/W and XMAP2/W/560, then re-execute.

00000022: Reactivate the system.

00000025: Activate the mapping service, then re-execute.

00000033: Set a mapping service identifier in the TP1/NET/HNA-560/20 common definition of the MCF communication configuration definition, then re-execute.