🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.unisys
Article #224

Re: seeking info on UDLC, P1024 and Uniscope

#224
From: Walt Kemmerer
Date: Mon, 11 Jan 1993 19:32
49 lines
2957 bytes
Bill,

The UDLC and Uniscope protocols are indeed Unisys-specific, both
hailing back to the old Sperry Univac side of the house.  As for
P1024, these are actually a series of airlines protocols (P1024A,
P1024B, and P1024C) that are implemented in the Unisys (Sperry)
Distributed Communications Processor (DCP) family under the heading
of AIR/net (with some other airlines specific stuff also being
thrown in, like AX.25 and Inverted and Real ALC).  The P1024C
data presentation bears a strong resemblance to Uniscpe data stream
but the protocol wrapper is quite different.

There is some documentation on the Uniscope and UDLC protocols in
the DCP "dump buster's guide", which is on the release tape for
the DCP software release, called TELCON.  While this document is
no longer being actively supported (it appears), the UDLC and
Uniscope stuff hasn't changed for some time.  There were also
actual documents on these protocols: look around for an old Sperry
document called the UDLC General Description (UP number not in
front of me), and any of the Uniscope family (U400, UTS4000, UTS20,
UTS40, UTS60) Programmer's Reference Manuals (I believe).  These
all pretty much were the same vis a vis the protocol wrapper that
Uniscope implements but the data presentation layer capabilities
varied in the different mambers of the family.  I believe I have
copies of several of these (including the UDLC document), but I'll
have to unarchive them to give you the old UP numbers, and then
you're on your own in getting Unisys to decipher what they are
called these days (if they are even in print).

Best place for P1024 documentation is probably SITA, which has a
USA presence in GA, so you're in luck there.  Beware, however, that
many airlines use P1024 as a starting point and then implement
bilateral agreements to modify the protocol for their own specific
link.  This is a relatively common practice, so beware when an IBM
or Tandem P1024 variant is in play; check for bilaterals.

If I can be of further assistance, post a follow-up here in
comp.sys.unisys and I'll see what I can do to help you out.  The
whole arena of Unisys (Sperry) comms is pretty much under-documented
but it's not all that hard to decipher :-)

Cheers, Walt

----------------------------------------------------------
I/O Specialists, Inc. : kemmerer@ioscc.neosoft.com
3906 Green Fields     :-----------------------------------
Sugar Land, TX 77479  : Networking and Communications
713.858.0997          :-----------------------------------
Technical Details
Message-ID: <wwkiii.726780747@well.sf.ca.us>
Path: arc1-ca.pugleaf.net!sparky!uunet!well!well.sf.ca.us!wwkiii
References: <1993Jan11.172008.7292@nastar.uucp>

Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.unisys
Path: arc1-ca.pugleaf.net!sparky!uunet!well!well.sf.ca.us!wwkiii
From: wwkiii@well.sf.ca.us (Walt Kemmerer)
Subject: Re: seeking info on UDLC, P1024 and Uniscope
Message-ID: <wwkiii.726780747@well.sf.ca.us>
Sender: news@well.sf.ca.us
Organization: Whole Earth 'Lectronic Link
References: <1993Jan11.172008.7292@nastar.uucp>
Date: Mon, 11 Jan 1993 19:32:27 GMT
Lines: 49