herzlich@NGP.UTEXAS.EDU (Larry Herzlich) (09/16/86)
We discovered an interesting thing about the SET TERMINAL command for
VMS 4.4. We have an Apple LaserWriter connected to a terminal print
queue and were having problems with getting more than 2 pages of
output. It seems that under 4.3 we could say:
SET TERMINAL /NOINTERACTIVE
and we got proper flow control.
Under 4.4, if you set /NoInteractive on the terminal, it turns on
Passall and kills flow control. BTW, the combination of /NoPassall
AND /NoInteractive results in the terminal having /PASSALL turned on.
The best part is that neither /INTERACTIVE or /PASSALL are
in the new DCL dictionary or in the release notes. The only reference
was in the I/O user's manual (1 line).
----Larry Herzlich
University of Texas at Austin
Computation Center
herzlich@ngp
cc.lherzlich@a20.utexas.eduegisin%watmath.waterloo.edu@RELAY.CS.NET (Eric Gisin) (09/20/86)
cc.lherzlich@a20.utexas.edu asks: > We discovered an interesting thing about the SET TERMINAL command for > VMS 4.4. We have an Apple LaserWriter connected to a terminal print > queue and were having problems with getting more than 2 pages of > output. It seems that under 4.3 we could say: > SET TERMINAL /NOINTERACTIVE > and we got proper flow control. > > Under 4.4, if you set /NoInteractive on the terminal, it turns on > Passall and kills flow control. BTW, the combination of /NoPassall > AND /NoInteractive results in the terminal having /PASSALL turned on. > Passall was replaced with Pasthru in VMS 4.0, in the release notes it said passall would be undocumented and unsupported in future releases. Interactive is just NoPassall, i.e. they're the same bit. It looks like NoInteractive does not prevent logins in VMS 4.4 anymore, and Pasthru never did. I presume you want to set up the Apple LW line to a mode where logins are not enabled, you can read/write directly to the line, and you can start and stop a printer queue. There is no such mode in VMS, I consider this a bug. (at least not if you need type ahead, which you do in this situation). What I do is set the terminal Spooled initially, and I have a command procedure to either stop the queue, NoSpool the terminal and allocate it; or deallocate the terminal and set it Spooled. I use these commands before and after I do `set host/dte dev$lw'. I don't know if this meets your needs. Eric Gisin, egisin@waterloo.csnet
carl@CITHEX.CALTECH.EDU (Carl J Lydick) (09/21/86)
It appears, then, that there was a bug in SET TERMINAL under VMS v4.3: prior to version 4.0 VMS and starting again with version 4.4 VMS, the /PASSALL and the /INTERACTIVE qualifiers were complementary, and that is the way they were documented in version 4.3. To get "raw" terminal I/O with flow control handled properly, you use the /PASTHRU qualifier. As to the lack of documentation for the /INTERACTIVE and /PASSALL qualifiers, these are, apparently, being phased out (and it's about time). Since /PASTHRU honors the /TTSYNC modifier, /NOINTERACTIVE (as you wish it to be interpreted) is equivalent to /PASTHRU/TTSYNC, /PASSALL to /PASTHRU/NOTTSYNC, and /INTERACTIVE to /NOPASTHRU.