Chapter 3: Configuring a TRS

Defining a default SQL language handler

The values you provide for defining the default SQL language handler to TRS depend on the following:

The environment on the mainframe (CICS, IMS, or MVS)
The status of TRS security (enforced or not enforced)

To define a default SQL language handler for your site configuration, use the sgw_addrpc procedure:

sgw_addrpc rpc_name, tran_id, region, security

Refer to Table 3-6 for the appropriate rpc_name and tran_id parameters, then set region and security to the appropriate values for your site.

**Table 3-6: Default SQL language handler settings by host and security settings**
TRS	CICS host (MainframeConnect)	MVS host and IMS host (OmniSQL Access Module)
TRS Security Enforced	Set rpc_name = name you create Set tran_id = AMD2	Set rpc_name = name you create Set tran_id = SYRT
TRS Security Not Enforced	Set rpc_name = SYRT Set tran_id = AMD2	Set rpc_name = SYRT Set tran_id = SYRT

If security is enforced, define the rpc_name that you create as the default SQL language handler when defining the tran_group. When security is not enforced, the default SQL language rpc_name must be SYRT.

Example

Following is an isql example of the sgw_addrpc procedure, which defines a default SQL language handler:

exec sgw_addrpc SYRT, AMD2, TESTREG, both

go

where:

Language requests are routed to MainframeConnect for DB2 UDB, which has a predefined CICS tran_id of AMD2.
TESTREG is the region parameter value that corresponds to the LU 6.2 or TCP/IP connection that provides access to the CICS region running MainframeConnect for DB2 UDB.

If TRS security were enforced for this example, the TRS system administrator would need to define a transaction group (using sgw_addtrngrp) with SYRT as the default language RPC. SYRT then would become the default SQL language handler for all TRS users assigned to that transaction group.

View this book as PDF