PAD Services

Configuring X.3 Profile Parameters

Parameter Values

config_name Mandatory. Specifies the configuration set name, a character string that identifies the X.3 parameter set. Each config_name must be unique. This is a required parameter for all PAD services if user-defined X.3 parameters are to be used. This name must match the x3 value given in the x29hosts file for pad_spt, printer, or pad_uucp entries. Since X3 has no effect on pad_em entries, a dummy string for config_name together with a profile number should be entered for padem profile parameters.

profile_number Optional. Applies only to the padem configuration. This is a number that must match the number entered for profile in the pad_em {} section of the x29hosts file. If the profile entry exists and is assigned a value in the x29hosts file, it must also appear in the x3config file.

X.3_parameter _no Mandatory. This is an integer value from 1 to 22. See “X.3 parameter descriptions” later in this chapter for a full description of each X.3 parameter.

value1, value2 Mandatory. These are the values to be used in X.3 configuration. Each value is defined for a specific X.3 parameter: value1 is for line-mode configuration; value2 is for raw-mode configuration. Only x29server implements raw-mode data transfer and only parameters 3 and 4 are used for raw-mode data transfer. x29printd, x29uucpd, and padem do not use value2.

Modifying Parameters

Initial parameter settings can be changed at any time during a call. This occurs when x29server detects an ioctl() call to configure the PTY for a PAD terminal. This system call could be issued by the UNIX login process, by a shell initialization script such as .login, or by an application.

Each ioctl() request is examined by the server. If a mapping exists between the terminal I/O parameter and X.3, the terminal I/O value is checked against the current X.3 setting. If the request calls for a change,

164

Chapter 6