mmm error occurred during input mapping. reason code=aa...aa, maintenance code1=bb...bb, maintenance code2=cc...cc, connection name=dd...dd, logical terminal name=ee...ee
- mmm: MCF identifier
- aa...aa: Reason code
- 00000001: Insufficient process-specific memory.
- 00000002: Insufficient receive buffer length.
- 00000003: Insufficient number of receive buffers.
- 00000004: The data stream of the extended host access message is incorrect.
- 00000005: Code conversion was unsuccessful.
- 00000007: The map server identifier is defined.
- 00000008: The specified device name is invalid.
- 00000016: The loaded physical map was created by other than XMAP2/W.
- 00000017: In the loaded physical map, the user map bits in OPH and IPH are on.
- 00000018: The reserved item name in the map definition statement is invalid.
- 00000019: A value other than an INC constant, defined in the map definition statement, appeared in the receive message.
- 00000021: An XMAP2/W log file error occurred.
- 00000023: The physical map has been destroyed.
- 00000024: Resource allocation failed when the mapping service was opened for XMAP2/W.
- 00000027: The physical map is not found.
- 00000028: The XMAP2/W module cannot be activated.
- 00000029: In XMAP2/W, there is insufficient memory to load the physical map.
- 00000030: A system call error occurred in XMAP2/W.
- 00000031: The XMAP2/W server went down.
- 00000032: No client can be connected because the XMAP2/W server resource is full.
- 00000033: The physical map is too large.
- 00000035: A shared memory allocation error occurred in XMAP2/W.
- 00000036: XMAP2/W and XMAP2/W/560 are of different versions.
- 00000038: A memory allocation error occurred in XMAP2/W.
- 00000039: The is insufficient local memory for the mapping service.
- 00000040: There is insufficient shared memory for the mapping service.
- 00000041: The mapping service has not been activated.
- 00000044: An input/output error occurred for XMAP2/W.
- 00000045: A macro that declares that the mapping service facility should be used is not specified in the main function of TP1/NET/HNA-560/20.
- 00000046: The mapping service attribute definition contains an error.
- bb...bb: Maintenance code 1
- cc...cc: Maintenance code 2
- dd...dd: Connection name
- ee...ee: Logical terminal name
- S:
- When the reason code is 00000001
- Releases the connection.
- When the reason code is 00000002 to 00000008 or 00000023 to 00000046
- Ignores the input message and continues processing.
- When the reason code is 00000016 to 00000019 or 00000021
- Continues processing.
- For any other reason code
- Discards the input message and continues processing.
- O: Contact the OpenTP1 administrator.
- Countermeasure: Take whichever of the following actions is appropriate for the displayed reason:
- 00000001: Allocate sufficient process-specific memory, then re-execute.
- 00000002: Increase the receive buffer length in the MCF communication configuration definition, then re-execute.
- 00000003: Increase the number of receive buffers in the MCF communication configuration definition, then re-execute.
- 00000004: Contact the maintenance personnel.
- 00000005: Contact the maintenance personnel.
- 00000007: Specify the mapping service identifier in the TP1/NET/HNA-560/20 common definition of the MCF communication configuration definition, then re-execute.
- 00000008: Specify the device name in the logical terminal definition of the MCF communication configuration definition, then re-execute.
- 00000016: Create XMAP2/W, then re-execute.
- 00000017: Re-execute using the physical map created by XMAP2/W.
- 00000018: Check the reserved item name in the map definition statement. If the reserved item name is found to be correct, contact the maintenance personnel.
- 00000019: Check the INC constant in the map definition statement. If the INC constant is found to be correct, contact the maintenance personnel.
- 00000021: Check the XMAP2/W log file attributes, then re-execute.
- 00000023: Correct the physical map, then re-execute.
- 00000024: Check MAPCNT of the mapping service attribute definition, then re-execute.
- 00000027: Check that the physical map library contains a physical map, then re-execute.
- 00000028: Check that XMAP2/W has been installed, then re-execute.
- 00000029: Check the memory for loading a physical map with XMAP2/W, then re-execute.
- 00000030: Reactivate the system.
- 00000031: Check that the XMAP2/W server is active, then re-execute.
- 00000032: Increase the number of XMAP2/W servers or reduce the number of clients, then re-execute.
- 00000033: Check mapsize of the XMAPC server attribute definition file, then re-execute.
- 00000035: Reactivate the system.
- 00000036: Check the XMAP2/W and XMAP2/W/560 versions, then re-execute.
- 00000038: Reactivate the system.
- 00000039: Allocate sufficient memory, then re-execute.
- 00000040: Check MAPNAME, MAPCNT, and POOLSIZ, specified in the mapping service attribute definition, then re-execute.
- 00000041: Activate the mapping service, then re-execute.ause of the input/output error, remove it, then re-execute.
- 00000044: Determine the cause of the input/output error, remove it, then re-execute.
- 00000045: Declare that the mapping service facility should be used in the main function of TP1/NET/HNA-560/20. Or, correct the specification of MAPPATH in the mapping service attribute definition, then re-execute.
- 00000046: Check and correct the mapping service attribute definition, then re-execute. If the cause cannot be identified, contact the maintenance personnel.
- Other value: A failure has occurred which is not mentioned in the reason code list.
- The last four digits of maintenance code 2 indicate the return code for XMAPC.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.