A fix is available
APAR status
Closed as program error.
Error description
Resource contention during autobind of plans bound on Db2 10 for z/OS.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: The following users are affected: * * - All Db2 13 for z/OS users of local plans * * last bound in V10. * * - All Db2 12 for z/OS users of the DSNTIJPE * * premigration job and all Db2 13 for z/OS * * users of the DSNTIJPM premigration job. * **************************************************************** * PROBLEM DESCRIPTION: Transaction timeouts after migration * * to Db2 13 could occur due to local * * application plans bound on Db2 10 that * * go through concurrent autobinds. * * * * The code to generate REPORT07 in the * * Db2 12 DSNTIJPE and Db2 13 DSNTIJPM * * premigration jobs calls the Dsn_Error * * routine with an incorrect reference to * * the previous report, REPORT06. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** These plan auto rebinds were not called out by the activation of the function level V12R1M510. Thus, the traditional issue of concurrent plan autobinds after migration to Db2 13 can occur on the Db2 10-bound plans, and a customer can experience transaction timeout. REPORT07 in premigration jobs DSNTIJPE in Db2 12 for z/OS and DSNTIJPM in Db2 13 for z/OS provide queries to find the Db2 10-bound plans. The code to generate REPORT07 in the Db2 12 DSNTIJPE and Db2 13 DSNTIJPM premigration jobs calls the Dsn_Error routine with an incorrect reference to the previous report, REPORT06.
Problem conclusion
Db2 code has been changed to allow support for V10 plans on V13 without going through autobind. REPORT07 in migration jobs DSNTIJPE in Db2 12 for z/OS and DSNTIJPM in Db2 13 for z/OS have been modified to reflect that Db2 10-bound plans will now be suppported in Db2 13 without an autobind requirement. The code to generate REPORT07 in the Db2 12 DSNTIJPE and Db2 13 DSNTIJPM premigration jobs is also corrected to call the Dsn_Error routine referencing REPORT07, instead of REPORT06. Additional Keywords: RC00E30302 DB2MIGV13/K DB2MIGV12/K
Temporary fix
Comments
APAR Information
APAR number
PH59303
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
D10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-01-19
Closed date
2024-08-21
Last modified date
2024-09-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI98122 UI98123
Modules/Macros
DSNTAAL DSNTIJPE DSNTIJPM
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"D10","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
03 September 2024