[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DOCUMENT T1.0 |
| Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
| Moderator: | CLOSET::ADLER |
|
| Created: | Mon Feb 09 1987 |
| Last Modified: | Thu Oct 31 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 897 |
| Total number of notes: | 4397 |
511.0. "Terminal logging and Document processing" by CUPOLA::HAKKARAINEN (with hasty reverence) Mon Jun 15 1987 11:44
This is probably more of a VMS question than a Document question,
but ...
A user had to leave before an interactive Document job was finished
running. While leaving, the user accidentally press F1 (Hold Screen)
key.
The next morning, the user noticed that the job had not finished and
was puzzled why the job had stalled. When I pressed F1 again, releasing
the output, the job had hardly progressed at all. It did finish within
a few minutes and all was dandy.
So, why did processing stall when screen output was on hold? There
wasn't a lot of text to follow, just the usual messages from device
conversion and printing. I presume that if the user had specified
/nolog, the processing would have completed, even if the terminal
had melted.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 511.1 | Good instincts, bad reality. | CLOSET::PARMENTER | | Mon Jun 15 1987 14:32 | 9 |
| If my memory serves me, VMS will keep running until the next time
it has to do terminal I/O. At that point, it performs no further
actions until it has the terminal's attention. This has nothing
to do with Document at all, and relates more to the historically
mute relationship of software and hardware at DEC (have they ever
talked to each other very well?).
David
|