PM90884: Ouncemake is constructing the wrong path to the source file in the ppf file

APAR status

• Closed as program error.

Error description

• After scanning a C application that was generated with
  ouncemake, AppScan Source is unable to locate the source file;
  ouncemake is constructing the wrong path to the source file in
  the ppf file.
  
  For example:
  In a makefile, one of the compilation commands contain the
  following path to a source file:
  
  \path\to\source\file.c
  
  Even if currently in \path\to\source directory, nmake is still
  able to interpret the location of file.c and compiles everything
  successfully. However, ouncemake is unable to interpret
  \path\to\source\file.c and constructs a relative path to the
  file that is incorrect. For example, in the project (.ppf) file,
  we see the path to file.c as the following using a relative
  path:
  
  .\path\to\source\file.c
  
  Since the ppf file was created in \path\to\source, trying to
  access .\path\to\source\file.c is invalid since that is
  essentially interpreted as...
  
  \path\to\source\path\to\source\file.c
  
  When the .paf file is imported and scanned, the problem is seen
  and AppScan Source is unable to locate the file and scan it.
  
  Ouncemake should be behaving similarly to nmake.
  

Local fix

Problem summary

• The ouncemake utility on Windows was incorrectly interpreting
  paths beginning with \ as relative paths, instead of absolute
  paths.
  

Problem conclusion

• The problem has been fixed.
  

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

  SEC APPSCAN SRC

• Fixed component ID

  5724Z3400

Applicable component levels

• R880 PSY

     UP