What are the steps required to establish a TCP/IP connection from a PC to an IDMS mainframe, using CA IDMS Server?
PCs and web applications can connect to an IDMS mainframe using various means. Using TCP/IP is the most efficient.
To establish a connection from the PC to the mainframe you will need to have installed both the CA IDMS Server and the IDMS SQL option. With those in place, there are several steps to review.
First, you'll have to ensure that the TCP/IP configuration is defined to the mainframe appropriately. Here's the syntax you can use to add it if it's not there; this is also the syntax you should see if it is installed. This is the syntax to install the TCPIP line and the listener TCPJSRV. In case it's helpful, this information is documented on page 28 in the IDMS Server 17.0 User Guide in Chapter 3: "Defining the CA IDMS System Using TCP/IP".
Basically the SYSGEN must have these definitions:
ADD LINE TCPIP TYPE IS SOCKET MODULE RHDCD1IP.
ADD PTERM TCPJSRV
TYPE IS LISTENER
PORT IS 3781 (whatever port number)
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 99.
ADD LTERM TCL0001 PTERM IS TCP0001.
You would add as many PTERM/LTERM pairs (using the BULK REpEAT COUNT clause) as you will need for access to IDMS Server for this CV. Many clients add about 100 PTERMS/LTERMS to allow 100 concurrent JDBC or ODBC connections.
Second, the default port number for CA IDMS is 3709. This can be used if only a single DC/UCF system is used on the host machine. Otherwise, a recommended convention is to append the system number to 37. (Example 3781 above).
You'll also need to address security for the task RHDCNP3J & for the task specified on the listener Pterm. You must grant execute authority on task RHDCNP3J to group PUBLIC or all groups because the line driver invokes it before the user id and password are received. Alternatively, you can turn off security for task RHDCNP3J by including an entry in the security module RHDCSRTT. You must also ensure that EXECUTE privilege for the task defined in the TCPIP listener PTERM (ideally IDMSJSRV, as in the syntax above) has been granted to the user doing the connect.
Here's the syntax for RHDCSRTT definition to exclude security for Task RHDCNP3J, if that's the option you want to go with:
#SECRTT TYPE=OCCURRENCE, X
Third, we have many Knowledge Base documents available on Support Online addressing specific topics that may be relevant here. Listed below are some on troubleshooting TCPIP problems; you may find them useful as we work through this:
TEC446639 Checklist for TCP/IP Listener Implementation
TEC507311 Message DC301001 Invalid Device TYPE new TCPIP line
TEC543621 TCPIP is not active on IDMS. Log shows DC088071
TEC525582 At IDMS r17.0; there's a new SYSGEN option for TCPIP.
Finally, please review the IDMS Server 17.0 User Guide Chapter 3 entitled "Defining the CA IDMS System Using TCP/IP". It contains each of the steps to implement TCP/IP for the wireless protocol.
The IDMS Server 17.0 User Guide Chapter 3 entitled "Defining the CA IDMS System Using TCP/IP" contains each of the steps to implement TCP/IP for the wireless protocol.
User Guide r17
Nice write-up Jen.