Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ucsd!sdcsvax!ucsdhub!esosun!seismo!uunet!hi-csc!tim
From: tim@tim.UUCP (Tim Giebelhaus)
Newsgroups: comp.sys.apollo
Subject: Re: remote process info?
Message-ID: <223@tim.UUCP>
Date: 5 Mar 89 18:36:00 GMT
References: <8903032320.AA19843@cod.nosc.mil>
Reply-To: tim@apcimsp.UUCP (Tim Giebelhaus)
Organization: mpls
Lines: 27

In article <8903032320.AA19843@cod.nosc.mil> dennis@PEANUTS.NOSC.MIL (Dennis Cottel) writes:
>A map listing of DSPST shows the following "secret" library calls:
>
>   rem_proc1_$info
>   rem_proc2_$info
>
>Would someone please mail me the calling sequence for these routines?
>What I'm specifically after is a way to get the process time for the
>idle process on remote machines, similar to what was done in the
>recently posted "load_stat" program.  Thanks.

"Unsupported" would be a better word than "secret".  Routines which are 
not documented may change between releases without warning of any kind.
Also, you will find no support from Apollo for unsupported system calls
(unless you have a prior agreement with marketing which is usually only
given to some OEMs).

Thus, if you can't find the call in a public manual, use it at your
own risk.  If there is a system call you would like to see made public,
please file an APR with the /com/crucr or /usr/apollo/bin/mkapr command.
APR's are the only supported method of getting changes done to the
operating system.  APRs are also what Apollo uses internally to get
changes done.
-- 
UUCP: uunet!hi-csc!apcimsp!tim
ARPA: tim@apollo.com
Contents of this message has nothing to do with work.