News about Unisys Terminals and Communications

(includes Sperry/Univac, Burroughs Corporation, and Convergent Technologies)

 //////////////////////////////////////////////////////////////////////////////

The Unisys History Newsletter was written and published by George
Gray.  George is a Systems Programmer for the State of Georgia
Department of Administrative Services and is heavily involved in
Unite Inc., a Unisys User Group.  He is also a columnist for
UniSphere magazine.  On the World Wide Web, the URL is:

    http://www.cc.gatech.edu/services/unisys-folklore/

    http://www.unite.org/

You might possibly benefit by navigating the support maze via:

    http://www.service.unisys.com/language/english/html/public/othersit.html

It also may be amusing to look at

    http://www.unisys.com/

(The Unisys Web sites are so heavily graphical that it is completely useless
to try to view the pages via Lynx.  Netscape Navigator works, if you can wait
for the numerous 94-Kbyte GIF and JPEG image maps to be transmitted to you.
Perhaps Unisys is hoping to sell you high-speed networking equipment?)

Archival information on the Burroughs Corporation is available from
the Charles Babbage Institute; see this URL:

    http://www.cbi.umn.edu/burros/burros.htm

The eastern chapter of UNITE also created:

    http://members.aol.com/eunite/index.html
    <eunite@aol.com>


 `.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`

Convergent Technologies, a pioneering maker of networked workstations,
was absorbed by Unisys, and the CTOS products seem to have ended up in
the Unisys Payment Systems Division.  If you have Convergent questions, 
you could ask them by email to

    <paymtsys@po1.pl.unisys.com>

I have no idea if you'll get an answer.


 //////////////////////////////////////////////////////////////////////////////

1995

A division of Attachmate Corporation makes products emulating Unisys
terminals.

[Unisys, if you didn't hear, was formed from the merger of Burroughs
Corporation and Sperry Univac.  Attachmate is similarly the result
of vendor mergers: KEA Systems and Digital Communications Associates
(DCA) are two of the predecessors.]

Terminal emulators include InterCom. for Unisys T27 emulation
(available for Windows, Macintosh, DOS, and UNIX), and PEP for UTS
20/40/60 emulation (available for Windows, Macintosh, DOS, and UNIX).

For information about product part numbers and suggested retail
prices, telephone the Attachmate Unisys Division at +1 513/745-0500.
(This office is in Cincinnati, Ohio.)

     1997:  http://www.attachmate.com/unisys/

     1998:  http://www.atm.com/Unisys/C2208p.asp

The main contact point for other Attachmate products is

    Attachmate Corporation
    3617  131st Ave SE
    Bellevue, WA  98006
    voice: +1 206/644-4010
     WATS:    800/426-6283
    
      URL:  http://www.atm.com/

 //////////////////////////////////////////////////////////////////////////////

Path: cs.utk.edu!stc06.ctd.ornl.gov!fnnews.fnal.gov!mp.cs.niu.edu
      !vixen.cso.uiuc.edu!uwm.edu!msunews!talberg
From: talberg@cps.msu.edu (Jeffrey P Talberg)
Newsgroups: comp.terminals
Subject: Unisys terminal emulation on Web
Date: 20 Jul 1995 17:25:03 GMT
Organization: Michigan State University
Message-ID: <3um3hf$e2d@msunews.cl.msu.edu>

Core Technology is pleased to announce its presence on the World Wide Web.

Core Technology has been in the Unisys business for over fourteen years and
has offered "best of breed" terminal emulation and file transfer (FileSWEEP)
products for the A and V series mainframes on Windows, DOS, and Macintosh
platforms.

Core Technology recently announced the availability of a break-through 
offering called MultiBridge.  MultiBridge is a gateway offering based on 
Novel's IPX/SPX protocol.  It allows for a choice of multiple high-speed
protocols.  MultiBridge also eliminates the need for NetBIOS, which frees
users to run multiple platforms on a gateway.

We invite all to come visit us at this URL:

    http://www.ctc-core.com/

    Core Technology Corporation
    7435 WestShire Dr.
    Lansing, MI 48917

    Phone: +1 517/627-1521
            1-800/338-2117

    Email:  <sales@ctc-core.com>

    Demand fax: +1 517/627-8866

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
From: Tom O. Smith <tosmith@mich.com>
Subject: Re: Telnet for A series UNISYS system
Date: 22 Mar 1996 14:06:37 GMT
Organization: Virtual Soft Inc.
Message-ID: <4iuc5d$6be@server3.mich.com>

In article 3151A41E.79B9@mich.com,
        Terence Conklin <conklin@mich.com> said:
>
> For what it's worth, Virtual Soft's PCLink! for Windows includes
> WINSOCK Telnet support
> and a number of DEC VTxxx emulations, besides its T-27 emulation
> and TCP for Unisys (Burroughs) A-series, as part of the base product.
> A visual FTP client is also included (something like File
> Manager.)   A number of sites use PCLink! as a single package to
> access their A-series and Unix systems.
>
> While 3270 emulation is also included, I haven't tried using it
> over Telnet, and I doubt it would have the same functionality as
> TN3270 (the Telnet3270 spec) though I haven't read through that spec.
>
> Terence Conklin
> Conklin Systems
> conklin@mich.com


For more information on "PCLink! for Windows", please call Virtual
Technologies, Inc. at +1 810/853-6000 or just browse on the Web:

    http://www.virtualgrp.com/

    The Virtual Group
    2950 Waterview Drive
    Rochester Hills, Michigan 48309  USA
     voice: +1 810/853-6000
       fax: +1 810/853-6248 
    e-mail: <info@virtualgrp.com>



 `.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`

Another Unisys connectivity/terminal-emulation vendor:

Quickware
(in Arizona?)
office hours 8:30 - 4:30 Mountain time
e-mail: <qw@amug.org>
 voice:  1-800/375-3148
   fax: +1 602/678-6977  


 //////////////////////////////////////////////////////////////////////////////

Path: cs.utk.edu!stc06.ctd.ornl.gov!fnnews.fnal.gov!usenet.eel.ufl.edu
      !newsfeed.internetmci.com!swrinde!cs.utexas.edu!bcm.tmc.edu
      !crick.ssctr.bcm.tmc.edu!rick
From: rick@crick.ssctr.bcm.tmc.edu (Richard H. Miller)
Newsgroups: comp.terminals,comp.misc,comp.sys.misc,comp.sys.unisys,alt.geek
Subject: Re: Help! IDENTIFY Sperry UTS-30 Terminal?
Followup-To: comp.terminals,comp.misc,comp.sys.misc,comp.sys.unisys,alt.geek
Date: 21 Nov 1995 16:41:26 GMT
Organization: Baylor College of Medicine, Houston, Tx
Distribution: world
Message-ID: <48svfm$lds@gazette.bcm.tmc.edu>
References: <48rtqs$3v4@server1.oxford.net>


Rob M. VanHooren (rob@oxford.net) wrote:
: Greetings!

: I've just had 1/2 dozen of the following fall from the sky into my
: lab, and as it happens, they have not the required paperwork (auughh!)

: I would like to connect these to either (or both of) a DEC microVAX
: (old - about the size of a refrigerator, also inheirited, and in to
: process of being properly identified as well) or an intel box running
: Linux, SCO, or QNX (whichever I feel most happy with, as I am
: evaluating the 3 of them concurrently -- and then must decide on
: either Ultrix or VMS for the uVAX).  Hrrrumph.


Sorry, they will do you no good unless you have a Unisys DCP (or GCS/CTMC)
since they are synchronous terminals using the Uniscope protocol. They will
not work with an asynch system.


--
Richard H. Miller                 Email: rick@bcm.tmc.edu
Technical Projects, Lead          Voice: (713)798-3532
Baylor College of Medicine        US Mail: One Baylor Plaza, MEDT1103
                                           Houston, Texas 77030

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals,comp.misc,comp.sys.misc,comp.sys.unisys,alt.geek
Path: cs.utk.edu!stc06.ctd.ornl.gov!fnnews.fnal.gov!muir.math.niu.edu
      !mp.cs.niu.edu!vixen.cso.uiuc.edu!uwm.edu!lll-winken.llnl.gov!hookup
      !news.mathworks.com!news.kei.com!simtel!torn!fonorola!news1.fonorola.net
      !server1.oxford.net!usenet
From: rob@oxford.net (Rob M. VanHooren)
Subject: Help! IDENTIFY Sperry UTS-30 Terminal?
Date: Tue, 21 Nov 1995 06:54:55 GMT
Organization: QSR Consulting
Message-ID: <48rtqs$3v4@server1.oxford.net>
NNTP-Posting-Host: burgessville-106.oxford.net
Keywords: IDENTIFY SPERRY TERMINAL HELP

Greetings!

I've just had 1/2 dozen of the following fall from the sky into my
lab, and as it happens, they have not the required paperwork (auughh!)

