Resource limits hit after migrating from DB2 HPU V3.1 to DB2 HPU V4.1

Technote (FAQ)


Question

Why are resource limits hit after migrating from DB2 HPU V3.1 to DB2 HPU V4.1?

Cause

After migration from DB2 HPU V3.1 to DB2 HPU V4.1 was complete, DB2 HPU jobs started returning errors that indicated that resource limits were exceeded. As a result, DB2 HPU V4.1 was backed out of the production environment.

Answer

In this case, the user changed the ASUTIME RLST settings to allow for longer running requests, which alleviated resource limits from being reached. This solution helped this specific case, but the solution might not be appropriate in all cases.

IBM knows of no reason why migration from HPU V3.1 to V4.1 should cause an increase in resource consumption.

To further analyze this type of issue, IBM Software Support needs to study the difference in behavior between DB2 HPU V3.1 and DB2 HPU V4.1. To help IBM Software Support, indicate whether there was a change in behavior on the same unload job in DB2 HPU V3.1 and in DB2 HPU V4.1 and send the following information:

  • Job log of the unload that was run in DB2 HPU V3.1
  • PARMLIB (INZTVAR/INZUTIL) for DB2 HPU V3.1
  • Job log of the unload (same as in DB2 HPU V3.1) that was run in DB2 HPU V4.1 before the ASUTIME RLST update
  • PARMLIB (INZTVAR/INZUTIL) of DB2 HPU V4.1

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 Tools for z/OS
DB2 High Performance Unload

Software version:

4.1.0

Operating system(s):

z/OS

Reference #:

1623377

Modified date:

2013-02-14

Translate my page

Machine Translation

Content navigation