[Info-vax] Process memory settings

[Syltrem]

"H Vlems" <hvlems at freenet.de> wrote in message 
news:5c0a0f63-8ddd-4eb3-a428-9c01482bb75c at c2g2000yqi.googlegroups.com...
On Aug 12, 11:14 pm, "Syltrem" <syltremz... at videotron.ca> wrote:
> "sapienzaf" <sapie... at noesys.com> wrote in message
>
> news:310855e6-266d-4c11-a076-01663c547896 at b14g2000yqd.googlegroups.com...
> On Aug 12, 4:47 pm, "Syltrem" <syltremz... at videotron.ca> wrote:
>
>
>
>
>
> > I have a process running some program and while it does so,
> > $ write sys$output F$GETJPI("","WSSIZE")
> > grows until it reaches
> > $ write sys$output F$GETJPI("","WSAUTHEXT")
>
> > Then I get
> > %LIB-F-INSVIRMEM, insufficient virtual memory
>
> > How do I raise the Authorized Working Set Extent ?
> > I tried WSEXT in Authorize with no luck, also Sysgen's PQL_MWSEXT
>
> > This is efinitely not something I play with very often, and I can't seem
> > to
> > find anything with Google...
>
> > Pls help !
> > Thanks
> > Syltrem
> >I agree with Richard, that you should find out why the program is
> >consuming so much memory (unless that's your expectation).
> >Otherwise, increase PGFLQUOTA in Authorize.
>
> Oh! I tried to increase PGFLQUOTA too...
> Same problem.
>
> And the program... well I didn't want to get into that and reveal it... 
> It's
> the Cobol compiler.
> Syltrem- Hide quoted text -
>
> - Show quoted text -

> Well, mentioning the Cobol compiler really stopped the conversation...
> Could there be a problem in the Cobol source file you're compiling? A
> syntax error that makes the compiler do strange things?
> Hans

> (is this VAX-Cobol?)


The program compiles on an old VAX-4100...
Now I'm trying to compile it on a not-as-old Alpha-4100 as I<d like to get 
rid of the VAX

Syltrem