IBM Support

PM16375: addins locations are not getting detected by DOORS in batch mode

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem
    Addins locations don't get picked up by DOORS when running in ba
    tch mode. Using exactly the same settings in non-batch mode is s
    uccessful.
    
    This applies to addins specified in either the registry, or comm
    and line.
    
    This results in errors such as 'No such file or directory' when
    running in batch mode with batch startup files #including files
    in the addins location
    
    To Reproduce
     - create a network share \\host\share and add this as an addins
     entry in the registry
     - create a folder 'config' in the share, and a file inside call
    ed batchInclude.dxl
     - inside batchInclude.dxl define 'string ss = 'ABE' '
     - create a file inside your batch startup files called batchSta
    rt.inc
     - inside batchStart.inc enter '#include ?config\batchInclude.in
    c?'
     - run DOORS in batch mode
    
    An error appears stating that the file batchInclude.inc couldn't
     be found.
    
    This works when running in non-batch mode, and using the standar
    d startup files location.
    
    Possible Workarounds
    Use full, static paths for include files?
    
    Additional Notes
    Introduced at some point since v8.3.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Addins locations don't get picked up by DOORS when running
    in batch mode. Using exactly the same settings in non-batch
    mode is successful.
    
    This applies to addins specified in either the registry, or
    command line.
    
    This results in errors such as "No such file or directory"
    when running in batch mode with batch startup files
    #including files in the addins location
    

Problem conclusion

  • The code has been changed so that addins locations are now
    used when running DOORS in batch mode
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM16375

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-11

  • Closed date

    2010-09-17

  • Last modified date

    2010-09-17

  • 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

    TLOGIC DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R920 PSN

       UP



Document information

More support for: Rational DOORS

Software version: 9.2

Reference #: PM16375

Modified date: 17 September 2010