SOCKET Usage

Teleprocessing Network Statements › SOCKET › SOCKET Usage

SOCKET Usage

To use the CA IDMS Server "wire protocol" drivers, define a listener PTERM/LTERM pair for the built-in server program, IDMSJSRV. This PTERM must specify the RHDCNP3J task defined during installation, SYSTEM mode, and the port used by the driver. The default port, 3709, is used by the drivers and registered with the Internet Assigned Number Authority (IANA) for CA IDMS. 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.

Note: Be advised that all CA IDMS systems that have task-level security turned ON must turn off security for the RHDCNP3J task. The following SECRTT entry example displays how this can be performed. Tailor this entry to meet your site-specific requirements in your CA IDMS SRTT table.

#SECRTT TYPE=OCCURRENCE,RESNAME='RHDCNP3J',
   RESTYPE=TASK,
   SECBY=OFF

Additional listener options parameters can be specified as keyword-values pairs in the PARM string on the PTERM definition. The following are the PARM keyword guidelines:

Options are not case-sensitive.
Options can appear in any order, separated by commas, with no embedded spaces in the string (leading spaces are ignored).
If an error occurs, the server writes a message to the DC log and ignores the rest of the options.

The parameters are:

ACCt=profile-key-name: Profile key name for accounting information. If specified, any accounting information supplied by the client as part of the signon is added to the user profile. This allows SQL statements access to the accounting information using the PROFILE function. Procedures written in COBOL or CA ADS can use the IDMSIN01 GETPROF callable service to access the accounting information.
BUFLen=default-length: Length of the default buffer used for data received from and sent to the client. The default buffer is allocated when the task starts and freed when the task ends. Larger buffers are allocated dynamically as needed for individual requests and freed immediately after results are returned. The default is 1024 bytes. Specifying a larger buffer can minimize storage allocation requests while using more of the storage pool. The client can override this value.
BUFMax=max-length: Maximum length the client interface can specify for the default buffer.
TASK=task-code: Specifies the default task code used for signon security, timeouts, and as the next task after a pseudo converse. The IDMSJSRV task is defined during installation as a model task for this purpose. The client can override this task code.
ATTACH=Y: Causes IDMSJSRV to end the initial task immediately after processing the signon request. The specified task is attached on the next request from the client interface. If not specified (or No), IDMSJSRV copies the timeouts from specified task to the current task, which ends when (and if) explicitly requested by the client interface.
TIMeout=seconds: Specifies the maximum timeout the client can request for the external wait or resource timeout interval. A value of -1 allows the client interface to specify any value. A value of 0, the default, takes the value from the task or system default.