IZ03755: FILE DP: DYNAMIC FILENAME NOT SUPPORTING GLOBALIZED FILENAMES

APAR status

• Closed as program error.

Error description

• Approver: BEH
  
  Environment:
  ------------
    Windows XP Chinese Version
    ITM 6.1 FP05 Universal Agent - File DP
  
  
  Problem Description:
  --------------------
    When importing the following metafile into UA, it doesn't
  work. Expected "hostname:PRVHJB035000" item doesn't show in TEP
  navigator window, and the data file specified in //SOURCE
  statement isn't monitored at all.
  
  Metafile: (written in UTF-8)
  //APPL PRVHJB0350
  //NAME PRVHJB0350 E
  //SOURCE FILE E:\work\(Chinese Chars)\PRVHJB0350_{YYYYMMDD}.LOG
  TAIL
  //ATTRIBUTES ','
  Date D 15
  PRVHMD D 10
  Information D 100
  Message Z 2048
  
  Test data file:
  (E:\work\(Chinese Chars)\PRVHJB0350_20070723.LOG)
  20070326083039,PRVHMI0030,Job start,[starttime=2007-03-26
  08:30:41]
  20070326083048,PRVHMI0030,Job start,[starttime=2007-03-26
  08:30:41]
  20070326083041,PRVHMI0030,Job start,[starttime=2007-03-26
  08:30:41]
  20070326083043,PRVHMI0030,Job start,[starttime=2007-03-26
  08:30:41]
  20070326083043,PRVHMI0030,Job start,[starttime=2007-03-26
  08:30:41]
  20070326083042,PRVHMI0030,Job start,[starttime=2007-03-26
  08:30:41]
  20070326083043,PRVHMI0030,Job start,[starttime=2007-03-26
  08:30:41]
  
  When I specify the following file names in //SOURCE line, it
  works well as expected;
  - Static file name containing Chinese characters
  - Dynamic file name PRVHJB0350_{YYYYMMDD} containing ONLY
  single-byte characters
  
  But, when the dynamic file path contains Chinese characters, it
  seems that UA cannot find the SOURCE file.
  
  I could also recreate this problem using Japanese characters in
  Windows Japanese version.  I think this issue will possibly
  occur when specifying the dynamic file path containing
  multi-bytes characters in //SOURCE line.
  
  
  Detailed Recreation Procedure:
  ------------------------------
    Using Chinese Windows system, it is easy to recreate the issue
  by following the steps below:
  
    1. Create a directory containing Chinese characters, e.g.
  E:\work\(Chinese Chars).
    2. Store PRVHJB0350_20070723.LOG in the directory
    3. Create the following metafile encoded in UTF-8
       --
       //APPL PRVHJB0350
       //NAME PRVHJB0350 E
       //SOURCE FILE E:\work\(Chinese
  Chars)\PRVHJB0350_{YYYYMMDD}.LOG TAIL
       //ATTRIBUTES ','
       Date D 15
       PRVHMD D 10
       Information D 100
       Message Z 2048
       --
    4. Import the metafile to UA
    5. See the TEP client window.  Expected
  "hostname:PRVHJB035000" item doesn't show in the navigator
  window.
  
  
  Related Files and Output:
  -------------------------
    Followings are warning and error messages written in the
  Universal Agent log file (hostname_um_*.log ) when importing the
  metafile:
  ...
  (46A55A8D.0000-8FC:kbbssge.c,52,"BSS1_GetEnv")
  DPTGTDIR="C:\work\(mult-bytes directory name)"
  (46A55A8D.0001-8FC:kbbssge.c,52,"BSS1_GetEnv")
  DPTGTDIR="C:\work\(multi-bytes directory name)"
  (46A55A8D.0002-8FC:kglqpwnt.c,346,"OpenDir") Warning:
  GetFileAttributes
  code <2>
  (46A55A8D.0003-8FC:kglqpwnt.c,348,"OpenDir") Warning: var
  <DPTGTDIR>
  value <C:\work\(multi-bytes director name)>
  (46A55A8D.0004-8FC:kumpdcmf.c,1366,"KUMP_DetermineCurrentMonitor
  FileName
  ") Monitor file directory C:\work\(multi-bytes directory name)
  open
  failed. STC1 status 5
  ...
  
  "(multi-bytes directory name)" is actually Chinese or Japanese
  Kanji characters encoded in UTF-8.  The GetFileAttribute Win32
  API returns the error code 2 (ERROR_FILE_NOT_FOUND) because
  UTF-8 non-ascii characters are passed to it without
  code-conversion.  I suspect this is the cause of this problem.
  

Local fix

• n/a
  

Problem summary

• The path of a file that contains globalized text is not being
  converted, as it should.
  

Problem conclusion

• Added call to a UTF8 method to convert the path part of the
  fully qualified file being monitored.
  
  The fix for this APAR is included in the following maintenance
  vehicle:
      | interim fix | 6.1.0.6-TIV-ITM-IF0005
  
  Note: Search the IBM Technical support web site for maintenance
  package availability
  

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:

Fix information

• Fixed component name

  UNIVERSAL AGENT

• Fixed component ID

  5724K1000

Applicable component levels

• R610 PSY

     UP