PM26520: UNLOAD LOB TO HFS CAUSES MANY RACF MESSAGES ICH408I IF USER IS N NOT AUTHORIZED TO ISSUE THE CHOWN COMMAND

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Running Unload utility to unload a lob tablespace to
  HFS files, the console log is flooded with Racf messages
  like this  :
  ICH408I USER(SQ504F4#) GROUP(SQ504   ) NAME(SUB-U OPC GEBAC)
    /appl/db2tools/wbiD2E0/dnfsysou/lob1dnf/C0W6HRNQ
    CL(FSSEC   ) FID(00000020000000010000000000000000)
    INSUFFICIENT AUTHORITY TO CHOWN
    EFFECTIVE UID(0001320000)  EFFECTIVE GID(0000001320)
  The unload finishes OK, but the client is not happy with
  this message flood.
  This message started to occur after applying the ptf for
  PK54326.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of LOBs  *
  *                 with HFS.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When LOB data is written into a new HFS *
  *                      file, a warning message "INSUFFICIENT   *
  *                      AUTHORITY TO CHOWN" is incorrectly      *
  *                      issued, although the LOB data has been  *
  *                      successfully written into the new HFS   *
  *                      file.  Instead the warning should not   *
  *                      be there.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The following warning message "INSUFFICIENT AUTHORITY TO CHOWN"
  is incorrectly issued when LOB data is written into a new HFS
  (Hierarchical File System) file even though the LOB data has
  been successfully written to the new file.  The warning message
  should not be issued.
  
  The following example helps to illustrate the problem.
  
  In a given application, define a LOB file to be written to and
  then write to it.
  
    DCL LOC2 SQL TYPE IS BLOB_FILE;
  
    LOC2_NAME_LENGTH = 17;
    LOC2_DATA_LENGTH = 0;
    LOC2_FILE_OPTIONS  = SQL_FILE_CREATE;
    LOC2_NAME  = 'u/OE1/LOBTest.xml';
  
    EXEC SQL SELECT LOB_COL INTO :LOC2 FROM T1;
  
  
  Because DB2 code does not handle the HFS user group id name
  properly, when the last statement is executed, the warning
  message "INSUFFICIENT AUTHORITY TO CHOWN" is issued.  The
  message indicates that "CHOWN", the 'change owner' in unix, does
  not have the proper authority, but the data is written
  successfully to the LOBTest.xml file.
  

Problem conclusion

• The code in DB2 has been modified to map the HFS user group id
  name properly and prevent the warning message from being issued
  incorrectly.
  
  Additional Keywords: SQLLOB
  

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:

  UK63898 UK63899

Modules/Macros

• DSNOLFRV
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK63898

     UP11/01/28 P F101

• R910 PSY UK63899

     UP11/01/28 P F101

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.