| Title: | MAILBUS 400 User Forum |
| Notice: | kits 100-109 - Infocenter //www.digital.com/info/messaging |
| Moderator: | IOSG::MARSHALL |
| Created: | Thu Jun 11 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3210 |
| Total number of notes: | 9174 |
We currently handle bugs in dxbook and the latest I am working on
is a crash that occurs when you attempt to print certain
enteries as postscript to a file. What happens is a recursive
loop that never returns while attempting to convert the book
selection to postscript. I am writing here because two of
the book enteries that cause the crash are in the Mailbus_400
documentations. Here is the "path" to the enteries:
Library 1
Documentation Library Contents
Mailbus 400
Planning and Setup
Tables
2-1 Worksheet for a Routing Domain (causes crash)
2-2 Worksheet for a Peer MTA Entry (causes crash)
2-3 Worksheet for Agent Entry (does not crash)
I suspected intially that tables are a problem but as I have
found, 2-3 is fine but 2-1 and 2-2 crash. I believe either
the converstion program that makes books from SDML files
are the SDML files for 2-1 and 2-2 are the problem. However
I need a copy of the SDML files for all three inorder to
see what the difference is between the ones that work
and the ones that crash. I was told that the individual
departments are responsible for the libraries for their
components. Can someone from the MAILBUS_400 group please
contact me regarding getting hold of the SDML files for
these enteries. I can be reached at:
[email protected] tel#: (310)337-5178
Any help is much appreciated.
Robert A. Zawarski
Platinum Solutions (Locus)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3124.1 | Upgrade? | FORTY2::KNOWLES | Per ardua ad nauseam | Thu Jan 30 1997 09:01 | 4 |
Thank you for your observation. This problem is not apparent in V2.0.
How old is the version you are using?
b
| |||||
| 3124.2 | Correction | FORTY2::KNOWLES | Per ardua ad nauseam | Thu Jan 30 1997 09:33 | 7 |
Correction - I misread your note and could not reproduce your bug; now
I can.
It is much more likely to be due to Bookreader's notorious print
routines than to the SDML coding.
b
| |||||
| 3124.3 | Meta-correction | FORTY2::KNOWLES | Per ardua ad nauseam | Thu Jan 30 1997 16:29 | 13 |
Wrong again. It didn't crash the system on OpenVMS, so I assumed the
hang those tables caused meant the Bookreader process had crashed. In
fact, it was very busy writing an enormous file. But the loop must be a
complete one, because the enormous file contains hundreds (if not
thousands) of printable postscript images.
This suggests to me very strongly that the bug is in Bookreader rather
than VAX DOCUMENT.
If I can be of any further help, contact me either by mail or on DTN
830-3592.
b
| |||||