- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- CVS Version Control on OpenVMS 8.3 Alpha
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2010 08:47 AM
тАО01-19-2010 08:47 AM
CVS Version Control on OpenVMS 8.3 Alpha
I am trying to implement CVS on OpenVMS 8.3, Alpha. Corporate supports the CVS repository server on a Linux/Unix box. I intend to version Source, Object and Executable (keep the matching set).
I have successfully Added, Checked-out, Checked-in (Committed) COBOL source and COBOL EXE files. Upon checkout, the EXE runs find.
However, the intermediate object (.OBJ) files when checked out, give a link error (see attachement).
Wondering if there are CVS client options I need to use, etc. The only CVS client I could find was from a download I did in 2006 for version 1.9.27.
Any thoughts on this subject?
Thanks,
John Farmer
john dot farmer at genworth dot com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2010 09:05 AM
тАО01-19-2010 09:05 AM
Re: CVS Version Control on OpenVMS 8.3 Alpha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2010 02:25 PM
тАО01-19-2010 02:25 PM
Re: CVS Version Control on OpenVMS 8.3 Alpha
I'm assuming checkin/out uses FTP or similar to move the file between systems?
This might "just work" on Itanium, as OBJ modules are:
Record format: Undefined, maximum 512 bytes, longest 0 bytes
which will possibly survive ftp enough to be recognised.
EXE files are FIX 512, so FTP won't break them as long as they're copied as BINARY.
On Alpha, OBJ modules are as Helmut said:
Record format: Variable length, maximum 0 bytes, longest
Can you pre process the file being checked in and post process the file being checked out?
You may be able to get away with changing the record format. Change it to FIXED 512 before checking in, then back to VAR after checking out. Make sure it uses BINARY FTP for copying.
$ SET FILE/ATTR=(RFM:FIX,MRS:512) CHECKIN.OBJ
now checkin CHECKIN.OBJ
checkout CHECKOUT.OBJ
$ SET FILE/ATTR=(RFM:VAR,MRS:0) CHECKOUT.OBJ
Use ANALYZE/OBJECT to validate. I was able to FTP the FIX512 file, off VMS, then back, change back to VAR and successfully ANALYZE/OBJ.
Note that you'll lose the true LRL, but that probably won't matter. If you find it does, there are a few options:
1) "remember" the real LRL for each file "somewhere" and restore it with the RFM and MRS (yuk!)
2) Find a reasonable maximum and set them all to the same (kludge)
3) After fixing RFM and MRS:
$ CONVERT CHECKOUT.OBJ CHECKOUTFIX.OBJ
(this will recalculate the correct LRL, at the expense of reading through and copying the whole file)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2010 06:20 PM
тАО01-19-2010 06:20 PM
Re: CVS Version Control on OpenVMS 8.3 Alpha
CCSS - Computer Consulting System Services, LLC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2010 02:00 AM
тАО01-20-2010 02:00 AM
Re: CVS Version Control on OpenVMS 8.3 Alpha
This might "just work" on Itanium, as OBJ modules are:
Record format: Undefined, maximum 512 bytes, longest 0 bytes
<<<
Additionally, EOF must be preserved.
>>>
Use ANALYZE/OBJECT to validate. I was able to FTP the FIX512 file, off VMS, then back, change back to VAR and successfully ANALYZE/OBJ.
<<<
Side note, analyze will not work, if there are major problems in the structure so these problems show, but in general, ANALYZE/OBJECT (and /IMAGE) is not a verification tool, it is a formatting tool.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2010 07:22 AM
тАО01-20-2010 07:22 AM
Re: CVS Version Control on OpenVMS 8.3 Alpha
$ cvs -d
":pserver:myusername@myserver.mycompany.com:/CVS/TestRepos" add "MYPROG.OBJ"
I hoped someone was using CVS from the VMS client that could give some pointers. I plan to version source (cob source, copybooks, etc.), object and executable, so I had all the "Parts" in play at a particular point in time.
Two other VC products are supported in the company, PVCS and small pockets of SubVersion. Are their clients available for VMS for either of those, and if so, do they interact with VMS any better than CVS?
For the moment, the Object file issue is the only negative I've found. Although CVS does seem to constrain a bit requiring checkout/in in the module subdirectory only. That will take some scripting to get it to fit into our dev/model/prod flow.
Thanks,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2010 08:23 AM
тАО01-20-2010 08:23 AM
Re: CVS Version Control on OpenVMS 8.3 Alpha
Are you setting binary mode for the objects/executables you are storing in CVS? You should probably set your CVSROOT/cvswrappers file to include the lines:
*.exe -k 'b'
*.obj -k 'b'
*.olb -k 'b'
*.bck -k 'b'
so CVS will treat these file types as binary.
This won't fix the record attributes issue noted above (you'll probably have to write a command procedure around the checkout/export to set the attributes correctly), but it will keep CVS from doing keyword substitution in your binary files.
Hope this helps a little!
Glenn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2010 05:56 PM
тАО01-20-2010 05:56 PM
Re: CVS Version Control on OpenVMS 8.3 Alpha
http://nchrem.tnw.tudelft.nl/openvms/software2.html#cvs
Tim.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2010 06:55 AM
тАО01-21-2010 06:55 AM
Re: CVS Version Control on OpenVMS 8.3 Alpha
I am unable to build my one EXE from source as I don't have a C compiler, only COBOL.
Thanks,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2010 08:08 AM
тАО01-21-2010 08:08 AM
Re: CVS Version Control on OpenVMS 8.3 Alpha
http://www.kednos.com/cvs/cvs.exe
This is version 1.12.9 for OpenVMS Alpha.
Tim.