mmm maintenance information=(a,bbb,cc,dd,ee,ffffffff)

mmm: MCF identifier

a: Error type

H: Invalid NIF header

P: Protocol error

X: Invalid HNA command

T: Invalid TH or RH

bbb: Matrix identification

atm: Session management matrix

snd: Send type matrix

rcv: Receive type matrix

slu: HNA2 interface processing matrix

cc: Matrix status code (maintenance information)

dd: Matrix event code (maintenance information)

ee: Incorrect data identification

00: Inquiry, response, or send-only message

10: Send confirmation

20: TH or RH

31: BIND command

4f: Initialization

c1: Send suspension

c3: Only-send completion

c9: Initial

d5: Receive rejection release

d9: Receive rejection

e2: UAP abnormal termination or retransmission impossible

ff: Invalid message type

ffffffff: Incorrect message detail code

Incorrect message detail codes are listed in the table below.

S: Proceed as indicated in the KFCA15050-E or KFCA15052-E message output immediately before this message.

O: Contact the OpenTP1 administrator.

Countermeasure: Take one of the following actions, as indicated in the table of incorrect message detail codes:

If the configuration definitions do not match

Check the remote and local system definitions, correct them, then re-execute.

If the remote system BIND parameter is invalid

For DCCM3/NIF, obtain maintenance information, then contact the maintenance personnel.

For ADM, set a valid BIND parameter value for the remote system, then re-execute.

For other than above

Obtain maintenance information, then contact the maintenance personnel.

Bit position	ee
	ff	31	20	Other than left
231	0	1: Invalid RQ code 0: Normal	1: Invalid ordinary or urgent flow identification 0: Normal	1: Invalid message length 0: Normal
230	0	1: Invalid activation type 0: Normal	1: Invalid request or response type 0: Normal	1: Invalid system ID#1 0: Normal
229	0	1: Invalid FM profile 0: Normal	1: Invalid data type 0: Normal	1: Invalid virtual terminal number 0: Normal
228	0	1: Invalid TS profile 0: Normal	1: Invalid FM header identification 0: Normal	1: Invalid message identification 0: Normal
227	0	1: Invalid PLU protocol 0: Normal	1: Invalid chain identification 0: Normal	1: Invalid message type (continuation or completion indication) 0: Normal
226	0	1: Invalid SLU protocol 0: Normal	1: Invalid confirmation response (1) identification 0: Normal	1: Invalid message type (request or answer indication) 0: Normal
225	0	1: Invalid PLU or SLU common protocol 0: Normal	1: Invalid confirmation response (2) identification 0: Normal	1: Invalid message type (response retransmission request indication) 0: No second header
224	0	1: Invalid communication mode 0: Normal	1: Invalid exception response identification 0: Normal	1: Invalid message type (extended header indication) 0: Normal
223	0	1: Invalid SLU send pacing 0: Normal	1: Invalid bracket start identification 0: Normal	1: Invalid message type (only-send indication) 0: Normal
222	0	1: Invalid SLU receive pacing 0: Normal	1: Invalid bracket termination identification 0: Normal	1: Invalid message type (send confirmation indication) 0: Normal
221	0	1: Invalid maximum SLU send RU size#2 0: Normal	1: Invalid send right assignment identification 0: Normal	1: Invalid message type (second header indication) 0: Normal
220	0	1: Invalid maximum SLU receive RU size#2 0: Normal	0	1: Invalid message type (third header indication) 0: Normal
219	0	1: Invalid PS profile number 0: Normal	0	1: Invalid NIF version number 0: Normal
218	0	1: Invalid PS profile 0: Normal	0	0
217	0	1: Invalid PLU name length#1 0: Normal	0	0
216	0	1: Invalid PLU name#1 0: Normal	0	0
215	0	1: Invalid user data length 0: Normal	0	0
214 - 20	0	0	0	0

#1

Configuration definition mismatch

Invalid system ID

The system ID specified in the ownsid and otrsid operands of the -o option for the mcftalccn command does not match the system ID of the remote system.

Invalid PLU name length, invalid PLU name

The connection destination host PLU name, specified in the pluname operand of the -l option for the mcftalcsc command does not match the PLU name of the remote system.

#2

Invalid BIND parameter of the remote system

Incorrect maximum SLU send RU size

The maximum SLU send RU size can be between 0 and 80 bytes.

Invalid maximum SLU receive RU size

The maximum SLU receive RU size can be between 0 and 80 bytes.