| FileView itself doesn't care about TTY_DEFCHAR2, but it does create
a terminal device for each sub-process it creates to run tasks.
I'm hoping this is the explanation for a bug we were trying to track
down, which we weren't able to reproduce locally. The problem was
that sub-process creation would fail with a "terminal has associated
mailbox" error on the terminal device. I just checked the system on
which the problem occurred, and they do indeed have an illegal value in
TTY_DEFCHAR2... I've asked them to correct it and let me know if the
FileView problem "heals up."
SO, the reason the task is marked "pending" is that the subprocess
creation fails with something other than a quota error. (FileView will
be corrected to report the error.) However, the jury is still out on
why subproc creation fails when TTY_DEFCHAR2 contains an illegal
value...
Thanks for pointing this out,
Tom
|
| According to Forrest Kenney, that flag in TTY_DEFCHAR2 (200 hex) is
used by the TTY driver to indicate an associated DCL mailbox. So
subprocess creation fails when it tries to assign the device, and it
appears there is already an associated mailbox. Forrest says the driver
should be changed to ignore it when the illegal value is set in your
sysgen params. But for now, keep TTY_DEFCHAR2 legal...
Tom
|