- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- CMS Invalid history record.
-
-
Categories
- Topics
- Hybrid IT with Cloud
- Mobile & IoT
- IT for Data & Analytics
- Transformation
- Strategy and Technology
- Products
- Cloud
- Integrated Systems
- Networking
- Servers and Operating Systems
- Services
- Storage
- Company
- Events
- Partner Solutions and Certifications
- Welcome
- Welcome
- Announcements
- Tips and Tricks
- Feedback
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- Converged Data Center Infrastructure
- Digital Transformation
- Grounded in the Cloud
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- Networking
- OEM Solutions
- Servers: The Right Compute
- Telecom IQ
- Transforming IT
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Categories
-
Forums
-
Blogs
-
InformationEnglish
CMS Invalid history record.
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-16-2007 01:16 AM
04-16-2007 01:16 AM
CMS Invalid history record.
CMS Invalid history record.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-16-2007 07:04 AM
04-16-2007 07:04 AM
Re: CMS Invalid history record.
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-16-2007 11:38 PM
04-16-2007 11:38 PM
Re: CMS Invalid history record.
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-17-2007 04:00 AM
04-17-2007 04:00 AM
Re: CMS Invalid history record.
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-23-2007 02:36 AM
04-23-2007 02:36 AM
Re: CMS Invalid history record.
Re: CMS Invalid history record.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2018 Hewlett Packard Enterprise Development LP