DFS1964E DESTINATION TMEMBER NAME=nnnnnnnn NOT ACCESSIBLE, REASON CODE=xx, TPIPE NAME=yyyyyyyy


or

DESTINATION NAME=nnnnnnnn NOT ACCESSIBLE, REASON CODE=xx, LUNAME=yyyyyyyy

Explanation

The specified destination cannot be accepted for processing from an LU 6.2 device and is discarded. If the LU name is network-qualified, it can be up to 17 bytes long. The reason codes and their meanings are the following:

Code (dec)
Explanation
01
The destination name specified by the requestor from LUNAME= is for an IMS MSC destination. This type of destination is not valid for queuing messages from an LU 6.2 application program that is not on an IMS system that has MSC support for APPC.
02
The destination name specified by the requestor from LUNAME= is for a local LTERM. This type of message switch function is not supported from an LU 6.2 application program.
03
The destination name specified by the requestor from LUNAME= is for an IMS Fast Path transaction or an IMS response mode transaction. This type of transaction is not valid for queuing messages from an LU 6.2 device with an asynchronous request (ALLOCATE, SEND_DATA, DEALLOCATE).
04
The destination name specified by the requestor from LUNAME= can accept only single segments. Because multiple segments were detected from the requestor, the input is discarded (ALLOCATE, SEND_DATA, SEND_DATA).
05
The destination name specified by the requestor from LUNAME= is an IMS remote transaction name that is not acceptable. The cause could be that the destination IMS is not capable of accepting an APPC transaction.
06
If the first form of the message is issued, the reroute destination name for Message Control/Error exit specified from LUNAME= and DESTINATION NAME=, or from DESTINATION NAME=, is not accessible because the message originated in this system and there is no base LU name in this system to receive an output message.

If the second form of the message is issued, the reroute destination name for the Message Control/Error exit specified on TMEMBER NAME= and TPIPE NAME= is not accessible.

07
In a shared queues environment, the destination name specified by the requester from LUNAME= is for a dynamic (non-CPIC and non-MSC-remote) transaction. This is not allowed because APPC-entered transactions must be run on the same local IMS on which the transaction was entered. Dynamic transactions represent transactions that only run on other IMS systems in the shared queues group.
09
Rollback (ROLB) retry count was exceeded. The system is unable to process transaction.

This message appears on the IMS master terminal and the write-to-operator (WTO) terminal.

System action

The reroute request is ignored and the associated default action is performed. See DFSCMUX0 for default actions.

Programmer response

Take the appropriate action for each reason code:
Code (dec)
Action
01
Do not attempt to use an MSC-defined transaction
02
Use the DFSAPPC facility for message switch support
03
Use the synchronous process (ALLOCATE, SEND_DATA, RECEIVE_AND_WAIT)
04
Because multiple segments were detected from the requestor, the input is discarded (ALLOCATE, SEND_DATA)
05
Verify that the destination IMS is at system product level of Version 5.1
07
Determine which IMS systems in the shared queues group have the transaction defined locally, and enter the transaction on one of these systems.