OpenTP1 Version 7 Messages
KFCA14865-I
mmm connection name=aa....aa logical terminal name=bb....bb kind=cc....cc receive buffer length=dd....dd received message length=ee....ee unreceived message length=ff....ff
- This message reports additional information when a reception buffer overflow is detected. It is output together with the KFCA14806-W and KFCA14816-E messages.
- mmm: MCF identifier
- aa....aa: Connection name (connection ID of MCF communication configuration definition (mcftalccn -c))
- bb....bb: Logical terminal name (logical terminal name of MCF communication configuration definition (mcftalcle -l))
- cc....cc: Segment assembly type
- MASM: Assembly facility for received messages
- UOC (STD): UOC for determining input segment, provided as standard with TP1/NET/TCP/IP
- UOC (USR): UOC for determining input segment, specific to user
- dd....dd: Length of buffer that stores received messages
- ee....ee: Received message length
- ff....ff: Unreceived message length
- For MASM or UOC (STD) segment assembly types
- The difference between the message length specified in the message length area (first 4 bytes of received message) and the length of already received messages
- For UOC (USR) segment assembly type
- Size of remaining relevant messages (rest_data_size of dctcp_sguoc_prot)
- Countermeasure: Determine whether the total length of received messages (the sum of already received messages and unreceived messages) is appropriate.
- If total length of received messages is appropriate:
- Carefully review the length of the buffer (in mcftbuf -g length) specified in the buffer group definition.
- If total length of received messages is not appropriate:
- If the segment assembly type is MASM or UOC (STD), carefully review the remote system. If the segment assembly type is UOC (USR), carefully review the remote system and the user-specific UOC for determining input segment.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.