APAR status
Closed as program error.
Error description
AppScan Source does not seem to properly resolve the macros when importing a Visual Studio solution file. The VS file contains a macro to the path of the solution file: $(SolutionDir) which is defined here: http://msdn.microsoft.com/en-us/library/c02as0cs(v=vs.100).aspx In Visual Studio, this appears to properly resolve to the location of the solution file, but in an AppScan Source imported solution file, the include directories show that $(SolutionDir) actually resolved to $(ProjectDir) instead. This is causing a problem in terms of being able to locate the proper header files.
Local fix
Problem summary
When a Visual Studio project contained header files referenced using $(SolutionDir), AppScan Source incorrectly resolved the variable to the project directory, rather than the solution directory.
Problem conclusion
The problem has been fixed.
Temporary fix
Comments
APAR Information
APAR number
PM91984
Reported component name
SEC APPSCAN ENT
Reported component ID
5724T5200
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-06-27
Closed date
2013-11-04
Last modified date
2013-11-04
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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSS9LM","label":"IBM Security AppScan Source for Automation"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Document Information
Modified date:
04 November 2013