Restricting bind operations

You can use the DB2® resource limit facility to set limits on the amount of resources used by bind operations.

Procedure

To restrict bind operations:

Use an RLST resource limit table and specify RLFFUNC='1' and qualify rows by authorization ID and LU name. The same precedence search order applies:
  1. AUTHID and LUNAME match.
  2. AUTHID matches.
  3. LUNAME matches.

    A value of PUBLIC for LUNAME applies to all authorization IDs at all locations, while a blank LUNAME governs bind operations for IDs at the local location only.

  4. If no entry matches, or if your resource limit table cannot be read, the resource limit facility does not disable bind operations.

Example

The table below is an example of an RLST resource limit table that disables bind operations for all but three authorization IDs. Notice that the binder from the local site is able to bind but that the binder from San Francisco is not able to bind. Everyone else from all locations, including the local one, is disabled from processing binds.

Table 1. Restricting bind operations
RLFFUNC AUTHID LUNAME RLFBIND
1 BINDGUY PUBLIC
1 NIGHTBND PUBLIC
1 (blank) PUBLIC N
1 BINDER SANFRAN N
1 BINDER (blank)