PM93270: ACCESS DSNHDECP FOR DB2 SETTINGS AS IN PRIOR RELEASES

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Starting in with HPU v4.1. In order to avoid wrong
  (inconsistent) settings, DB2 HPU does no longer reads the
  settings from the DSNHDECP module but uses the GETVARIABLE
  function to get the information. As some HPU users might have
  used inconsistent setting, by mistake or on purpose, this
  enhancement can have impacts on the HPU output of existing
  unload jobs. For example, if the wrong DSNHDECP provided to HPU
  (via the setting of the DSNEXIT parameter) did not have the same
  setting for DATE or TIME format, the output data of a lot of
  unload jobs unloading date or time data can be changed after an
  upgrade to HPU v4.1 or later release.
  
  This PTF will fit HPU with the ability to keep the behavior that
  existed in HPU 3.2 and prior releases.  In other words starting
  with HPU v4.2, HPU will read access the DSNHDECP module to
  obtain DB2 settings the way HPU v3 and prior worked.
  
  PB11941
  

Local fix

• Depending on the setting discrepancy and on the HPU usage, there
  might be solutions to get the same output as in HPU 4.1. For the
  example mentionned above, if the HPU native syntax is used, the
  ULDATE, DATEDEL and ULTIME setting can help solve the problem.
  Contact your IBM support for getting advice on the solution to
  implement.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 High Performance Unload.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: From release 4.1 on, in order to avoid  *
  *                      wrong (inconsistent) settings, DB2 HPU  *
  *                      does no longer read the settings from   *
  *                      the DSNHDECP module but uses the        *
  *                      GETVARIABLE function to get the         *
  *                      information. As some HPU users might    *
  *                      have used inconsistent setting, by      *
  *                      mistake or on purpose, this enhancement *
  *                      can have impacts on the HPU output of   *
  *                      existing unload jobs. For example, if   *
  *                      the wrong DSNHDECP provided to HPU (via *
  *                      the setting of the DSNEXIT parameter)   *
  *                      did not have the same setting for DATE  *
  *                      or TIME format, the output data of a    *
  *                      lot of unload jobs unloading date or    *
  *                      time data can be changed after an       *
  *                      upgrade to HPU 4.1 or later release.    *
  *                      DB2 HPU should be fitted with the       *
  *                      ability to keep the behavior that       *
  *                      existed in HPU 3.2 and prior releases.  *
  *                      PB 11941                                *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Enhancement.
  

Problem conclusion

Temporary fix

Comments

• APPLY the PTF.
  

APAR Information

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

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

Modules/Macros

• INZ$$PRM
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R420 PSY UK96461

     UP13/08/08 P F308

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.