A fix is available
APAR status
Closed as program error.
Error description
In some cases, the allocation parameters HPU to allocate its work datasets show that they are undersized as they do not allow the dataset allocated that way to contain the maximal amount of data expected for this dataset. The HPU process is not stopped however for the following reasons. - The work file allocation by HPU is based on an estimate that is usually quite oversized. Therefore, even if the allocation parameters do not look sufficient, it is worth an attempt to perform the unload with these parameters. - Moreover, on many sites, there are SMS routines that override the allocation done by the user to make it more relevant and avoid the allocation issues. If HPU blocked the unload when it believes the allocations parameters are not relevant, it would not take benefit from this mechanism. - The same way, it would not take benefit from the Tools that are sometimes installed to avoid ABENDSx37. However, the attempt to work with the potentially undersized dataset might lead the process to fail because of an ABENDSx37 on a work file, In such a case, it would help the user identify where the allocation issue comes from if HPU issued a message indicating that the allocation parameters (displayed by the INZX111 message) are potentially not relevant as they do not allow to allocate the maximum amount of data expected. The documentation of this new message would give the user directions on how to change the HPU settings or unload statement to solve the issue. RFE PB44551
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of High Performance Unload * **************************************************************** * PROBLEM DESCRIPTION: * * PI95262: * * Customer is migrating from competitive vendor and they use * * function ZONEDDECOVP(F,F). This allows * * the customer to Unload negative values and have them remain * * as negative values if needed. This * * option is needed as this is currently part of their business * * logic. Without this option, negative * * values are unloaded as positive values and this does not * * satisfy their needs. This option should be * * have the ability to be set at the Product level and also at * * the job level. * * * * PI97040: * * When the same OUTDDN is used in several selects, HPU accepts * * to write in the same file the result of * * several select statements. We use a template to avoid having * * to allocate manually the output files. * * With AUTOTAG keyword or not HPU does not correlate the * * AUTOTAG and the controls for the TEMPLATE * * allocation at the moment. * * * * PI97510: * * Unlike with prior versions, where the RECFM and LRECL DCB * * parameters of the SYSPRINT DD statements * * were taken into account provided the QUIESCE YES option was * * not requested, the RECFM=VBA and * * LRECL=124 are systematically set for the SYSPRINT data set * * instead. * * * * PI98153: * * In some cases, the allocation parameters HPU to allocate its * * work datasets show that they are * * undersized as they do not allow the dataset allocated that * * way to contain the maximal amount of data * * expected for this dataset. * * The HPU process is not stopped however for the following * * reasons. * * - The work file allocation by HPU is based on an estimate * * that is usually quite oversized. Therefore, * * even if the allocation parameters do not look sufficient, it * * is worth an attempt to perform the * * unload with these parameters. * * - Moreover, on many sites, there are SMS routines that * * override the allocation done by the user to * * make it more relevant and avoid the allocation issues. If * * HPU blocked the unload when it believes the * * allocations parameters are not relevant, it would not take * * benefit from this mechanism. * * - The same way, it would not take benefit from the Tools * * that are sometimes installed to avoid * * ABENDSx37. * * However, the attempt to work with the potentially undersized * * dataset might lead the process to fail * * because of an ABENDSx37 on a work file, In such a case, it * * would help the user identify where the * * allocation issue comes from if HPU issued a message * * indicating that the allocation parameters * * (displayed by the INZX111 message) are potentially not * * relevant as they do not allow to allocate the * * maximum amount of data expected. The documentation of this * * new message would give the user directions * * on how to change the HPU settings or unload statement to * * solve the issue. * **************************************************************** * RECOMMENDATION: * * Apply the PTF for problem resolution * ****************************************************************
Problem conclusion
Code has been changed to fix this problem
Temporary fix
Comments
APAR Information
APAR number
PI98153
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-05-18
Closed date
2018-06-29
Last modified date
2018-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI56979
Modules/Macros
INZUTILK
Fix information
Fixed component name
DB2 HI PERF UNL
Fixed component ID
5697F4400
Applicable component levels
R510 PSY UI56979
UP18/07/06 P F807
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":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 February 2021