T.R | Title | User | Personal Name | Date | Lines |
---|
4956.1 | where? | TOOK::MINTZ | Erik Pavlik Mintz | Tue Apr 27 1993 00:19 | 4 |
| Is the users seeing the old notifications in the notification window,
or highlighted on the map, or both?
-- Erik
|
4956.2 | Update on the notification problem. | CSC32::W_MCGAW | | Tue Apr 27 1993 18:33 | 11 |
| Hi Erik,
I followed up with the customer on this and he informed me that the old
notifications were only appearing in the notification window. BTW, he
also indicated that the bottom 5 selections under the applications pull
down menu don't work from a served window. The LAN autopology and
Notification Services work o.k. for him. The failing selections
complain about missing files and appear to be trying to run on the node
the window is being served to , not the DECmcc host node.
Walt
|
4956.3 | Update on notifications and applications menu | CSC32::W_MCGAW | | Fri May 14 1993 11:42 | 21 |
| Hi,
This is an update to .2.
The customer now says that he got the notification information second
hand it it only seemed to happen once. They will continue to monitor
this and call back if it occurs again.
The applications failure seems to be directly tied to how the window is
served. The customer only has a two user license on the DECmcc host
node. To serve the window, he is doing DCL task to task to kick off
the .com procedure used to issue the set display and manage/enterprise
commands. This results in a network process on the DECmcc node (the
failing configuration). If the customer sets host to the DECmcc host
and issues the set display and manage/enterprise commands interactively
(which is running from an interactive and not a network process) then
all of the applications menu selections function properly. I am still
trying to figure out why this works (or fails) this way but if you have
any suggestions / comments, I'd like to hear them.
Walt
|
4956.4 | Served window is working now. | CSC32::W_MCGAW | | Mon Jun 14 1993 18:41 | 9 |
| Hi,
The problem with the served window has been resolved. In the task to
task procedure that serves the window from the MCC station back to a
different window station, we changed the process startup to run as a
detached process instead of a network process. Now the applications
from the menu start correctly.
Walt
|