Problem with transferring CMS library from Alpha to Integrity (330 Views)
Reply
Occasional Contributor
Mark miller_14
Posts: 4
Registered: ‎09-22-2004
Message 1 of 8 (330 Views)

Problem with transferring CMS library from Alpha to Integrity

[ Edited ]

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.  

 

Please use plain text.
Trusted Contributor
John McL
Posts: 280
Registered: ‎02-24-2008
Message 2 of 8 (296 Views)

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) ?

Please use plain text.
Occasional Contributor
Mark miller_14
Posts: 4
Registered: ‎09-22-2004
Message 3 of 8 (270 Views)

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.

 

 

Please use plain text.
Esteemed Contributor
H.Becker
Posts: 354
Registered: ‎04-09-2009
Message 4 of 8 (243 Views)

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?

Please use plain text.
Occasional Contributor
Mark miller_14
Posts: 4
Registered: ‎09-22-2004
Message 5 of 8 (235 Views)

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

Please use plain text.
Honored Contributor
Steven Schweda
Posts: 9,055
Registered: ‎02-23-2005
Message 6 of 8 (220 Views)

Re: Problem with transferring CMS library from Alpha to Integrity

Please use plain text.
Trusted Contributor
John McL
Posts: 280
Registered: ‎02-24-2008
Message 7 of 8 (188 Views)

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?

Please use plain text.
Respected Contributor
John Reagan
Posts: 131
Registered: ‎05-30-2004
Message 8 of 8 (149 Views)

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?

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation