IZ22709: FILENAME KEYWORD FOR SUB_SOURCE AND SUB_ORIGIN DOES NOT SET DBCS FILE NAME PROPERLY

APAR status

• Closed as program error.

Error description

• FILENAME keyword for sub_source and sub_origin
  deos not set DBCS file name properly.
  ---
  If FILENAME keyword is specified for "sub_source" and
  "sub_origin", and "LogSources" has the file name that includes
  DBCS characters in itsself, forwared evets makes garbled
  character in the "sub_source" and "sub_origin" slots.
  [ex]..
  "LogSource=C:\Tivoli\JAPANESE.log" <===file name consist of DBCS
   and,
   "sub_source FILENAME" or "sub_origin FILENAME" <===fmt file
   then,
    the JAPANESE (DBCS) file name specified in the "sub_source" or
  "sub_origin" slots are displayed as garbled characters.
  

Local fix

• By specifing the DBCS file name directly into these "sub_source"
  and "sub_origin" in the FORMAT file (without using the
  "FILENME" keyword) can avoid this symptom..
  ie:
  "LogSource=C:\Tivoli\JAPANESE.log" <===file name consist of DBCS
  
  sub_origin "C:\Tivoli\JAPANESE.log"
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of TEC EEIF adapters on Windows
  ****************************************************************
  * PROBLEM DESCRIPTION: When using the LOGFILE keyword on a
  * Windows system, if the logsource contains characters in the
  * extended character set or DBCS characters, the slot value may
  * not contain the expected characters (most likely, question
  * mark chars instead).
  ****************************************************************
  * RECOMMENDATION: Apply maintenance vehicle listed below
  ****************************************************************
  The internal header was assumed to be in UTF-8 already by
  consuming methods- some of which xlate back to native then back
  again. I made this assumption true.
  

Problem conclusion

• After translating the portion of the header which is used to
  derive the filenames into UTF-8, the name matches the system
  names now. Of course, all characters must be from the same
  system codepage (in other words, users can not mix characters
  from different codepages and expect non-garbled chars).
  
  The fix for this APAR is contained in the
  following maintenance packages:
  
  | LA Fix | 3.9.0.8-TIV-TEC-LA0091
  
  Note: Search IBM Technical Support web site for maintenance
  package availability.
  

Temporary fix

• N/A
  

Comments

APAR Information

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

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

Fix information

• Fixed component name

  TIVOLI ENT.CONS

• Fixed component ID

  5698TEC00

Applicable component levels

• R390 PSY

     UP