Why do processes go into HOLD HE queue? (SCI51379)

Answer

1) If the session cannot be established with the remote system, then the process will go through all short term waits, then all long term waits before placing the process into the HO HE queue.  At that point, someone would have to manually release those processes in HO HE using the direct command cha proc pnum=# release;

2) If the problem was not a "session unable to establish error" which would have put the process in to a timer retry, but rather an error that required manual intervention of some type, "SDIP_CALL: NAME TRANSLATION FAILURE". Thus there would be no reason for the process to retry.   The problem would have to be fixed before any transfer could occur.

3)  If Secure Plus is enabled, and there is a security error, the process will not retry and will go directly into the HOLD queue.

Check the netmap definition for the remote node.
Check DNS name is correct and correct port number is defined in netmap.cfg.  Can DNS name be PING'ed.
Check that the remote side is not having any network issues.
Check that Direct processes have been started on the remote.