PAD Services
Remote PAD Support (x29server)
| 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” 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” below for more |
| information on this. |
Launching Applications Automatically
A
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.
If the application and cud fields do not appear in the pad_spt file, the /bin/login (default) program is automatically launched.
142 | Chapter 6 |