1829716 Members
2683 Online
109992 Solutions
New Discussion

WSQUOTA exceeds 65536

 
SOLVED
Go to solution
Ronny_7
Regular Advisor

WSQUOTA exceeds 65536

Hi,

Is there any article on WSQUOTA cannot exceeds 65536 on OpenVMS V6.2-1H3 running Alpha systems and what is the impact if set above 65536?

Regards,
Ronny
10 REPLIES 10
Mac Lilley
Frequent Advisor

Re: WSQUOTA exceeds 65536

Hello Ronny

Maximum value for WSQUOTA is 65536. This is documented in the System Management manual (I only have VMS v7 documentation available but I expect that this value hasn't changed for v7)

ML
Martin P.J. Zinser
Honored Contributor

Re: WSQUOTA exceeds 65536

From the help in Authorize (VMS 7.3):

MODIFY

/WSQUOTA

/WSQUOTA=value

...

The value cannot be greater than the value of WSMAX and cannot
exceed 64K pages. This quota value replaces smaller values of
PQL_MWSQUOTA.
Antoniov.
Honored Contributor

Re: WSQUOTA exceeds 65536

WSQUOTA is the max amount of physical memory a user process can lock. With 65536 you can lock 33Mb for every process with actual page size.
Antonio Maria Vigliotti
Martin P.J. Zinser
Honored Contributor

Re: WSQUOTA exceeds 65536

The 33 MB are the value for the VAX (512 byte Pages) on Alpha this should be 512 MB (8k Pages)
Antoniov.
Honored Contributor

Re: WSQUOTA exceeds 65536

Dear Martin,
I believe page size is 512 byte.
Reading SYSMAN value on AXP, system say pagelets for param WSMAX but AUTHORIZE say pages for WSQUOTE.
How much is page size on AXP?
Antonio Maria Vigliotti
Burkart Beat
Frequent Advisor

Re: WSQUOTA exceeds 65536

Hi
There is a SYSGEN Parameter WSMAX who limits this WSQUOTA. Try changing this SYSGEN Parameter ...
Best regards
Beat
Antoniov.
Honored Contributor

Re: WSQUOTA exceeds 65536

Hello,
Page size is 512 byte always.
Look for VMS operating system documentation;
- OpenVMS System Manager User Manual;
- Chap. 7: management user account
- System resource
- Understanding Pages and Pagelets.

To change WSMAX
>MC SYSMAN PARAM SET WSMAX 65536

Then you can change user WSQUOTA

Exceed WSQUOTA could not be a good idea. I prefer assign more virtual memory to user modifying PGFLQUOTA; naturally your system have sufficient virtual memory. See documentation about NPAGEDYN, NPAGEVIR, PAGEDYN, VIRTUALPAGECNT params.
Warning: theese params are very dangerous.

By
Antonio Maria Vigliotti
Ronny_7
Regular Advisor

Re: WSQUOTA exceeds 65536

Hi Everyone,

Thank you all who have responded to this query.

I need more informations on what could be the impact if the WSQUOTA is set above 65536?

Also is this 65536 in pages or pagelets?

Regards,
Ronny
Antoniov.
Honored Contributor
Solution

Re: WSQUOTA exceeds 65536

Hi Ronny,
I checked 4 U changind WSQUOTA on a old AXP 400.

First, I modified SYSGEN param WSMAX. System accept value greater then 65536 because on AXP you can assign 65536 pages; value is written in pagelets that are 4, 8, 16 or 32 times page. On my system, 1 page = 16 pagelets. If I'll write 1048576 system accept; no greater value is accepted.
Note the modify in SYSGEN o SYSMAN is not correct procedure to modify a system parameter, but I will a direct response from system.
Now I wrote 1048576 and I've rebooted the system: the value is above the physical memory and on bootstrap system correct my value leaving a value greater then 65536.
I don't changed a value with AUTHORIZE and I think system accept any value less then WSMAX.
Now I restored original value of WSMAX.

Bye
Antonio Maria Vigliotti
Ronny_7
Regular Advisor

Re: WSQUOTA exceeds 65536

As per above replies.