| Title: | Zap Technical Conference |
| Notice: | ZAP Version 5.3 is available. See note 1.1 |
| Moderator: | ZAPDEV::MACONI |
| Created: | Mon Feb 24 1986 |
| Last Modified: | Mon May 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 170 |
| Total number of notes: | 492 |
This note contains a technical problem reported to Zap support via VMSMail.
It has been reproduced as accurately as possible to maintain its integrity.
Problem reported by: Gary Kessler @GUIDUK::KESSLER
Products used: Zap version 3.3, using standard exception file
Problem description:
When using asyncronous DECnet between his Rainbow and the Vax
system running Zap, the Vax process is deleted due to excessive
idle time. The Rainbow is executing a procedure called Spawner
which, when a command is issued from the Rainbow, spawns a process
to service the request.
After the default 20 minute idle time limit expires, the
process is deleted. Zap indicates that the process was executing
the image SYS$SYSTEM:SET.EXE at termination time. The commands
used to initiate the Asyncronous DECnet were:
$ SET TERMINAL/PROTO=DDCMP/SWITCH=DECNET/MANUAL
%SET-I-SWINGINPR, Terminal line now becoming a DECnet line.
Other utilities, such as WHAT and SHOW PROCESS/USERS indicate
that the process is idle with no image.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3.1 | Workaround for problem | MRADM::K_MACONI | The Doctor | Mon Feb 24 1986 13:05 | 25 |
The problem seems to be caused because of the product that you
are using on the Rainbow. Spawner causes a subprocess to be created
each time you perform a command on the Vax. Unfortunately, most
of these processes will not last long enough for Zap to detect that
they exist.
The temporary solution is to either extend the idle time limit
of SET, or make it immune. This, however, will cause your system
to have the problem that if a user issues a set command and does
nothing else, they will be immune.
Since there seems to be only one user involved, or at the least
very few users, I would suggest that you make SET immune for those
users only.
The last solution is to reduce the sensitivity of Zap on your
system. Since a spawn command does require a small about of cpu
time, you could reduce the sensitivity to as low as 1 and see what
the results are on your system. Remember, the lower that sensitivity,
the less often a user will be Zapped (due to the reduction in the
minimum amount of work required to be done).
The problem of lines becoming DECnet lines is being addressed
and it may be possible for Zap to be modified to treat these lines
specially.
| |||||