A fix is available
APAR status
Closed as program error.
Error description
An unload run in native mode against a table space created with the DEFINE NO option and having LDS not yet defined unduly ends with completion code 4 after having issued allocation error messages about Lds of the table space. If the table space is not a partition-by-growth table space, messages such as the following ones are issued: for non PBG tablespace , non expected messages : - to the system console (WTO messages) IKJ56228I DATA SET lds name NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED - to the SYSPRINT dataset: INZU370I LDS ALLOCATION FAILED FOR dbname.tsname, DB2 CATALOG IS ACCESSED TO UPDATE LDS NAME. INZU371I THE LDS NAME HAS NOT BEEN MODIFIED BY THE SWITCH PHASE INZI800E ERROR ACCESSING TO A DATASET. ACTION: ALLOCATE RC: 0x1708 REASON: 0x2 DDN: DSN: lds name If the tablespace is a partition-by-growth table space, messages such as the following ones are issued: for PBG tablespace , non expected messages in WTO : - to the system console (WTO messages) IKJ56228I DATA SET lds name NOT IN CATALOG OR CATALOG CAN NOT BE IKJ56231I UTILITY DATA SET NOT ALLOCATED, SYSTEM OR INSTALLATION ERROR+ IKJ56231I TEXT UNIT X'0002' CONTAINS INVALID PARAMETER - to the SYSPRINT dataset: INZU370I LDS ALLOCATION FAILED FOR dbname.tsname, DB2 CATALOG IS ACCESSED TO UPDATE LDS NAME. INZI800E ERROR ACCESSING TO A DATASET. ACTION: ALLOCATE RC: 0x35c REASON: 0x2 DDN: DSN: lds name (truncated) PB57339 Corrective maintenance to PE UI60268 and UI60061.
Local fix
if applicable, run the unload in SQL mode by specifying the DB2 FORCE option
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of High Performance Unload for z/OS * **************************************************************** * PROBLEM DESCRIPTION: * * PH11503: * * The LOAD control cards generated for a logical unload * * against the table from a partition-by-growth table space * * unduly specify a PART option. Their use as an input for the * * LOAD utility leads to a failure reported through a message * * such as DSNU256I - 108 14:27:52.98 DSNURWI - INVALID * * PARTITION SPECIFICATION. * * This occurs when the unload command request the data be * * unloaded at the partition level by using a TEMPLATE * * statement that specifies a data set name with the &PART * * variable. * * * * PH12190: * * When unloading data in dataset stored on tape with stacking, * * the last output dataset (OUTDDN or UNLDDN) written to tape * * with stacking, requested through a TEMPLATE statement * * specifying a tape unit and STACK YES, is unexpectedly * * reported as DELETED by the system through messages such as * * the following ones * * IEF285I dataset name DELETED * * IEF285I VOL SER NOS= tapename * * * * PH12191: * * An unload run in native mode against a table space created * * with the DEFINE NO option and having LDS not yet defined * * unduly ends with completion code of 4 after having issued * * allocation error messages about Lds of the table space. * * - If the table space is not a partition-by-growth table * * space, messages such as the following ones are issued: * * + for non patition-by-growth tablespace, non expected * * messages : * * - to the system console (WTO messages) * * IKJ56228I DATA SET lds name NOT IN CATALOG OR CATALOG CAN * * NOT BE ACCESSED * * - to the SYSPRINT dataset: * * INZU370I LDS ALLOCATION FAILED FOR dbname.tsname, DB2 * * CATALOG IS ACCESSED TO UPDATE LDS NAME. * * INZU371I THE LDS NAME HAS NOT BEEN MODIFIED BY THE SWITCH * * PHASE OF AN UTILITY * * INZI800E ERROR ACCESSING TO A DATASET. ACTION: ALLOCATE RC: * * 0x1708 REASON: 0x2 * * DDN: DSN: lds name * * - If the tablespace is a partition-by-growth table space, * * messages such as the following ones are issued: * * + for PBG tablespace , non expected messages in WTO : * * - to the system console (WTO messages) * * IKJ56228I DATA SET lds name NOT IN CATALOG OR CATALOG CAN * * NOT BE ACCESSED * * IKJ56231I UTILITY DATA SET NOT ALLOCATED, SYSTEM OR * * INSTALLATION ERROR+ * * IKJ56231I TEXT UNIT X'0002' CONTAINS INVALID PARAMETER * * - to the SYSPRINT dataset: * * INZU370I LDS ALLOCATION FAILED FOR dbname.tsname, DB2 * * CATALOG IS ACCESSED TO UPDATE LDS NAME. * * INZI800E ERROR ACCESSING TO A DATASET. ACTION: ALLOCATE RC: * * 0x35c REASON: 0x2 * * DDN: DSN: lds name (truncated) * * * * PH12347: * * The list of parmlib parameters values displayed by the * * DISPLAY_PARMLIB/DISPPARM feature contains an incorrect value * * of VUU030/ULOPTNS where the parentheses from the actual * * valiue of this parameter have been replaced by blanks. * * For example, if ULOPTNS is set to * * (LOADINDDN(NO),PADDING_STRICT(YES)), the parameter is * * displayed as VUU030/ULOPTNS = LOADINDDN NO, PADDING_STRICT * * YES * * * * PH12410: * * Db2 HPU stops with ABENDU1129 with reason code of F when the * * following situation nnot compliant with its optimization * * process is met: * * - the unload requires CCSID conversion * * - a binary zero exists * * + either in the data to be converted * * + or in the data once converted into the target CCSID * * In such a case, finding out which data contains the binary * * zero is very dificult. * * Instead of ending with an ABEND, Db2 HPu should issue a * * message providing more information to help locating the data * * with binary zero(es) such as in the following example: * * * 250 * OPTIMIZATION NOT ALLOWED * OUT * C1 * * * 0000004841484120 * * where the concerned output ddname and columns are indicated * * and with more details such as in the following example: * * * 250 * OPTIMIZATION NOT ALLOWED * OUT * PART 0001 PGNUM * * 00000002 ID 02 * DB : DBTLS00 TS : TS2355 * * if the HANDLE_RECOR_ID feature is enabled. * * * * * * PH12835: * * Fix 1 - A logical unload ends with completion code 8 ter * * having issued a message as follows * * INZI187E DB2 COMMAND ERROR, DB2 RETURN CODE: 8 REASON CODE: * * 00E60820 EXPLANATION * * DSNT300I -DZBA AUTH-ID job user NOT AUTHORIZED TO PERFORM * * START ON * * DATA BASE object. REQUEST REJECTED * * DSN9023I -DZBA DSNTDDIS 'START DATABASE' ABNORMAL * * COMPLETION * * and the table space involved in the unload unduly has the RO * * restricted state once the unload step has completed. * * This occurs when the following conditions are fulfilled: * * - the LOCK of the unloaded table is requested either through * * the LOCK YES option or by the setting the ULLOCK parmlib * * parameter to YES * * - the ULLOCKTE parmlib parameter is set to START_RO * * - the submitter of tbe job does not have the privilege to * * run the START DATABASE command against the table space * * involved in the unload * * - the QUITSUSR parmlib parameter specifies an explicit * * userid (i.e. it is not set to CURRENT_USER) that has the * * privilege to run the START DATABASE command against the * * table space involved in the unload * * * * Fix 2 - An ABENDS0C4 occurs during the unload - in native * * mode - of XML data from a FlashCopy dataset. * * This occurs if the index associated to the involved XML * * column is not compressed and uses a bufferpool which size is * * greater than 4K. * * * * Fix 3 - An unload - in native mode - requesting some XML * * data be unloaded from a FlashCopy dataset unduly stops with * * completion code of 8 after having issued the following * * message * * INZU362E UNLOAD 00001 FROM TABLESPACE database.tablespace * * FAILED * * POS(x, y) RC = 0x139a005 * * This occurs if the FlashCopy used as input was taken before * * the XML index related to the involved XML column had been * * altered to become not compressed. * * * * PH12836: * * To make diagnosis easier, the values of the parmlib * * parameters should always be available in the joblog of HPU * * whenever a failure occurs. * * Therefore, in case of ABEND or error (RC >= 8 unless RC was * * set to 8 because of the UNLZLRC feature), * * - if the DISPLAY_PARMLIB feature is not requested, the HPU * * parameters are written to the SYS00001 ddname formatted as * * by the DISPLAY_PARMLIB feature * * - if the DISPLAY_PARMLIB feature is requested, HPU writes * * to the SYS00001 ddname an explanation about the ddname the * * parmlib parameters have been written to. * **************************************************************** * RECOMMENDATION: * * Apply the PTF. * ****************************************************************
Problem conclusion
Code has been changed to fix this problem.
Temporary fix
PH12835: Fix 1 - Either give the submitter of the job the privilege to run the START DATABASE command against the tablespace involved in the unload or set ULLOCKTE to LOCK. Fix 2 - If applicable, consider running the unload from a non-FlashCopy image copy. PH12190: None, unless only one data set is unloaded in which case STACK YES can be removed. PH12191: If applicable, run the unload in SQL mode by specifying the DB2 FORCE option
Comments
×**** PE20/04/03 FIX IN ERROR. SEE APAR PH24051 FOR DESCRIPTION
APAR Information
APAR number
PH12191
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
510
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-05-16
Closed date
2019-06-27
Last modified date
2021-06-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI63956
Modules/Macros
INZTDSC INZUTILC INZ$$PRM INZCRXSM INZCRXSQ INZUTILK INZTVAR INZUTIB2 INZUTIB1
Fix information
Fixed component name
DB2 HI PERF UNL
Fixed component ID
5697F4400
Applicable component levels
R510 PSY UI63956
UP19/07/02 P F907 {
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0"}]
Document Information
Modified date:
15 June 2021