- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: WSEXTENT >= WSDEFAULT & WSQUOTA always?
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
тАО09-10-2008 09:33 AM
тАО09-10-2008 09:33 AM
PQL_MWSDEFAULT 207864
PQL_MWSQUOTA 417728
PQL_MWSEXTENT 32768
thanks
Clark
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 10:23 AM
тАО09-10-2008 10:23 AM
Re: WSEXTENT >= WSDEFAULT & WSQUOTA always?
I thaught wsextent was the amount with which it increments your usage when you need to add more.
So it allocates wsdefault when you start, then increments as needed by wsextent at a time to a maximum of wsquota.
Or am I remmebering wrong?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 10:33 AM
тАО09-10-2008 10:33 AM
Re: WSEXTENT >= WSDEFAULT & WSQUOTA always?
>>>
I thaught wsextent was the amount with which it increments your usage when you need to add more.
So it allocates wsdefault when you start, then increments as needed by wsextent at a time to a maximum of wsquota.
Or am I remmebering wrong?
<<<
You start at wsdefault, growing up to wsquota. Then, if you need more AND VMS has enough memory, you can grow further up to wsextent.
The increment you're remembering is probably WSINC.
cu,
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 11:44 AM
тАО09-10-2008 11:44 AM
Re: WSEXTENT >= WSDEFAULT & WSQUOTA always?
Be careful not to have Wsquota > pgflquota, which can lead to strange errors, and is a bad idea.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 12:12 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 12:48 PM
тАО09-10-2008 12:48 PM
Re: WSEXTENT >= WSDEFAULT & WSQUOTA always?
As with all these limits...it's a limit. If your WSDEAULT is let's 2000 that doesn't mean your working set starts with 2000. It starts with far less for example when you switch from DCL code to running your user image. Depending on the programs page fault dynamics it may eventually grow the working set to WSQUOTA...only if it generates high pagefault rates per second. If certain conditions are met and still paging it may grow the working set to WSEXTENT.
If you think you have enough physical memory and an application account needs it set its WSDEFAULT/WSQUOTA/WSEXTENT to WSMAX.
/Guenther