Controlling users' access to DB2-related CICS transactions

Use the CICS transaction-attach security mechanism to control users' access to: CICS transactions that access DB2 to obtain data, the DSNC transaction, and to any other transactions that issue CICS DB2 attachment facility commands and DB2 commands.

About this task

When transaction-attach security is enabled, RACF, or an equivalent external security manager, checks that the CICS user is authorized to run the transaction that they have requested.

To protect DB2-related transactions using transaction-attach security, follow the instructions in Transaction security. The process is the same for all CICS transactions; there are no special considerations for DB2-related transactions as far as the transaction-attach security mechanism is concerned. The instructions tell you how to: If you have defined transactions other than DSNC to issue CICS DB2 attachment facility commands and DB2 commands (for example, if you have created a separate transaction to run each command), remember to define these transactions to RACF as well.

You can now control which CICS users can use transactions that access DB2. Add the appropriate users or groups of users to the access list for the transaction profiles, with READ authority. RACF Profiles has some recommendations about this.

For transactions that issue CICS DB2 attachment facility commands and DB2 commands, bear in mind that:
  • CICS DB2 attachment facility commands operate on the connection between CICS and DB2, and they run entirely within CICS. DB2 commands operate in DB2 itself, and they are routed to DB2. You can distinguish DB2 commands from CICS DB2 attachment facility commands by the hyphen (-) character, which is entered with DB2 commands.
  • If you have access to the DSNC transaction, CICS allows you to issue all of the CICS DB2 attachment facility commands and DB2 commands.
  • If you have defined separate transactions to run individual CICS DB2 attachment facility commands and DB2 commands, you can give different CICS users authorization to subsets of these transaction codes, and therefore to subsets of the commands. For example, you could give some users authority to issue CICS DB2 attachment facility commands, but not DB2 commands. CICS-supplied transactions for CICS DB2 has the names of the separate transaction definitions that CICS supplies for the CICS DB2 attachment facility commands and the DB2 commands.
CICS DB2 attachment facility commands do not flow to DB2, so they are not subject to any further security checking. They are only protected by CICS transaction-attach security. However, DB2 commands, and CICS transactions that access DB2 to obtain data, are subject to further stages of security checking by DB2's own security mechanisms, as follows:
  • When a transaction signs on to DB2, it must provide valid authorization IDs to DB2. The authorization IDs are checked by RACF or an equivalent external security manager.
  • Because the transaction is issuing a DB2 command or accessing DB2 data, the authorization IDs that it has provided must have permission to perform these actions within DB2. In DB2, you can use GRANT statements to give the authorization IDs permission to perform actions.
In addition, the CICS region itself must be authorized to connect to the DB2 subsystem.

Providing authorization IDs to DB2 for the CICS region and for CICS transactions tells you how to authorize the CICS region to connect to the DB2 subsystem, and how to provide valid authorization IDs for transactions.

Authorizing users to access resources in DB2 tells you how to grant permissions to the authorization IDs that the transactions have provided to DB2.



dfhtk40.html | Timestamp icon Last updated: Sunday, 4 June 2017