version control tool
kr
environment. What tools are stable and proven?
Pardon me if this is too simple question..I am new to nonstop .
Keith Dick
The only version control program I know of for use from Guardian is CONTROL, from the company named Network Concepts (NCI):
http://www.nci-sw.com/control.htm
I have never used it, so I cannot tell you anything about it. Maybe someone else who has used it will see your post and respond with more information about it.
There might be more Guardian-based version control programs. If so, I hope someone else will post information about them for you.
At one time, there was a rather good Guardian-based version control program only for internal use in NonStop software development. I am pretty sure it was dropped some time ago, in favor of a PC-based version control program. In any case, it was not available outside of Development.
If you are willing to do your version control work using a Unix tool and have the OSS environment installed, you could get RCS from the ITUG library of open source products and use it. The ITUG open source library is here:
http://ituglib.connect-community.org/apps/Ituglib/SrchOpenSrcLib.jsf
That ITUG open source library is available to anyone. ITUG has another library of user-contributed programs that is available only to ITUG members. I looked through its index, but did not see any version control program there.
If none of those options seems suitable to your situation, do keep in mind that you could use a version control system on another system, such as a PC-based version control system or a Unix- or Linux-based version control system. The extra steps of moving the source files to and from the NonStop system make that approach a little less desirable, but it does work.
kr
Thanx Keith again.
I went thru this list before troubling with my question. The CVS is
available as part of this, but I don't know it is only for for OSS.
The documentation says "
"If you have a NonStop Integrity or Blades system running H- or J-
series NonStop OS, the binaries download is contained in the file with
the 'TNS/E' link. If you have a Himalaya running G-series NonStop OS,
the binaries download is contained in the file with the 'TNS/R' link."
&& CVS has TNS/E for the latest version.
Yes, PC based approach is bit cumber some and error prone to human
errors. Also, it limits automated builds/tests/check-in mails etc.
Wonder how nonstop developers are managing without these tools in
place:)..
dimandja
Good question. Before moving to Tandem (almost 30 years ago), I
worked on a large IBM system (government sponsored with all the bells
and whistles included). When I took the plunge to Tandem, I did feel
a bit naked. There were no groundbreaking tools besides a bare-bone
Edit and a few other plain trinkets.
But, Tandem programmers proved quite inventive in developing their own
tools. That appealed greatly to me. Working on Tandem was like being
a systems guru, a database designer, and a developer, all rolled up in
one. It was way more exciting than being a mere consumer on a mega-
mainframe.
A regular Tandem programmer is far more knowledgeable about their
machine than any regular mainframer.
Randall
The two leading production SCM solutions specific to NonStop are NCI's
Control (as above) and Emperex' PrimeCode/RMS (www.emperex.com). Both
have long and good track records and understand Guardian and OSS file
systems. If you want to use either of these with ECLIPSE on
workstations, I can help with that part.
Randall
r_s%b^e_c!k_e&r@n%e_x_b_r_i_d_g_e(dot)com (remote all the funky
characters, please).
Keith Dick
I see that the short bit of documentation on the ITUGLIB web page does not specifically say that the programs work only in the OSS environment, but that actually is the case. The NonStop OSS environment is reasonably close to a POSIX-compliant environment, so porting open source packages, most of which are developed for Linux or BSD systems, to OSS is usually pretty easy. The Guardian environment is not at all close to being a POSIX-compliant environment, so it is not practical to try to get most open source packages to work in Guardian.
Now, it is possible to issue OSS commands from the Guardian environment, using the OSH command from TACL. So I think it would be fairly easy for programmers working in the Guardian environment to use a version control program that sits in the OSS environment. A few TACL routines probably could make that fairly easy to use.
Some developers much prefer doing their editing and compiling on the PC, using ETK or the Eclipse plugins which give them the cross-compilers and other program development tools (even an interface to get SQL catalog information so that INVOKE and SQLCOMP works on the PC). In such a setup, a PC-based version control system fits in very well. I don't know how easy it is to do the test part of automated bild/test/check-in from the PC, but I imagine something is available for that. I believe one could have a script running on the PC move the object files over to Guardian with ftp, use telnet to connect to Guardian, issue via the telnet connection whatever Guardian commands are needed to run the tests, and check the results of the tests via telnet.
Before the PC-based development tools were available, there were the Guardian-based version control programs already mentioned. Before those were available, most projects just were very careful to manage versions of their project in a series of subvolumes, one per version. A version control package is nice to have, but not essential. Then, we had to do without. Now, you have numerous choices to select from.
wbreidbach
>
> - Zitierten Text anzeigen -
We are using control for source control and it works fine. Even our
auditors are happy with that.
Years ago I developed my own toolbox for source control, including a
tool for writing to an archive, another tool to get the data from the
archive. The "archiv"-tool writes an edit (101)-file to the archive
with all the necessary information for recreating that version. The
"dearch"-tool get a version from the archive based ón a timestamp and
recreates the edit-file with a given name with all the original
characteristics including the modification timestamp.
Pete
The 2 options, as others have already pointed out, are CONTROL and
PrimeCode/RMS.
PrimeCode/RMS is the more sophisticated of the two and having worked a
lot with both, I recommend PrimeCode/RMS by a wide margin. The basic
difference is that PrimeCode/RMS does release management while CONTROL
only does source management.
In practical terms, it means that RMS is able to compile DDLs, Objects
and Executables *within* the product and can keep track of complex
relationships between sources dictionaries and objects. RMS
automatically knows which programs are affected by a field change in a
DDL or when an object library is changed. With CONTROL it's up to the
release manager to extract the correct versions of everything and
compilation is done "manually" outside of the product.
kr
Concluding this with a summary:
1. Tandem based -- PrimeCode/RMS -- Pros: Takes care of total life
cycle, Limitations/Cons: Price
2. PC based: Any opensource/commercial with Eclipse (supplied by HP) :
Pros: Less cost overhead/Unlimited options. Cons: May need some
customization
Just for your knoweldge base, the following tools (combined ) are very
good combination in opensource world
1. IDE -- Eclipse
2. Source Control -- CVS
3. Issue tracking/Project management/Wiki etc: www.redmine.com
4. Source Explorer: opengroak
Thanx a lot to all for sharing the knowlege.
Randall
For the ECLIPSE ecosystem, there are other options too, that integrate
($ indicates upfront pay with support, otherwise you're on your own).
1. IDE - ECLIPSE
2. Source Control -- CVS, Subversion, RMS($), Control($)
3. Issue tracking/PM/Wiki: www.redmine.com, Bugzilla, Mylyn.
Cheers,
Randall