- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Problems with the MOUNT system service
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
тАО07-27-2006 11:10 PM
тАО07-27-2006 11:10 PM
Anyone any ideas ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2006 11:26 PM
тАО07-27-2006 11:26 PM
Re: Problems with the MOUNT system service
$ help /message LKWSETFUL
gives the following information
LKWSETFUL, locked portion of working set is full
Facility: SYSTEM, System Services
Explanation: No more pages can be locked in the working set because there
would not be enough remaining pages available dynamically for
the image to continue execution.
User Action: Use the DCL command SET WORKING_SET to increase the working
set limit, if the limit is not already set at the maximum
allowed. If the working set limit is already at the maximum
allowed, correct the program that attempted to lock too many
pages in the working set.
Hope that helps
regards
Heinz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2006 01:24 AM
тАО07-28-2006 01:24 AM
Re: Problems with the MOUNT system service
You should review the quotas of all usernames. There is some dcl to help with this at
http://dcl.openvms.org/stories.php?story=05/07/28/2894075
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2006 05:26 AM
тАО07-28-2006 05:26 AM
Re: Problems with the MOUNT system service
This has caused some problems (especially with BEA MessageQ), so we're going to restore the old behaviour on Alpha for users of the $LCKWSET system service.
-- Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2006 07:50 PM
тАО07-30-2006 07:50 PM
Re: Problems with the MOUNT system service
In answer to some of the questions, the source code was written and is owned by ourselves. I don't believe any pages are explicitly locked into memory but I will check. The process quotas have not changed from VMS 7.3 to 8.2 but again I will check the user/process quotas for the working set and adjust.
During my initial investgations I did try to increase the working set QUOTA but it did not appear to make any difference, as soon as the SYS$MOUNT service is called the LKWSETFUL error is returned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2006 08:12 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2006 09:10 PM
тАО07-30-2006 09:10 PM
Re: Problems with the MOUNT system service
I've just found by updating the WSQUOTA from 8192 to 65535 the MOUNT system service completes without error. I have adjusted the user account entry for the user that runs the process. I have checked the actual quota assigned to the process by using the GETJPI lexical function and it is now correctly set to 65535.
When I look at the process using SHOW PROC/CONT the working set is shown as 3728.
This seems to have sorted the problem out - Many thanks to all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2006 09:52 PM
тАО07-30-2006 09:52 PM
Re: Problems with the MOUNT system service
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2006 11:20 PM
тАО07-30-2006 11:20 PM
Re: Problems with the MOUNT system service
process parameter but not having sufficient quota for the user account from which the process is started.
All seems OK now, but all processes started from the modified user account will get the newly increased working set quota ! I'm not sure what the effect of this will be on the overall system page usage.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2006 11:31 PM
тАО07-30-2006 11:31 PM
Re: Problems with the MOUNT system service
as a workaround, you could add a SET WORKING_SET/QUOTA=8192 command into that user's LOGIN.COM to limit the working set quota for that user's account.
Just before starting the image, that uses the $MOUNT system service, increase the process WSQUOTA up to authorized limit with $ SET WORKING_SET/QUOTA=65535 and reset it back to 8192 after the image has finished.
Volker.