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: CP dxl
Topic Summary:
Created On: 19-Apr-2004 19:56
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.
 19-Apr-2004 19:56
User is offline View Users Profile Print this message


Timothy Ryan

Posts: 5
Joined: 17-Nov-2003


Hi all:

I have read all of the messages on the system about generation of metrics and have downloaded Dave's *.dxl script from last year.

I too need to generate a status-report showing the status of each CP since the last baseline (rather than a simple metrics report). ... i.e.:

- CP's added
- CP's rejected
- CP's reviewed.
- CP's Approved
- CP's Applied

The manual process of calling up each module and filtering multiple times it is HORRENDOUS in my environment (many many modules).

I have written quite a few *.dxl scripts now but this one has me stumped as I have searched through the entire *.dxl manual and it is no help at all wrt accessing CP information.

Did anyone ever manage to get such a *.dxl CP script to work?

Thanks

Tim Ryan

tryan@drs-esg.com (work)
timDavidRyan@aol.com (home)
Report this to a Moderator Report this to a Moderator
 19-Apr-2004 21:44
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

CP information is housed in the CP partner module; NOT in the live module.

There is a dxl function: string fnGetCPModulePath(string NameFull)

It gets the name of the CP partner module of the given live module. I'd be tempted to write a function:

string fGetCPName(Module mCurr)
{ // Get the name of the CP partner module
if (null mCurr) return("")
return(fullName(mCurr))
}

Module mCurr = current
string NamePartner = fGetCPName(mCurr)

Then open the partner. Then start looking for CPs yaddy yaddy via the CP module's attributes.

- Louie

Perhaps you should remove your home email from your Sig.

Edited: 19-Apr-2004 at 21:45 by Louie Landale
Report this to a Moderator Report this to a Moderator
 20-Apr-2004 14:15
User is offline View Users Profile Print this message


Grant Cyboron

Posts: 6
Joined: 28-Jan-2004

On the other hand, if all you want to do is open the CPS Partner module, there is a function "fnCPS_OpenPartner(current Module)" that will directly open the CPS partner of any module you can get a handle for (assuming it has a CPS partner of course). It is in "standard/cps/partner/partner.inc" so you need to do a #include of that file first. It makes the CPS Partner the current module when it is opened. I have used this in a script to generate some statistics on how long Change Proposals entered against the currently open module have been in various states without being acted on.

Another case of a function that is not documented. Found this one by poking around in the "standard" folder. It is the only thing in the "\standard\cps\partner\partner.dxl" file.

Grant Cyboron

-------------------------
Grant Cyboron
L-3 Communication Systems East
mail grant.cyboron@l-3com.com
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.