Troubleshooting
Problem
Sterling Connect:Direct for UNIX statistics showing errors: XIPT016I XSMG621I XSMG631I XSMG601I
Symptom
The combination of error messages below is the result of the UNIX® netmap containing a remote node definition with sess.pnode.max set higher than the remote node will allow.
The errors messages are issued when the Sterling Connect:Direct for UNIX attempts to establish more sessions than the remote node will allow.
If the remote node netmap specifies the same number of sessions as the UNIX® netmap, the messages may still be issued if the total maximum sessions of the remote node are exceeded. For example, if remote node is Sterling Connect:Direct for z/OS and the number of sessions exceeds the Sterling Connect:Direct for z/OS MAXSECONDARY init parm value. The Sterling Connect:Direct for z/OS JESMSGLG would contain a message indicating that the MAXSECONDARY value had been exceeded
- STAA005I - TASK NOT CREATED. MAX SECONDARY TASK COUNT REACHED.
The XSMG601I message text will be "SMGR (snode) didn't receive FMH68 during session start." when Secure+ is used for the connection from Sterling Connect:Direct for UNIX to the remote node.
Error Message
Without Secure+
E XIPT 09/23/2010 12:14:00 ndm_error_set(): rc=16 fdbk=0 msgid=XIPT016I stext=TCP lost the connection. System error is Broken pipe.
E XSMG 09/23/2010 12:14:00 ndm_error_set(): rc=8 fdbk=0 msgid=XSMG621I stext=A receive from the remote node operation failed.
E XSMG 09/23/2010 12:14:00 ndm_error_set(): rc=16 fdbk=16 msgid=XSMG631I stext=SMGR failed to receive an FMH. Diag=XIPT016I.
E XSMG 09/23/2010 12:14:00 ndm_error_set(): rc=16 fdbk=16 msgid=XSMG601I stext=SMGR did not receive FMH70.
E SSTR 09/23/2010 12:14:00 Session not started, SNODE:EUROPE.OS390.48, message id:XIPT016I
When Secure+ used
E XIPT 09/24/2010 10:15:51 ndm_error_set(): rc=16 fdbk=0 msgid=XIPT016I stext=TCP lost the connection. System error is Broken pipe.
E XSMG 09/24/2010 10:15:51 ndm_error_set(): rc=8 fdbk=0 msgid=XSMG621I stext=A receive from the remote node operation failed.
E XSMG 09/24/2010 10:15:51 ndm_error_set(): rc=16 fdbk=16 msgid=XSMG631I stext=SMGR failed to receive an FMH. Diag=XIPT016I.
E XSMG 09/24/2010 10:15:51 ndm_error_set(): rc=16 fdbk=16 msgid=XSMG600I stext=SMGR (snode) didn't receive FMH68 during session start.
E SSTR 09/24/2010 10:15:51 Session not started, SNODE:EUROPE.OS390.48, message id:XIPT016I
Diagnosing The Problem
To reference meaning, cause and solution for Sterling Connect:Direct messages, refer to the Message Lookup utility for your product.
Resolving The Problem
Set the session limits to the same value on both remote node entries.
Note: No change to the .local node is required.
For example, if Sterling Connect:Direct for z/OS defines a remote Sterling Connect:Direct for UNIX with maximum 4 session then the Sterling Connect:Direct for UNIX netmap should define a limit of 4 outbound sessions to the remote z/OS system.
z/OS Netmap . Adjacent node entry for remote Sterling Connect:Direct for UNIX is setting a limit of two inbound sessions.
ADJACENT.NODE=( -
(unix.node.name,port,ipaddress,TCP) -
PARSESS=(2 1) -
SESS.SNODE.MAX=2 -
ENVIRONMENT=UNIX -
)
Sterling Connect:Direct for UNIX should limit its outbound sessions in the remote node netmap entry for this Sterling Connect:Direct for z/OS system to 2 sessions.
netmap.cfg
zos.node.name:\
::descrip=zOS:\
:sess.total=4:\
:sess.pnode.max=2:\
:sess.snode.max=2:\
Historical Number
NFX9956
Was this topic helpful?
Document Information
Modified date:
24 July 2020
UID
swg21557725