Adding an RPC

To define a new RPC to TRS for each new Open ServerConnect transaction and map it to a region, use this procedure:

exec sgw_addrpc rpc_name, tran_id, region, security

where:

rpc_name is the TRS alias for the remote procedure. This is the name the client uses to call this RPC.

Length: maximum of 30 characters.

tran_id is the name by which the associated transaction is known on the mainframe. This is the mainframe transaction that TRS calls when a client requests the named procedure. The value of this field must be in uppercase. If the first character is numeric, the tran_id must be in quotes. Length:

For CICS: maximum of 4 characters
For IMS: maximum of 8characters
For MVS: maximum of 8 characters

region For LU 6.2, specifies the region name used to identify the LU 6.2 connection configuration in the sgw_addcon procedure.

At least one defined connection configuration must have this value specified as its region. See “Adding a connection configuration”. An entry in this field is required.

For TCP/IP, specifies the region name used to identify this TCP/IP connection in the sgw_region procedure. See “Defining regions to TRS”. This field is required.

Length: maximum of eight characters.

region (TCP/IP only) Specifies the region name used to identify this TCP/IP connection in the sgw_region procedure. See “Defining regions to TRS”. This field is required. Length: maximum of eight characters.

security specifies the type of user login information that TRS passes to the mainframe. The security parameter is not case sensitive.

The security parameter can have any of the following values to specify the information to send:

none. Do not send login information to the mainframe.

userid. Send only the user ID to the mainframe. To determine which userid is used, see the Security level source section.

This setting is not applicable when using the TRS TCP/IP Library.

both. Send both the user ID and the password to the mainframe. To determine which userid is used, see the Security level source section.
If you are using LU 6.2, TRS passes the information in the conversation-level security fields of the SNA LU 6.2 Function Management Header 5 (FMH-5).
With TCP/IP, TRS passes these fields to the Listener Transaction when the called transaction starts.

For example, if you use native CICS security, the none value corresponds to the CICS security option NONE, userid corresponds to IDENTIFY, and both corresponds to the security option VERIFY.

SNA network products vary in that some do not allow only the user ID to be forwarded; in other words, the ALREADY VERIFIED bit may not be set. Check your platform-specific DirectConnect and vendor SNA documentation for restrictions.

Example

To add an RPC named SYD2, use this command:

exec sgw_addrpc SYD2, SYD2, TESTREG, none

This maps SYD2 to the mainframe transaction named SYD2, which executes in the mainframe region named TESTREG. A user ID or password is not passed through to the mainframe when the RPC is invoked.