[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Traditional Video Terminals and Monitors |
Notice: | See 3230 for Sun River information |
Moderator: | REGENT::LASKO |
|
Created: | Tue Mar 18 1986 |
Last Modified: | Thu May 22 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3256 |
Total number of notes: | 14159 |
3246.0. "Curious VT520 Wait State PRoblem,help required please" by SEDTMA::HANCOCK (Use what you (used to) sell) Tue Feb 04 1997 10:51
Hi,
can anyone advise me on how to go about troubleshooting
this little scenario.
VT520 terminals connected to DECservers,700 and 900. Users log in
multiple times to several systems,using multisessions.One particular
application (a DECforms application) gives a problem whereby,if the
screen is refreshing,and the user flicks forward a session whilst
the screen is updating,when they come back to that session ,the
VT520 goes into a wait state,and cannot be released.They either have
to power the thing right off,or go back to the good session,log it
out,and flip back to the "hung" session and ^R it to bring it back
to life.
Any ideas where the problem might lie,or where to start looking ?
VMS is at 6.2,Servers are at current shipping images..
Cross Posted in TERMINALS,TERMINAL_SERVERS,LAT,and DECFORMS
Cheers Mick Hancock MCS South UK
T.R | Title | User | Personal Name | Date | Lines |
---|
3246.1 | | REGENT::LASKO | Tim - Printing Systems Business | Tue Feb 04 1997 12:52 | 13 |
| I had what sounds like the same problem with DECserver multisessions
all the way through beta testing and into the final releases of the
VT520/525. [VT525 QAR 145, if anyone feels like looking it up.] My
usual procedure for reproducing it was to log in quickly to all four
sessions on the terminal but it would happen when multiple sessions
were trying to update the screen at once, too. I ended up switching
back to VMS SSU for multisessions because of this bug. A ^T would
almost always reset the session (less drastically) in this situation.
The resolution I got from the product team at the time was that it was
a bug in the DECserver multisession implementation that had been
demonstrated to "the DECserver people". Don't know if it ever got fixed
and most of the people involved are now gone....
|