A fix is available
APAR status
Closed as program error.
Error description
Specifying MAXPRIME in the definition of a TEMPLATE should limit both the primary and the secondary allocation. Currently it only limits the primary allocation, leading to a secondary that may be too big to fit on the DASD. The HPU manual specifies for MAXPRIME: Specifies the maximum allowable primary space allocation. The value is expressed in cylinders (CYL). This value constrains the primary space value, the PCTPRIME calculation, and the size of each secondary allocation. In addition the DB2 UTilities Guide gives more detains on the space allocation: By default, for data sets on disk, 100 percent of the required space that is estimated by DB2 is allocated as a primary quantity. If this amount of space is typically not available on a single volume, specify the PCTPRIME option with a value lower than 100. Alternatively, if you want the upper limit of the primary quantity based on size instead of percentage, use the MAXPRIME option. After the primary space is allocated, a secondary quantity that is equal to the estimated required space is divided into the specified number of secondary extents. This number is identified by the NBRSECND option. Individual utilities might request larger secondary extents to compensate for localized uncertainty in the space estimations. If you specify either PCTPRIME or MAXPRIME, any secondary allocation requests are limited to the size of the primary allocation. DB2 HPU should follow these rules when calculating primary and secondary allocations. PB11591
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 High Performance Unload. * **************************************************************** * PROBLEM DESCRIPTION: Specifying MAXPRIME in the definition * * of a TEMPLATE should limit both the * * primary and the secondary allocation. * * Currently it only limits the primary * * allocation, leading to a secondary * * that may be too big to fit on the DASD. * * The HPU manual specify for the * * MAXPRIME: Specifies the maximum * * allowable primary space allocation. * * The value is expressed in cylinders * * (CYL). This value constrains the * * primary space value, the PCTPRIME * * calculation, and the size of each * * secondary allocation. In addition * * the DB2 UTilities Guide gives more * * detains onthe space allocation: * * By default, for data sets on disk, 100 * * percent of the required space that is * * estimated by DB2 is allocated as a * * primary quantity. If this amount of * * space is typically not available on a * * single volume, specify the PCTPRIME * * option with a value lower than 100. * * Alternatively, if you want the upper * * limit of the primary quantity based on * * size instead of percentage, use the * * MAXPRIME option. After the primary * * space is allocated, a secondary * * quantity that is equal to the * * estimated required space is divided * * into the specified number of secondary * * extents. This number is identified by * * the NBRSECND option. Individual * * utilities might request larger * * secondary extents to compensate for * * localized uncertainty in the space * * estimations. If you specify either * * PCTPRIME or MAXPRIME, any secondary * * allocation requests are limited to the * * size of the primary allocation. DB2 * * HPU should follow these rules when * * calculating primary and secondary * * allocations. * * PB 11591 * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** The infgucb module was fixed so that the secondary quantities are set to MAXPRIME is this option is specified.
Problem conclusion
APPLY the PTF.
Temporary fix
Comments
APAR Information
APAR number
PM65383
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-23
Closed date
2012-08-08
Last modified date
2012-09-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
INZRSAVE
Fix information
Fixed component name
DB2 HI PERF UNL
Fixed component ID
5697F4400
Applicable component levels
R410 PSY UK80919
UP12/08/15 P F208
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUUV","label":"IBM Db2 High Performance Unload for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 February 2021