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: [DOORS 8.0] quit after script execution in batchmode
Topic Summary:
Created On: 15-Dec-2005 09:59
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.
 15-Dec-2005 09:59
User is offline View Users Profile Print this message


Ben Herfurth

Posts: 37
Joined: 9-Jun-2005

Hello,

I am executing scripts via batchmode in WinXP. After the script finished DOORS tells me to "Hit Enter" to exit doors. Is there a batch option, so doors exits itself after executing the script? Doors 7.1 did it by default, and I dont find an option for DOORS 8 to do so too.

Anyone any idea? a dxl command will do fine too, if there is one.

Thanks in advance,

Ben




Edited: 15-Dec-2005 at 10:03 by Ben Herfurth
Report this to a Moderator Report this to a Moderator
 15-Dec-2005 22:46
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I had a big pile of maintanence DXL running every morning, scheduled to run back to back, running in v7.1. Had this problem but don't recall how I dealt with it. However, this is how I schedule DXL to run:

[1] The Scheduled task says to Run: C:\DOORS-Stuff\DosBatFiles\CpsReport-DDX-Batch.bat
[2] This batch file looks like this:
"C:\Program Files\Telelogic\DOORS 7.1\bin\doors.exe" -u landalo -P "MyDoorsPassword" -b "C:\DOORS-Stuff\DXL-v7\BatchStuff\CpsReport-DDX-Batch.dxl"
[3] The CpsReprt-DDX-Batch.dxl file is pretty tricky since it executes a file that has the ability to display a dialog and run interactively. That is, the original knows not to "show" the dialog when in batch mode, and all the confirm's are designed to handle "true" as the default action. But lets suppose your DXL written is designed to work in batch mode.

I have this nagging memory that the "hit enter to exit DOORS" message is received if the batch program does any "ack"ing or its ilk, or does any "print"ing. The DXL output window is displayed. Once I figured out how to trap all those and direct them to an output text file, the batch file ended naturally; which had the huge desirable effect of freeing up virtual memory before the next batch was run.

I had to write two special Include files for running batch. The first one defines new functions for all normal outputs from DXL, there is an "ack(string)" and a "message(string)" and a "print(string)" functions. These functions insert the string message into a buffer with an EOL. The second one is included after the main program, and outputs this buffer to a text file and then displays it. It was pretty ugly overall, but I can now run my normal interactive DXL in batch mode if I need to.

- Louie
Report this to a Moderator Report this to a Moderator
 21-Dec-2005 17:53
User is offline View Users Profile Print this message


Kevin James

Posts: 32
Joined: 12-Dec-2005

Hey Ben,

I am very new to DOORS, but in playing around with DXL today I have found that the output window does not open if I don't do any printing (all my output is going to logs).  The "doors -b" command seems to run and exit quickly without ever popping up that extra window.

Kevin
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.