Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uwm.edu!bionet!agate!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  I love my Apollo's (ACL-calls)
Message-ID: <9012061511.AA04340@richter.mit.edu>
Date: 6 Dec 90 15:11:40 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 17

Most of the ACL manager calls are unreleased calls. Use /systest/ssr_util/dmpf
(the hex file dumper) to look at /com/edacl. You'll see the names of all of
the global subroutine calls near the end of the listing. If you can get DBX or
DDE to display the assembly language for /com/edacl, you may be able to figure
out the arguments to the calls. Frankly, if HP/Apollo hasn't released the calls,
it's because they don't want you to use them. I think it might be easier to use
the Unix "system" call or maybe the Aegis "pgm_$invoke" call to run the
/com/edacl program from within your own program, feeding it (edacl) the ACL
you want to set.


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter.mit.edu@eddie.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)