Hi all,

we are facing memory problems in our uniface application running on
VMS.
Can you pls tell me what can be possible reasons?

What are the commands and tools to monitor memory usage on VMS?

To add some more details about the problem -

we are using Uniface 7206 with service pack 601 or 604 on VMS 7.3-2.
Once the application starts running, the user is thrown out (comes out)

of it in 1 or 2 hours due to 'out of memory' or 'process quota
exceeded' ... 

Thanks for quick reponse. 

Regards, 
tm

In article <1132143104.113248.68440@g44g2000cwa.googlegroups.com>, tuza_mitra@yahoo.com writes:
>we are facing memory problems in our uniface application running on VMS.
>Can you pls tell me what can be possible reasons?

SYSGEN or UAF quota parameters most likely.

>What are the commands and tools to monitor memory usage on VMS?

Besides the usual recommendations (SHOW MEMORY, SHOW PROCESS/ALL/IDENT=...
and ACCOUNTING/FULL/SINCE/IDENT=...) I would recommend AVAILMAN (or AMDS).
You can download it (after a survey) from here (license is included in VMS)

	http://www.openvms.digital.com/openvms/products/availman/

>To add some more details about the problem -
>
>we are using Uniface 7206 with service pack 601 or 604 on VMS 7.3-2.
>Once the application starts running, the user is thrown out (comes out)
>
>of it in 1 or 2 hours due to 'out of memory' or 'process quota exceeded' ... 

Sounds like a memory leak.
Better contact the ISV to check for a patch to Uniface in addition.

-- 
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail  peter@langstoeger.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist

I'd guess at PGFLQUOTA for the user


"Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message 
news:437b4f90$1@news.langstoeger.at...
> In article <1132143104.113248.68440@g44g2000cwa.googlegroups.com>, 
> tuza_mitra@yahoo.com writes:
>>we are facing memory problems in our uniface application running on VMS.
>>Can you pls tell me what can be possible reasons?
>
> SYSGEN or UAF quota parameters most likely.
>
>>What are the commands and tools to monitor memory usage on VMS?
>
> Besides the usual recommendations (SHOW MEMORY, SHOW PROCESS/ALL/IDENT=...
> and ACCOUNTING/FULL/SINCE/IDENT=...) I would recommend AVAILMAN (or AMDS).
> You can download it (after a survey) from here (license is included in 
> VMS)
>
> http://www.openvms.digital.com/openvms/products/availman/
>
>>To add some more details about the problem -
>>
>>we are using Uniface 7206 with service pack 601 or 604 on VMS 7.3-2.
>>Once the application starts running, the user is thrown out (comes out)
>>
>>of it in 1 or 2 hours due to 'out of memory' or 'process quota exceeded' 
>>...
>
> Sounds like a memory leak.
> Better contact the ISV to check for a patch to Uniface in addition.
>
> -- 
> Peter "EPLAN" LANGSTOEGER
> Network and OpenVMS system specialist
> E-mail  peter@langstoeger.at
> A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist 

"Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message 
news:437b4f90$1@news.langstoeger.at...
> In article <1132143104.113248.68440@g44g2000cwa.googlegroups.com>, 
> tuza_mitra@yahoo.com writes:
>>we are facing memory problems in our uniface application running on VMS.
>>Can you pls tell me what can be possible reasons?
>
> SYSGEN or UAF quota parameters most likely.
>
>>What are the commands and tools to monitor memory usage on VMS?
>
> Besides the usual recommendations (SHOW MEMORY, SHOW PROCESS/ALL/IDENT=...
> and ACCOUNTING/FULL/SINCE/IDENT=...) I would recommend AVAILMAN (or AMDS).
> You can download it (after a survey) from here (license is included in 
> VMS)
>
> http://www.openvms.digital.com/openvms/products/availman/
>
>>To add some more details about the problem -
>>
>>we are using Uniface 7206 with service pack 601 or 604 on VMS 7.3-2.
>>Once the application starts running, the user is thrown out (comes out)
>>
>>of it in 1 or 2 hours due to 'out of memory' or 'process quota exceeded' 
>>...
>
> Sounds like a memory leak.
> Better contact the ISV to check for a patch to Uniface in addition.
>

I second that

You can check the accounting file (account/full/id=) for your process and 
determine how much memory it was using, that could help.
--> look at Peak working set and Peak page file

Also check the process as it is running with show proc/accounting/id=
--> Look for Peak working set size
If it's growing steadily, memory leak problem (keeps on requesting some more 
and never releases it)

Syltrem

> -- 
> Peter "EPLAN" LANGSTOEGER
> Network and OpenVMS system specialist
> E-mail  peter@langstoeger.at
> A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist 

In article <437b4f90$1@news.langstoeger.at>, 
peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:
...
>Better contact the ISV ...
...

This is an excellent suggestion.
It is very likely they know more about the application and its
memory needs/problems than general OpenVMS people.

-- 
      Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USA
          (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)
      All opinions expressed are my own and not necessarily my employer's.

I had an application that did pretty much the same thing. turned out to
be a routine that was using dynamic memory to work a stack, and was not
'putting it back' properly.  After a couple of days, it would be so
hacked up that the program just sat there thrashing while it tried to
manipulate the stack.  Once the fix was made to properly return popped
stack entries, all was well again.

steve