HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: CMSReserveElement Warning
Operating System - OpenVMS
1828726
Members
2577
Online
109984
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
Go to solution
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
05-02-2007 09:02 AM
05-02-2007 09:02 AM
We are using the CMS software (CMS Version V3.9-2) and few days ago one of our staff received the folowing message;
CMSReserveElement Warning: CLEARSTONE_PKG.DQL not found
The command was;
$cmsreserve clearstone_pkg.dql
However, the module is definitely in the library. Does anyone know what might cause the above error even though the element is in the CMS library.
Thank you.
Regards,
Trace Trembath
CMSReserveElement Warning: CLEARSTONE_PKG.DQL not found
The command was;
$cmsreserve clearstone_pkg.dql
However, the module is definitely in the library. Does anyone know what might cause the above error even though the element is in the CMS library.
Thank you.
Regards,
Trace Trembath
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2007 09:08 AM
05-02-2007 09:08 AM
Re: CMSReserveElement Warning
CMS sho elem may show the element, but the file may have been deleted. The best way to determine if the file is present would be to do a directory [cms_library...]clearstone_pkg.dql and see if the file shows up.
Another possibility is that the file is on a member of the volume set that is not mounted, but that might be a different error.
Another possibility is that the file is on a member of the volume set that is not mounted, but that might be a different error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2007 09:14 AM
05-02-2007 09:14 AM
Solution
It appears you have a local wrapper around the CMS utility, with a symbol named cmsreserve that invokes it. This wrapper could be a DCL procedure, or it could be an image using the callable CMS interface.
The error message shown is most definitely not an error from CMS itself, based on the format and content.
You'll need to investigate the details of the environment, in addition to investigating the CMS library itself.
An unexpected local definition of the CMS$LIB logical name can potentially cause a procedure go go off the rails, for instance. What happened appears to depend on what this local command procedure does. There exists a limitless number of ways for a procedure or an image to go off the rails.
The first step: issue the DCL command SHOW SYMBOL CMSRESERVE to see where that symbol goes, and from there off you go on your quest.
Stephen Hoffman
HoffmanLabs LLC
The error message shown is most definitely not an error from CMS itself, based on the format and content.
You'll need to investigate the details of the environment, in addition to investigating the CMS library itself.
An unexpected local definition of the CMS$LIB logical name can potentially cause a procedure go go off the rails, for instance. What happened appears to depend on what this local command procedure does. There exists a limitless number of ways for a procedure or an image to go off the rails.
The first step: issue the DCL command SHOW SYMBOL CMSRESERVE to see where that symbol goes, and from there off you go on your quest.
Stephen Hoffman
HoffmanLabs LLC
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP