CA Ideal Commands › ASSIGN AUTHORIZATION Command (SQL Access) › DB2 Considerations

DB2 Considerations

DB2 qualifies unqualified names as follows:

• For static mode: Using the authorization ID of the user who performs the GENERATE PLAN.
• For dynamic mode: In batch, using the authorization ID of the user who runs the job; or online, using the auth‑id based on the option for AUTH in the RCT entry for the current transaction.

Only a single level of authorization substitution is allowed. For example, if both ASSIGN ATZ SBL NEW HOU and ASSIGN ATZ HOU NEW KRI are issued, HOU replaces authorization ID SBL, not KRI.

If more than one assignment is made, only the first assignment applies. For example, if both ASSIGN ATZ SBL NEW HOU and ASSIGN ATZ SBL NEW KRI are issued, HOU replaces authorization ID SBL, not KRI. To reassign authorizations, use the RESET command and another ASSIGN command.

The ASSIGN AUTH command applies only to CA Ideal programs included in the plan. It does not affect any programs already bound into a package.