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: How to Handle Deleted Baselines
Topic Summary: DXL Script Choking on Deleted baselines
Created On: 7-Jan-2008 16:47
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.
 7-Jan-2008 16:47
User is offline View Users Profile Print this message


Tara Wilk

Posts: 43
Joined: 7-Mar-2006

I have a script that loops through baselines. One of my more important
documents has two deleted baselines. Is there any way to check to
see if a baseline has been deleted? (Isbaseline, baseline Exists do not work for this.)

Barring that, can baselines be purged? (Please know that another company is
handling our DOORS admin which is why I'm kind of stuck,)
THanks,
Tara

-------------------------
Tara L. Wilk Curmudgeon-at-large, NGC engineer in spare time
Report this to a Moderator Report this to a Moderator
 7-Jan-2008 16:59
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

Good question.

I'm using DOORS 8.1 and when I run the attached script it doesn't even see the deleted baseline (Baseline 26.0) or it just skips over it.

......
Baseline: 24.2
Baseline: 25.0
Baseline: 25.1
Baseline: 26.1

I'm pretty sure you can't purge a deleted baseline, as once it's deleted it can not be recovered, so in a sense when you delete it you purge it. In 8.1, it only makes an entry in the view baselines dialog that a baseline was deleted.

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com

Edited: 7-Jan-2008 at 17:00 by Scott Boisvert
Report this to a Moderator Report this to a Moderator
 7-Jan-2008 21:30
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Unlike modules and objects which have an invisible deleted state different than the purged state, Baselines (and also attrs) either exist or not. Deleted baselines are gone.

As far as I know there is no way to detect it for sure, but you could infer that a baseline was gone by plowing through History [1] there would be gaps in histor [2] some attributes will magically have changed values between baselines even though there is no History to record the change [3] a deleted non-suffixed baseline should be detectable since its number is missing; that is if baseline 1.1 and 1.3 exist, you can infer 1.2 was deleted; but if 1.1 and 1.2b exist, its not certain that there were any in between. None of these methods are 100% deterministic, however.

- Louie
Report this to a Moderator Report this to a Moderator
 7-Jan-2008 21:33
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

Another question I should probably ask, is if it is really choking on the deleted baseline or if it's choking on a corrupted baseline.

I've had issues with scripts and corrupted baselines, but never deleted ones. For some reason I was able to get around the issue by putting the baselines in an array first, then looping through them to get the info that I needed.

Not sure how I stumbled onto the solution, but I had been working for about 20 hours straight.......The mind was wandering into places I would rather not talk about from lack of sleep....

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com
Report this to a Moderator Report this to a Moderator
 8-Jan-2008 09:20
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

The deleted baseline may be a red herring.

If you are doing stuff with the baseline within a baseline loop then you are asking for trouble. Don't know why - that's just the way it is.

You must instead loop through baselines and store handles in a skip and then access them outside of the loop.

I'll see if I can find the thead where Louie explains his experiences with this issue.

-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 9-Jan-2008 00:48
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Yes I had this years ago. Turns out my outer "for bl in mod do" loop had a nested "for bl in mod do" loop burried in one of the library routines. DOORS doesn't seem to like that at all and the inner loop was messing up the outer loop. Seems to do the same thing if you have nested "for lnk in obj" loops as well.

Yes, the standard method for these things is to insert them into a skip list and THEN deal with them, something like attached. Take note of the 'Sequencer' that insures the baselines are retrived in the original order detected.

- Louie

Be advised that this doesn't work for 'History' types, since making an assignment with a History variable does NOT copy the value, it makes an alias. You cannot therefore plow through History keeping track of the last History that modified Object Text; instead you would plow through counting History, keeping track that perhaps #34 was the last one, then plow through History again until you came to #34.
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.