IBM Support

PM19811: exporting RIF defintion without locks fails when a layout DXL co lumn is included in the view


You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem
    When you export a RIF definition in which a module has a layout
    DXL column which uses DXL to trace changes in a target module an
    d the 'locks for local data' is set to 'no locks' or 'no locks.
    exported data is read only', then you will get an error when you
     try to export the RIF partition and it will fail.
    To Reproduce
    - create modules 'source' and 'target' with some objects
    - create links from source to target
    - create a trace column in source using the analysis wizard repo
    rting on out-links
    - save the view as v
    - create a RIF defintion in the parent project
    - add source (module version: current, locks for local data: no
    locks, include data in view: v)
    - add target (module version: current, locks for local data: no
    locks, include data in view: standard view)
    - add link module
    - shutdown and reopen the DOORS client
    - try to export the RIF definition just created
    - error: 'could not open module 'target' - formal module is not
    open for edit'
    Possible Workarounds
    don't include the layout DXL in the view
    use some sort of locks in the 'locks for local data' option
    Additional Notes
    in DOORS 9203 this fails with a diagnostic log and DXL error
    in 9202 and 9204 this will fail without a diagnostic log

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * PROBLEM DESCRIPTION:                                         *
    * RECOMMENDATION:                                              *
    Layout DXL with trace information opens the modules at the
    end of the link when the view is selected.
    The RIF export is not expecting these modules to be opened
    in this mode when exporting causing the error.
    - error: "could not open module 'target' - formal module is
    not open for edit"

Problem conclusion

  • Ensure all modules that are opened during each pass of the
    RIF code are closed by iterating over the modules that are
    open within the project and closing any that were not open
    at the start of the export where required.

Temporary fix


APAR Information

  • APAR number


  • Reported component name


  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention


  • Submitted date


  • Closed date


  • Last modified date


  • 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


  • Fixed component ID


Applicable component levels

  • R920 PSN


Document information

More support for: Rational DOORS

Software version: 9.2

Reference #: PM19811

Modified date: 08 December 2010