From: Mark D. Jilson [jilly@clarityconnect.com]
Sent: Wednesday, July 05, 2000 12:35 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: RMS tuning breaking programs, any ideas

You are exceeding you PIOPAGES area.  If you have access to the DSNLINK
knowledge base then searching on PIOPAGES & RMS will give you all the
information that you will need to properly configure PIOPAGES for your
desired RMS values.

David Mathog wrote:
> 
> Can anybody hazard a guess why raising BLOCK and BUFFER together would
> cause a program to fail, but raising each alone caused no problem?
> 
> $ sho rms
>           MULTI-  |                MULTIBUFFER COUNTS               | NETWORK
>           BLOCK   | Indexed  Relative            Sequential         |  BLOCK
>           COUNT   |                     Disk   Magtape  Unit Record |  COUNT
> Process   127     |    0         0        0       0         0       |    0
> System     16     |    0         0        0       0         0       |    8
> 
>           Prolog    Extend Quantity      VCC_DFW
> Process     0              0                0
> System      0              0                0
> $!
> $! the next "fetch" command works properly
> $!
> $ fetch pir1:a1hu
> $!
> $! the next "fetch" command fails
> $!
> $ set rms/buffer=255
> $ fetch pir1:a1hu
> $!
> $! the next "fetch" command works properly
> $!
> $ set rms/block=0
> $ fetch pir1:a1hu
> 
> It looks like setting block AND buffer up to their maximum is causing
> something in this program to fail, but setting either one alone that
> high has no effect.   "fetch" is part of the GCG package, and it goes
> N levels deep in libraries, and is commercial.  I've also recently
> seen this same block+buffer=BOOM effect when sending mail using EDT
> as the editor.  On trying to exit from EDT I was greeted with:
> 
> Output file could not be created
> File name:USRDISK:[USERS.MATHOG]MAIL_394E_SEND.TMP;1
> %RMS-F-DME, dynamic memory exhausted
> 
> Which made no sense to me at all, since at the time there was a lot
> of free dynamic memory in the system:
> 
> Dynamic Memory Usage (bytes):      Total        Free      In Use     Largest
>   Nonpaged Dynamic Memory        2711552      625792     2085760      257536
>   Paged Dynamic Memory           2932736     1199872     1732864     1194720
>   Lock Manager Dynamic Memory    1384448      688128      696320
> 
> The process where this all happend has:
> 
> Maxjobs:         0  Fillm:       100  Bytlm:        50000
> Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
> Maxdetach:       0  BIOlm:       100  JTquota:       2048
> Prclm:          10  DIOlm:       100  WSdef:          150
> Prio:            4  ASTlm:       102  WSquo:          256
> Queprio:         0  TQElm:        40  WSextent:      2048
> CPU:        (none)  Enqlm:      2600  Pgflquo:     100000
> 
> Thanks,
> 
> David Mathog
> mathog@seqaxp.bio.caltech.edu
> Manager, sequence analysis facility, biology division, Caltech

-- 
Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY
	- jilly@clarityconnect.com			- Brett Bodine fan
	- Mark.Jilson@Compaq.com			- since 1975 or so
	- http://www.jilly.baka.com               -