[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

223.0. "PQL_M > PQL_D ?" by PTOSS1::MINSHALLJ () Wed Feb 19 1997 16:11

    At my customer site many of the PQL_Mxxx values are higher than the
    corresponding PQL_Dxxx value.  I would have expected the minimum
    values to always be lower than the default values.   This occurs
    on both a VAX and an Alpha running VMS 6.2-1h3.  It affects such 
    things as ASTLM, DIOLM, BYTLM, but doesn't affect the working set
    parameters.
    
    Does it cause any problems with VMS if the min is higher than the
    default?  
    
    Are there any cases where it makes sense to have a min > default?
    
    Thanks,
    
    Jerry
T.RTitleUserPersonal
Name
DateLines
223.1Benign CruftXDELTA::HOFFMANSteve, OpenVMS EngineeringWed Feb 19 1997 16:179
   The PQL_M* minimum value will override the PQL_M* default value, if
   the default value is set below the minimum value.  This rather perverse
   parameter configuration should not adversely affect OpenVMS operation.
   (I'd assume AUTOGEN is grumbling about these settings in its report.)

   I'd clean out MODPARAMS and re-AUTOGEN, as there's probably a large
   amount of other cruft present in this MODPARAMS file, too...

223.2AUSS::GARSONDECcharity Program OfficeWed Feb 19 1997 17:4620
re .0                             
    
>    Does it cause any problems with VMS if the min is higher than the
>    default?  
    
    Nope. It's perfectly valid. The default is applied first to supply
    every quota that is not specified to SYS$CREPRC and then the minimum is
    applied to all quotas regardless of whether they were explicitly
    specified or defaulted.
    
    Note that the defaults are not relevant to processes that run LOGINOUT
    and specify /AUTHORIZE (or the programming equivalent) since then
    LOGINOUT will replace every quota set by SYS$CREPRC using the above logic
    with the value from SYSUAF but will then reapply the appropriate minimum.
    
>    Are there any cases where it makes sense to have a min > default?
    
    Not much except that the minimum can be raised or lowered independently
    of the default and so the logic that VMS applies and having a
    reasonable default make sense.