Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!info-vax
From: GKN%OAK.SAINET.MFENET@LLL-MFE.ARPA
Newsgroups: mod.computers.vax
Subject: Physical memory query - my mailer has CC: problems
Message-ID: <8512051843.AA07284@ucbvax.berkeley.edu>
Date: Wed, 4-Dec-85 20:03:00 EST
Article-I.D.: ucbvax.8512051843.AA07284
Posted: Wed Dec  4 20:03:00 1985
Date-Received: Thu, 5-Dec-85 20:54:34 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27
Approved: info-vax@sri-kl.arpa

Date:    Wed,  4-DEC-1985 20:04 EST
To:      Info-VAX@SRI-KL.Arpa
Message-ID: <[OAK.SAINET.MFENET].2F632D00.008E704B.GKN>
US-Mail:   Science Applications;  P.O. Box 2501;  Oak Ridge, TN  37831
Telephone: (615) 482-9031
X-VMS-Mail-To: ARPA%"Info-VAX@SRI-KL.Arpa"

        From:   Arpa%"kholt@BBNCC3.ARPA"  4-DEC-1985 10:35
        Subj:   physical memory
        Date:   Tue, 3 Dec 85 15:11:01 EST

        Does anyone know how the DCL SHOW/MEMORY and SHOW/SYS commands decide how many
        pages of physical memory are free / busy?  Although SYS$GETSYI seems like the
        right idea, I don't see how to get the data I need.

Well, the DCL Show Memory command does all sorts of gymnastics waltzing around
inside of VMS and the SBI counting up memory controllers and such like.
Getting at this data is a non-trivial operation, and it is not possible to
do with normal non-privileged user-mode code.

The number that shows up in the "Physical Memory" column is the sum of the
$GETJPI parameters JPI$_PPGCNT (process page count in working set) plus
JPI$_GPGCNT (global page count in working set) for the process in question.

Hope this helps.

gkn