mmm error occurred during output 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 send buffer length.

00000003: Insufficient number of send buffers.

00000005: Code conversion failed.

00000007: The map name length is incorrect or no map name has been specified.

00000008: No mapping service identifier has been defined.

00000009: The device name is incorrect.

00000012: Multiple-segment sending of a terminal-side UAP activation request message is impossible.

00000013: Multiple-segment sending of a system message is impossible.

00000014: The UAP name specification of the terminal-side UAP activation request message is invalid.

00000015: The user data specification for the terminal-side UAP activation request message 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 of the map definition statement is invalid.

00000020: The cursor address specified by UAP using the control item of the map definition is invalid.

00000021: An XMAP2/W log file error occurred.

00000022: The display operation, specified in the map definition statement for issuing the system message, is ERASE.

00000023: The physical map has been destroyed.

00000024: Resource allocation was impossible when the mapping service was opened for XMAP2/W.

00000025: The map name specified by UAP is invalid.

00000027: No physical map is found.

00000028: The XMAP2/W module cannot be activated.

00000029: There is insufficient memory to load the physical map with XMAP2/W.

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: There is insufficient local memory for the mapping service.

00000040: There is insufficient shared memory for the mapping service.

00000041: The mapping service is not active.

00000042: A macro is not specified that declares that the mapping service facility should be used in the main function of TP1/NET/HNA-560/20. Or, the specification of MAPPATH in the mapping service attribute definition contains an error.

00000043: The mapping service attribute definition contains an error.

00000044: An input/output error occurred in XMAP2/W.

00000047: The message type specified by UAP is invalid.

00000048: The message serial number specified by UAP is invalid.

00000049: The final character could not be converted to a code because the send data ended at byte 1 of the 2-byte code.

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 00000015 or 00000022 to 00000048

Terminates the session when the initial screen is displayed or a branch is made with an ordinary message.

Ignores the ordinary message and continues processing if a response is made to that message.

When the reason code is 00000016 to 00000021 or 00000049

Continues processing.

For any other reason code

Terminates the session if there is a branch from the initial screen display or an ordinary message.

Discards the message and continues processing if there is a response from an ordinary message.

O: Contact the OpenTP1 administrator.

Countermeasure: Take whichever of the following actions is appropriate for the displayed reason code:

00000001: Allocate sufficient process-specific memory, then re-execute.

00000002: Increase the send buffer length of the MCF communication configuration definition, then re-execute.

00000003: Increase the number of send buffers in the MCF communication configuration definition, then re-execute.

00000005: Contact the maintenance personnel.

00000007: Check the uap length in the UAP send buffer, then re-execute.

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

00000009: Specify the device name in the logical terminal definition of the MCF communication configuration definition, then re-execute.

00000012: Check the terminal-side UAP activation request message, then re-execute.

00000013: Check the host UAP associated with the system message, then re-execute.

00000014: Specify a valid UAP name length for the terminal-side UAP activation request message, then re-execute.

00000015: Specify a valid user data length for the terminal-side UAP activation request message, then re-execute.

00000016: Create a physical map with XMAP2/W, then re-execute.

00000017: Re-execute using the physical map created by XMAP2/W.

00000018: Check the reserved item name for the map definition statement. If the reserved item name is found to be correct, contact the maintenance personnel.

00000020: Check the cursor address specified by UAP using the control item of the map definition statement. If the cursor address is found to be correct, contact the maintenance personnel. (When displaying the initial screen, do not specify the CURS definition of the map definition statement.)

00000021: Check the XMAP2/W log file attributes, then re-execute.

00000022: Check the display operation specified in the map definition statement, then re-execute.

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

00000024: Check MAPCNT of the mapping service attribute definition, then re-execute.

00000025: Check that all map names specified by UAP are blank. If all the map names are found to be blank, contact the maintenance personnel.

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 into which a physical map is loaded by 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 versions of XMAP2/W and XMAP2/W/560, then re-execute.

00000038: Reactivate the system.

00000039: Allocate the sufficient memory, then re-execute.

00000040: Check the MAPNAME, MAPCNT, and POOLSIZ specified in the mapping service attribute definition, then re-execute.

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

00000042: 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.

00000043: Check and correct the mapping service attribute definition, then re-execute. If the cause cannot be identified, contact the maintenance personnel.

00000044: Determine the cause of the input/output error, remove it, then re-execute.

00000047: Check the message type specified by UAP. If the message type is found to be correct, contact the maintenance personnel.

00000048: Check the message serial number specified by UAP. If the message serial number is found to be correct, contact the maintenance personnel.

00000049: Correct the send data length specified by UAP.

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.