mmm error occurred during input mapping processing. discards input message. reason code=aa...aa, maintenance code1=bb...bb, maintenance code2=cc...cc, logical terminal name=dd...dd
- mmm: MCF identifier
- aa...aa: Reason code
- 00000001: Process-specific memory became insufficient.
- 00000002: The receive buffer size became too small.
- 00000003: The number of receive buffers became too small.
- 00000004: The map name length is invalid or the map name is not set.
- 00000005: An error occurred on the mapping service.
- 00000006: The application name is invalid.
- 00000007: The input logical segment is invalid.
- 99999990: A logic conflict occurred.
- bb...bb: Maintenance code 1
- cc...cc: Maintenance code 2
- dd...dd: Logical terminal name
- S: Discards the input message and continues processing.
- O: Contact the OpenTP1 administrator.
- Countermeasure: Take one of the following countermeasures according to the reason code:
- 00000001: Allocate sufficient process-specific memory and re-execute.
- 00000002: In the connection definition of the MCF communication configuration definition, set the message receive buffer length to a value larger than the value indicated by maintenance code 2. Then, re-execute.
- 00000003: Specify the sufficient number of message receive buffers in the connection definition in the MCF communication configuration definition and re-execute.
- 00000004: Set a map name with 1 to 6 characters and re-execute.
- 00000005: The code indicated by maintenance code 2 is the error detail code of mapping service. See the manual OpenTP1 Protocol TP1/NET/XMAP3 and correct the source of the error.
- 00000006: Set an application name with 1 to 8 characters and re-execute.
- 00000007: Set the endian of the map definition so that it conforms to the host byte order, and then start over from the map creation.
- 99999990: Contact the maintenance personnel.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.