PM98302: Windows backslash under Build Forge 8.0 .bset treated as escape characters

APAR status

• Closed as user error.

Error description

• When attempting to use Windows path syntax using backslashes,
  they are process as escape characters during build execution.
  This can cause the expected command syntax to be improper and
  fail the build step.
  
  Steps to reproduce:
  
  Create test project that can be used to configured a variable
  via .bset using the Windows path syntax
  
  ie:
  .bset env 'CCview=M:\${viewname}'
  
  Expected result:
  
  The .bset variable is configured as expected.
  
  ie:
  456   Sep 8, 2013 5:25:21 PM      STEP   .bset env
  'CCview=M:\${viewname}'
  457   Sep 8, 2013 5:25:24 PM      EXEC   .bset env 'CCview' =
  'M:\WinView32-102' (New Variable)
  
  Actual result:
  
  The .bset variable is configured incorrectly, as the backslash
  is used as an escape character for the '$'.
  This causes the variable syntax expected to be resolved to be
  assigned to the variable.
  
  ie:
  349   9/14/13 12:56 PM      STEP   .bset env
  'CCview=M:\${viewname}'
  340   9/14/13 12:56 PM      EXEC   CRRBF0406I: .bset env
  'CCview' = 'M:${viewname}' (New Variable)
  
  Workaround:
  
  Added additional backslashes to be processed correctly.
  
  ie:
  .bset env 'CCview=M:\\${viewname}'
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• as described in variable interpretation documentation,
  backslash characters escape the next character from
  interpretation.  This is the expected behavior.
  

APAR Information

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

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

Fix information

Applicable component levels