This document describes how to set your CA IDMS CV up to use TCP/IP and how to change your ODBC data sources to use the new "IDMS" communications protocol.
With the introduction of the TCP/IP based “wire” protocol for ODBC processing in CA-IDMS/Server from r17 onwards, there is no reason to continue to use CCI for such connections.
TCP/IP based processing is more robust, reliable and faster than CCI and eliminates the need for the CCITCP & CCIENF address spaces for CA IDMS Server processing.
CA Technologies strongly recommends that clients migrate all of their ODBC processing for those clients using the CA-IDMS/Server product to the "IDMS" (or TCP/IP based) communications protocol. No application coding changes are necessary and the modifications required to implement this change are very simple.
Update CV System Generation
Use the following system generation syntax as a sample of the statements required to support the usage of TCP/IP based ODBC connections in the CV. Listed below are the customization points that you should consider:
· The PORT IS value in the listener PTERM (TCPJSRV) is what must be used later in the definition of any data sources intending to use this new communications interface. By default, the PORT number is set to 3700. This number can be changed at the discretion of your site. The port number specified must be unique within your LPAR.
· The REPEAT COUNT in the bulk PTERM definition should be set to the maximum number of concurrent connections you expect to use.
DEFAULT STATUS IS ON
DEFAULT TCP_NODELAY OPTION IS OFF
DEFAULT STACK IS DEFAULT
MAXIMUM NUMBER OF SOCKETS IS DEFAULT
MAXIMUM NUMBER OF SOCKETS PER TASK IS DEFAULT
PLUGIN MODULE IS RHDCD1IP
SERVICES FILE IS SERVICES CASE SENSITIVE
ADD LINE TCPIP
TYPE IS SOCKET
ADD PTERM TCPJSRV
TYPE IS LISTENER
PORT IS 3700
TASK IS RHDCNP3J
MODE IS SYSTEM PARM IS 'TASK=IDMSJSRV'
ADD LTERM TCLJSRV
PTERM IS TCPJSRV
ADD PTERM TCP0001
TYPE IS BULK
REPEAT COUNT IS 49
ADD LTERM TCL0001
PTERM IS TCP0001
For more information, see Defining the CA IDMS System Using TCP/IP.
Work with your Mainframe Network Security Administrator
Access to mainframe-based ports are often times secured behind a network firewall. If such is the case at your site, you will need to work with your mainframe network security administrator to gain access to whatever "listener" port number you selected in your TCPJSRV PTERM definition.
Ensure that Task Code RHDCNP3J is Unsecured
If task-level security is enabled on your CA-IDMS CV, then you must bypass security for the RHDCNP3J task. The TCP/IP line driver invokes task RHDCNP3J before the user-id and password are received. Therefore, task code RHDCNP3J must be unsecured and executable by any user.
You can achieve this directly in your RHDCSRTT assembly with this macro entry:
Or you can GRANT it to PUBLIC with these security definitions:
CREATE RESOURCE CATEGORY ODBC_TCPIP
ADD TASK RHDCNP3J
GRANT EXECUTE ON CATEGORY ODBC_TCPIP TO PUBLIC
The task code specified in the TASK= clause in the listener PTERM (IDMSJSRV by default) is executed after the user-id and password are received and as such it can be used to implement security to allow specific users and groups access to the connection being defined.
Change Data Source definitions to use protocol IDMS
To change your CA IDMS data source definitions to use the wire protocol, go into the ODBC Data Source Administrator application, click either the User DSN or System DSN tab as appropriate, and then click on the data source you wish to change.
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AJZrAAO" alt="pic1.jpg" width="471" height="390">
Click Configure, and then click the Server tab. Select the "IDMS" Communications Protocol. Then specify the host name of the LPAR where your CV is running and the PORT NUMBER as defined in the listener PTERM.
<Please see attached file for image>
<Please see attached file for image>style="display: block; margin-left: auto;" src="/servlet/servlet.FileDownload?file=0150c000004AJZsAAO" alt="pic2.jpg" width="462" height="434">
Click Apply, OK and then OK again to exit the ODBC Administrator.