PM31868: INCORRECT OUTPUT IN FM/DB2 OPTION 4.3 WHEN '*' SPECIFIED IN A SELECT CLAUSE INCLUDING DB2 CATALOG TABLES.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When using FM/DB2 option 4.3, VARCHAR columns incorrectly
  displayed when '*' is specified in a SELECT clause including
  DB2 catalog tables.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of File Manager DB2 component.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Missing (blank) data shown for some     *
  *                      DB2 catalog table columns after         *
  *                      executing a SELECT statement with a     *
  *                      join of 2 or more DB2 catalog tables,   *
  *                      when entered using FM/DB2 options 4.3   *
  *                      or 4.4.  Alternatively message 'UNICODE *
  *                      conversion error codepage 1208 to       *
  *                      codepage 37.  Return code 4, reason     *
  *                      code 7 from CUNLCNV routine.' displayed *
  *                      in the FM/DB2 editor session, when the  *
  *                      data is displayed - after attempting    *
  *                      to execute the SELECT statement as      *
  *                      previously described.                   *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  The problem relates to FM/DB2 accessing data for unicode-encoded
  columns in native unicode format, rather than allowing DB2 to
  automatically convert the unicode data to the CCSID of the
  terminal.  While this feature is useful when editing a single
  DB2 object, it is problematic when processing a join - as in the
  reported problem.  The problem arises when an erroneous attempt
  is made to convert EBCDIC data - rather than unicode data - to
  EBCDIC, using the system unicode conversion routines.
  

Problem conclusion

• File Manager DB2 component has been updated to correct the
  problem.  "Unicode-processing", where DB2 data that is
  unicode-encoded is retrieved in native unicode format, is
  restricted to the situation where a single DB2 object is being
  processed.
  

Temporary fix

Comments

APAR Information

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

  PM31804

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

Modules/Macros

• FMN2LVL
  FMN2LVLJ
  FMN2LVLK
  

Fix information

• Fixed component name

  FILE MANAGER Z/

• Fixed component ID

  5655W4700

Applicable component levels

• RB1B PSY UK66922

     UP11/04/22 P F104

• RB12 PSY UK66923

     UP11/04/22 P F104

• RB13 PSY UK66924

     UP11/04/22 P F104

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.