Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!rutgers!ames!ucbcad!ucbvax!SRI-KL.ARPA!STEINBERGER
From: STEINBERGER@SRI-KL.ARPA (Richard Steinberger)
Newsgroups: mod.computers.vax
Subject: ASTs (again)
Message-ID: <12287793400.13.STEINBERGER@SRI-KL.ARPA>
Date: Fri, 20-Mar-87 00:05:07 EST
Article-I.D.: SRI-KL.12287793400.13.STEINBERGER
Posted: Fri Mar 20 00:05:07 1987
Date-Received: Sat, 21-Mar-87 09:14:53 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 30
Approved: info-vax@sri-kl.arpa

I have been using f$getjpi(PID,"ASTLM") to continuously monitor the number of
remaining ASTs in my quota.  (The parameter may not be ASTLM - I'm not using
the machine that the code runs on now - But it does give the remaining ASTs
correctly).  That is, I run a program on one terminal and use the f$getjpi
call (in a loop) to keep track of the AST count (displayed).

When the count decreases it means (I believe) that another AST has been 
queued.  When the count of remaining ASTs increases it means that an AST
was just delivered to the monitored process.

Is there a way to ascertain what hardware device actually delivered the AST?
Can additional information be found?  I know the exact MACRO instruction (in
the application code) that results in the remaining AST count being
incremented by 1 (it happens to be a CHMK instruction in SYS$DASSGN).

Where is the (software) information about what ASTs are queued stored and how
is it accessed?  When you're 'sitting' at the DCL prompt, usually 2 (or is
it 3?) ASTs are queued.  I assume these are for CONTROL-T, CONTROL-Y and/or
CONTROL-C or user TTY input.  I would like to be able to know what ASTs
are queued (i.e. from what devices and what AST routines would be called)
at any given moment.

Thanks to all who reply.

Regards,
	Ric Steinberger
	steinberger@kl.sri.com

      (415) 859 - 4300
-------