| Funny you should ask. I have such a program. Note that nowhere in this
topic does any of this have anything to do whatsoever with the Atari ST
or Whack, except that in the case of VWSSSU which uses the same line
protocol and shares one source code module.
Your options are many, some of which you have
already mentioned, but I include for completeness:
1 - Create a new terminal emulator and run SET HOST from it.
Advantages: It's supported, SET TERM/PAGE works across the link.
Disadvantages: An extra local process for each session, the
performance drawbacks of network packet per I/O behavior.
[I don't recommend this for frequently used connections in your local area.]
2 - Connect comm port to a LAT and use SET HOST /DTE on it.
Advantages: It's supported. You get multiple sessions by
defining LOCAL and BREAK characters, and using these to
switch between them.
Disadvantages: All sessions share the same window, you only get
to use one at a time, and the terminal display is not
updated when you switch sessions.
[I rarely use it, I use KERMIT instead.]
3 - Use VMS Kermit on your comm port.
Advantages: You get file transfer capability, and it works a
tad better than SET HOST /DTE on flow control and things.
Disadvantages: Unsupported, otherwise same as 2.
4 - Use VWSLAT, discussed in VSG::VWSLAT. I help maintain VWSLAT,
along with Jerry Leichter. The latest version is in
PRNSYS::SYS$SYSTEM:VWSLAT.EXE and SYS$HELP:VWSLAT.HLB. This
turns your VAXStation into a terminal server, as you say.
However, I KNOW OF NO PROBLEMS WHERE VWSLAT CAUSES "HAVOC" ON
THE ETHERNET.
Advantages: Fast, loaded with options, as many sessions as you
want with only one VMS process, each in separate windows
under either VWS or DECWindows. It's used by hundreds of
workstation users around the company. As long as your
workstation does not have LAT enabled, VWSLAT can be used without
any elevated privs.
Disadvantages: You must disable the LTDRIVER and incoming LAT
connections on your workstation while you are using VWSLAT.
You can't have somebody CONNECT to your workstation while
you CONNECT to someone else's. SOME groups of users have
had random access violations in processing CONNECT commands.
[Unless you need incoming LAT, I would recommend using this program.]
5 - Use VWSSSU. VWSSSU is essentially "Whack" for your
VAXStation. It appears a lot like VWSLAT, in that you get
multiple sessions on a remote system in separate windows, but
the sessions are multiplexed using TDSMP on a serial line. (The
protocol behind the VMS SSU ENABLE command and DECServer SET
MULTI ENABLE command).
Advantages: VWSSSU can be used across long modem links and other
situations where serial lines are the only practical link.
Disadvantages: Not well documented. Flow control can be quirky
at times. I don't have a "real" release, but have given it
to a few people that have asked about this capability. If
using DECServer SET MULTI ENABLE command, you only get 4
sessions. If using the VMS SSU ENABLE command, you get up
to 10 sessions, but they are all on the same node.
To try it, take PRNSYS::DUA1:[LOMICKAJ.VWSSSU]VWSSSU.EXE. (If
you are not up to VMS V5 yet, take VWSSSU_V4.EXE.) Make it a
foreign command (VWSSSU :== $SYS$LOGIN:VWSSSU.EXE) and say
"$ VWSSSU CSA0:", or whatever device you call your comm port.
Be sure to allocate it and set the speed ahead of time.
Once you have sessions enabled, you can create additional ones
with the CONNECT command. It takes the same qualifiers as the
CHILD command. (See PRNSYS::RELEASED_TOOLS:[CHILD]CHILD.TXT for
information about the CHILD utility.)
[VWSSSU works, so if you really think it's right for you, go for it, but
I still think VWSLAT is the way to go.]
|