[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
117.0. "Zap V5.0 stack dump!" by UTRTSC::WIJKAMP (One day, you won't drink beer, you'll drink GROLSCH) Tue Aug 25 1992 09:11
Hello,
A customer came up with the following ZAP problem.
He resently installed ZAP V5.0, VMS V5.4-1.
Now on average every 2 day's his zap process gets killed with the
following errors.
%ZAP-I-STATUS, Status at 23-AUG-1992 04:29:40.53 Pass = 5040 Stop = 122
Exit = 0 User = 0 Error = 0
%PAS-F-FILALRCLO, file is already closed
File "HISTORY_FILE" Filename ""
%TRACE-F-TRACEBACK, Symbolic stack dump follows
module name routine name line rel PC abs PC
0013A5C0 0013A5C0
00134C94 00134C94
ZAP$MONITOR ZAP$MONITOR 2802 00000C86 0012B826
00131E3E 00131E3E
Since I have no knowledge of ZAP, and non off my collegues, I hope
somebody knowledgeable can help me to solve this problem.
Thanks in advance for any help/advise,
Greetings,
Ren� Wijkamp,
Software support, The Netherlands.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 117.1 | Monitor is failing during shutdown | ZAPDEV::MACONI | The Doctor is In | Tue Aug 25 1992 11:02 | 14 |
| Hi,
After checking the source code I did find a bug which can cause the
failure that your crash indicates. However, it can only occur when the monitor
is being shut down by the ZAP$RUN_STATUS value of "EXIT". Check to see if the
customer has a job out there that periodically shuts down the monitor. ZAP V5.0
no longer needs to be shut down to flush the log file as the history file may
be used at any time.
This bug will be fixed in the next release.
Thanks,
Keith Maconi
|