| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 381.1 | Now that you mention it ... | ATLAST::BOUKNIGHT | Everything has an outline | Fri May 15 1987 11:30 | 7 |
| The message "There have been more than 0 error messages ..." seems
a bit strange. Will it ever say "more than 27 error messages" or
does it always say 0? Sounds like convoluted English to me. Far
better would be to say "There were Severe or Fatal errors and
processing will not continue beyond this point."
jack
|
| 381.2 | plannin ahea | VAXUUM::KOHLBRENNER | | Fri May 15 1987 14:58 | 6 |
| SOMEBODY is going to request the ability to set the number
of "acceptable" E-level messages greater than 0, so then the
message will say "There have been more than nn messages of
severity E". Every other language product lets you fiddle
with the number of messages of W and E severity, so we planned
ahead to that day...
|
| 381.3 | | TOPDOC::HIDER | Paul Hider | Sun May 24 1987 20:29 | 13 |
|
This note seems to have drifted off the rather serious problem
outlined in 381.0. Namely, that in BL8 there is no indication in
the notification message that a job failed, whereas in BL7 the
notification would indicate failure.
Since we insist that our numerous DOCUMENT users use batch for
their documents this is a serious setback for us.
Please could someone address this issue!!
..Paul
|
| 381.4 | a specific case | TOPDOC::HIDER | Paul Hider | Tue May 26 1987 21:32 | 22 |
|
hmm.. It looks as though I may have been a little premature here,
my apologies. As it would happen my first test showed up the problem.
The following profiles illustrate the problem as I experienced it.
The following profile, when DOC/BAT'd, exits with success status.
<profile>
<contents_file>
<element>(nonexistant_file.gnc)
<endprofile>
The following profile, when DOC/BAT'd, exits with error status.
<profile>
<element>(nonexistant_file.gnc)
<endprofile>
In both cases "nonexistant_file.gnc" should NOT exist.
..Paul
|
| 381.5 | see 418.1 | CLOSET::ANKLAM | | Mon Jun 01 1987 14:04 | 4 |
|
see 418.1. I think this is the same problem.
|
| 381.6 | DOC-F-MSG, message text ? | RDCV01::FSL | Rob Aldridge, FSL/BACIS | Wed Aug 19 1987 19:12 | 17 |
| (this "kinda" relates back to the base note)
How does one enable the displaying of the message text from
failed batch jobs?
That is to say, if I use
"$ DOCUMENT /BATCH=(NOTIFY) ..."
how do I get something more informative than
"Job DOC$XX terminated with error status, "
"%NONAME-F-NOMSG, Message number nnnnnnnnnn"
to display on my terminal when the job fails?
-Rob-
|
| 381.7 | will look into some kind of solution for future... | VAXUUM::PELTZ | �lvynstar Dun�dain | Thu Aug 20 1987 15:38 | 19 |
|
> how do I get something more informative than
> "Job DOC$XX terminated with error status, "
> "%NONAME-F-NOMSG, Message number nnnnnnnnnn"
>
> to display on my terminal when the job fails?
This is a bug within the SUBMIT command (which document
uses.) If the error message returned with a DOC-F message
status, then SUBMIT cannot expand the message since it
is not in the system message file.
If you look in your log file you will see exactly what
the error message was since DOCUMENT knows how to expand
its own messages.
Chris
|