HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Archival of CMS historical data when moving to a L...
Operating System - OpenVMS
1828377
Members
3457
Online
109976
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
08-21-2007 05:20 AM
08-21-2007 05:20 AM
Archival of CMS historical data when moving to a LINUX platform
Is there any product/facility available to allow the extraction of all CMS historical data (versions, history, classes, etc) and allow importing of this data to a LINUX based Code Management System - RCS or ClearCase(preferably)?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2007 07:16 AM
08-21-2007 07:16 AM
Re: Archival of CMS historical data when moving to a LINUX platform
It would probably be best to ask this question of whomever is dealing with RCS or ClearCase -- asking for help from the folks on the platform you're departing from is, well, not likely to attract much attention. Simply put, the folks you're moving to have more of an investment here, and a better idea of the capabilities of the tools.
That written, I'd be mildly surprised if this CMS import tool existed. Source code migrations are pretty isolated affairs. (You might find a two-step sequence around; convert from CMS to "something else", and from there into the target environment.)
Extract it into text and process it into what might be expected by ClearCase, Git, SVN or such.
Consider packaging all of the CMS library up into a big zip (with the "right" version of CMS, MMS, etc, installation kits included), though it would likely also be useful to specifically extract the CMS history into a separate text file and check it into the source code control environment.
Also consider creating and packaging up the CMS release ("reference") directories, too, so you have a way to see back into the source pool at "major" points in your development process.
You could certainly use the callable CMS API to write up a tool to feed in the data required in the target environment. I've been dealing with the CMS API for eons; it's certainly capable of managing an export tool. Albeit a tool that you or somebody you designate gets to write.
That written, I'd be mildly surprised if this CMS import tool existed. Source code migrations are pretty isolated affairs. (You might find a two-step sequence around; convert from CMS to "something else", and from there into the target environment.)
Extract it into text and process it into what might be expected by ClearCase, Git, SVN or such.
Consider packaging all of the CMS library up into a big zip (with the "right" version of CMS, MMS, etc, installation kits included), though it would likely also be useful to specifically extract the CMS history into a separate text file and check it into the source code control environment.
Also consider creating and packaging up the CMS release ("reference") directories, too, so you have a way to see back into the source pool at "major" points in your development process.
You could certainly use the callable CMS API to write up a tool to feed in the data required in the target environment. I've been dealing with the CMS API for eons; it's certainly capable of managing an export tool. Albeit a tool that you or somebody you designate gets to write.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP