ACC X.25 Protocol User's Guide

ZX25D X.25 Protocol Driver
Virtual Circuit Definitions
Chapter 348
Udata This parameter allows X.25 call user data to be
specified for X25.SVC.AUTO, X25.SVC.IO or X25.SVC
virtual circuits which will generate outgoing calls. This
call user data will be stored in a logical terminal table
(LTT) extension area.
The Udata entry is related to the previous Lterm or
Term entry that came before it. In other words, the
affected LTT extension area belongs to the LTT created
for the previous Lterm or Term entry. A Udata entry
after a Pterm entry will cause an error to be reported.
Call user data can be up to 16 bytes in length. These
bytes may be ASCII characters (one character per byte)
and non-ASCII byte values. You must specify a Udata
string within a single pair of double quotes following
the Udata keyword. Example:
Udata "abcdef"
A non-ASCII byte value may be specified using the
following notation: “\0<octal_value>”
’0’ is the zero ASCII character. <octal_value> is the
octal representation of the byte value that you want.
Any octal value greater than that which can be held in
a byte (“\0377”) will be flagged as an error. Note that
when specifying a byte value of zero, you must use
“\00”. If you place leading zeroes between the required
leading zero and your <octal_value>, these extra
leading zeroes will be ignored.
You may also intermix ASCII characters and the
non-ASCII byte notation. Example:
Udata "abc\045def"
This will place the ASCII characters “abc” into the
Udata buffer, followed by a binary octal value 45 in the
next byte, followed by the ASCII characters “def”.
If you want the characters “\0” to be interpreted as
ASCII characters for Udata rather than as an indicator
of a non-ASCII binary byte, then place a ’\’ in front of
them to “escape” them. Example: