A fix is available
APAR status
Closed as program error.
Error description
(HPU 5,1 only) An ABENDS0C4 or an ABENDS0C1 can occur while unloading, in native mode, LOB or XML data into several partitioned data sets (PDS) PB52375 The data unloaded from image copies (COPYDDN option) is not consistent with the content of the image copies. The unloaded data can be affected as follows: - an expected row is missing - an unexpected row is present This can occur if the following conditions are fulfilled - the data is unloaded from image copies (COPYDDN option) which processing involves a sort, which occurs when one of the following condition applies: + the image copy is retrieved from the DB2 catalog (COPYDDN LAST_IC or COPYDDN integer option) and the catalog (SYSIBM,SYSCOPY table) indicates it is an INLINE image copy + the input image copy is allocated in the JCL (COPYDDN ddname option) and the keyword INLINE or FROM_COPYTOCOPY or MERGE_IIC is specified - the involved image copies were taken while concurrent updates of the table occurred, in other words the images copies contain duplicate pages PB52517 (HPU 5.1 only) The PGDFIN parameter which sets the Percentage of displaced pages in inline FIC (in other words, percentage of page to be sorted) in an image copy is ignored and a value of 100 is taken instead. When sorting the data from an image copy is needed, the sort program is invoked with an overestimated number of records to be sorted. The impact of this issue might depend on the sort program used specified via the SORTUTIL parameter. PB52607
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of High Performance Unload * **************************************************************** * PROBLEM DESCRIPTION: * * Description * * PI95023: * * An unload requesting the unloaded data be written into * * several files (e.g. OUTDDN(ddmain,ddcopy)) enters an * * everlasting wait state if a zIIP processor is used. * * * * PI95798: * * An ABENDU1003 occurs after the following message INZX111 * * nnnnK / ppppK REQUESTED ON uu UNIT(S), SIZE=(aaaa * bbbb) * * has been issued with value zero or negative values for nnnn * * (primary quantity) and uu (unit-count). * * This can occur if the following conditions are fulfilled: * * - the index scan feature is used * * - the value specified for WRKSPACE is PARTIAL * * - the work datasets are to be allocated on disk (i.e. aaaa * * * bbbb, the amount of data to allocate is less than the value * * specified for WRKUNTSW) * * - the value specified for WRKMXPR is less than 500000 * * The occurrence of the failure depends on the amount of data * * to allocate and the value specified for WRKMXPR. The lower * * their values, the more likely the issue. * * The issue always occurs for the allocation of TnnnMG files. * * * * PI95886: * * The data unloaded from the global image copy (COPYDDN * * option) of a partition-by-growth table space only contains * * the row from the first partition although the table space at * * the time of copy contained more than one partition and the * * unload statement does not restrict the unload to data from * * the first partition. This occurs if the DDLDDN option is * * specified. * * * * PI95966: * * DB2 HPU unduly allocates the TnnnMG data sets with * * DALBLKLN=0. This incorrect value which can lead to ABENDSx37 * * for these data sets involved in the indescan feature. * * * * PI96114: * * The unload of LOB data into a spanned data set (SPANNED YES * * option) can hang. * * * * PI96265: * * Output fields for time data formatted with the US format * * (TIME_C or TIME_DB2 with a DB2 set with a the USA time * * format) contain incorrect or invalid data whenever the value * * to unload is a time after midday. * * For example, the output field for 13.05 (in ISO format) * * contains 11.05 PM instead of 01.05 PM which is a wrong * * well-formed value and the output field for 22.00 gives 20.00 * * PM which is an invalid value. * * The problem occurs in the following cases: * * case 1) when the DB2 subsystem is not defined with TIME USA * * and when the time format specification (specified either by * * the ULTIME variable or through the OPTIONS block) is TIME_C, * * regardless of the processing (native or SQL) mode. * * case 2) when the DB2 subsystem is defined with TIME_USA and * * when the time format specification (specified either by the * * ULTIME variable or through the OPTIONS block) is TIME_C or * * TIME_DB2 and the unload is processed in native mode (the * * result of unloads processed in SQL mode is correct). * * * * PI96359: * * When HPU terminates in ABEND, very useful diagnosis * * information is issued if the $DIAG DD name is allocated. * * As getting this useful information requires adding the $DIAG * * DD card and recreating the case, it would be far more * * efficient to get this information at the time of the first * * occurrence of the issue, especially when intermittent issues * * are concerned. * * * * PI96550: * * An ABENDS0C4 or an ABENDS0C1 can occur while unloading, in * * native mode, LOB or XML data into several partitioned data * * sets (PDS). * * The data unloaded from image copies (COPYDDN option) is not * * consistent with the content of the image copies. The * * unloaded data can be affected as follows: * * - an expected row is missing * * - an unexpected row is present * * This can occur if the following conditions are fullfilled * * - the data is unloaded from image copies (COPYDDN option) * * which processing involves a sort, which occurs when one of * * the following condition applies: * * + the image copy is retreived from the DB2 catalog * * (COPYDDN LAST_IC or COPYDDN interger option) and the catalog * * (SYSIBM,SYSCOPY table) indicates it is an INLINE image copy * * + the input image copy is allocated in the JCL (COPYDDN * * ddname option) and the keyword INLINE or FROM_COPYTOCOPY or * * MERGE_IIC is specified * * - the involved image copies were taken while concurrent * * updates of the table occurred, in other words the images * * copies contain duplate pages * **************************************************************** * RECOMMENDATION: * * Apply the PTF for problem resolution * ****************************************************************
Problem conclusion
Code has been changed to fix this problem
Temporary fix
PI95023: Disable the zIIP use by specifying ZIIP OFF. PI95798: Specify the value FULL for WRKSPACE. PI95966: Disable the indexscan feature by specifying INDEXSCAN NO.
Comments
APAR Information
APAR number
PI96550
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-04-11
Closed date
2018-04-24
Last modified date
2018-07-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI55424
Modules/Macros
INZUTILK
Fix information
Fixed component name
DB2 HI PERF UNL
Fixed component ID
5697F4400
Applicable component levels
R510 PSY UI55424
UP18/04/27 P F804
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