- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Problem with transferring CMS library from Alpha t...
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
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
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
08-09-2013 12:34 PM - edited 08-09-2013 01:29 PM
08-09-2013 12:34 PM - edited 08-09-2013 01:29 PM
Problem with transferring CMS library from Alpha to Integrity
We are moving a CMS library between a Alpha and Integrity server. Both servers are running OpenVMS 8.4 and CMS version 4.5. Prior to the transfer "CMS Verify" was run to check the status of the library. The library then transferred using backup, and restore on the Integrity server We again run "CMS Verify" run the Integrity server to check the status. As a final check we did a simple "cms show history" then we noticed the history was not same. We have run difference between the "*.HIS" files between both servers and no difference were found. The number and files size were check and no issues were found. Finally ran "CMS SHOW library/FULL" on both servers and again no difference were found.
Update...
More detail checks we have found that after the transfer CMS is not displying "Create", "Fetch", or "Verify" history records on the elements in the library.
Any ideas as to why we are see a difference in the history.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2013 05:14 PM
08-11-2013 05:14 PM
Re: Problem with transferring CMS library from Alpha to Integrity
Are the records displayed if you explicitly specify that you want to see them, i.e. if you use /TRANSACTION=(CREATE,FETCH,VERIFY) ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2013 09:06 AM
08-12-2013 09:06 AM
Re: Problem with transferring CMS library from Alpha to Integrity
If I use "/trans=create" I get the "create" records plus all other history records. On the Alpha box that command gives me just the "create" records only".
The command "/trans=all" does not show all the transactions either.
If I use "/trans=create" it looks like the tranfser between the servers is correct, it just that CMS on the Integrity server has issue with displaying the records correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2013 01:59 AM
08-13-2013 01:59 AM
Re: Problem with transferring CMS library from Alpha to Integrity
Looks like a bug in CMS for I64. There are more commands which aren't listed with SHOW HISTORY, for example INSERT. The bug also shows in CMS libraries created on I64. This affects my tool which uses the history output to create a git repository (on a non-VMS system) from a CMS library.
There seems to be a workaround: SHOW HISTORY /NOTRANSACTIONS.
Did you report this to HP and did you get any feedback?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2013 05:30 AM
08-13-2013 05:30 AM
Re: Problem with transferring CMS library from Alpha to Integrity
No, I have not as of yet reported this to HP. I will be as soon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2013 12:56 PM
08-13-2013 12:56 PM
Re: Problem with transferring CMS library from Alpha to Integrity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2013 03:37 PM
08-14-2013 03:37 PM
Re: Problem with transferring CMS library from Alpha to Integrity
This says a lot about HP's testing.
Wouldn't you think that the correct functioning of CMS History would be rather important to users?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2013 01:13 PM
08-20-2013 01:13 PM
Re: Problem with transferring CMS library from Alpha to Integrity
I'll guess (but I don't know) that a CMS test system involves creating a new library, doing all sorts of commands, and checking the history. Testing the ability to "import" a history file from another system is less common and perhaps not tested as well. I'm surprised that the format is different. I wonder if it works correctly in a mixed-architecture cluster with shared storage?