Import/Export and ClearCase version control
Posted 18 September 2002 - 04:05 AM
am in the process of migrating from Native Version 40R518 to Native Version 50R109.
In V50 I have seen a new (to me) import/export menu P4X.
This produces a *.jbx file as opposed to a *.prx.
I haven't had much luck finding any documentation on P4X so was wondering if anyone had any experience using it.
Readability of the export file is of particular interest as the company I work for has recently adopted Rational ClearCase as its version control application of choice. However, all the nice comparison features work well and good on HTML etc, but aren't of much use when looking at *.prx files.
Basically I like to hear from anyone who's had experience (good or bad) using a version control application like ClearCase with ProIV - how you went about it/useability/etc.
Any and all help will be much appreciated.
Thanks and regards,
Posted 18 September 2002 - 12:54 PM
The P4X menu used to be there is 4.6 also.. I think.
It seems to be the same as the SuperLayer import/export with a few extra things.
The .jbx that you talk about is the export file type that is used for exporting 'Task' definitions that are used by the 'Bus & Tasks' part of ProIV. This has been around for some time.
Posted 18 September 2002 - 01:20 PM
However, I'm actually 95% of the way through a project that partially integrates ClearCase with ProIV. It can't tell the difference between versions of prx's (we tried all sorts of horrible things), but it does do all the check-in, check-out, version history and so on.
End result - we have a list of every function, file and global logic sat in the clearcase explorer, user does a check-out, it imports that version into the dev system, and when they check-in, it grabs a copy back.
Next job is automatic label deployment...
Posted 18 September 2002 - 01:59 PM
This allows a more efficient storage of the source as most CMS store only differences on ASCII files.
One tip - don't do as I did and use different file formats for Screens, Reports & Updates as someone is sure to rewrite a Function & change the type!
Posted 19 September 2002 - 01:27 PM
A few years ago, I did a considerable amount of research and development work on representing Pro-IV source as text for configuration management purposes.
I created some components which I call 'text adapters' to extract and replace Pro-IV source code in a human-readable (and hence CMS-friendly) text-file format.
I spoke to several organizations using Pro-IV but in the end it seemed unlikely they would be prepared to pay enough for the product to justify developing it fully. It was therefore put 'on the back burner' as they say.
Basically, because the text adapters are only a part of the overall configuration-management puzzle, it was difficult to find a pricing strategy likely to recoup the development costs. At the time, it seemed a user-base larger than I though was likely would be needed to drive the price point down.
Then again, perhaps I was speaking to the wrong people
As it happens, I have done some more work on the adapters this year as part of another project and I could probably provide a (restricted) demo in one or two months if people were sufficiently interested.
If I was persuaded enough people would purchase this as a commercial product at a viable price then I would certainly consider pursuing it.
Posted 19 September 2002 - 02:30 PM
If you have the bootstraps then a basic dump to a sequential file based on PROXFR1 should be pretty easy. I'd be happy to provide advice, but talk to Richard - he's working at a more creative level on this.
Posted 19 September 2002 - 08:49 PM
Unfortunately I'm not allowed to post the source as it would probably violate PRO-IV's NDA's
Might be able to post a runtime version - at the moment though it's in v4.0.
However I have seen several companies out there which have signed PRO-IV NDA's which contain words to the effect of 'you must NOT NOT redistribute PRO-IV bootstraps'
Posted 20 September 2002 - 07:22 AM
Enhancements to the system were the usage of a P_LINT function to compare functions and show any suspect code and a comment function that removed any unused logics and placed common comments in all used logics.
Posted 20 September 2002 - 10:22 AM
If there were really only one customer it would probably make sense to cut some corners on platforms and areas of Pro-IV which were not used. However, I think that is very unlikely to be a realistic scenario.
To do the job properly, I would guess at a ballpark cost of $250K. Please note this is strictly a well-informed guess and no detailed estimating has been done.
Please note that this definitely would not allow for mainframe support - for which I would need access to suitable facilities and probably some additional technical assistance.
I am also assuming V5 will not introduce any fundamentally new problems - I haven't got into V5 in sufficient detail yet.
Posted 20 September 2002 - 12:42 PM
The 5.0 bootstraps are not much different than 4.6. So it shouldnt cause you too much of a problem.
5.5 has a few extra files, due to the support of ActiveX, but I dont think it will be that complicated. But I havent looked into it yet.
The problem you will have, is VIP. Basically the VIP files seem to be a copy of the standard files, obiously with extra fields and they are keyed differently. There are also LOTS of extra Xref files.. totaling upto above 100.
That is gonna cause lots of problems for people who have there own utils... If you use VIP that is. If you dont use it then you will be fine, with a few mods.
Posted 20 September 2002 - 01:16 PM
Is there any procedure for loading a non-VIPped function (eg. one imported from V4.x) into a VIP environment?
In other words, is there something that can be run to create all the necessary cross-references and so on for otherwise correct source code?
Seems to me such a facility would be important anyway.
Posted 23 September 2002 - 03:05 AM
Ok, after a quick look, this should import a function into VIP... But I haven't checked it out thoroughly.. so be careful
1) Remove the Prod flag from the function @VIPW510 in $SM
2) Go into @FUN with the function @VIPW510 and window on the Parameters field.
3) Hit add mode and enter a new param with the following values I,$FUN,A,8
4) DO NOT try to gen this function, as its run time only!!
5) Then in your function you can GLOBAL_LSCALL(@VIPWFUN,0001) and set the parameter to the function you wish to import into the VIP bootstraps.
I think this should be ok... but have a play around with it, cause I've just worked it out since there are no docs/info about it.
And its probably best if you do it in a test env first, cause you never know what could happen...
Posted 23 September 2002 - 12:01 PM
By opening a single native function it will automatically be loaded to VIP if not present.
On the subject of case integration:-
VIP is delivered with a set of Stub functions (source provided that may be tailored for this purpose. These
are called @VIPSBnn and are invoked when the CCN option
is ticked (within Administration). CCN short for change control number has been designed to provide permit/block and
change number assignment against the VIP object booking model. I will be publishing more on this shortly and welcome input in this area.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users