- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- CMS Invalid history record.
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
тАО04-16-2007 01:16 AM
тАО04-16-2007 01:16 AM
CMS Invalid history record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2007 07:04 AM
тАО04-16-2007 07:04 AM
Re: CMS Invalid history record.
Or you can patch the data that CMS doesn't like. That involves finding the record and sorting out what CMS doesn't like. If it's a binary date, patch it. If it's a text date, you can still patch it.
Or you can blow away all of the history.
CMS is traditionally sensitive to more than a 30 second skew from the current time.
Both CMS V3.6-10 and OpenVMS (VAX and Alpha) V6.1 are over a decade old, and long since unsupported. You might upgrade and see if newer CMS deals with it more to your satisfaction. A bunch of corruptions got fixed in newer releases. (But since you're here, I'm guessing that upgrade is not an option.)
If you can't upgrade, try patch; directly "bomb" library. Or blow away the history and/or start over with a new library. (Do make a copy of the library, and practice on that.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2007 11:38 PM
тАО04-16-2007 11:38 PM
Re: CMS Invalid history record.
I'm not familiar with patching. What is the method? Is there a recommended tool?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2007 04:00 AM
тАО04-17-2007 04:00 AM
Re: CMS Invalid history record.
Patching a CMS library component file is an advanced-level repair technique -- you're literally bombing data bytes within the history file with new values, directly writing to the CMS file and repairing whatever it is that CMS doesn't like about these records. (Or attempting same.)
I've found various corruptions that used to crop up occasionally with V3.5, V3.6 and V3.7 have largely disappeared with more recent releases. There's no chance you can try a CMS upgrade and see if a newer VERIFY/REPAIR will address this case?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2007 02:36 AM
тАО04-23-2007 02:36 AM