![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Null Module message when DXL is run in Batch mode Topic Summary: Created On: 31-Dec-2008 18:34 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have a number of scripts that I run outside of DOORS in order to export data. It's been a while since I ran these scripts and I believe we may have upgraded from DOORS 8.1 to DOORS 8.3 since I last ran them.
Anyway, for some reason, these batch process DOORS scripts don't seem to work any more - with the problem being that the project name referenced in the DXL script isn't located. When I run the script in batch mode, I get a "-I- DXL: null module" message in my DOS window. Here's the thing, I can run this exact same script from within DOORS and it works just fine. To further complicate this issue, I should mention that I have similar scripts that I run on another DOORS database (also Version 8.3) in our company that are written exactly the same, and they work in batch mode. I've attached an example from the end of a script that exports to HTML. This script worked fine until recently, and I now get the dreaded "Null Module" message above when run in batch mode, but it runs just fine from within DOORS. Any suggestions? Thanks!! |
|
![]() |
|
![]() |
|
One possible cause for this is that in batch module there is no explicit current module, thus if your code expects a current module, you have to set it yourself.
------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
|
![]() |
|
Thanks, but my script explicitly calls out the module name. It actually works from another users PC, so I'm guessing now that it's an access issue.
|
|
![]() |
|
![]() |
|
Just a hunch, but I suspect a name clash with a global variable.
Try enclosing the entire script in braces {} and try again. Also ensure that autodeclare is turned off. ------------------------- Tony Goodman Smart DXL limited www.smartdxl.com |
|
![]() |
|
![]() |
|
Eureka!!
Enclosing the entire script in braces, as you suggested Tony, did the trick!! I'm all set, but I'm curious about the reference you made to making sure "autodeclare" is turned off. I searched the DOORS and the DXL help files on "autodeclare" and couldn't find a thing. Nevertheless, the adding of braces to the entire script removed any potential conflict with DOORS global variables, and I appreciate your suggestion. Sorry it took a while to reply, but I didn't receive any notification that my topic had any recent activity, so I'll look into how that gets set in this forum. ("Recieve notification when new comments are added...") Thanks again!! |
|
![]() |
|
![]() |
|
There is no help on autodeclare.
It is discussed here ------------------------- Tony Goodman Smart DXL limited www.smartdxl.com |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.