| 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 |
I have two customers having problems with ZAP 4.0.
1) The customer has ZAP running on a two node cluster of 6210's, with
VMS 5.2. When the TRACE option is set to FALSE nothing happens. None
of the parent or sub-processes are affected, even when the max idle
time has expired.
2) The customer has modified the ZAP.MSG file adding custom text to it.
When the modified file is used by ZAP a file size error is returned.
Can the ZAP.MSG file be modified and if so what is the maximum TEXT
length and file size?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 69.1 | ZAP V4.0 FT3-2 | WAV12::MACONI | The Doctor is In | Thu Feb 22 1990 16:27 | 15 |
It appears that the Assets program accidentally released a field test
version of ZAP instead of the final version. The correct version is
being submitted again.
The correct version was retested and TRACEBACK (disabled and enabled)
works correctly on VMS V5.1 and V5.2. In addition, the array error
in the last note was also corrected in the final version (this was
caused by the terminal name field being increased from 7 to 8
characters. The field test released did not work correctly under
versions of VMS prior to V5.2.
To determine which version you are running, check the ZAP.LOG file.
ZAP will display its actual version when it starts. The field test
will not work under VMS V5.0,5.1. However, under VMS 5.2+ it appears
that only the TRACEBACK (disabled) option has problems.
| |||||