When you try to generate a document-style report from either the
Publish menu in IBM Engineering Requirements Management DOORS
,
or the IBM Engineering Lifecycle Optimization - Publishing
Launcher, you
receive a DXL error.
About this task
Note: If you generate a document-style report from a Engineering Requirements Management DOORS view
that has many elevated columns, you may receive a DXL halted with runtime error. To work around this
problem, redesign the template to use the Module/Object/Column query and identify the columns by
their name attribute.
Error examples:
E- DXL: <Line3>could not open include file (source/DOORS/dxl/schema
discovery/const.inc) (No such file or directory).
E- DXL: <RPE_HOME\source\DOORS\dxl\doors driver\getDOORSVersion.dxl:>could not open
include file (source/DOORS/dxl/doors driver/getDOORSVersion.inc) (No such file or
directory).
This issue is caused by how Engineering Publishing refers to
the getDOORSVersion.inc files needed for the DOORS
data extraction. In PUB, the
.inc files are referred to with relative paths instead of absolute paths. If
DOORS is
already installed when you install PUB,
PUB
creates the add-ins registry so that DOORS
can resolve those relative paths. If PUB
installed before DOORS ,
this registry cannot be created, which often results in DXL errors. If the error was caused for this
reason, you can reinstall the PUB
add-ins.The path that is specified in the add-ins registry includes a full path, which is built
by the DOORS
DXL interpreter with the relative path that is provided by PUB and with
the base
folder that is specified in the addins property of your DOORS
installation. Example: HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.X\Config.
If you installed the products in the correct order, it is also possible that a command-line entry
overwrote the value set in this registry. For example, the key
HKEY_CURRENT_USER\Software\Telelogic\DOORS\9.X\Config also was also created and
had overwritten the value set in HKEY_LOCAL_MACHINE registry key. If the error
was caused for this reason, you can specify the add-ins path as a command-line option when starting
DOORS .
Select one of these workarounds:
Procedure
-
Uninstall and reinstall the PUB
add-ins:
-
Start IBM Installation Manager.
-
Click Modify.
-
Select PUB and
click Next.
-
Select the languages to install and click Next.
-
Clear the Install add-ins feature and click Next.
Note: Launcher">You
cannot clear the Launcher
feature selection.
-
Review the summary by verifying that the add-ins are listed in the Removing
Feature section, and then click Modify.
-
When the modification completes, click Finish.
-
Click Modify.
-
Select PUB and
click Next.
-
Select the languages to install and click Next.
-
Select the Install Addins feature and click Next.
Note: Launcher">You
cannot clear the Launcher
feature selection.
-
Review the summary by verifying that the add-ins are listed in the Adding Feature section, and
then click Modify.
When the add-ins are reinstalled, PUB creates
an entry for the add-ins in the registry.
-
When the modification completes, click Finish.
-
Add the path to the PUB
installation in the DOORS
registry keys.
-
Start DOORS
with the
<addins> command-line switch.
Specify the add-ins path as a command-line option when starting
DOORS .
Example:
C:\Program Files\IBM\Rational\DOORS 9.x\bin\doors.exe
-data 36677@giediprime
-addins C:\Program Files\IBM\PUB
Note: If the path to the add-ins folder contains
spaces, enclose it in quotation marks.
-
Copy the PUB DXLs
into a folder that is already known to DOORS .
If you already use the add-ins command-line switch and do not want another folder added to it,
you can copy the entire source folder from PUB
installation into the folder that is specified by the add-ins switch. For example, if you start
DOORS
with the following command: C:\Program Files\IBM\Rational\DOORS 9.x\bin\doors.exe
-data 36677@giediprime -addins Z:\DOORS\SharedAddins
, then you must copy the
source folder into the Z:\DOORS\SharedAddins folder.