Under TRS security, every client login must be defined to TRS. For each client, this login definition:
Specifies the client login ID and password
Optionally specifies a host login ID and password
Includes lists of the connections and host transactions available to clients using the login
By working with mainframe systems programmers and security administrators, and by carefully defining user IDs, host IDs, transactions, and connections, the TRS administrator can restrict client access to particular host resources.
When the TRS administrator defines a remote procedure call (RPC) to TRS, these security options are available:
None
User ID
Both (user ID and password)
Each option represents the type of login information that is passed to the mainframe when a client calls the RPC. The TRS administrator sets security parameters for a transaction when defining the associated RPC to TRS.
When security is enforced at TRS, the mainframe verifies that the caller is authorized to access the requested transaction. If proper authorization exists, the transaction executes; otherwise, the mainframe returns an error message to the user.
