PK70097: DSNTIAUL LOBFILE CAN'T UNLOAD LOB TO INDIVIDUAL FILE 08/08/12 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The problem I have is with DB2 9 for z/OS sample
  unload program DSNTIAUL;  specifically the new LOBFILE
  parameter to unload a LOB (32K in length> to individual file,
  but failed and LOB is truncated into SYSREC.
  
  Redbooks:
  
  http://ftp-developpez.com/db2/ibmredbooks/sg247270.pdf
  6.2 DSNTIAUL
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of DSNTIAUL in DB2 Version 9.1 for *
  *                 z/OS are affected by this change.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the LOBFILE parameter is specified *
  *                      to request use of LOB file references,  *
  *                      DSNTIAUL ignores it and instead directs *
  *                      LOB data to the standard SYSRECnn       *
  *                      data set.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  DSNTIAUL is a sample dynamic SQL processing application that is
  used primarily to unload data from DB2 tables to an externalized
  format.  DSNTIAUL also generates a LOAD control statement that
  can be used in conjunction with the DB2 LOAD utility to load the
  externalized data back into DB2.
  
  By default, DSNTIAUL creates two types of output data sets:
    - a data set containing the LOAD utility control statement(s)
    - one or more data sets that contain the FETCHed data
      associated with the generated LOAD utility control
      statement(s)
  
  Data contained in the FETCHed output data sets is subject to
  truncation.
  
  The LOBFILE parameter provides a vehicle to create a third type
  of output data set:
    - the full content of a LOB cell.
  
  When the LOBFILE parameter is used, DSNTIAUL should write the
  content of each LOB cell to a dynamically-allocated data set,
  place the name of the LOB cell data set into the FETCHed
  output data set, and indicate that a LOB file reference
  variable is used in the LOAD statement.
  
  Recent changes to DSNTIAUL by PTF UK27144 introduced a bug that
  can cause DSNTIAUL to ignore the LOBFILE parameter.
  

Problem conclusion

• In response, this APAR modifies DSNTIAUL to honor the
  LOBFILE parameter.
  .
  This PTF modifies only the source code for DSNTIAUL in the
  prefix.SDSNSAMP target library.  The changes do not become
  effective until the DSNTIAUL load module has been rebuilt
  from the updated source code and the DSNTIAUL plan has been
  bound from the new DBRM.  See the ++HOLD actions section of
  this PTF for information on how to prepare and bind DSNTIAUL.
  

Temporary fix

Comments

APAR Information

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

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

  UK40014

Modules/Macros

• DSNTIAUL
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK40014

     UP08/10/04 P F810

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.