Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Automatically run export script in regular intervalls
Topic Summary:
Created On: 16-Mar-2006 15:08
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 16-Mar-2006 16:09
User is offline View Users Profile Print this message


Pekka Mäkinen

Posts: 276
Joined: 18-Mar-2004

You can use batch mode to run your script and then use some operating system command to schedule the running of this batch mode script. For more information, use the search function to search for "batch mode" if this forum (DXL Exchange).

-------------------------
Pekka.Makinen@softqa.fi
SoftQA Oy -http://www.softqa.fi/
Report this to a Moderator Report this to a Moderator
 20-Mar-2006 17:41
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Getting regular scripts to run in batch mode is a bit of a drag. Of major consern are [1] scripts that require a current module. Batch Mode scripts will need to open a specific module since there are no open modules when the script starts. [2] Confirm, Query, and dialog boxes cannot get any input from the user since there is no user to push the buttons.

No, you need to write DXL specifically intended for batch mode. Fortunately your code can include "if (batchMode())" statements to deal with the differences; e.g. "if (batchMode()) Response = 0;else Response = query("What do you want to do", Options)". Another example I use is this: "if (batchMode()) <call the main "DoIt" apply callback on the Dialog>; else show dbDialog". That is, in batchMode presume the user pushes the "OK" button on a dialog that you've Realized but not yet Shown.

Once you do that you need can schedule a task whose "target" is something like this: "...\bin\doors.exe -u MyUser -P MyPassword -b MyBatchMode.dxl" Notice your password is typed in UNencrypted. That can be a real beast for security. What I did was create a local DOS batch file with that target within it, and restricted R access to the batch file to myself only (so Only I can see my password). Now the Scheduled tast invokes the batch file and anyone can see the schedule task. Scheduled tasks will require you to input your system login name and password in the "Run As" section; but that stuff is encrypted so its OK.

Its real sticky.

- Louie
Report this to a Moderator Report this to a Moderator
 22-Mar-2006 01:25
User is offline View Users Profile Print this message


Dermot O'Bryan

Posts: 1
Joined: 21-Dec-2005

I have a similar problem in that I am calling via RunFile()  from an external application.  When I run the script localy with the module open it works correctly.  When I run it from the execuatable which starts a new session of Doors, it gives an error when I try to read data from the module selected.  I am stuck as the command to 'Open' the Module. Is there an alternate mode to access the data without 'Opening' the Module? If not, what command do I use to open it?
Report this to a Moderator Report this to a Moderator
 22-Mar-2006 06:19
User is offline View Users Profile Print this message


Pekka Mäkinen

Posts: 276
Joined: 18-Mar-2004

You open a module either in read-only mode or in exclusive edit by the read or edit commands:

From DXL Help:

read, edit, share (open module)
Declaration
Module read(string name
[,bool disp])
Module edit(string name
[,bool disp])
Module share(string name
[,bool disp])
Operation
These functions return a module handle for the module named name. The name argument can be an absolute or relative path. The read function opens the module for reading, edit for unshared editing, and share for shared editing. The optional disp flag allows the visibility of the opened module to be specified; the module is displayed in a window if disp is true or omitted.

-------------------------
Pekka.Makinen@softqa.fi
SoftQA Oy -http://www.softqa.fi/
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.