Datacom Server is being upgraded to R15.0. The user is attempting to connect to the server using the R15.0 client. This is the first attempt to connect to a server in the sandbox environment and the suspicion is TCP is not set up correctly.
Release : 15.0
Component : DATACOM SERVER
DSV00134I-Protocol = CCI entered TCPIP options ignored.
DSV00049I-CA Datacom Server Version 15.0 Initialized-#DB_SERVER
"DSV00134I-Protocol = CCI entered TCPIP options ignored"
CCI is the default so if you want to use TCP/IP, add the Datacom Server startup option: PROTOCOL=TCP or PROTOCOL=BOTH
From the Documentation:
**********************************************************
From the DATACOM TOOLS 15.1 section "Startup Options":
PROTOCOL=
Specifies the communication protocol that is used to transmit data between workstations or client applications and the Mainframe Server.
If CCI is specified, the native TCP/IP protocol (z/OS only) will not be available. All other TCP/IP parameters are ignored.
If TCP is specified, the native TCP/IP interface is initialized (z/OS only). TCPIP_PORT, TCPIP_HOST, and TCPIP_CONNECT_QUEUE can be specified or the defaults are used. See those options for their defaults. No CCI communications are allowed or seen by the Mainframe Server when using the CA Datacom Server Communication Utility (SVCOMPR) to issue commands, such as EOJ or STATUS as documented in PDC RI66876.
If BOTH is specified, both CCI and the native TCP/IP interface are initialized (z/OS only). TCPIP_PORT, TCPIP_HOST, and TCPIP_CONNECT_QUEUE can be specified or the defaults are used. See those options for their defaults. Both CCI and TCP/IP communication protocol can be used.
Either BOTH or TCP keywords are required to be able to use a JDBC Type 4 driver connection.
Valid Entries: CCI, BOTH, TCP
Default: CCI
********************************************************
Please be sure to check all the startup up options in our documentation for further detail on how each parameter is supposed to be configured. Click Here