PI90635: WRONG # OF RECORDS WRITTEN IN INZX090

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The value given by the message INZX090 is incorrect in the
  following case : when the size of rows to unload is higher than
                                                              2GB.
  Example : INZX090 DDN UNLDDS TS RKWW1171 : -1127021630 RECORDS
  WRITTEN
  
  PB51066
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of High Performance Unload                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The number of records displayed by the INZX090 message is    *
  * incorrect when the number of rows to be unloaded in a single *
  * ddname is greater than 17179869184.                          *
  *                                                              *
  * Example : INZX090 DDN UNLDDS TS RKWW1171 : -1127021630       *
  * RECORDS WRITTEN                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the PTF for problem resolution                         *
  ****************************************************************
  This fix includes the following APARs:
  PI85634:  Invalid load control cards lead to DSNU088I  DSNUGTIS
  - INVALID CHARACTER OPERAND - ''' in DB2 load.
  PI85937:  An unload job requesting the data from an image copy
  to be unloaded using the DDLDDN fails with a completion code of
  8
                  after having issued the following message:
  
                                INZU366I UTILITY RETURN CODE 8
  (REASON CODE 0x32a00b). but no message explaining the reason of
  the error.
  
                  This occurs if one of the following condition is
  fullfilled
                              1) the DDLDDN data set contains
  certain king of syntax error such as a truncated CREATE TABLE
  without any IN database or IN database.tablespace clause.
  2) the CREATE TABLESPACE in the DDLDDN data set contains at the
  same time SEGSIZE 0 and NUMPARTS the tablespace is considered as
  a segmented
                                  tablespace instead of a
  partitioned tablespace.
  PI86356:  DB2 HPU issues one of the following misleading
  messages below
                              INZU095E SYNTAX ERROR - PROCMSG
  KEYWORD ONLY VALID WITH UNLOAD BLOCK.
                              INZU095E SYNTAX ERROR - SELMSG
  KEYWORD ONLY VALID WITH UNLOAD BLOCK.
                  when the PROCMSG or SELMSG keywords are
  specified at the SELECT level which is actually not supported
  although the documentation
                  might say it is. As these keywords cann only be
  specified in the GLOBAL block, these messages gives incorrect
  and misleading information.
  PI86361:  The last record of the PROCMSG data set is missing. It
  occurs whenever the PROCMSG ddname option is specified and the
  related
                  ddname is allocated via a DD card. As in some
  cases, the PROCMSG data set should contain only one record.
  Because of this issue,
                  in such a case, the PROCMSG data set is empty.
  
  PI88373:  The unload unduly fails after issuing the following
  message:
                               INZU200E LOAD STATEMENT ERROR :
  DATE/TIME/TIMESTAMP FORMAT INVALID FOR COLUMN column_identifier
  
                  Although the DATE/TIME/TIMESTAMP format
  specified via the "OPTIONS DATE/TIME/TIMESTAMP format" is a
  valid input for the LOAD utility.
  PI88517:  The message INZU015E GLOBAL STATEMENT : UNEXPECTED
  KEYWORD is issued when the end of GLOBAL statement, i.e. a
  semicolon is
                  missing. This potential error should be
  suggested to the user to facilitate trouble shooting in such a
  case.
  PI90634:  Undue INZRE40 PAGE NO. page number IN LDS NO.LDS
  number OF PAGESET pageset ISNOT IN SEQUENCE, SCAN ABORTED when
  unloading a
                  partition which page number has the high order
  bit set.
  PI90657:  For trouble shooting purposes, it is useful to know
  what parmlib the unload actually uses. When it is dynamically
  allocated,
                  which is the usual case, in HPU 5.1, there is no
  more track of this allocation are there used to be in versions
  up to HPU 4.3
                  with a message such as
  
                               IEF237I 0AA0 ALLOCATED TO $INFPLIB
  
                               IEF285I   HINZ430.SINZPARM
  KEPT
                  A message should be issued by the unload in such
  a situation to tell which data set has been allocated a the
  parmlib.
  PI90667:  The INZX089 and INZX090 messages are not issued into
  SYSPRINT but as WTO messages although GLOBAL SELMSG SYSPRINT is
  specified.
  

Problem conclusion

• Code has been changed to fix this problem
  

Temporary fix

Comments

• ×**** PE20/07/10 FIX IN ERROR. SEE APAR PH26122  FOR DESCRIPTION
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI52374

Modules/Macros

• INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI52374

     UP17/12/07 P F712

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.