Lists the Network error messages from N400 through N449.
Restriction:This topic applies to Windows environments only.
N406: Bad transaction program identifier: identifier.
The tp_id parameter of the APPC verb is not valid. Either the TP_STARTED verb has failed or the tp_id returned after issuing the TP_STARTED verb was not moved into the current verb control block.
N407: Bad conversation identifier: identifier.
The conv_id parameter used in an APPC verb is invalid. The most likely cause of this error is a failure on the remote system that is severe enough to deallocate the conversation.
N408: Bad logical unit alias: alias.
The local LU alias referenced is not defined. A local LU name in communication manager must be defined with an alias that matches the name of the XDB Server.
N410: Allocation failure retry. Sense code: code.
A conversation cannot be started. On a system that has allocated conversations successfully in the past, the error might be recoverable without intervention. The sense code could be used to isolate the problem.
N412: Bad conversation type parameter.
The conversation_type APPC verb parameter is invalid. Only basic conversations and mapped conversations are supported.
N418: Unknown partner mode/alias:"<".
The partner LU alias referenced is not defined. A partner LU in communication manager must have an alias that matches the PLU alias name entered when defining a location using XDBGPROF.EXE.
N433: Bad type.
The type APPC verb parameter value is invalid.
N434: Undefined transaction program name: name.
The tp_name referenced was not found. The transaction program must be defined on the host system and match the value configured using XDBGPROF.EXE. When connecting to DB2 using DRDA the tp_name is X07F6C4C2 and the tp runs in the DDF address space.
N436: Allocate not pending.
A receive_allocate APPC verb was issued and timed out before an incoming allocate request was received.
N437: Invalid process.
A process issued a receive_allocate verb that was not started by the attach manager.
N438: Security not valid.
The partner LU rejected the UserID or password used in the allocate call. Turn on security at the client using the Configuration utility. Make sure the UserID and password are valid for the host environment.
N444: Conversation type mismatch.
The partner LU rejected the allocate call because the conversation type of the local TP does not match the conversation type of the remote TP.
