IV72073: PATH TO MONITORED FILE NAME STARTS WITH DOUBLE SLASHES (//)

Tivoli Log File Agent, Version 6.3.0 Fix Pack 01 (6.3.0-TIV-ITM_LFA-FP0001)
Tivoli Log File Agent, Version 6.3.0 Fix Pack 02 (6.3.0-TIV-ITM_LFA-FP0002)
Tivoli Log File Agent, Version 6.3.0 Interim Fix 05 6.3.0-TIV-ITM_LFA-IF0005

APAR status

• Closed as program error.

Error description

• Using the RegexLogSources option to monitor a file which
  contains a regular expression meta character in the *first*
  directory of the path, the resulting file name path starts with
  2 forward slashes (//).
  For example: RegexLogSources=/LFA_.*/ts_.*\.log
  the File Name field contains "//LFA_test/ts_01.log".
  The extra starting slash is a cosmetic issue only and does not
  cause any issues.  The file is properly monitored.
  
  The extra forward slash at the beginning of the path might be
  seen on the portal in the File Name field in the Data Collection
  workspace or in the agent logs.
  
  Affected Versions:
  The problem exists on Log File Agent v6.3.0 and v6.2.3.2.
  This problem is platform independent.
  However on Windows systems, if you specify the drive letter
  preceding the path in the RegexLogSources option, the problem
  does not occur.
  
  Problem Determination:
  On the the portal in the File Name field of the Data Collection
  workspace, the File Name field contains, for example,
  //LFA_test_logs/ts_01.log
  
  On the LO agent system, enable a minimum of the following
  tracing:
  KBB_RAS1: ERROR (UNIT:kumpdcm ALL)
  
  The following trace points in the the agent RAS1 log
  <hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log show the
  double forward slashes:
  
  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  - - - -
  ...
  ...:kumpdcm2.c,279,"KUMP_GetNextMemberDouble") Directory /
  Member
  LFA_test_logs matched ^LFA_.*$; FilePathSpec2 NULL; and will
  now use //LFA_test_logs
  ...:kumpdcm2.c,161,"KUMP_GetNextMember") Entry
  ...:kumpdir.c,139,"KUMP_OpenDir") Successfully opened
  directory //LFA_test_logs 7F1748059310 7F1748059390
  ...:kumpdcm2.c,179,"KUMP_GetNextMember") Directory handle
  7F1748059310 name //LFA_test_logs was successfully opened
  ...
  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  - - - -
  
  RECREATE INSTRUCTIONS:
  
  1. In the .conf file, specify RegexLogSource which contains a
  regular expression meta character in the *first* directory of
  the path.
  
  2. Start the kloagent and monitor the file.
  

Local fix

•  None.
  
  Workaround: On Window systems, if you specify the drive letter
  preceding the path in the RegexLogSources option, the problem
  does not
  occur.
  

Problem summary

• Using the RegexLogSources option to monitor a file which
  contains a regular expression meta character in the first
  directory of the path, the resulting monitored file name path
  starts with 2 forward slashes (//).  This can be seen in the
  agent RAS1 log
  <hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log and in
  the File Name field of the Monitored File Status.
  
  The extra starting slash is a cosmetic issue only
  

Problem conclusion

• Check if there is a slash in the directory name before adding
  one.
  
  The fix for this APAR is included in the following maintenance
  vehicle:
  
     | interim fix | 6.3.0-TIV-ITM_LFA-IF0005
  
  Note: The Log File Agent fix is available at
  http://www.ibm.com/support/docview.wss?uid=swg24041113
  

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

  ITM LOG FILE AG

• Fixed component ID

  5724C04LF

Applicable component levels

• R630 PSY

     UP