I would like to connect these to either (or both of) a DEC microVAX
(old - about the size of a refrigerator, also inheirited, and in to
process of being properly identified as well) or an intel box running
Linux, SCO, or QNX (whichever I feel most happy with, as I am
evaluating the 3 of them concurrently -- and then must decide on
either Ultrix or VMS for the uVAX).  Hrrrumph.

Please be kind and aid this unfortunate human with a proper
identification and whatever specs you might be able to reliably
imagine.  Each unit has 2 parts: a video screen, and keyboard.

There are ports on the rear of the video unit for the keyboard
connection (9-pin, a la atari-2600 joystick), one marked J5
Peripheral, which I assume is for a printer (DB-25) and J6
Communication (DB-25), which I assume is for a serial link to the
intended host.  

Green monochrome character terminal, 80x24 +2 fixed status lines at
the bottom.  Lower right-hand side indicates "Sperry UTS 30".  Tags on
the underside declare the following:

Video unit:
	FCO Status Record Type / Feature 3575-01 Serial 18230
	Built by Gene 09/84
	Feature Selection Label		Type #357599000
	CS	/	NXXXX
	C		3381-00				Keyboard unit:		FT18
	C		4084-00				55-03047-053	7/86
	F		3980-00				2836974-25
	F		3981-00				F4725-25
	F		3988-00
	F		3982-00
	F		3991-00
	F		8217-01
	
Once powered on, the display indicates the following on the 24th
display line (note <tc>= triangular-shaped character):
	
	<tr> UNISCOPE MODE (F3991-00)   READY  - 3R3E 00 <tr>

25th line is a row of dots, which I assume are delimiting the terminal
area.  Beginning at the left margin of the 26th line is 

		1 ROW-01 COL=01

which changes accordingly as I move the box-shaped cursor (which has a
diagonal line through it, as opposed to being solid inverse-green)
around the screen.

Other questions:  how might I identify if the communications port is
synchronous (in which case I believe I would be knackered?).  Is there
a key-sequence to enter some sort of configuration mode on the unit to
specify terminal settings?  Any information at all would be helpful,
really.  And if you happen to be responding to this because you have
one (or more) of these beasties, I'll repay you with a keyboard for
them, since I have 6 extra with the lot.

Sperry, I understand, merged with Unisys some time ago, and their
telephone girl didn't seem to be of much help in deciding where to
send me for help.

Thank you kindly for any assistance you may be able to render.
It would be most advantageous for you to follow-up via e-mail to
rob@oxford.net in addition to a posting here.

Kind regards,
				Rob M. VanHooren
				Ontario, Canada.


 //////////////////////////////////////////////////////////////////////////////


Newsgroups: comp.terminals,comp.misc,comp.sys.misc,comp.sys.unisys,alt.geek
Path: cs.utk.edu!gatech!europa.chnt.gtegsc.com!news.kreonet.re.kr
     !usenet.seri.re.kr!news.dacom.co.kr!newsfeed.internetmci.com
     !news-feed.mci.newscorp.com!news.delphi.com!usenet
From: lwilton@BIX.com (Loren Wilton)
Subject: Re: Help! IDENTIFY Sperry UTS-30 Terminal?
Date: 22 Nov 1995 04:14:50 GMT
Organization: Delphi Internet Services Corporation
Lines: 41
Message-ID: <48u83q$rok@news1.delphi.com>
References: <48rtqs$3v4@server1.oxford.net>
Reply-To: lwilton@BIX.com (Loren Wilton)
NNTP-Posting-Host: bix.com
X-Newsreader: NetBix 1.225
X-Newsreader-Author: lwilton@BIX.com (Loren Wilton)


Well, I'm from the Burroughs side of the house, but I fooled with Sperry
terminals for a while so I will give some of the basics a shot.

The thing is a "Sperry Uniscope Terminal" that speaks Uniscope protocol.
This is a polled, block-mode protocol.  The host sends out a terminal address
with "do you have anything interesting" and the terminal responds with "no",
or a whole boatload of data.  In general the terminal sends all the characters
to the right of the last one of those little triangular characters, up to
*and including* the character currently under the cursor.  Lacking any of the
field separators on the screen, it sends from the first character to the
cursor.

