Limiting resources for statements from remote locations

Several important guidelines and restrictions apply when you use the resource limit facility in a distributed processing environment.

About this task

Introductory concepts

Resource limits apply only to the following types of SQL statements:

SELECT
INSERT
UPDATE
MERGE
TRUNCATE
DELETE

Resource limits apply only to dynamic SQL statements.

Procedure

To use the resource limit facility in conjunction with distributed processing:

Remember the following guidelines:

Option	Description
Dynamic statements from requesters that use DRDA protocols using TCP/IP	You can create a DSNRLMT`xx` table to limit resources by client information (RLFFUNC='8' or RLFFUNC='9') such as: Application name User ID Workstation ID IP address You can use a DSNRLST`xx` table for this purpose. However, you must then govern by package name (RLFFUNC='2' or RLFFUNC='7')(RLFFUNC='2' or RLFFUNC='7'). In this case, you must also: Specify a blank value for PLANNAME column. Specify 'PUBLIC' for the value of the LUNAME column for all remote LUs. You cannot specify the LUNAME of the requester. The 'PUBLIC' value also applies to local locations. If the value of the LUNAME column is blank, DB2 assumes that the row applies only to the local location, and the row does not apply to any incoming distributed requests.
SQL statements from requesters that use DRDA protocols using SNA	You can use a DSNRLMT`xx` table to govern by the following types of client information (RLFFUNC='8' or RLFFUNC='9'): Application name User ID Workstation ID However, IP address cannot be used, because no IP address is provided to DB2 under this DRDA protocol. You can use a DSNRLST`xx` table for this purpose. However, you must then govern by package name (RLFFUNC='2' or RLFFUNC='7'). In this case, you must also: Specify a blank value for PLANNAME column. Specify the LU name of the requestor or 'PUBLIC' for the value of the LUNAME column. A 'PUBLIC' value in the LUNAME column also applies to local locations. If the value of the LUNAME column is blank, DB2 assumes that the row applies only to the local location, and the row does not apply to any incoming distributed requests.

Option

Description

Dynamic statements from requesters that use DRDA protocols using TCP/IP

You can create a DSNRLMTxx table to limit resources by client information (RLFFUNC='8' or RLFFUNC='9') such as:

Application name
User ID
Workstation ID
IP address

You can use a DSNRLSTxx table for this purpose. However, you must then govern by package name (RLFFUNC='2' or RLFFUNC='7')(RLFFUNC='2' or RLFFUNC='7'). In this case, you must also:

Specify a blank value for PLANNAME column.
Specify 'PUBLIC' for the value of the LUNAME column for all remote LUs. You cannot specify the LUNAME of the requester.

The 'PUBLIC' value also applies to local locations. If the value of the LUNAME column is blank, DB2 assumes that the row applies only to the local location, and the row does not apply to any incoming distributed requests.

SQL statements from requesters that use DRDA protocols using SNA End of change

You can use a DSNRLMTxx table to govern by the following types of client information (RLFFUNC='8' or RLFFUNC='9'):

Application name
User ID
Workstation ID

However, IP address cannot be used, because no IP address is provided to DB2 under this DRDA protocol.

You can use a DSNRLSTxx table for this purpose. However, you must then govern by package name (RLFFUNC='2' or RLFFUNC='7'). In this case, you must also:

Specify a blank value for PLANNAME column.
Specify the LU name of the requestor or 'PUBLIC' for the value of the LUNAME column.

A 'PUBLIC' value in the LUNAME column also applies to local locations. If the value of the LUNAME column is blank, DB2 assumes that the row applies only to the local location, and the row does not apply to any incoming distributed requests.

If no qualified row is present in the resource limit table to limit access from remote locations, the limit is controlled by the value of the RLFERRD subsystem parameter.