Before migration to Db2 12, you must convert your resource limit facility (RLF) tables to take advantage of longer field sizes that were introduced in Db2 11 and in DB2 version 8.
Before you begin
If you completed this task in a previous release, no action is necessary.
Ensure that the routines to be monitored are bound with APPLCOMPAT(V11R1) or higher.
About this task
Certain obsolete RLF table formats are deprecated, or unsupported starting in Db2 12.
- Starting in Db2 12, DSNRLSTxx table formats and related index formats from before DB2 version 8 format are not supported. When Db2 detects DSNRLSTxx tables with unsupported formats, it issues message DSNT731I.
- DSNRLMTxx table formats and related index formats from before Db2 11 are deprecated. In Db2 12, if Db2 detects DSNRLMTxx tables in a deprecated format, it issues message DSNT732I, processing for the START RLIMIT command continues, and the resource limit facility starts using the deprecated objects.
Installation job DSNTIJSG contains the JCL for creating RLF tables.
Procedure
To convert RLF tables to the new format:
- Stop the resource limit facility by issuing the following command.
-STOP RLIMIT
- If a DSNRLSTxx table was never updated to the format introduced in DB2 version 8, alter the data types for all of the following columns to VARCHAR(128).
This step is required before migration to Db2 12.
- Take one of the following actions to create RLF tables with the longer field lengths.
- Alter the existing DSNRLMTxx table column data types for RLFEUAN, RLFEUID, and RLFEUWN to specify the new longer lengths.
- Alter RLFEUAN to VARCHAR(255)
- Alter RLFEUID to VARCHAR(128)
- Alter RLFEUWN to VARCHAR(255)
You cannot alter a subset of the listed columns. You must alter all the above columns or none.
Important: After you change table or index definitions, consider reorganizing data to improve performance. After you change data types or column lengths by using ALTER TABLE statements, Db2 places the table space that contains the modified data in advisory REORG-pending (AREO*) status. The table space is in AREO* status because the existing data is not immediately converted to its new definition. Reorganizing the table space prevents possible performance degradation.
Tip: When data is in REORG-pending or AREO* status, use the REORG utility with the SCOPE PENDING option to automatically reorganize partitions. With this option, you avoid identifying which partitions require reorganization and customizing the REORG control statement.
- Create a new DSNRLMTxx table with the new longer lengths client information fields. Installation job DSNTIJSG contains the JCL for the creation of RLF tables.
You can copy the data from an existing RLF table to a new table. The following example copies data from DSNRLMT01 to DSNRLMT02.
INSERT INTO authid.DSNRLMT02
( RLFFUNC, RLFEUAN, RLFEUID, RLFEUWN, RLFIP,
ASUTIME, RLFASUERR, RLFASUWARN, RLF_CATEGORY_B )
SELECT
RLFFUNC, RLFEUAN, RLFEUID, RLFEUWN, RLFIP,
ASUTIME, RLFASUERR, RLFASUWARN, RLF_CATEGORY_B
FROM authid.DSNRLMT01;
- Start the resource limit facility with the ID of DSNRLMTxx table to be used.
The following example shows that RLF is activated with DSNRLMT02. The ID in the START command is also applied to the DSNRLSTxx table.
-START RLIMIT ID=02