ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

TCPLINE and TCP Port number for CA IDMS Web Services

book

Article ID: 187603

calendar_today

Updated On:

Products

IDMS IDMS - Database

Issue/Introduction

In the process of installing CA IDMS Web Services, specific LINE, PTERM, and LTERM definitions are required in the Sysgen. Some questions may arise as part of that process. 

Environment

Release : 19.0 or any fully supported release

Component : IDSERV

Resolution

When implementing CA IDMS Web Services, specific syntax is required in defining the TCPIP LINE, LTERM(s), and PTERM(s) but we don't enforce use of any specific name(s) or port number(s).

The TCP/IP connection needs 'listener' Pterms associated with the TCPIP line; and you can define multiple LISTENER Pterms within the TCPIP line if you want to. Each listener PTERM must have a unique Port number as well as a PARM IS TASK=xxxxxxxx', where xxxxxxx is a taskcode. Most sites just use a single TCIP line and specify task IDMSJSRV.

If you check our documentation for LINE definitions, it indicates that a type of SOCKET must be specified in order to use generic listener Lterms for DDC & for TCPIP. That's here:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/database-management/ca-idms/19-0/using/using-system-generation/teleprocessing-network-statements/line-statement/line-statement-parameters.html

If you look a little further in the same manual, you'll see details about the SOCKET. A synopsis is on this page, with detailed syntax & parms in the subsequent sections:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/database-management/ca-idms/19-0/using/using-system-generation/teleprocessing-network-statements/socket.html
 
However, some sites require (or desire) the ability to have both secure and unsecure connections to the CV via Web services. To implement this requires two different Pterm/Lterm 'Listener' pairs, one for each type connection; and they can both be on the same Line. These Pterms can be named whatever you like; TCPWSRV is just the default name we provide and suggest, to make it's purpose easily recognizable. The Port number for each TCPIP 'Listener' must be specified in the sysgen definition, and must be unique. The port-number/host-name (or IP address) combination must be unique across the LPAR. This means that a port assigned to a listener pterm cannot be shared across CVs within the same LPAR. However, these 'listener' Pterms can share the same task code if you like, or they can each have a unique task code. The main reason why different task codes might be desired is in case a site would like to specify different limits for each one.   
 
For the secured connection the Listener Pterm will be used for the inbound connection, and this must be specified in your PAGENT policy if you have employed that; PAGENT is a CISCO tool that runs on a CISCO router and directs traffic. This is equivalent to the ATTLS (Application Transparent Transport Layer Security).
 
 At run-time, the Web Services client will need to specify which port it wants to use- the secure or unsecure one.  
 
When implementing Web Services across multiple IDMS CVs, each CV (running on the same LPAR) must have a unique Listener Port.   The combination of HOST-NAME and Port-Number must be unique across the network.
 

Additional Information

Documentation for the Sysgen telecommunications definitions (Lines, etc) can be found here:
 
Details about definining the Socket type Line are found here: