[comp.os.vms] VS3200

jan-olof@ttds.UUCP (Olof Andersson Bergs) (08/03/88)

I have recently got a vaxstation 3200, We run VMS4.7A and workstation
software 3.0. I like a lot but there is one thing I dont like. If I copy
a file to the screen with TYPE it takes forever (200-300 lines) before
I can abort the command with CTRL-C or CTRL-Y. CTRL-S and CTRL-O are also
slow to resond. The key HOLD SCREEN is much faster but I want to abort
the TYPE command. We also have some Vaxstation 2000 running the same
software without this disturbing delay.

Is there a fix for my problem, I have called DEC Sweden but nobody
knew anything about this although they could reproduce it.

Thanks
  Jan-Olof Andersson

BITNET  JANOLOF@SEQZ51
-- 

UUCP: ..seismo!mcvax!enea!ttds!jan-olof 	Jan-Olof Andersson
						Dep. Physical Metallurgy
TEL:  (46) 8 7908387				Royal Inst. Technology
						100 44 Stockholm
						Sweden

cfchiesa@bsu-cs.UUCP (Christopher Chiesa) (08/04/88)

In article <1163@ttds.UUCP>, jan-olof@ttds.UUCP (Olof Andersson Bergs) writes:
> I have recently got a vaxstation 3200,  [...]
> ... If I copy
> a file to the screen with TYPE it takes forever (200-300 lines) before
> I can abort the command with CTRL-C or CTRL-Y. CTRL-S and CTRL-O are also
> slow to resond. The key HOLD SCREEN is much faster but I want to abort
> the TYPE command. We also have some Vaxstation 2000 running the same
> software without this disturbing delay.

This sounds an awful lot like what I experience when I use a slow dialup 
line to access VMS.  I have to hit control_Y or control_C almost IMMEDIATELY
after issuing the TYPE command (or any command that generates a long output)
if I only want to see the first 20-or-less lines.

My interpretation of this is that my terminal, at 1200 (or, in the bad ol' 
days, 300) baud, can't keep up with the VMS output.  (What with intervening
terminal and network servers, VMS thinks EVERY terminal is 4800 baud.)  The
net effect is that, by the time my terminal gets around to displaying the 
line I want to see before aborting, VMS has sent out a lot more material that
I can't do anything to stop -- it is "on the way," and is beyond the reach of
Control_C or Control_Y.

I am wondering whether there is some difference in the hardware connection
BETWEEN your various Vaxstations and the VMS host: I'd expect you to say yes,
that the VS's that DO experience the delay, and those that DON'T, are con-
nected differently somehow.

* One note: I've been wrong before, and it could be something completely 
different than this.  Take this with a grain of salt and by all means listen
to other explanations in preference to this one.  But who knows, maybe this
is it.  Looking for explanations in high places often causes those in low 
places to go unseen. *

Chris Chiesa
  Recent graduate,
   Ball State University
-- 
UUCP: <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!cfchiesa 
cfchiesa@bsu-cs.UUCP                                           

ted@mitre-bedford.ARPA (Edward J. Ede) (08/04/88)

>In article <1163@ttds.UUCP>, jan-olof@ttds.UUCP (Olof Andersson Bergs) writes:
> I have recently got a vaxstation 3200,  [...]
> ... If I copy
> a file to the screen with TYPE it takes forever (200-300 lines) before
> I can abort the command with CTRL-C or CTRL-Y. CTRL-S and CTRL-O are also
> slow to resond. The key HOLD SCREEN is much faster but I want to abort
> the TYPE command. We also have some Vaxstation 2000 running the same
> software without this disturbing delay.

I saw this is the VWS 3.3/4.0 user's guide while flipping through it last
week.  I'm not sure how helpful this will be, but it's worth a try.
Try definining the logical UIS$VT_FAST_SUSPEND (in the SYSTEM table)
to be true.  Appendix B, page 5 of the VWS user's guide states:

   Fast suspend is an optimization for GPX system that can reduce the
   time it takes for a CTRL/S to take effect.  When this is enabled, the
   cursor will not blink during the CTRL/S.  NOTE: There is no benefit to
   using this on a VAXstation I, VAXstation II, or QVSS-based system.

In playing with these logicals, one usually has to create a _new_
window for them to take effect.  If you're only running VWS 3.2, give
it a shot.  I'm running 3.2 on my VS2000 and live icons and copy/paste
(undocumented features in 3.2) work great.

Good luck

Ted Ede -- ted@mitre-bedford.arpa -- The MITRE Corporation -- Burlington Road  
|        -- Bedford MA, 01730 -- Mail Stop B015 -- (617) 271-2524 --        |
|                   - this line intentionally left blank -                  |
+---------------------------------------------------------------------------+