HP X.25/9000 User's Guide HP-UX 11i v3 (5900-1523, August 2011)

If the pty_slave_fname field contains an entry, x29server considers
any communication initiated by this entry to be restricted to exclusive
use by the TTY/ PTY (master/slave) pair. The call is refused if the TTY/PTY
pair does not exist, is already in use, or cannot be accessed (permission
should be set to 666).
logging Optional. Specifies the logging level for each call. Log information is
stored in the file /var/x25/log/x29server/x29logXXXXX, where
XXXXX is the process ID of the current x29server child process.
Logging can be at levels 0, 1, 2, or 3. Level 0 is no logging and the
default is level 1 (error logging). Level 2 is error and warning logging.
Level 3 is error, warning, information, and status logging.
reverse_charge Optional. Specifies reverse charge options for the calling address.
Possible settings are: disabled (or disable), enabled (or enable).
With the default value (disable), reverse charge calls will not be
accepted. When reverse charging is enabled and is requested by the
remote PAD or system, the call is accepted and is charged to the local
system. You must also configure the X.25 interface card to allow reverse
charging (refer to “Configuring remote system access” (page 23) in
Chapter 3 for instructions on how to use SMH to enable reverse
charging) in order for reverse charging to work with PAD services.
size_parity Optional. Legal values are 8_none (the default), 7_even, and 7_odd.
Specifies the character size and parity setting of the remote PAD and
terminal. This parameter is useful when the asynchronous port of the
PAD cannot be configured in 8 bits. In this case, this parameter must
be set to match the remote PAD and terminal settings. x29server will set
the PTY pair correctly so that 7-bit PAD users can log in without problems.
Note that size and parity processing will only be performed on input
from the PAD to the system.
x3 Optional. This is the X.3 configuration set name for this x29server
session. If this entry is included in the /etc/x25/x29hosts file, the
configuration name and its set of X.3 parameters must also be specified
in the /etc/x25/x3config file. If more than one X.3 configuration
set with the same name exists in x3config, the first one is used. X.3
parameters are not downloaded unless both the X.3 configuration set
name and the parameters are given.
application Optional. Used with cud to specify the full path name of the application
to be launched when the connection is established (maximum 80
characters, no wildcards). See “Launching applications automatically”
(page 98) below for more information.
cud Optional. Specifies a yes or no condition. Legal values for this field are:
enable (or yes), disable (or no). See “Launching applications
automatically” (page 98) below for more information on this.
Launching applications automatically
A user-level application can be launched automatically by configuring the application and
cud fields in the pad_spt section of the x29hosts file.
The application parameter specifies the name of the user application (or script) to be
automatically launched when the connection is established. The cud parameter is used like an
on/off switch to enable or disable the use of Call User Data (CUD) instructions.
If you are using a UNIX script, it must contain the character string #!/bin/ksh at the beginning
of the first line. If this string is not included, the system will return an error code.
98 PAD services