| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 136.1 | Yes, it can be done. | ZAPDEV::MACONI | The Doctor is In | Fri Jul 02 1993 10:58 | 22 |
| What type of database are you refering to? Is this an RMS, RDB, etc database?
If all you need to do is force all users running a specific image to EXIT the
image at a specific time, then it can be done.
If you do not want people to run, say MYDB, from 7pm until 9pm while you do your
defrag each night, then you can code a rule which says:
NODE: *
USERNAME: *
UIC: [*,*]
IMAGE_NAME: MYDB
PROCESS_CLASS: ALL
TERMINAL_NAME: *
FROM: 19:00
UNTIL: 21:00
WARN: N
IDLE_LIMIT: 0
ACTION: EXIT or STOP ! Exit to kill image, Stop to kill process
The idle limit of 0 will cause ZAP to kill the image/process as soon as it sees
it being run.
|
| 136.2 | | VITAL::KEEFE | Bill Keefe - dtn 223-1837 - PKO1 | Tue Jul 06 1993 16:15 | 15 |
| I tried the suggestion and it doesn't seem to have any effect.
Here's the ZAP$CONFIG.DAT:
0 DEBUG FALSE
1 ENABLE TRUE
2 GROUP_DW TRUE
3 HISTORY TRUE
4 IGNORE_SUSP FALSE
5 INSWAP FALSE
6 LENIENT TRUE
7 SEND 9,7,5,3,1
8 SENSITIVITY 5
9 TRACEBACK FALSE (tried this both ways)
|
| 136.3 | The exception database controls what is done. | ZAPDEV::MACONI | The Doctor is In | Thu Jul 08 1993 11:46 | 1 |
| The changes are in the Exception database, not the Configuration database.
|
| 136.4 | | VITAL::KEEFE | Bill Keefe - dtn 223-1837 - PKO1 | Thu Jul 08 1993 12:55 | 16 |
| Sorry, I should have included both. Here's the rule from the Exception
database:
Nodename: *
Username: *
UIC: [*,*]
Image Name: TARGETHOTCHECK
Process Class: ALL
Terminal Name: *
From Time: 00:00
Until Time: 23:59
Send Warnings: N
Idle Time Limit: 0
Action: EXIT
|
| 136.5 | Use the REPORT feature to debug the setup. | ZAPDEV::MACONI | The Doctor is In | Fri Jul 09 1993 16:40 | 31 |
| There can be one or two problems here:
1. The exception database rules are "out of order" and a different
rule is applying to the process in question.
2. The process is being grouped with other processes due to the
configuration file parameters.
To determine what is happening:
1. Generate a report in Zap via:
DEFINE/SYS/EXEC ZAP$RUN_STATUS REPORT
2. Read the report and check the rule that is applying to the process.
If:
a: The wrong rule is being used, then the rule is after
another rule that can apply to the process.
Change the order of the rules.
or
b: The right rule is being used, but the idle time limit
is not 0.
It may be grouped with other DECwindows processes.
If so, set LENIENT to FALSE.
If you still do not know, send me a copy of your REPORT file at my mail
address above.
Keith
|
| 136.6 | | VITAL::KEEFE | Bill Keefe - dtn 223-1837 - PKO1 | Wed Jul 21 1993 13:40 | 1 |
| Changing LENIENT to FALSE fixed the problem. Thanks.
|