Good Morning Bill,
You did not specifically state whether you wanted to increase a user-account, or if wished to limit a specific user. The basic command(s) that you would invoke while in sysuaf-- "UAF> MODIFY SMITH/FILLM=64" (no quotes,)would be the same, but the action may not take the desired effect.
In the previous example of the fillm (open file limit) quota, the value of 64 may be over-ridden by one of the Sysgen-Parameters PQL_MFILLM. Basically, any of the user-acct quotas in sysuaf.dat are checked against the PQL_Mxxxxxx values in Sysgen. The "M" after the "underscore" (PQL_) specifies Minimum. If the minimum value specified in Sysgen is greater than the entry in SYSUAF, then the user-job will receive the SYSGEN value, instead of the SYSUAF entry.
Basically, if you wanted to limit the user SMITH to a FILLM value of 64, the preceding command (UAF> MODIFY SMITH/FILLM=64) will do trick; as long as the Sysgen-Parameter PQL_MFILLM is less than 64. If however, the Sysgen-Parameter PQL_MFILLM = 100, then all user-accounts on the system will have a minimum value of 100.
OVMS initially utilizes the PQL_Mxxxxx and the PQL_Dxxxxx parameters during user-process creation in a temporary data-structure known as the PQB. These entries in the Process-Quota-Block are then compared to the Sysuaf-Entries for the user-account. If there is no corresponding User-Account/UIC for the newly created process (CREPRC) then the PQL values will be tranferred to the JIB, PCB, and PHD data-structrures.
If there is a corresponding Sysuaf-Entry, then the OS will compare the PQL_Mxxxxx values in the PQB to the entries in Sysuaf, and insert the higher/greater value of either the PQL_Mxxxxx or Sysuaf. Basically the OS wants to make sure that if the System Manager had specified at a system-wide level via SYSGEN, a minimum value for "all" user-accounts, (via PQL_Mxxxxx)then it will not use a lower setting in SYSUAF.
If however, you wish to increase a specific user-account's value such as the number of Direct-I/O's; eg. UAF> MODIFY SMITH/DIOLM=80 would increase the setting to 80, given the default value of only 32 for PQL_MDIOLM in Sysgen.
Also, one must take into consideration that many quotas are shared/pooled system-wide between a process and all of its sub-processes. "Typically" if the quota is indeed shared, the values are stored in the JIB data-structure. And, if the specific quota is not shared, these quotas are stored in the PCB and PHD data-structures.
If you discover that you have a user-process going in "RWJIB," then it is stalled in a Resource-Wait-State, due to insufficient SYSUAF-Quotas that are shared/pooled. But if the User-Process is in "RWAST", it is typically waiting for a Non-Pooled Quota.
By invoking the DCL-Command --
$show process/quota/id=aabbccdd you will see the remaining/available quotas for a given process.
Hope this helps, and that it wasn't too long or confusing...
Thanx,
whynot3k
