Hello Anne,
We are using PowerBuilder and Clearcase for some months now. We have put
both the pbl's and the objects under source control, and are labeling both.
I think this is the most secure solution.
Problem 1 : I haven't had this problem (yet)
Problem 2: Apparently, when you do a hex dump of the .srd-files, you will
notice that they all end with 0x0D 0x00. This last character makes Clearcase
believe it is a binary file. I believe this is more a Powerbuilder bug than
a Clearcase bug.
Unfortunately, I don't have an easy solution for it.
Problem 3: We have faced the same problem over here. The only solution,
although I don't like it, is to use a shared view. We have created a view
per project. All developers working on a project, work in the same view.
We have also another problem : If you use in the configuration file another
view, than the one you are using to browse through your files, Powerbuilder
will select the view in which you are browsing, to display the files, but it
will use the config spec of the view in the configuration file when you do a
checkout. This may lead to creation of branches you don't want.
Hope this helps,
Christophe Beunens
> ----------
> From: Reichert, Anne @ Horsham[SMTP:ReichertA@CROWNVANTAGE.com
> Sent: Monday, January 03, 2000 22:46
> To: cciug@Rational.Com
> Subject: [cciug] Using ClearCase to version PowerBuilder Objects
>
>
> This mail is strictly for people using PowerBuilder's SCCAPI to ClearCase.
> I'd appreciate any help or advice there is out there.
>
> I have been using ClearCase to version PowerBuilder objects for at least
> 18
> months now. Our platform is Windows NT 4.0 service pack 3, PowerBuilder
> 6.5
> and ClearCase 3.2.1. My largest application is made up of 70 pbls
> containing approximately 2800 objects. We use multiple branches and
> config
> specs in order to support production and development at the same time and
> every developer has there own set of views (1 for production and 1+ for
> new
> development). One thing that puzzles me, from searching the CCIUG
> archives
> on a key word of "PowerBuilder" is the number of people who are versioning
> their pbls. Everything I had read (granted there was not much provided)
> advised against versioning pbls. And right now I can't even imagine
> versioning the pbl and not the object. I have run acrossed many little
> problems and some larger ones and have gotten next to no help from
> ClearCase
> tech support. I feel their knowledge base when it comes to supporting
> ClearCase and PowerBuilder is very limited. Initially they respond to my
> problems then they never get back to me and provide any answer or
> solution.
> This has happed several times, so lately I don't even call I just get
> frustrated and then develop a work around or solve the problem myself.
> Anyway, I guess I though I would see if anyone else out their has the
> encountered the same problems as me.
>
> Problem # 1: Occasionally the registration symbol will disappear from
> next
> to the object, but the exported text file does still exist in the VOB.
> You
> can not reregister it, you get the message "object already is registered",
> and you can not unregister it, you get the message "object not previously
> registered". What has happened is that the connection between the object
> in
> the VOB and PowerBuilder has been lost and I can not figure out how to
> reconnect it. This problem has happened when a checkin occurs while in
> PBNATIVE and not SCCAPI. It has also happened when clearing a checkout
> has
> failed due to unknown reasons.
>
> Problem# 2: I am unable to perform cleardiff or a merge on datawindows
> with
> the extension .srd. I get a message telling me "can not perform
> diff/merge
> on binary data". Well they are not binary data files to say the least and
> no one at tech support was able to help me define them as anything
> different. I don't think they even understood the problem.
>
> Problem#3: In PowerBuilder, an object is checked out by a view other than
> your own. You do a version tree on the object, and the version tree
> displayed is based on the config spec of the view that has the object
> checked out, not your own. This is easily recreated, the view name is
> displayed at the bottom of the version tree. If you do the version tree
> on
> the exported object through the Explorer integration the information
> displayed is accurate. The problem only happens when an object is checked
> out and you are looking at it through PowerBuilder. I see this as a
> critical problem. I am not able to build on anything other that the
> checked
> out object, because I can not get any other version of the object
> synchronized into my pbl. The only work around is to have the developer
> check in the object temporarily, and this is getting to be unacceptable.
> After several emails and phone calls to tech support on this issue, (and
> they had no problem recreating the issue) they never got back to me with a
> solution.
>
> Sorry for being so long winded, I figured I would get it all out of my
> system at once. I do have other questions and problems but these are my
> first priority.
>
> Thanks,
>
> Anne Reichert
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
Visit us at http://www.cedelinternational.com
or http://www.cedelglobalservices.com
or http://www.cedelbank.com
***************************** IMPORTANT MESSAGE *********************************
Internet communications are not secure and therefore Cedel International does not accept legal responsibility for the contents of this message.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Cedel International or any company forming part of Cedel International.
*********************************DISCLAIMER *************************************
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:16 EDT