SystemAction: Server operation continues. Support for the TCPName and
CLIOPort server options is enabled.
User Response: None.
ANR5104E (S/390)Unableto initialize CLIO/S (IBM)TCP/IP driver - error creating listening
socket.
Explanation: The server’s CLIO/S communication driver is unable to create its
critical listening socket; therefore, CLIO/S (IBM)TCP/IP communication cannot be
initialized.
SystemAction: Server initialization continues. CLIO/S (IBM)TCP/IP
communication initialization will be retried every minute. This message will be
suppressed after being issued for the third time; however, attempts to initialize
CLIO/S communications will continue every minute until messageANR5103I is
issued indicating CLIO/S driver is ready for service.
User Response: Checkthat TCP/IP is running, and that TCPName, in the options
file, matches the name of the target TCP/IPaddress space.
ANR5105I (S/390)Interlink TCPaccess driver is ready for service on port interlink port number.
Explanation: The server’s Interlink TCPaccess communications driver is ready to
receive connection requests from clients connected through Interlink TCPaccess.
SystemAction: Server operation continues. Support for the ICSSname and
ICSPort server options is enabled.
User Response: None.
ANR5106E (S/390)Unableto initialize Interlink TCPaccess driver - error opening listen endpoint.
Explanation: The server’s Interlink TCPaccess driver is unable to create its critical
listen endpoint; Interlink TCPaccess communication cannot be initialized.
SystemAction: Server initialization continues. Interlink TCPaccess
communications will be retried every minute and this message will suppressed after
being issued three times.
User Response: Checkthat TCPaccess is running and that ICSSname, in the
options file, matches the TCPaccess subsystem name you intend to use. The
ICSSname option should match the SSN parameter of the PROC statement in the
TCPaccess startup procedure. Refer to Interlink TCPaccess publications for details.
644
Version 3 Release 7