![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Automate the Archiving Processing Topic Summary: Created On: 27-May-2005 20:39 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have a script that loops through all of our projects in a DOORS 7.1 database and archives them.
I have tested running the script in DOS batch mode and scheduled the task. I am just wondering if anybody has done something similar of automating the archival process, or knows of any "best practises" which we can use? Does Telelogic have any add-on products to automate the process? |
|
![]() |
|
![]() |
|
v52 left LOTS of residual locks which prevented any archiving (thousands every week). Our archive script had to get a list of all the locks in the database and then remove them. Turns out if someone had a module open Exclusive, it remained open on their client when the server was remote (typical), but successfully closed the module when the server was local (my local Sandbox).
v71 seems to clear up residual locks; but your archive won't work if someone left a module open. Don't have a good way to log everyone out of DOORS, disable logins, remove the locks, and THEN archive everything, then enable logins. But I may find a way to turn off the DOORS service, then start it, then run the Archive figuring nobody has had a chance to login. Putting the date in the name of the file makes it easier to identify later. Perhaps: string NameProjArchive = "Project_" name(proj) "_" today() ".dpa" - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Automate the Archiving Processing
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.