DFS3553E AN ISC TCPIP SESSION FAILED TO INITIATE - NODE = nodename USER = username RSNCD=nnn

For requests that originate from IMS, the node name displayed in the message text might be provided by a Logon exit routine (DFSLGNX0), a logon descriptor, the NODE keyword in an /OPNDST command, or by the NAME keyword in a TERMINAL system definition macro.

For requests that originate from the session partner, the node name displayed in the message text is provided by the session partner.

003

IMS data communications processing has not been started. Issue the /START DC command and attempt to initiate the session again.

004

An SOPB storage request failed for a newly created IMS terminal control block. This error is an internal error. Collect the documentation indicated in the problem determination section and contact IBM® Software Support for assistance.

005

An installation-supplied Logon exit routine (DFSLGNX0) specifies both AUTOSIGN and NOAUTSGN for a static ISC TCP/IP terminal. The AUTOSIGN and NOAUTSGN values are mutually exclusive.

007

The session partner attempted to start an ISC TCP/IP session with a terminal that is not statically defined to IMS and ETO is not enabled in this IMS system. Either statically define a terminal by coding the TYPE and TERMINAL system definition macros and the ISCTCPIP keyword in the DFSDCxxx PROCLIB member, or enable ETO dynamic terminals by specifying ETO=Y in the IMS or DCC startup procedure and coding an ETO logon descriptor for the terminal.

009

The system latch cannot be obtained. This error is an internal error. Collect the documentation indicated in the problem determination section and contact IBM Software Support for assistance.

010

An installation-supplied Logon exit routine (DFSLGNX0) rejected the logon attempt of a request to start an ISC TCP/IP session. Review the code of the DFSLGNX0 exit routine to determine why the logon attempt was rejected.

011

No logon descriptor was found.

012

An IMS terminal control block cannot be obtained. This error is an internal error. Collect the documentation indicated in the problem determination section and contact IBM Software Support for assistance.

013

The internal dispatcher prefix block cannot be located. This error is an internal error. Collect the documentation indicated in the problem determination section and contact IBM Software Support for assistance.

014

IMS failed to hash the IMS terminal control block. This error is an internal error. Collect the documentation indicated in the problem determination section and contact IBM Software Support for assistance.

015

The session partner attempted to start an ISC TCP/IP session with a node that does not support ISC TCP/IP.

016

The ISC TCP/IP node is stopped.

017

A /CLSDST command was issued to disconnect the target node.

018

A TCPWORK storage request failed for a newly created IMS terminal control block. This error is an internal error. Collect the documentation indicated in the problem determination section and contact IBM Software Support for assistance.

019

A TCPWORK storage request failed for an existing IMS terminal control block. This error is an internal error. Collect the documentation indicated in the problem determination section and contact IBM Software Support for assistance.

022

The request to start a session specified a node name that has one or more existing sessions. The logon descriptor specified in this request is different from the logon descriptor in use by the existing sessions that are active with this node. Change the logon descriptor that is used in the request to start a session or specify a different node name. To see the logon descriptor that is currently in use by this node, use the QUERY NODE command.