UTS
Artem E. Livshits
I'd be glad to get any information about an Uniscope Proticol
specification.
I've seached the Internet trying to find a document describing
the protocol of an UTS terminal and found only references to Uniscope.
Unfortunately, I've found no documents disclosing this Protocol.
Could someone help me?
---
Artem E. Livshits
Mike Darnell
The protocol of a UTS terminal is Uniscope protocol. It's basically a
brand of bi-sync terminal protocol, but would also work in an async mode.
Back when it was "Univac" or "Sperry", there was a Uniscope protocol
manual, but I haven't seen one in years. It costs about $10. The
Unisys publication number is UP 10683.
I think the protocol was also described in the UTS400 terminal manual.
However, I haven't seen one of these for a while either. They can still
be bought for about $15. The Unisys publication number is UP 8359.
For contacts with others interested in Uniscope protocol, see:
http://www.cs.utk.edu/~shuford/terminal/unisys_news.txt
--
Mike Darnell
http://www.geocities.com/Heartland/Estates/4499
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Clarence Reece
would be glad to make a copy & mail to you. If interested leave me your
address. If you respond to this please send a copy to my work e-mail ar
cre...@jackcoopper.com
Regards,
Clarence Reece
Jack Cooper Transport
Kansas City, MO
Check it out! http://www.jackcooper.com
cre...@jackcooper.com
--
Clarence A. Reece
1709 SE 7th Terrace
Lee's Summit, MO 64063
(816) 525-4027
cre...@kctera.net
Artem E. Livshits <a...@tais.ru> wrote in message
news:01be8ca2$08d88230$16c7c7c7@art...
Erwin Richard
I happen to have some documentations about The Uniscope Protocol
Unisys Uniscope Protocol Reference Manual
UP-10683 Rev.1 Feb 1988
Ericsson Alphascop System 41 Documentation (UTS Emulation Parts only)
1983
If you can't get the official Manual from Unisys, I'd be happy to "snail
mail" you a copy.
However, many sytems nowadays communicate over TCP/IP using the INT-1
Protocol, which is a proprietary protocol by Unisys / Sperry. You have to
sing a nondisclosure agreement with Unisys to get documentation for this.
Erwin
Williams, Steve
> You have to
>sing a nondisclosure agreement with Unisys to get documentation for this.
Hmmm. With my voice they'd be bound to give me whatever I need as soon
as possible.
Steve.
Erwin Richard
sweetest voice wouldn't help me in that case...
Erwin
Williams, Steve <st...@lgx.ch.unisys.com> wrote in message
news:37250428....@ernie.rsvl.unisys.com...
Lueko Willms
schrieb Erwin....@service.rba.ch (Erwin Richard)
auf /COMP/SYS/UNISYS
in 372386f0@rba-bone
ueber Re: UTS
ER> However, many sytems nowadays communicate over TCP/IP using the INT-1
ER> Protocol, which is a proprietary protocol by Unisys / Sperry. You have to
ER> sing a nondisclosure agreement with Unisys to get documentation for this.
INT-1 is only a very small wrapper around the actual UTS i.e.
Uniscope screen controls.
Lüko Willms
/------------ L.WI...@LINK-F.rhein-main.de -- Will...@compuserve.com
/------------ Lueko....@T-Online.de -- "Get PGP Key" im Betreff
"Ohne Pressefreiheit, Vereins- und Versammlungsrecht ist keine
Arbeiterbewegung möglich" - Friedrich Engels (Februar 1865)
Wim Morrison
F.rhein-main.de says...
> INT-1 is only a very small wrapper around the actual UTS i.e.
> Uniscope screen controls.
Absolutely not! You must be thinking of INT-1 device dependent mode 1 as
used by Mapper. As one who has written not one but two implementations of
INT-1 I can assure you it is in no way a small wrapper.
Wim Morrison
Unisys APT CSC
Artem E. Livshits
> INT-1 is only a very small wrapper around the actual UTS i.e.
> Uniscope screen controls.
May be you even know exactly what portion of information
INT-1 adds to the actual Uniscope?
I'd be very appriciative if you shared a INT-1 level data structures
with me.
---
Artem E. Livshits
Erwin Richard
One of the explanations of a Unisys (Switzerland) Representative was that
they wouldn't want to be held liable for bugs in ther actual implementations
which might not adhere to the specs.
About the complexity INT-1 adds, this is probably totaly dependent of what
functionality of the protocol you are actually using.
Artem E. Livshits <a...@tais.ru> wrote in message
news:01be916e$98abab50$16c7c7c7@art...
Lueko Willms
schrieb wim.mo...@unisys.com (Wim Morrison)
auf /COMP/SYS/UNISYS
in MPG.119166fc7...@129.223.24.15
ueber Re: UTS
Hello Wim,
long time no see...
WM> In article <7Ffr9...@lf111.link-f.rhein-main.de>, L.WILLMS@LINK-
WM> F.rhein-main.de says...
WM> > INT-1 is only a very small wrapper around the actual UTS i.e.
WM> > Uniscope screen controls.
WM>
WM> Absolutely not! You must be thinking of INT-1 device dependent mode 1 as
WM> used by Mapper.
Not only Mapper, but any application using full screen forms,
including those built with DPS/2200.
Using INT-1, one can control if only the variable fields are
transmitted or both variable and protected ones, one can erase just
the variable fields, or both protected and variable, but I don't find
in the INT-1 specification any commands to define those screen forms
(protected/unprotected areas, Character control etc).
WM> As one who has written not one but two implementations of
Which ones? Excuse my curiosity...
WM> INT-1 I can assure you it is in no way a small wrapper.
In the DCP/CMS line traces I looked at, the volume of the INT-1
protocol headers was always quite small compared to the actual device
dependent Uniscope or 3270 device control...