| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2540.2 | clarification - does this help ? | IOSG::STANDAGE | My hovercraft is full of eels | Wed Feb 26 1997 15:55 | 21 |
|
Hi Martin,
This isn't necessarily an answer, but might clarify things.
Setting OA$AIDA_QUOTA_WARNING_LEVEL to 25 will mean that if any
resource gets within 25% of it's maximum, then the warning mechanism
will come into place. By default, the warning mechanism is 5 logged
messages to the AIDA server log file (one per minute), followed by
REPLY/BELLs to the Manager.
So, in your instance is BYTLM is set to 200,000, you won't get any
warnings until the AIDA server reaches 75% of that value (150,000).
From your base note I wasn't too sure what the 20,000 value was
referring to.
-Kevin.
|
| 2540.3 | BYTLM is a pooled quota but... | IOSG::SEATON | Ian Seaton, IOSG Office Server Development | Wed Feb 26 1997 17:27 | 33 |
| Martin,
There are two things that may be relevant here, first is that BYTLM is
shared among all jobs in a process tree. When a subprocess is started
part of the BYTLM of the parent is given to the subprocess reducing the
BYTLM of the parent, the resource monitor checks the CURRENT BYTLM not
the INITIAL BYTLM of the process. Secondly, BYTLM is altering all the
time with each QIO/ENQ etc. but the Resource Monitor only runs once
every minute so a short reduction will not be noticed.
If Aida has started up say 5 DDS subprocesses then each will have been
given a chunk of the parent's BYTLM reducing the value against which
the instantaneous BYTCNT is tested so it may still not be within the
25% limit even though it is within 25% of the INITIAL BYTLM.
It is interesting point that perhaps we should be looking at the
initial value instead of the current value as this might represent a
better picture of the threat of quota shortage to the server, hmmm....
(The other side of that picture is that the DDS subprocesses quotas have
already been accounted for by the server as it started them so perhaps
itis correct to only deal with it's own quota.)
To check the various parts of the theory you need to look at the BYTLM
for the the Aida Server, you can either use f$getjpi(pid,"BYTLM") or
use the System Dump Analyser (ANALYZE/SYSTEM, SHOW PROC/IND=ipid). You
can see the BYTCNT via the same method (SDA shows both together)
comparing the two will show you the current levels.
BTW: the logicals are scanned each interval so you don't need to
restart the server unless you've stopped the quota checking explicitly by
defining OA$AIDA_QUOTA_INTERVAL to be 0 at some point.
Ian
|
| 2540.4 | worth checking | GIDDAY::LEH | | Thu Feb 27 1997 05:39 | 21 |
| > To check the various parts of the theory you need to look at the BYTLM
> for the the Aida Server, you can either use f$getjpi(pid,"BYTLM") or
> use the System Dump Analyser (ANALYZE/SYSTEM, SHOW PROC/IND=ipid). You
> can see the BYTCNT via the same method (SDA shows both together)
> comparing the two will show you the current levels.
f$getjpi(pid,"bytcnt") is also avail to show the unused value, while
f$getjpi(pid,"BYTLM") indicates the allocated quota. The accumulated usage can
be captured with f$getjpi(pid,"bufio"), e.g.
$ slash = "/"
$ bufio=F$GETJPI(pid,"bufio")
$ bytcnt=F$GETJPI(pid,"bytcnt")
$ bytlm=F$GETJPI(pid,"bytlm")
$ WRITE SYS$OUTPUT "BYTLM total/unused/quota ",BUFIO,slash,BYTcnt,slash,BYTlm
I recalled the warning did work for FCS, but never tried AIDA myself. Should
be a simple task to try a ridiculously high value, say 98 percent for
OA$AIDA_QUOTA_WARNING_LEVEL
Hong
|
| 2540.5 | Indeed Bytlm is not monitored | UTRTSC::SMEETS | Workgroup support | Tue Mar 04 1997 08:00 | 86 |
| Hi,
First of all thanks for your replies. Sorry, I didn't respond ealier but
I was send to a customer in order to help with a very urgent DEC/EDI problem.
I think Ian is correct in .3. My customer has the warning level defined as 99%
and even than there are no warnings given for the Bytlm.
e.g.
26-FEB-1997 21:28:24.14 ************ ************************
Server starting
26-FEB-1997 21:29:24.15 Resource Monitor
%OARTL-W-WARNQUOTA, TQCNT has less than 99% remaining
26-FEB-1997 21:29:24.29 Resource Monitor
%OARTL-W-WARNQUOTA, PGFLQUOTA has less than 99% remaining
26-FEB-1997 21:29:24.41 Resource Monitor
ASTCNT: 1995/2000 BIOCNT: 1998/2000
BYTCNT: 193280/193280 DIOCNT: 500/500
ENQCNT: 2000/2000 FILCNT: 1986/2000
TQCNT: 147/150 WARNING! PGFLQUOTA: 194416/200000 WARNING!
APTCNT: 0 GPGCNT: 1952
PPGCNT: 3408 STS: 00140001
STATE: 0000000E EFCS: E0000000
EFCU: E0000000 PID: 00000135
WSEXTENT: 65536 WSQUOTA: 4096
WSSIZE: 6800 WSAUTH: 4096
PRCNAM: "AIDA$SERVER_1"
26-FEB-1997 21:30:25.07 Resource Monitor
%OARTL-W-WARNQUOTA, TQCNT has less than 99% remaining
26-FEB-1997 21:30:25.18 Resource Monitor
%OARTL-W-WARNQUOTA, PGFLQUOTA has less than 99% remaining
26-FEB-1997 21:30:25.29 Resource Monitor
ASTCNT: 1995/2000 BIOCNT: 1998/2000
BYTCNT: 193280/193280 DIOCNT: 500/500
ENQCNT: 2000/2000 FILCNT: 1986/2000
TQCNT: 147/150 WARNING! PGFLQUOTA: 194416/200000 WARNING!
APTCNT: 0 GPGCNT: 2000
PPGCNT: 3408 STS: 00140001
STATE: 0000000E EFCS: E0000000
EFCU: E0000000 PID: 00000135
WSEXTENT: 65536 WSQUOTA: 4096
WSSIZE: 9200 WSAUTH: 4096
PRCNAM: "AIDA$SERVER_1"
26-FEB-1997 21:31:25.97 Resource Monitor
%OARTL-W-WARNQUOTA, TQCNT has less than 99% remaining
26-FEB-1997 21:31:26.09 Resource Monitor
%OARTL-W-WARNQUOTA, PGFLQUOTA has less than 99% remaining
26-FEB-1997 21:31:26.20 Resource Monitor
ASTCNT: 1995/2000 BIOCNT: 1998/2000
BYTCNT: 193280/193280 DIOCNT: 500/500
ENQCNT: 2000/2000 FILCNT: 1986/2000
TQCNT: 147/150 WARNING! PGFLQUOTA: 194416/200000 WARNING!
APTCNT: 0 GPGCNT: 2000
PPGCNT: 3408 STS: 00140001
STATE: 0000000E EFCS: E0000000
EFCU: E0000000 PID: 00000135
WSEXTENT: 65536 WSQUOTA: 4096
WSSIZE: 9200 WSAUTH: 4096
PRCNAM: "AIDA$SERVER_1"
26-FEB-1997 21:32:26.89 Resource Monitor
%OARTL-W-WARNQUOTA, TQCNT has less than 99% remaining
26-FEB-1997 21:32:26.99 Resource Monitor
%OARTL-W-WARNQUOTA, PGFLQUOTA has less than 99% remaining
26-FEB-1997 21:32:27.10 Resource Monitor
ASTCNT: 1995/2000 BIOCNT: 1998/2000
BYTCNT: 193280/193280 DIOCNT: 500/500
ENQCNT: 2000/2000 FILCNT: 1986/2000
TQCNT: 147/150 WARNING! PGFLQUOTA: 194416/200000 WARNING!
APTCNT: 0 GPGCNT: 2000
PPGCNT: 3408 STS: 00140001
STATE: 0000000E EFCS: E0000000
EFCU: E0000000 PID: 00000135
WSEXTENT: 65536 WSQUOTA: 4096
WSSIZE: 9200 WSAUTH: 4096
PRCNAM: "AIDA$SERVER_1"
But if the Bytlm is watched by using G$GETJPI or ANAL/SYSTEM than once sees
a decreasing value.
So I think this should be modified in the documentation or even better modify
the code in order to get a better indication of the remaining BYTLM.
So should I raise an IPMT ?
Martin
|
| 2540.6 | IPMT Level 3 UTO101336 (cfs. 49416) | UTRTSC::SMEETS | Workgroup support | Thu Mar 06 1997 07:18 | 0
|