Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

unisys UTS terminal comparison

134 views
Skip to first unread message

Joe Silagi

unread,
Apr 28, 2004, 5:23:28 PM4/28/04
to
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


Colin Zealley

unread,
Apr 28, 2004, 6:06:43 PM4/28/04
to
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 micro 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

"Joe Silagi" <jo...@wrq.com> wrote in message
news:khVjc.89572$vn.2...@sea-read.news.verio.net...

Joe Silagi

unread,
Apr 29, 2004, 2:23:07 PM4/29/04
to
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


"Colin Zealley" <colin....@unisys.com> wrote in message
news:c6p9tj$nbr$1...@si05.rsvl.unisys.com...

Dan

unread,
Apr 29, 2004, 4:43:47 PM4/29/04
to
Go to http://www.bookstore.unisys.com and order Uniscope Protocol
Manual

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


Dan Nissen


"Joe Silagi" <jo...@wrq.com> wrote in message

news:fKbkc.90119$vn.2...@sea-read.news.verio.net...

andrew williams

unread,
Apr 30, 2004, 4:08:07 AM4/30/04
to
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.


"Joe Silagi" <jo...@wrq.com> wrote in message news:<fKbkc.90119$vn.2...@sea-read.news.verio.net>...

Colin Zealley

unread,
Apr 30, 2004, 9:47:44 AM4/30/04
to
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

"Joe Silagi" <jo...@wrq.com> wrote in message

news:fKbkc.90119$vn.2...@sea-read.news.verio.net...

Kurt Duncan

unread,
Apr 30, 2004, 9:40:35 AM4/30/04
to
"Dan" <dan.n...@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).


Tom Sherren

unread,
Apr 30, 2004, 12:13:32 PM4/30/04
to
In article <995f2314.04043...@posting.google.com>, andrew....@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.

Dan

unread,
Apr 30, 2004, 5:14:57 PM4/30/04
to
And, having managed the support and development of DPS 1100 from 1980
to1990, 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

"Kurt Duncan" <kurt....@lsil.com> wrote in message
news:c6tl0l$n95$1...@news.lsil.com...

Matthew L Daniel

unread,
Apr 30, 2004, 5:53:10 PM4/30/04
to
> 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

I have been asking everyone I know in the Unisys circles this question,
so I'll toss it out here, too. Is there a document for purchase by the
general populous (i.e. not requiring a confidentiality agreement) that
describes INT-1 and/or DCA?

Thanks,
-- /v\atthew
--
Matthew L Daniel
//Be cautious of the .mil spam-guard in my address.

Stephen Fuld

unread,
Apr 30, 2004, 7:12:33 PM4/30/04
to

"andrew williams" <andrew....@t-online.de> wrote in message
news:995f2314.04043...@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
e-mail address disguised to prevent spam


LX-i

unread,
May 2, 2004, 5:53:56 PM5/2/04
to
Dan wrote:
> And, having managed the support and development of DPS 1100 from 1980
> to1990, 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 ~ ~
~ / /\ - | ~ LXi...@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 ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Dan

unread,
May 7, 2004, 9:35:35 AM5/7/04
to
I think the simple answer is no. There never was one. Unisys has a number
of competitors in the Communication Processor hardware market, and such a
document would have allowed them to get a leg up on Unisys.

Dan

"Matthew L Daniel" <mda...@scdi.com.mil> wrote in message
news:slrnc95imb....@cafebabe.intra...

0 new messages