Very Computer

Currently I'm trying to evaluate the use of PVCS Tracker 6 along
with PVCS VM (Version Manager) 6.5 and Sybase PowerBuider.
PB and VM integrate rather fine, PowerBuilder's "Library Painter"
has an interated checkout/checkin feature making it unnecessary
to cope with the Version Manager GUI, as far as the PowerBuilder
objects are concerned.

The integration of PVCS Tracker and Version Manager includes
the association of SCRs (System Change Requests) with
actions in VM (like checkin), as well as submitting new SCRs
or update existing ones (TrackerLink), or doing checkout/-ins
from within Tracker (Update/Checkout,-in).
So far, so good ... but there seem to be no integration
of Tracker with PowerBuilder, since the PB Library Painter's
Checkout/-in dialogs are not modified by Tracker's installation
(as opposed to Version Manager, which afterwards had a new button
"Associate SCRs" on the Checkin dialog, and the TrackerLink menu
item under the "Admin").

Is there any way to reach a higher integration ? Checking out
PowerBuilder objects with the Version Manager GUI is only
theoretically possible, since the text files VM stores for
PowerBuilder objects can not be imported into PowerBuilder
directly. You have to add a header line with $pbexport$<object_name>
before export, import it into a work library, modify it there,
export it, delete the $pbexport$ line, check back in
and then synchronize the PowerBuilder Library the object was registered
in. That's simply impossible to perform ...

Any opinions, ideas or insights how to reach a satisfiable
level of integration of the three tools ?

TIA, Werner

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Quote:

>Currently I'm trying to evaluate the use of PVCS Tracker 6 along
>with PVCS VM (Version Manager) 6.5 and Sybase PowerBuider.
>PB and VM integrate rather fine, PowerBuilder's "Library Painter"
>has an interated checkout/checkin feature making it unnecessary
>to cope with the Version Manager GUI, as far as the PowerBuilder
>objects are concerned.

>The integration of PVCS Tracker and Version Manager includes
>the association of SCRs (System Change Requests) with
>actions in VM (like checkin), as well as submitting new SCRs
>or update existing ones (TrackerLink), or doing checkout/-ins
>from within Tracker (Update/Checkout,-in).
>So far, so good ... but there seem to be no integration
>of Tracker with PowerBuilder, since the PB Library Painter's
>Checkout/-in dialogs are not modified by Tracker's installation
>(as opposed to Version Manager, which afterwards had a new button
>"Associate SCRs" on the Checkin dialog, and the TrackerLink menu
>item under the "Admin").

>Is there any way to reach a higher integration ? Checking out
>PowerBuilder objects with the Version Manager GUI is only
>theoretically possible, since the text files VM stores for
>PowerBuilder objects can not be imported into PowerBuilder
>directly. You have to add a header line with $pbexport$<object_name>
>before export, import it into a work library, modify it there,
>export it, delete the $pbexport$ line, check back in
>and then synchronize the PowerBuilder Library the object was registered
>in. That's simply impossible to perform ...

>Any opinions, ideas or insights how to reach a satisfiable
>level of integration of the three tools ?

>TIA, Werner

>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.

JJ,

That's good news, basically. Actually, I already ran
TrackerLink, but I'm not sure about the outcome: When launching
TL, there is a "SCC Provider" checkbox at the top; it is empty
and so is the dropdownlist. When pressing the "Activate" button
I received a warning "You have not selected a SCC Provider. Continue
to register ?". Ater confirming, it says:
"TrackerLink works best with Version software other than you have
 installed. Although the rest of TrackerLink will behave normally,
 you will be not able to attacj revision number to your SCRs
 without using PVCS Version Manager, it's SCC Interface and our
 extensions to the SCC API. Please contact INTERSOLV for the latest..."

My questions:

- Did I miss something during Tracker's installation, so that the
  "SCC Provider" checkbox is empty

- Do I have to purchase any additional, SCC related PVCS components
  (we have licenses for PVCS Version Manager 6.5, and for PVCS
  Tracker 6.0 and PVCS Professional) ?

- Is is possible to get to a state, where I can associate SCRs
  while checking objects out/in from PowerBuilder ?

Any opinions, ideas, experiences or workarounds are welcome ...

TIA, Werner

In article

Ok, I can see clearer now ...

I had to install the PVCS SCC API interface (from the \pvcsscci
folder on the PVCS CD); afterwards, the "SCC Provider" listbox
presented two entries, "TrackerLink" and "Version Manager".
Selecting TrackerLink, I succeeded in connecting thru
this interface from PowerBuilder (I set up a small toy project);
though it seems to be a problem switching interfaces for
existing PB applications (i.e., applications registered for PVCS
native interface in PB.INI).

Anyway, now we can associate SCRs (System Change Requests) with
checkout/-in actions, since with SCC API TrackerLink integrates into
the PowerBuilderLibrary Painter by presenting the TrackerLink dialog
in the course of a check action.

Werner

Quote:> > >before export, import it into a work library, modify it there,
> > >export it, delete the $pbexport$ line, check back in
> > >and then synchronize the PowerBuilder Library the object was
> registered
> > >in. That's simply impossible to perform ...

> > >Any opinions, ideas or insights how to reach a satisfiable
> > >level of integration of the three tools ?

> > >TIA, Werner

> > >Sent via Deja.com http://www.deja.com/
> > >Share what you know. Learn what you don't.

> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.