Implementing security in TRS entails defining both client logins and RPCs.
Under TRS security, every client login must be defined to TRS. For each client, this login definition indicates:
The client login ID and password
A host login ID and password (optional)
Lists of the connections and host transactions available to clients using the login
Your TRS administrator can restrict client access to specific host resources by working with mainframe systems programmers and security administrators, and also by carefully defining user IDs, host IDs, transactions, and connections.
When the TRS administrator defines an RPC to TRS, these security options are available:
None
User ID
Both (user ID and password)
By defining an RPC to TRS, the TRS administrator sets security parameters for transactions associated with the RPC. Each option above indicates the type of login information passed to the mainframe when a client calls an RPC.
In enforcing TRS security, the mainframe verifies that the requesting client has authorization to access the specified transaction. If no proper authorization exists, the mainframe returns an error message.