Unless there is a configurable "tty mode" (which I kinda doubt on a UTS-30,
you can't make it send one character at a time, as you are used to with
VT-100 terminals.

Uniscope protocol was typically a sync protocol, often at 9600 baud.  The
baud rate will be configurable in some way, and sync/async *may* be
configurable, or may require a hardware option.  There is a mode configuration
page where many of the options are set, but I forget how to get to it at
the moment.  Others will doubtless tell you how.

I believe the "1" at the front of the status line display is telling you
the page number that is visible.  These terminals often were configured
with two pages that could be displayed.  Each page had its own terminal
address (unlike Burroughs TD series terminals).  Typically, the first page
was used for terminal session data, and the second page was used for data
sent to the attached printer, although this was by convention and it could
be used just like the first page.

You should be able to order a manual for at least a UTS-40 from literature
distribution.  While some of the details will be different, it will give
you the basic operating characteristics of the box.  I believe that it also
describes Uniscope protocol and the rather odd pinout on that DB-25
datacomm connector; but that may have been in another manual.  Unfortunately
all my Sperry DCP info is packed in a box where I can't get to it easily.

Hope some of that helps.  (Also hope I didn't tell you any lies!)

	Loren

 //////////////////////////////////////////////////////////////////////////////
	
Newsgroups: comp.sys.unisys
Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!cs.utexas.edu
      !howland.erols.net!newsfeed.internetmci.com!eanews1!plnews.pl.unisys.com
Date: 2 Oct 1996 14:13:47 GMT
From: ColinZealley@unn.unisys.com (Colin Zealley)
Organization: Unisys UK
Message-ID: <52ttar$avh@mail.pl.unisys.com>
References: <51tvig$7h5@mail.pl.unisys.com> <324B53E7.33F0@tannasen.pp.se>
Subject: Re: UTS Terminal definition wanted

In article <324B53E7.33F0@tannasen.pp.se>, tornkvist@tannasen.pp.se says...
>
> Dear Colin,
> My problem are two: first I do not know anything about the UTS20
> definitions and second I need to interface an application (expand a
> source) to an existing UTS host.
> Detlef.

Detlef,

      in separate response thread,Ron Smith & Keith Stone gave you some good
info about UTS. Your post talks of an "existing UTS Host" - what do you mean?
Are you trying to use a UTS terminal to talk to a Unix box? The other thread
suggests that.

A thought occurs to me. The terminal in question wouldn't be a UTS-10, would
it? If I remember rightly, that was Sperry's first attempt at an Asynchronous
terminal, and strictly speaking was NOT a UTS in the normal sense of the term
at all. If that's what it is, it's probably pretty close to a basic VT-style
ASCII terminal. Also, I think the UTS-30 intelligent terminal could be
persuaded to behave like an async terminal if you hooked the comms line to the
printer port and used the "Print" key instead of the "Transmit" key.

But all other UTS terminals use a Synchronous comms discipline (called
"Uniscope protocol" after the earliest terminals that handled it) which would
be humongously difficult to handle from an async machine.

The emulators that Ron and Keith speak of are to make a PC (or other
intelligent workstation) appear to be a UTS terminal, but are specifically and
only intended for use where the eventual host is a 2200 (or other ex-Sperry
machine). In most cases, these emulators no longer even use the original
Uniscope hardware connection wires (long outdated), but go over TCP/IP or some
such instead, thus embedding the screen control part of Uniscope protocol into
a completely different messaging envelope.

I hope this is some use to you; feel free to email me for more if you wish. I
did once write a "reverse emulator" for a Uniscope on the 2200, using CS-1100,
so I had to delve quite deeply into this area.

--
Colin V Zealley of Unisys UK - via Unisys Lotus Notes network or ...
SMTP:ColinZealley@unn.unisys.com
Unisys pays me, but the opinions are mine.


 //////////////////////////////////////////////////////////////////////////////

Newsgroups:   comp.sys.unisys
From:         "Ronald Q. Smith" <rqs1@rsvl.unisys.com>
Date:         1996/09/20
Message-Id:   <01bba721$26215a60$7feb3dc0@rqs1>
Sender:       news@rsvl.unisys.com (News Admin)
References:   <3240EDC5.6B0E@tannasen.pp.se>
Organization: Unisys - Roseville, MN
Subject:      Re: UTS Terminal definition wanted


UTS terminals cannot simply be entered in a Unix definition file.  They use
a polling protocol and sophisticated screen handling with features quite
different from those in DEC VTxxx type terminals (not necessarily better,
just different).  It is most like an IBM 3270 running in block mode.

The UTS terminal protocol is really a 1972 version of the ANSI standard
block mode terminal, but no one else ever implemented it.

There are UTS terminal emulator products available for Windows and most
Unix platforms from Attachmate and other companies.

-- 
Ron Smith
Unisys
Roseville, MN

 //////////////////////////////////////////////////////////////////////////////

Newsgroups:   comp.sys.unisys
From:         "Ronald Q. Smith" <rqs1@rsvl.unisys.com>
Date:         1996/09/27
Message-Id:   <01bbac77$c19fc660$7feb3dc0@rqs1>
Sender:       news@rsvl.unisys.com (News Admin)
References:   <3240EDC5.6B0E@tannasen.pp.se>
              <01bba721$26215a60$7feb3dc0@rqs1> <324B5932.E21@tannasen.pp.se>
Subject:      Re: UTS Terminal definition wanted

Detlef Scholle <tornkvist@tannasen.pp.se> wrote in article
<324B5932.E21@tannasen.pp.se>...
>
> thank you. I did hope for a VTxxx type ... It seems to be harder to solve
> now. But the emulators products are probobly not solving my problem. I 
> still think that I need to write a C-source. Is the documentation available? 
>
> What do you mean with ..."1972 version of the ANSI"... ..."noone has ever
> implemented it."? Are the emulator products not any implementation?
> Detlef.


There is an older manual that provided the full UTS protocol stack
including screen formatting.  A complete implementation in C would be
50,000+ lines of code.  Hopefully, your problem is small enough that you
only need to implement a subset.

The manual is UP-10683 Rev. 1 published in 1988.  The title is "Uniscope
Protocol Reference Manual."  See your Unisys representative and ask to
order a copy of UP-10683.R1.

-- 
Ron Smith --  Unisys --  Roseville, MN

 //////////////////////////////////////////////////////////////////////////////

Newsgroups:   comp.sys.unisys
Subject:      Re: UTS Terminal definition wanted
From:         Tom Sherren <tps@rsvl.unisys.com>
Date:         2 Oct 1996
Message-Id:   <3252C13C.348C@rsvl.unisys.com>
References:   <51tvig$7h5@mail.pl.unisys.com> <324B53E7.33F0@tannasen.pp.se>
              <52ttar$avh@mail.pl.unisys.com>

Per all the following regarding UTS emulation...   Doesn't/didn't the
IS6000 product for Unix include an "inverted Uniscope" handler (i.e. a
Unix program callable UTS emulator?  

-------------------------------
Tom Sherren
Unisys Corporation
LINC Engineering, Roseville, MN
1 612 635 6353              USA
-------------------------------

 //////////////////////////////////////////////////////////////////////////////


Newsgroups: comp.sys.unisys
Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!cs.utexas.edu
      !howland.erols.net!newsserver.jvnc.net!netnews.sbphrd.com!campbejr
Date: 3 Oct 1996 17:58:53 GMT
From: campbejr@phu989.mms.sbphrd.com (John R. Campbell)
Organization: SmithKline Beecham Pharmaceuticals Research & Development
Message-ID: <slrn4557vmt.8he.campbejr@phu989.mms.sbphrd.com>
References: <51tvig$7h5@mail.pl.unisys.com> <324B53E7.33F0@tannasen.pp.se>
            <52ttar$avh@mail.pl.unisys.com> <32535E62.25DD@tannasen.pp.se>
Subject: Re: UTS Terminal definition wanted


Detlef Scholle <tornkvist@tannasen.pp.se> wrote:
>
> I'm sorry that I haven't been clear.
>
> <snip>
>
> Now, the problem is that I don't now how to communicate with the Unisys
> system. The controller computer is an Unix-based PC (QNX, a realtime
> POSIX OS). If I only could do a RLOGIN without getting a lot of rubbish
> on my screen? That would be something to start with.
>
> What I think I need, is to emulate the Uniscope protocol.


No, what you need is the ability to emulate the *screen commands* of the
UniScope terminal.  You don't need to worry about syncs and all, you're
concerned with cursor motion, protect/unprotect, SOEs and FCCs.

That's pretty well documented in the UTS books.  I'd be surprised if
there isn't a "gateway" that maps all of that good stuff to a VT-100-ish
protocol.  (Though I doubt a "real" vt-100 has enough intelligence to
fake the UniScope's features without a *lot* of intelligence in between.)

Mind you, QNX is gonna be a big pain with this.  I hope you've coughed up
enough cash for their compiler ('cause you ain't gonna have a choice!).

-- 
John R. Campbell, Speaker to Machines, Resident Heckler          soup@jtan.com
 

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys,comp.terminals,comp.dcom.servers
Path: cs.utk.edu!news.msfc.nasa.gov!newsfeed.internetmci.com!in1.uu.net
     !psinntp!psinntp!psinntp!psinntp!bbnews1!eanews1!plnews.pl.unisys.com!news
From: Yves Gaffarel <yvesgaffarel@unn.unisys.com>
Subject: Re: Modem Sharing Problem
Date: Mon, 11 Mar 1996 12:23:27 -0800
Organization: YG
Lines: 53
Message-ID: <31448BBF.4585@unn.unisys.com>
References: <4hmjkg$qb2@insosf1.netins.net>
NNTP-Posting-Host: 129.227.66.47
To: rechristian@netins.net
CC: yvesgaffarel@unn.unisys.com

rechristian@netins.net wrote:
> 
> I have recently been put in charge of maintaing a system which uses
> the following:
> 
> Newbridge RS-232 Termination Unit MainStreet 2601
> RAD Modem Sharing Device (MSD)
> Unisys SVT1120 & UT200-1 Terminals
> 
> This system is a SYNCHRONOUS enviroment for the distribution of a
> state & federal law enforcement information network.
> 
> The problem we are having is that when ever we plug more than 3
> terminals into the MSD the terminals on the MSD "POLL" at an EXTREMELY
> SLOW RATE or brings the entire system down.
> 
> The system is fed on a DEDICATED 4 WIRE LEASED LINE. Two circuits on
> the pair. One pair feeds a terminal on PORT A of the Newbridge, Port B
> is fed to the MSD. Port B goes down when more than 3 terminals are
> used. Port A is unaffected by the problems on Port B.
> 
> One terminal on the MSD is about 150ft from the MSD, but even plugging
> in a local 4th terminal brings down the system.
> 
> Changing MSD's did not cure the problem.
> 
> We would like to find a different MSD or other solution to the problem
> so we can add the additional terminals we need without unplugging and
> plugging in different cables at different time periods.
> 
> Suggestions on curing this problem greatly appreciated.
> 
> Thanks in advance.


Are you running a 2200 ?  I do not know what is an SVT1120, but if it is
a Uniscope type terminal, I suggest to check how they are configured on
the host or DCP side : are they configured as "multidrop" (I if
remember the word correctly) ?  I believe they should be, as the MSD
is probably not aware of the Uniscope protocol...

You have two ways to configure several drops of Uniscope terminals,
depending on how they are connected.

If they are connected via a Multiplexor aware of the Uniscope
protocol, the Mux will help the host or the DCP, and you must
configure the host or DCP so that it is aware of that.  if the MSD
does not have that capability and the host expects the MSD do have it,
I expects problems.


-- 
Yves Gaffarel
Brussels, Belgium
mailto:yvesgaffarel@unn.unisys.com
X.400 : c=US, a=ATTMAIL, p=UNISYS, o=BE, ou=everpo1, s=GaffareY
The opinions expressed are personal and are not the opinions of any
organisation.


 //////////////////////////////////////////////////////////////////////////////

From: Paul Parrish <pparrish@atlanta.com>
Newsgroups: comp.sys.unisys
Subject: Re: CTOS discusion?
Date: Wed, 03 Apr 1996 09:01:33 -0500
Organization: Internet Atlanta
Lines: 38
Message-ID: <316284BD.3A8B@atlanta.com>

Randall Gellens wrote:
>
> In article <31600111.334943062@news.cityscape.co.uk>,
> dclairet@cityscape.co.uk says...
> >
> >Will Sappington <102040.3001@CompuServe.COM> wrote:
> >
> >>Is there any discussion of CTOS in this group?  If not, where?
>
> I have a CTOS question:
>
> Assume there is a Mac and a B39.  Say the Mac has built-in 10-Base-T and
> AAUI-15 Ethernet connectors, and has TCP/IP software installed (PPP works).
> Say there was an Ethernet slice for the B39 available.  If I wanted to use
> TCP/IP between them, how hard would that be?  What software would be needed
> on the CTOS side?  Would extra hardware (a hub?) be needed?


We use a B39 with TCP/IP in our network, however, we have no Mac
machines.  We do have Unisys U6000(UNIX), Sun, Linux, Windows NT, and
DOS/Windows machines and they all communicate well with the B39. We
use the Ethernet slice product (B25-EN3) with a tranceiver connected
via coax.  The software products we use are the Unisys
TCP/IP(NP25-TCP) and IDMSS(MB25-IDM--required to run the slice)
packages.  The TCP product comes with the usual utilities such as FTP,
Telnet, etc.  We have also tried the Unisys NFS package.  This worked
OK on CTOS-III but was not supported on the older BTOS O/S where we
really needed it.  The TCP/IP stuff worked on both O/S versions.
While the performance of the B39/TCP setup doesn't compare to the
other machines on the network, it gets the job done for us.

From what I've been told, there are better performance software
products out there.  An outfit called Sirus Systems (+1-804/733-7944)
has TCP/IP & NFS products for CTOS which they claim outperform the
Unisys offering.  However, my guess is that it's the Ethernet slice
configuration more than the software which is the culprit.  I know,
it's a 386--what do I expect?

I hope this helps. Good Luck!

Paul


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Path: cs.utk.edu!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu
      !newsfeed.internetmci.com!news2.cais.net!news.cais.net!usenet.seri.re.kr
      !news.imnet.ad.jp!news.join.ad.jp!wnoc-t
yo-news!unisysgw.unisys.co.jp!usenet
From: tomo@tdc.unisys.co.jp (Tomo Muramatsu)
Subject: Re: Telnet VT Emulator
Date: 8 May 1996 10:04:24 GMT
Organization: Nihon Unisys, Ltd., Tokyo Bay Deveropment Center
Message-ID: <4mprj8$n2r@lakshmi.tdc.unisys.co.jp>
References: <318758D8.1812@ccm.tdsnet.com>

Michael Klingensmith (OzarkLad@ccm.tdsnet.com) wrote:
>
> I am trying to determine if there is a program that will convert between
> a UTS terminal and VT terminal emulations.  In a nutshell, what I'm
> looking for is a way to telnet to a 2200 from a Unix system and have
> sufficient code translations to display full-screen displays (ie: IPF,
> DPS, custom).

> Any hints would be appreciated.

Please contact an Unisys person and ask about IS-6000 (a product
works on U6000 series).

I'm sorry I don't know IS-6000 well.

> --
> O-
> http://users.aol.com/ladozark


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!spool.mu.edu
  !usenet.eel.ufl.edu!bofh.dot!newsfeed.internetmci.com!ionews.ionet.net!usenet
Date: Thu, 06 Jun 1996 08:04:39 -0500
Organization: Hertz WorldWide Reservation Center
Message-ID: <31B6D767.7270@hertz.net>
From: John Bolene <jbolene@hertz.net>
Subject: Asych to UTS converter version 1R1J


To all those who have sent me mail on this subject--it was easier to
reply to the newsgroup.

The product is 9635-01 for DCP5/200, 9635-00 for all other models.

It is a DCP product that allows a DEC VT100 dial-in terminal to use
full-screen UTS products; the drawback is it is difficult to print the
screens due to the VT100 control codes.  Refer to document Software
Release Document for DCP Series Level 6R1A number 7441 0887-100.  This
product has been around for a number of years and has not changed.

John Bolene
jbolene@hertz.net

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!hookup
      !nntp-hub2.barrnet.net!news.sprintlink.net!news-peer.sprintlink.net
      !howland.erols.net!feed1.news.erols.com!uunet!news-in2.uu.net
      !nntp.crl.com!news3.crl.com!nexp.crl.com!usenet
From: "Rmcg" <95mar5@apc.net>
Date: 17 Oct 1996 03:45:11 GMT
Message-ID: <01bbbbdd$27989c20$4eb071cf@95mar5.apc.net>
References: <325EF6D9.5A27@nz.eds.com>
Lines: 5
Subject: Re: TCP/IP on DCP networks

Contact Ascom Timeplex.  They used to be owned by Unisys, and developed
communication abilities of Uniscope protocol, as well as Burroughs 
poll-select over x.25.  Uniscope requires a front-end PAD to translate the
address at each end, but it can be done.


    http://www.timeplex.com

    Ascom Timeplex
    North American Headquarters
    400 Chestnut Ridge Road
    Woodcliff Lake, New Jersey 07675

    voice WATS:  1-800/669-2298
    voice POTS: +1 201/391-1111

    Ascom Timeplex
    Europe/Africa/Middle East Headquarters
    Langley Business Centre
    Station Road, Langley
    Slough, Berkshire SL3 8DT
    United Kingdom
         voice: +44 0 1753 601000


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!spool.mu.edu
  !howland.erols.net!newsfeed.internetmci.com!eanews1!plnews.pl.unisys.com!news
From: Mike Muncey <mmuncey@po3.mv.unisys.com>
Date: 14 Oct 1996 23:06:15 GMT
Organization: Unisys Corporation
Message-ID: <53uh17$618@mail.pl.unisys.com>
Lines: 40
Subject: Re: TN3270 to A-Series

Chris Reed <creed@netcom.com> writes:

> Do you know the marketing style?  I have to plead with the salesman to
> buy what we need.

I have talked with my program manager who is getting the definative
answer.  From *memory*, we believe the style is "99MT".  This is the
SNA Envoy "MT" emulator for 3270 connections.


> The manual implies that one needs the ENVOY product.  Is this the same
> ENVOY product
> that is used with the SNA version on the CP2K?  Where does this fit?

This is an *updated part* of the SNA Envoy product.

When we introduced TN3270,
we created a style so that you can just order the MT Emulator for
Telnet TN3270.  SNA Envoy can use the updated MTE2, but Telnet
*requires* the updated MTE2 to work.

Telnet (in DSSSUPPORT) links BYFUNCTION to MTE2SUPPORT.  Appliction
output in received by Telnet.  Telnet then calls MTE2 to "translate"
to 3270.  The result is then written to the Port.  Client input is buffered by
Telnet until EOR.  MTE2 is called to "translate" to MT.  The result is
then sent to COMS (or whatever MCS the dialog is established to).

> Let me explain the whole situation.
>
> I am providing system support for a client that is using the Attachmate
> Extra 3270
> emulator.  To get to the A-11, they telnet (TN3270) to an IBM box.  They
> next use an SNA connection to the A which is running PU2/PU5 on the
> CP2K.  A-series is running ENVOY.
>
> We have had cases where the IBM net is down.  I have suggested that the
> users can telnet directly to the A.

This seems reasonable.


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Path: utkcs2!stc06.ctd.ornl.gov!news.he.net!uwm.edu!news-peer.gsl.net
      !howland.erols.net!newsfeed.internetmci.com!news-was.dfn.de
      !news-fra1.dfn.de!news-ge.switch.ch!news-zh.switch.ch
      !ubnnews.unisource.ch!193.223.116.4!193.223.112.132
Organization: RBA-Service
Message-ID: <01bc63bd$1b2e9e20$8470dfc1@wrba-ric-1365a>
References: <01bc5ed0$c9009b80$6d2ad7cd@selmonod.nsainc.com>
Date: 18 May 97 18:54:02 GMT
From: "Erwin Richard" <Erwin.Richard@service.rba.ch>
Subject: Re: UTS emualtors

Tony,

Not satisfied with products available on the market and with the need to
communicate from Windows NT Servers to OS2200 TIP sessions, I decided to
write an UTS emulator myself.

Currently the program consists of a DLL that implements the INT1 protocol,
a OCX that provides UTS terminal functionality and a Container Application
that allows to call the OCX standallone.

Current features are:

Limited emulation of UTS400 UTS20 and UTS40 terminals. Connects over TCP to
HLC and DCP but only to TIP applications.

At our company we use this tool to connect our TIP users, wich is the wast
majority. We still use Infoconnect or simple Telnet for Demand sessions.

I tried to make the emulation as simple as possible. That is: No remappable
Keyboard, no customizable toolbars or scripting language, no complicated
setup etc.

But because of the Emulation built in an OCX (nowadays called ActiveX
control), its fairly easy to write a container app around the OCX, that
provides specific features for the application environment.

drop me a line, if you are interested in a copy.


   a <selmonod@nsainc.com> schrieb im Beitrag
   <01bc5ed0$c9009b80$6d2ad7cd@selmonod.nsainc.com>...
>
> Hi all,
>
> I was wondering if anyone could tell me if there were any companies that
> provided UTS 20, UTS 30, UTS 40, UTS 60 emulation. I'm looking to OEM this
> product. If anyone knows who I can call, please let me know.
>
> Thanks In Advance!
>
> Tony Frame
> Network Software Associates, Inc.
> Vox: 703-875-0444
> Fax: 703-875-0451
> Email: <framet@nsainc.com>
>

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Organization: ProLog a PenTeleData, Inc Service
Message-ID: <33FCA152.96E6C9B4@theeddy.com>
Date: Thu, 21 Aug 1997 16:13:06 -0400
From: Larry Glamb <lglamb@theeddy.com>
Subject: Re: B38 and B25 Differences??
 
Pete wrote:
 
> I need some help if anyone can help...
>
> Are there any differences between the B25 and B38 keyboard and keyboard
> scancodes...
> I am trying to wedge a scanner thorugh the keyboard; the present scanner
> I got is B25 compatible (I have to buy a cable) so I want to know if
> this is going to work on a B36.
> Also are the keyboards the same?
>
> Pete
 
B25 was used as a generic prefix for peripherals compatable with all the
NGEN line (except possibly B27).   There were various flavors of
keyboards but they were generally designated in a suffix.
 
-- 
Later mode,
 
Larry Glamb (lGlamb@TheEddy.com)   http://www.theeddy.com/sabrina

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Organization: Unisys Mission Viejo, CA
Message-ID: <GJXS34010E646B@mpa15c.mv.unisys.com>
Date: Thu, 21 Aug 1997 16:34:01 -0700
From: Phil Wilson <PDW@mpa15c.mv.unisys.com>
Subject: Re: Java VM
 
On the subject of Java applets and MCP systems: There is a product
called NX/Webstation for Java that is a Java implementation of an MT
emulator.  You connect (with your browser) to your ClearPath NX running
NX/Webserver, load a page containing the applet and get an MT emulator
to access MARC, CANDE and other COMS windows.  Using CANDE from Netscape
is quite an interesting juxtaposition of software to actually see in
front of you.
 
      Phil Wilson        MV, Room B131, x6324
                         Mail stop 320

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Path: transfer.stratus.com!bigboote.WPI.EDU!cam-news-feed2.bbnplanet.com
    !cam-news-hub1.bbnplanet.com!news.bbnplanet.com!news.mathworks.com
    !gatech!128.186.6.106.MISMATCH!news.fsu.edu!nntp.cntfl.com!polaris.net!news
Date: 10 Oct 1997 01:45:15 GMT
Organization: Polaris Networking
Message-ID: <61k1bb$e1u@nexus.polaris.net>
References: <34364035.7940@mail.datasys.net>
From: waters@polaris.net (Jonathan Waters)
Subject: Re: STEP for windows

In article <34364035.7940@mail.datasys.net>,
  TIM AANONSEN <taanonsen@mail.datasys.net> says:
>
>I'm looking for a terminal emulator to run under MS_Windows 3.11
>
>I 'believe' the name of the product is 'STEP'
>
>Tim

STEP was a product from Master link for SPERRY UNIVAC (now Unisys) UTS20
UTS 40 and UTS 60 emulation

        Master Link was acquired by Computer Logics, who was acquired
by CHI, who was gobbled up by DCA (IRMA for IBM folks), who was gobbled
up by Attachmate.

        The product is still alive as "INFOCONNECT", from ICC
(Cincinnati, who was gobbled up and merged with CHI , etc.

 `.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`.`

Random report from an IRS contact:

The "tnUTE" terminal emulator (block mode over TCP/IP) is available
from PSC: for information, call +1 301/816-2555.


 //////////////////////////////////////////////////////////////////////////////

References: <380c52bb.92744014@news.wi.centuryinter.net>
    <7ue4th$2fr$1@samba.rahul.net> <g6OO3.17601$Bf6.213480@pm02news>
    <01HW.B4361E65020ED1D50409209F@news.talstar.com>
    <3811849C.FC483A73@rmi.net> <LEEQ3.15446$v11.16778@dfw-read.news.verio.net>
Date: Sun, 24 Oct 1999 20:00:02 -0400
Organization: TalStar Communications
Newsgroups: comp.sys.unisys
Message-ID: <01HW.B43915C102AE28B80409209F@news.talstar.com>
From: Edward Reid <edward@paleo.org>
Subject: Re: Battleship and Scrabble for CTOS?

On Sun, 24 Oct 1999 10:27:12 -0400, Ken McNeill wrote
> If I remember correctly, the TD850 (and wasn't there also a TD860?) was a
> color screen device.  Didn't that have something to do with the
> 'sloooownessss'?

At least one of them was B&W, and it was sloooooooooow. So slow that
Burroughs couldn't sell them, and resorted to supplying them as ODTs
instead. I was working for the State of Florida when Burroughs upgraded
our Conrac ODTs (I think they were still officially called SPOs). The
Conracs were horrible things with 40-character lines. We specified that
the upgrade consoles would not be TD860s, but Burroughs delivered
TD860s anyway.

On this terminal, if you put 24 CRs on the screen -- this was a time
when visible CRs were the norm -- all in column 1, and hit transmit, it
took the terminal about 4 seconds to analyze the screen and actually go
into transmit mode.

For this terminal used as an ODT, Burroughs implemented a system option
-- or perhaps it was a TERM option, I can't remember which, and it
seems to have been finally removed -- to send full-length lines, no
CRs, because the terminal was so slow to process CRs. It was quite
noticeably faster to send a full screen, without CRs.

The TD860 was also the subject of a CUBE Resolution -- submitted, if
memory serves, by Bob Dever -- which explicitly referred to it as a
boat anchor.

Edward Reid

 //////////////////////////////////////////////////////////////////////////////

Date: Mon, 25 Oct 1999 04:43:46 GMT
Organization: RoadRunner - TampaBay
Newsgroups: comp.sys.unisys
Message-ID: <6eRQ3.5121$24.67278@typhoon2.tampabay.rr.com>
From: Victor A. Garcia <vgarcia1@tampabay.rr.com>
Subject: Re: Battleship and Scrabble for CTOS?

The TD850 was B&W, or better say Black and Green, it was so slowwwww, that I
remember start a Clear/Start in a B1000, after that, turn on the SPO, the
B1000 was running, and the TD was still on selftest, so the system halt
because cannot find the SPO, wait for the count to finish, then hit start,
got it back, but it was annoying.

 //////////////////////////////////////////////////////////////////////////////

References: <380c52bb.92744014@news.wi.centuryinter.net>
    <7ue4th$2fr$1@samba.rahul.net> <g6OO3.17601$Bf6.213480@pm02news>
    <01HW.B4361E65020ED1D50409209F@news.talstar.com>
    <3811849C.FC483A73@rmi.net> <LEEQ3.15446$v11.16778@dfw-read.news.verio.net>
    <01HW.B43915C102AE28B80409209F@news.talstar.com>
Date: Sun, 24 Oct 1999 23:11:03 -0600
Organization: RMI.NET
Newsgroups: comp.sys.unisys
Message-ID: <3813E667.A1046FCD@rmi.net>
From: Louis Krupp <lkrupp@rmi.net>
Subject: Re: Battleship and Scrabble for CTOS?

Edward Reid wrote:
> I was working for the State of Florida when Burroughs upgraded
> our Conrac ODTs (I think they were still officially called SPOs).

The Conrac (I thought those went away with the B6700) was the successor
to the B5500's teletype, as I recall.  SPO stood for "Supervisory Print
Out" or something, but it was easier to say then "ODT" so it stuck.  We
(University of Denver) kept a bottle of Windex (tm) or something to
clean
the ODT's, and one of the operators labeled it "SPO-Brite."

Burroughs had an interesting line of CRT's.  Anybody else remember the
BIDS?  24x80 display, 1000 bytes of memory, fill those and it beeped a
lot.

> On this terminal, if you put 24 CRs on the screen -- this was a time
> when visible CRs were the norm -- all in column 1, and hit transmit, it
> took the terminal about 4 seconds to analyze the screen and actually go
> into transmit mode.
>
> For this terminal used as an ODT, Burroughs implemented a system option
> -- or perhaps it was a TERM option, I can't remember which, and it
> seems to have been finally removed -- to send full-length lines, no

> CRs, because the terminal was so slow to process CRs. It was quite
> noticeably faster to send a full screen, without CRs.

TERM FULLPAGE TRUE

> The TD860 was also the subject of a CUBE Resolution -- submitted, if
> memory serves, by Bob Dever -- which explicitly referred to it as a
> boat anchor.

The TD830 was nice.  I wonder what went wrong with the TD850, etc.

DU switched to VAXes about the time Burroughs (by then Unisys, I think)
came out with the successor to the TD series (CT's?).  There we were,
back to hardcopy operator terminals...

Louis Krupp

 //////////////////////////////////////////////////////////////////////////////


NNTP-Posting-Host: tr-raddatcj.tr.unisys.com
Date: Mon, 25 Oct 1999 09:37:41 -0400
Organization: ECDC Unisys Corp. Tredyffrin
Newsgroups: comp.sys.unisys
Message-ID: <7v1me0$i9m$1@trsvr.tr.unisys.com>
From: Curt Raddatz <curt.raddatz@ocsc.com>
Subject: Re: Battleship and Scrabble for CTOS?

Ah, yes.  The ET2000.  The most expensive terminal ever constructed! (IMHO)
I had someone actually give me one because he couldn't get it to do anything
useful.  After a period of time I gave up on it also and threw it in the
dumpster.  If I remember correctly they were like $4,000 or so and the only
ones that got sold were bundled as ODTs for other systems.

 //////////////////////////////////////////////////////////////////////////////

NNTP-Posting-Host: flux.talstar.com
References: <380c52bb.92744014@news.wi.centuryinter.net>
    <7ue4th$2fr$1@samba.rahul.net> <g6OO3.17601$Bf6.213480@pm02news>
    <01HW.B4361E65020ED1D50409209F@news.talstar.com>
    <3811849C.FC483A73@rmi.net> <LEEQ3.15446$v11.16778@dfw-read.news.verio.net>
    <01HW.B43915C102AE28B80409209F@news.talstar.com> <3813E667.A1046FCD@rmi.net>
Date: Mon, 25 Oct 1999 9:59:58 -0400
Organization: TalStar Communications
Newsgroups: comp.sys.unisys
Message-ID: <01HW.B439DA9E02DC66F201165F1F@news.talstar.com>
From: Edward Reid <edward@paleo.org>
Subject: Re: Battleship and Scrabble for CTOS?

On Mon, 25 Oct 1999 1:11:03 -0400, Louis Krupp wrote
> The Conrac (I thought those went away with the B6700) was the successor
> to the B5500's teletype, as I recall.

Yes, that was a B6700 I was talking about. Kept it long enough to
replace the Conracs. I was one of those wearing a black dot at the CUBE
conference in Phoenix when Burroughs announced the demise of the B6700.

> SPO stood for "Supervisory Print
> Out" or something, but it was easier to say then "ODT" so it stuck.

I think it was Supervisory Printer Output -- Print Out would be too
simple -- but hey. Funny thing is that Unisys has a new console called
SPO, except now it's Single Point Operations. It's been out a couple of
years at least, but I heard someone saying in Minneapolis that it still
doesn't really work with A-Series/NX/LX. Anyone using it? This is just
"heard in the hall"; I didn't get a chance to check it out. It's
certainly supposed to work with the A/NX/LX.

> We > (University of Denver) kept a bottle of Windex (tm) or something to
> clean
> the ODT's, and one of the operators labeled it "SPO-Brite."

I like it.

> Burroughs had an interesting line of CRT's.  Anybody else remember the
> BIDS?  24x80 display, 1000 bytes of memory, fill those and it beeped a
> lot.

Not only that, but you could put two screens on one 1KB controller,
giving 512 bytes per screen. However, that was "compressed": if the
message included tabs and CRs, they were stored in the display memory
and not expanded into spaces. Thus designing layouts to eliminate
extraneous spaces was important. Of course, COBOL wasn't good at
handling variable-length fields (COBOL85 is much better, but I'm
talking 1974, and that's real date 1974 not COBOL74). I took one
inquiry program that could not get all the standard information for the
reply in one screen and rewrote it in ALGOL, which could get it all 99%
of the time.

The BIDS had a beautiful display, better than anything since, because
the characters were actually drawn rather than bitmapped. Raster
technology won't match that until it reaches 300dpi.

> TERM FULLPAGE TRUE

Thanks for the reminder. Definitely not in the 45.1 System Commands
manual, so it's clearly been deimplemented.

> The TD830 was nice.  I wonder what went wrong with the TD850, etc.

I have no inside information, but that TD850 came along rather shortly
after the TD830. I suspect that they were both in development at the
same time, probably by different groups. Thus different managers and
different procedures, and also the TD850 didn't get evaluated against
the TD830 in time. Just guessing though.

> DU switched to VAXes about the time Burroughs (by then Unisys, I think)
> came out with the successor to the TD series (CT's?).

MT (for Modular Terminal).

Edward Reid

 //////////////////////////////////////////////////////////////////////////////

Reply-To: davetall@sprintmail.c0m
NNTP-Posting-Host: p-456.newsdawg.com
Date: Mon, 25 Oct 1999 16:54:09 GMT
Organization: http://extra.newsguy.com
Newsgroups: comp.sys.unisys
Message-ID: <38148ada.261202369@news.newsguy.com>
From: Dave Tall <davetall@sprintmail.c0m>
Subject: Re: Battleship and Scrabble for CTOS?

On Mon, 25 Oct 1999 09:30:53 +0100, "Colin Zealley"
<zippo@technologist.com> wrote:

>
>Dave Tall wrote in message <3811ddc1.85956352@news.newsguy.com>...
>[snip]
>>Rogue, IIRC, was an ALGOL port of the game Hack, which evolved into
>>Nethack and is still available on the net and played worldwide.
>
>Not quite. Maybe the other way round?
>
>Rogue is *the* old original game of this type, and was first available on
>Unix, written in c. If there was an ALGOL version of it for you stackhead
>types, that was presumably a manual rewrite since it would have predated the
>A Series c compiler by quite a few years. I used to play it on a Sperry
>5000/80 (I think) about 18 years or so ago.

>
>And just like Hack, Nethack, Moria, Angband, Omega, ut's on the PC now ...
>they're all available if you search the Web for "rogue-like games".

Yes, you're right.  I misstated the lineage.  Rogue is the original,
and this was a manual rewrite of that.  Rogue was known as Hack by the
time I became aware of the Large Systems port.

--------------------------
change c0m to com to reply


 //////////////////////////////////////////////////////////////////////////////


Date: 12 Nov 1999 00:53:04 EST
Newsgroups: comp.sys.unisys
Message-ID: <80ga00$o6m@chronicle.concentric.net>
From: Mark Foley <foleym@meftechno.com>
Subject: Attachmate InfoConnect IDK for screen scraper?


  My company has purchased the Attachmate InfoConnect IDK for Windows 32
bit.

  It has become my task to take this IDK and develop an application that is
essentially a screen scraper for a Unisys terminal emulation running on an
NT workstation. I'm
hoping that someone can point me in the write direction and get me started.
I have almost no
experience with terminal emulation or mainframes.

  First of all, all of the samples appear to be for the old style 16 bit
windows and messaging system.

  This platform is NT and I will be using Microsoft Visual C++.
Can anyone provide a sample C++ code blurb that demonstrates some IDK
functionality?

-  If I assume that the Terminal emulation is already in place and connected
to it's respective Host mainframe,  I would hope that my application is
capable of capturing Screen activity
as well as initiating screen updates.

- Is the library and DLL enough or do I need to have the InfoConnect
Manager running?


-  Functionally what is involved in this process? (Something like this...?)

  Determine and somehow connect to the active terminal emulation session.
  Catch and interpret datastream from session.
  Build datastream to update terminal emulation session.
  Send it..


  Thanks in advance!

 //////////////////////////////////////////////////////////////////////////////

Date: Fri, 12 Nov 1999 14:35:45 GMT
Newsgroups: comp.sys.unisys
Message-ID: <5BVW3.3281$H8.117427@typhoon2.kc.rr.com>
From: smyers <smyers@nospam.hotmail.com>
Subject: Re: Attachmate InfoConnect IDK for screen scraper?

Mark:

     I was formerly the Manager of Attachmate's Systems Engineers
(1991-1997) and used to work extensively on these products and kits. Unless
something has changed in the last 2 years (nothing I've heard would indicate
that) the information that I am providing should be accurate.

     First off, Attachmate offers 2 different development kits: IDK
(INFOConnect Developer's Kit) is actually a Unisys SKU and is the same
toolset that Attachmate uses to create the INFOConnect emulators (PEP and
InterCom). The other development kit is the ADK (Accessory Developers Kit).
The ADK is what you would typically use for screen scraping development.
Accessory comes from the framework that Attachmate uses to "plug in" various
emulators. When ICC and DCA merged in 1992 we noticed that Crosstalk had the
ability to become several different kinds of emulators, ICC took the
framework and adapted it for T27 and UTS functionality.

    If you are using the IDK, you will be in effect pulling the datastream
directly out of the communications module. Which means that you will have to
account for all of the various EOT and EOP and video characters inserted to
format the message for a screen. To do a simple screen scraping project, you
are dealing with a little bit of extra work AND have probably bought way
more than you needed. The methodology that you will employ is to launch
INFOConnect Manager, assign your application to a transport, begin listening
on the port, then start passing information back and forth (inserting all of
the screen code so that your mainframe application still thinks it's talking
to a terminal.

     With the ADK, you are in effect screen scraping and the methods and
terminology are fairly easy to work with. In fact we used to build demos
using nothing more than Microsoft Word and Excel. You are in effect doing a
HLLAPI connection (because of the differences with the 3270 this method is
called IHLLAPI) with the emulator. With that, you generally create the
application, identify the locations (on the terminal screen) for the data -
x,y coordinates and length, call a couple of ADK libraries into your app and
pass the coordinates in and then read the result set. The application is
assigned to a terminal session so once the application is launched it
launches the INFOConnect emulator, establishes a connection, and then waits
for your app to begin passing it info.  You don't worry about screen
formatting.

    In 1993 and 1994 I was working with a group within DCA that created an
screen scraping application called QuickApp that automated the mapping and
call process. We adapted it for T27 and UTS use and it can cut your
development time by half or more.

     If I were going to develop a screen scraping application, I would ask
about QuickApp first. The next product that I would ask about is the ADK,
the LAST product would be the IDK. That takes them in order of ease of use
and your apparent desired use. If they still offer the ADK, you were sold
the wrong tool for your application.

    I will forward an informational White Paper that I wrote a couple of
years back to explain the various development kits to the sales force at
Attachmate. I would call Attachmate and ask for verification (talk to an
SE--I would recommend George Swetzer or Guy DiSisto) that you are usign the
correct toolset.


Steve Myers
Sr. SE
Bluestone Software

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Date: Fri, 12 Nov 1999 19:46:13 +0100
Message-ID: <382c6056@rba-bone>
From: Erwin Richard <Erwin.Richard@service.rba.ch>
Subject: Re: Attachmate InfoConnect IDK for screen scraper?

Mark,

What you need is probably the InfoConnect UDK or Quick App. Another
possibility would be to code against the IHLLAPI interface (which is an
IBM/Microsoft standard that makes your app more portable to other mainframe
terminal emulations (IBM 3270)).

Be warned though, We made extremely bad experiences with the stability and
maintainability of INFOConnect based applications. IMHO the INFOConnect
Architecture is overly complex for most situations and while newer releases
try to hide some of the complexity, you as a programmer still have to deal
with it to a certain extent. I assume you are going to build an app against
Unisys UTS (OS2200 / TIP). In that case I would suggest looking at other
products like Quickware (http://www.qw.com/) before you decide.
Especially if you are thinking about mass deployment of that application.

After struggling with Unisys/Attachmate for Years we finally threw
INFOConnect away and never regretted it. I developped an own locked down
INT-1 / UTS emulator engine which we use for Screenscraping/Facelifting that
is very easy to mass-deploy. Inhouse we use QTerm UTS which is IMHO a much
better solution than INFOConnect. Furthermore QW is dedicated to its
products, while Attachmate has a whole bunch of different Productlines, and
Unisys is only a small part of their business. Im speaking out of my
European experience, things might be different at your place though.

Contact me per E-mail if you need further advice.

Erwin

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals, comp.sys.unisys
References: <90c768a3.0210140640.3ab9e717@posting.google.com>
Message-ID: <8bbacd38.0210281345.4f025649@posting.google.com>
Organization: http://groups.google.com/
Date: 28 Oct 2002 13:45:58 -0800
From: John Oman <john.oman@modisit.com>
Subject: Re: Unisys T27 Emulation Specification

Dan Weber <danweber@yahoo.com> wrote in message
news:<90c768a3.0210140640.3ab9e717@posting.google.com>...
>
> I need to implement a light Unisys T27 emulation into one of my
> applications. Does anyone have a T27 specification? PDF? Or where can
> I get/buy one?


We own a very simple T27 emulator that we send out with our other
products.  We also have a DLL you can include in a Visual Basic
project if that is something you desire.

John Oman
Directory of Tech. Development
Modis Professional Services


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys
Date: 28 Dec 2003 04:08:08 -0800
From: Netta <nk1234567@hotmail.com>
Subject: Unisys online test machine (uts)

Hi,

I work in emulations company, and we're going to implement the
Unisys/Univac UTS protocol. We have obtained the documentation, but I
was wondering if anyone here knows of an online ClearPath/UTS machine
which we can test against live.
I'm talking about:

- ClearPath OS 2200 / Unisys ClearPath® IX (2200 Series) / System 80
- Uniscope / Univac
- Protocol: UTS (20 / 40 / 60)


Thanks in advance,

Netta

 ..............................................................................

Newsgroups: comp.sys.unisys
References: <e0cb3b2e.0312280408.7ba84094@posting.google.com>
Message-ID: <6bbad151.0312281351.7efecd39@posting.google.com>
Date: 28 Dec 2003 13:51:45 -0800
From: Keith Stone <kstone@crewstone.com>
Subject: Re: Unisys online test machine (uts)

Hmmm. Seems like an odd time to be doing such an emulation. With all
the emulations already implmented, why not license from someone that
has it done already. It's a non-trivial implementation.

Keith Stone
Winston Salem, NC

 ..............................................................................

Newsgroups: comp.sys.unisys
References: <e0cb3b2e.0312290727.68acb2b0@posting.google.com>
Message-ID: <20031229181510.11565.00001050@mb-m25.aol.com>
Date: 29 Dec 2003 23:15:10 GMT
From: I Right I <irighti@aol.com>
Subject: Re: Unisys online test machine (uts)

nk1234567@hotmail.com (Netta) wrote in message
  news:<e0cb3b2e.0312280408.7ba84094@posting.google.com>...
>
>> > I work in emulations company, and we're going to implement the
>> > Unisys/Univac UTS protocol. We have obtained the documentation, but I
>> > was wondering if anyone here knows of an online ClearPath/UTS machine
>> > which we can test against live.

I'm assuming you're willing to pay for the time...I kind of doubt anyone will
give you machine time gratis and have you turn around and profit from it.


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Host: 150.215.80.8
NNTP-Posting-Date: Wed, 28 Apr 2004 21:23:28 GMT
Message-ID: <khVjc.89572$vn.255037@sea-read.news.verio.net>
Organization: WRQ
Date: Wed, 28 Apr 2004 21:23:28 GMT
From: Joe Silagi <joesi@wrq.com>
Subject: unisys UTS terminal comparison

Does anyone know of a reference that compares the capabilities of the
various UTS terminals?  Specially what are the differences between a UTS40,
UTS60 and UTS400.


TIA.
-joe

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Date: 28 Apr 2004 22:06:43 GMT
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
Message-ID: <c6p9tj$nbr$1@si05.rsvl.unisys.com>
Organization: Unisys - Roseville, MN
Date: Wed, 28 Apr 2004 23:06:43 +0100
From: Colin Zealley <colin.zealley@unisys.com>
Subject: Re: unisys UTS terminal comparison

UTS40 had a very wide variety of monochrome highlight capabilities--15 or
more different combinations of intensity, reverse video, flashing, etc.

UTS400 was also monochrome, had less highlighting choices than a UTS40, but
had significant brains--it even had its own COBOL compiler. I think it may
have been CP/M again, but I don't recall for certain.

UTS60 had colour display (graphics as well as character), and was the basis
of MAPPER's colour display management; most OS/2200 PC-based emulator
packages you see nowadays are actually emulating UTS60. Funny enough, there
never actually was a 'real' hardware UTS60--even the one that was sold as
such was actually a CP/M-based microcomputer running a Uniscope emulation
program enahnced to do colour as well. You could escape into CP/M by pressing
Function-M, if I recall correctly.

If you hung UTS60s on the old MAPPER 5, you even had the amusing situation
of a terminal with a maximum main memory capacity 6x that of its 'mainframe'
driver.

Colin

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Host: 150.215.80.8
NNTP-Posting-Date: Thu, 29 Apr 2004 18:23:07 GMT
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
Message-ID: <fKbkc.90119$vn.255332@sea-read.news.verio.net>
Organization: Verio
Date: Thu, 29 Apr 2004 18:23:07 GMT
From: Joe Silagi <joesi@wrq.com>
Subject: Re: unisys UTS terminal comparison

Great information.

In terms of compatibility... I assume this means that the 60 supports
everything that the 40 does plus graphics.  What about the 400?

Where is this best place to find command/escape sequence and  protocol
specifications for UTS terminals?

Thanks again,

-joe

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Date: 30 Apr 2004 13:47:45 GMT
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
    <fKbkc.90119$vn.255332@sea-read.news.verio.net>
Message-ID: <c6tle1$kje$1@si05.rsvl.unisys.com>
Organization: Unisys - Roseville, MN
Date: Fri, 30 Apr 2004 14:47:44 +0100
From: Colin Zealley <colin.zealley@unisys.com>
Subject: Re: unisys UTS terminal comparison

Joe Silagi wrote:
>
> In terms of compatibility... I assume this means that the 60 supports
> everything that the 40 does plus graphics.


No, the 40's monochrome capabilities were more sophisticated than a 60 had,
but it couldn't do colour character sequences, whereas the 60 could.

As Dan said, the best source is that manual.

Colin

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Date: 29 Apr 2004 20:43:50 GMT
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
    <fKbkc.90119$vn.255332@sea-read.news.verio.net>
Message-ID: <c6rpe6$2dl1$1@si05.rsvl.unisys.com>
Organization: Unisys - Roseville, MN
Date: Thu, 29 Apr 2004 15:43:47 -0500
From: Dan <dan.nissen@unisys.nospam.com>
Subject: Re: unisys UTS terminal comparison

Go to

    http://www.bookstore.unisys.com/ and order

    Uniscope Protocol Manual

    Published: 2/25/1988  Price: $16.30  Part: UP 10683 R1

Dan Nissen

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Host: 172.22.33.196
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
    <fKbkc.90119$vn.255332@sea-read.news.verio.net>
    <c6rpe6$2dl1$1@si05.rsvl.unisys.com>
Message-ID: <c6tl0l$n95$1@news.lsil.com>
Organization: LSI Logic Corporation
Date: Fri, 30 Apr 2004 08:40:35 -0500
From: Kurt Duncan <kurt.duncan@lsil.com>
Subject: Re: unisys UTS terminal comparison

"Dan" <dan.nissen@unisys.nospam.com> wrote in message
news:c6rpe6$2dl1$1@si05.rsvl.unisys.com...
>
> Go to http://www.bookstore.unisys.com/ and order  Uniscope Protocol Manual


I second this recommendation--I bought the book.  It does have some holes
(INT-1 & DCA aren't in there, and you have to already know the keyboard and
what the keys usually do), but it's reasonably complete regarding the
capabilities.  The UTS30 had personality packs, which allowed it to boot up
as a micro, a SperryLink, or a terminal.  It had line graphics which weren't
available on any other model (incl. the UTS60).

IIRC, it doesn't get into control page settings much.  I miss that; I can't
remember most of the more interesting settings (columns-per-page, default
colors, etc).

Some of the blink and reverse video options which worked well on the
monochrome terminals produces strange behavior on the colour terminals;
even the other models of monochrome weren't necessarily consistent when
you mixed blinking with highlight, etc.

DPS was great in terms of hiding terminal capability differences from
programs, but it was such an overhead beast I usually avoided it.  Always
avoided it, actually.  I supported it for the application community, but
never wrote a TIP transaction with it.  Too much baggage.  
Your Mileage May Have Varied.  (YMMV past tense).

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Date: 30 Apr 2004 21:14:58 GMT
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
    <fKbkc.90119$vn.255332@sea-read.news.verio.net>
    <c6rpe6$2dl1$1@si05.rsvl.unisys.com> <c6tl0l$n95$1@news.lsil.com>
Message-ID: <c6ufki$16ee$1@si05.rsvl.unisys.com>
Organization: Unisys - Roseville, MN
Date: Fri, 30 Apr 2004 16:14:57 -0500
From: Dan <dan.nissen@unisys.nospam.com>
Subject: Re: unisys UTS terminal comparison

"Kurt Duncan" <kurt.duncan@lsil.com> wrote:
>
> DPS was great in terms of hiding terminal capability differences from
> programs, but it was such an overhead beast I usually avoided it.  Always
> avoided it, actually.  I supported it for the application community, but
> never wrote a TIP transaction with it.  Too much baggage.


And, having managed the support  and development of DPS 1100 from 1980
to 1990, I always recommend DPS even today.  It may have a bit of baggage,
but it masks the COMPOOL and MCB differences (or let you know them), and
it runs not only on any UTS, but on IBM 3270/Dataspeed 40s and now in a
Web browser with the Java features.  Go DPS !

Dan

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
    <fKbkc.90119$vn.255332@sea-read.news.verio.net>
    <c6rpe6$2dl1$1@si05.rsvl.unisys.com> <c6tl0l$n95$1@news.lsil.com>
    <c6ufki$16ee$1@si05.rsvl.unisys.com>
Message-ID: <109arh479qdcb98@corp.supernews.com>
Organization: Posted via Supernews, http://www.supernews.com
Date: Sun, 02 May 2004 16:53:56 -0500
From: LX-i <lxi0007@netscape.net>
Subject: Re: unisys UTS terminal comparison

Dan wrote:
>
> And, having managed the support  and development of DPS 1100 from 1980
> to 1990, I always recommend DPS even today.  It may have a bit of baggage,
> but it masks the COMPOOL and MCB differences (or let you know them), and
> it runs not only on any UTS, but on IBM 3270/Dataspeed 40s and now in a
> Web browser with the Java features.  Go DPS !


DPS incurs a significant overhead, though, especially on the web browser 
side.  We've noticed a lot of savings in creating transactions that 
bypass that portion and just do pass-through text through WebTS.  To its 
credit, it does allow you to separate your presentation logic from your 
business logic, which is handy...  :)

I'm not saying I've never used it, or wouldn't use it in the future. 
However, I see its life span being shorter than other Unisys products, 
especially if they don't make it extended mode.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~   /   \  /         ~        Live from Montgomery, AL!       ~
~  /     \/       o  ~                                        ~
~ /      /\   -   |  ~          LXi0007@Netscape.net          ~
~ _____ /  \      |  ~ http://www.knology.net/~mopsmom/daniel ~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~         I do not read e-mail at the above address           ~
~    Please see website if you wish to contact me privately   ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Host: 195.27.201.52
NNTP-Posting-Date: Fri, 30 Apr 2004 08:08:08 +0000 (UTC)
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
    <fKbkc.90119$vn.255332@sea-read.news.verio.net>
Message-ID: <995f2314.0404300008.7510a5b3@posting.google.com>
Organization: http://groups.google.com
Date: 30 Apr 2004 01:08:07 -0700
From: andrew williams <andrew.williams@t-online.de>
Subject: Re: unisys UTS terminal comparison

This is from memory so it may be less than 100% accurate.

The UTS 200 (or U200, can't remember) supported .esc. sequences to
move the cursor around - including direct row/col positioning--but
not *that* much else.  I think they may possibly have had
reverse-video, but the only way to have blinking effects was to use
one of two special 'blink' characters.

The UTS 400 was the first one to support FCC sequences.  These allowed
fields to be defined which could be protected, (high-intensity,
low-intensity, blinking) and maybe one or two options more.

The UTS 10, UTS 20 and UTS 40 came next.  They were pretty similar to
each other and substantially expanded the FCC (field definition)
possibilities.  Fields could be Numeric, Alpha, Alphanumeric,
Left-Justified, Right-Just and again, maybe one or two options more. 
There was also a transmit-setting called CHANge mode where only fields
which had been changed would be transmitted--saving a lot of network
traffic.  CHANge mode was/is used with DPS, normally under TIP.

The UTS 30 added graphics (?) and possibly more FCCs--it was a
powerful beast--the UTS 60 added graphics and colour.  I seem to
remember that the UTS 60 was missing some of the more esoteric
functions of the UTS10/20/30/40 terminals (possibly just those of the
UTS 30), which would have been the first time that functionality had
been removed.  Since virtually everyone was by now using DPS to
generate the sequences, this did not really matter because DPS could
recognise different terminal-types and generate the appropriate FCC
sequences for them.

As to documentation, each terminal-type had it's own user-manual.  My
old UTS documentation is at home so I can't say what UP 10683 R1 does.

I certainly cannot remember one manual being valid for all variations
but that does not have to mean that there was no such manual.

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Date: 30 Apr 2004 16:13:32 GMT
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
    <fKbkc.90119$vn.255332@sea-read.news.verio.net>
    <995f2314.0404300008.7510a5b3@posting.google.com>
Message-ID: <c6ttvc$q83$1@si05.rsvl.unisys.com>
Organization: Unisys - Roseville, MN
Date: Fri, 30 Apr 2004 16:13:32 GMT
From: Tom Sherren <sorry@no.spam.i.am>
Subject: Re: unisys UTS terminal comparison

In article <995f2314.0404300008.7510a5b3@posting.google.com>,
andrew.williams@t-online.de (andrew williams) wrote:
>
> This is from memory so it may be less than 100% accurate.
>
            <snip> 

> The UTS 10, UTS 20 and UTS 40 came next.  They were pretty similar to
> each other and substantially expanded the FCC (field definition)
> possibilities.  Fields could be Numeric, Alpha, Alphanumeric,
> Left-Justified, Right-Just and again, maybe one or two options more. 
> There was also a transmit-setting called CHANge mode where only fields
> which had been changed would be transmitted - saving a lot of network
> traffic.  CHANge mode was/is used with DPS, normally under TIP.


The UTS10 was a "glass teletype",  VT2xx type async terminal.

 ..............................................................................

    [Archivist's Note:  The above "glass teletype" description is not how 
     persons fluent in DEC terminal technology would regard the VT220.]

 ..............................................................................

Newsgroups: comp.sys.unisys, comp.terminals
NNTP-Posting-Host: 78328cc8d76a55f648cb96a873bdd4a3
NNTP-Posting-Date: Fri, 30 Apr 2004 23:12:33 GMT
References: <khVjc.89572$vn.255037@sea-read.news.verio.net>
    <c6p9tj$nbr$1@si05.rsvl.unisys.com>
    <fKbkc.90119$vn.255332@sea-read.news.verio.net>
    <995f2314.0404300008.7510a5b3@posting.google.com>
Message-ID: <B3Bkc.5490$Ut1.159626@bgtnsc05-news.ops.worldnet.att.net>
Organization: AT&T Worldnet
Date: Fri, 30 Apr 2004 23:12:33 GMT
From: Stephen Fuld <s.fuld@PleaseRemove.att.net>
Subject: Re: unisys UTS terminal comparison

"andrew williams" <andrew.williams@t-online.de> wrote in message
news:995f2314.0404300008.7510a5b3@posting.google.com...
>
> This is from memory so it may be less than 100% accurate.

  [snipped descriptions of different terminal types]

Don't forget the UTS 40 TE.  It was a special version of the UTS 40 with
extra features designed for text editing.  That was back when it was sort
of reasonable to do "word processing" on a mainframe.  :-)


> As to documentation, each terminal-type had it's own user-manual.  My
> old UTS documentation is at home so I can't say what UP 10683 R1 does.
> I certainly cannot remember one manual being valid for all variations
> but that does not have to mean that there was no such manual.

I think that is right.  The protocol manual gave a lot of general
information but not some of the details of the some of the differences
among models.

-- 
 - Stephen Fuld

 //////////////////////////////////////////////////////////////////////////////

