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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1877.0. "LIB$GET_VM failure on some EM functions" by GIDDAY::BURT (Chele Burt - CSC Sydney, DTN 7355693) Tue Dec 01 1992 01:43

Hello and Greetings once more!

Customer has reported an occasional unpleasantness.
Customer is running ALL-IN-1 V3.0 (ex-beta site), under VMS v5.5-1, and with
         ****   the WordPerfect V5.1 integration (ex-beta)      ***

SOME users are OCCASIONALLY getting VMGETFATAL LIB$GET_VM errors, then being
thrown out of ALL-IN-1. They are logged out, and there is no opportunity
to do a GOLD W to expand the error message. The users then log back in again, 
perform whatever function it was they were doing previously, and everything 
is fine.

Problem has been reported to the customer about 6 times - no real pattern as
yet, other than it seems to occur on EM functions - eg RN, SMD & one of their
own, customised mail applications.

Error Message received prior to dumpout is:

%OA-F-VMGETFATAL, LIB$GET_VM failure, 280 bytes at 00000000 - IN OADSA IN ROUTIE


The only reference I've seen for this is when partition seeding fails with 
the same error message. (STARS article)

Virtualpagecnt  270144

Maxjobs:         0  Fillm:       100  Bytlm:        36000
Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
Maxdetach:       0  BIOlm:        50  JTquota:      15000
Prclm:          10  DIOlm:        50  WSdef:         1024
Prio:            4  ASTlm:       100  WSquo:         2048
Queprio:         0  TQElm:        50  WSextent:      4096
CPU:        (none)  Enqlm:       300  Pgflquo:      20000


Any thoughts on what the problem is and why it is happening?

Regards,
Chele B
T.RTitleUserPersonal
Name
DateLines
1877.1OA$MSG_TRAPIOSG::SCMCM+ Development Team from TorinoTue Dec 01 1992 07:4212
Hi Chele,

To get more info, one of the users could run the ALL-IN-1 
session with OA$MSG_TRAP enabled. ALL-IN-1 will ACCVIO,
but you're still in the ALL-IN-1 session.

Not much of help to the problem although, I'm afraid.

Ciao,

	Simon
1877.2PGFLQUO vs Peak Virtual Size ??AIMTEC::VOLLER_IGordon (T) Gopher for PresidentTue Dec 01 1992 19:0615
    Chele,
    
    After the process has ACCVIOed do a $SHOW PROCESS/ACC (or get the
    information from the ACCOUNTNG file).
    
    Note particularly the value for "Peak virtual size:". If this is
    greater than "Pgflquo:" from authorize then increase the process quota.
    
    It is not unknown for ALL-IN-1 (particularly integrated with customer
    written applications) to allow memory 'leaks'. These may well show up
    with the kind of symptoms you describe.
    
    Cheers,
    
    Iain.
1877.3how much?GIDDAY::BURTChele Burt - CSC Sydney, DTN 7355693Tue Dec 01 1992 22:2215
Hello again,

Unfortunately, the first suggestion works on the assumption that we 
know which user's process is going to shuffle off next. Only ONE of the users
believes that he's had the problem occur to him more than once (and he may not 
be correct in this statement).

I'll ask the customer to try the second "memory leak detection" suggestion, but
by roughly how much should pagefilequo be increased? The STARS article suggested
to go to 200000 - but that seems a tad excessive for a user :^)

Thanks & regards,

Chele

1877.4Try 40KAIMTEC::VOLLER_IGordon (T) Gopher for PresidentWed Dec 02 1992 17:059
    Chele,
    
    I agree that 200,000 is probably excessive.
    
    I would suggest that 40,000 should be adequate for regular users.
    
    Cheers,
    
    Iain.
1877.5Publis Service AnnouncementAIMTEC::WICKS_ASoon: warm beer, football, rainWed Dec 02 1992 20:1510
    iain,
    
    The STARS article that Chele refers to suggests 200,000K for the
    MANAGERs account and was probably based upon advice taken from 
    a certain person who shares a cube with you. if the article needs
    clarifying please use the Comment feature in STARS.
    
    Regards,
    
    Andrew.D.Wicks