AT&T UNIX™PC Unix System V Users Manual - tenox
AT&T UNIX™PC Unix System V Users Manual - tenox AT&T UNIX™PC Unix System V Users Manual - tenox
UA (4) (AT&T UNIX PC only ) UA (4) be short enough to fit on a line with the file name (say 50 characters max). If the first character of the description is an asterisk (*), then the description replaces the filename suffix in the folder display. Otherwise, the complete filename including the suffix is displayed. Default = Command Specifies which command is the default (typically Open or Run). Open = Action specification The action specification defines what to do when the file is opened via the user agent Open command. It typically involves creating a window and executing a process with the file passed to it as an argument. (See the "Action Specifications" section below for details.) Keyword = Action specification The remaining keywords that may be defined are all of this form. They are taken from the set of user agent commands listed in the section "Objects and Actions," and are optional. They should only be defined when the desired action differs from the default action. Comm_pkgs The Comm_pkgs file is used to support separately installed phone managers and terminal emulators, and to support external modems on any RS-232 port. ) Each entry defines a communications application that is invoked through the phone manager. All applications that are invoked in this way must have an entry in the Comm_pkgs file. A single application may have multiple entries under different names, allowing several methods of invocation. The following keywords can be used in the Comm_pkgs file: Name = Application package name. Suffix= The suffix the application package appends to its profiles. Connection= Defines the device type controlled by the application. It may be ACU, DIR, or OBM. Create= This is an optional field, depending upon the functionality supported by the application. It is the invocation sequence for the application to create a profile. Modify= This is also an optional field, depending upon the functionality supported by the application. It is the invocation sequence for the application to modify a profile. Setup= The standard invocation sequence for the package. The phone manager does the device "set-up" and dialing. The - 4 - �
UA ( 4) (AT&T UNIX PC only ) UA (4) child process inherits the file descriptors. Nosetup= The invocation sequence when no phone number is present in the data entry. No device "set-up" is provided. Originate= Specifies whether the application may be invoked from the console only, a remote terminal only, or from either. Allowed values are CONSOLE, REMOTE, or BOTH. The "Setup" and "Nosetup" fields contain macros for substitution by the phone manager. The macros are limited to passing the following information to the application: PHONENUM=phone number DEVICE=full device path PROFNAME=full path of profile entry PID=process ID of the phone manager HOSTNAME=phone directory name field FN=phone device file descriptor Check the table below to determine if the "Nosetup" or "Setup" action is desired. Port and Device Type: Phone Manager Actions Phone Port Device Phone Manager Number Type Type Set-up Dlal Invoke Macro yes serial ACU yes yes yes Setup no serial ACU no no yes Nosetup yes serial DIR Error Condition no serial DIR yes no yes Setup yes ph OBM yes yes yes Setup no ph OBM no no yes Nosetup The phone manager takes one of six paths. Port Types are either serial or ph (phone). Device Types are either an ACU (Automatic Calling Unit), which is a serial port to an external modem, DIR (direct) connection between a serial port and another computer, or OBM (On Board Modem) connecting to another computer. After determining whether or not to dial, the terminal emulator is invoked, and the macro Setup or Nosetup is used. Menu Objects The Office, Administration, and Preferences files define objects in the class menu objects. The minimum information which must be specified is the object Name and the action to take on Open. The Name keyword definition begins the object definition. Subsequent keyword definitions are assumed to belong to this object, until the next Name keyword is encountered. The other keyword that is typically defined is Help. - 5-
- Page 1076 and 1077: FSPEC ( 4) FSPEC ( 4) Several UNIX
- Page 1078 and 1079: GETTYDEFS ( 4) GETTYDEFS ( 4 ) sett
- Page 1080 and 1081: � , __
- Page 1082 and 1083: INITTAB ( 4) INITTAB ( 4) I etclini
- Page 1084 and 1085: I I �I I I I I � I I 1� 1 1 I
- Page 1086 and 1087: (� .
- Page 1089 and 1090: � LDFCN( 4) LDFCN( 4) NAME ldfcn
- Page 1091: LDFCN( 4) LDFCN{4) REWIND(Idptr) FE
- Page 1095 and 1096: MASTER ( 4) MASTER (4) NAME master
- Page 1097: MNTTAB (4) MNTTAB (4) NAME mnttab -
- Page 1100 and 1101: PASSWD (4) PASSWD ( 4) Haphazard mo
- Page 1102 and 1103: PHONE (4) 02 (short) 03 (short) 04
- Page 1104 and 1105: y . /
- Page 1107: PROFILE ( 4) PROFILE ( 4) NAME prof
- Page 1110 and 1111: RELOC (4) RELOC ( 4) R_ABS The refe
- Page 1112 and 1113: (�
- Page 1114 and 1115: SCCSFILE ( 4) SCCSFILE ( 4) time of
- Page 1116 and 1117: (�
- Page 1119 and 1120: SHLill ( 4) (AT&T UNIX PC only ) SH
- Page 1121 and 1122: SYMS ( 4) SYMS ( 4) NAME syms - com
- Page 1123 and 1124: UA ( 4) (AT&T UNIX PC only ) UA ( 4
- Page 1125: UA ( 4) Rename (AT&T UNIX PC only )
- Page 1129 and 1130: UA ( 4) (AT&T UNIX PC only ) UA ( 4
- Page 1131 and 1132: UTMP ( 4) UTMP ( 4) NAME utmp, wtmp
- Page 1133: INTRO ( 5) NAME intro - introductio
- Page 1136 and 1137: ,!)
- Page 1139: .� EQNCHAR (5) EQNCHAR (5) NAME e
- Page 1143 and 1144: GREEK (5) GREEK (5) NAME greek - gr
- Page 1145 and 1146: MAN(5) MAN ( 5) NAME man - macros f
- Page 1147 and 1148: MAN (5) MAN (5) . � FILES The mac
- Page 1149 and 1150: MM (5) MM ( 5 ) NAME mm - the MM ma
- Page 1151 and 1152: MODEMCAP ( 5) ( AT&T UNIX PC Only )
- Page 1153: � MPTX ( 5 ) MPTX ( 5 ) NAME mptx
- Page 1156 and 1157: REGEXP (5) REGEXP (5) ERROR( val )
- Page 1158 and 1159: REGEXP (5) REGEXP (5) #define UNGET
- Page 1160 and 1161: TERM (5) TERM ( 5) Commands whose b
- Page 1163 and 1164: TERMCAP (S) TERMCAP (S) NAME termca
- Page 1165 and 1166: TERMCAP (5) ti uc ue ug ul up us vb
- Page 1167 and 1168: TERMCAP (5) TERMCAP (5) character a
- Page 1169 and 1170: TERMCAP (5) TERMCAP (5) "abc" shift
- Page 1171 and 1172: TERMCAP (5) TERMCAP (5) If tabs on
- Page 1173 and 1174: TYPES ( S) TYPES ( S) NAME types -
- Page 1175 and 1176: VARARGS (5) VARARGS (5) NAME vararg
UA (4) (AT&T UNIX PC only ) UA (4)<br />
be short enough to fit on a line with the file name (say 50<br />
characters max). If the first character of the description is<br />
an asterisk (*), then the description replaces the filename<br />
suffix in the folder display. Otherwise, the complete<br />
filename including the suffix is displayed.<br />
Default = Command<br />
Specifies which command is the default (typically Open or<br />
Run).<br />
Open = Action specification<br />
The action specification defines what to do when the file is<br />
opened via the user agent Open command. It typically<br />
involves creating a window and executing a process with<br />
the file passed to it as an argument. (See the "Action<br />
Specifications" section below for details.)<br />
Keyword = Action specification<br />
The remaining keywords that may be defined are all of<br />
this form. They are taken from the set of user agent commands<br />
listed in the section "Objects and Actions," and<br />
are optional. They should only be defined when the<br />
desired action differs from the default action.<br />
Comm_pkgs<br />
The Comm_pkgs file is used to support separately installed<br />
phone managers and terminal emulators, and to support external<br />
modems on any RS-232 port. )<br />
Each entry defines a communications application that is invoked<br />
through the phone manager. All applications that are invoked in<br />
this way must have an entry in the Comm_pkgs file. A single<br />
application may have multiple entries under different names,<br />
allowing several methods of invocation.<br />
The following keywords can be used in the Comm_pkgs file:<br />
Name = Application package name.<br />
Suffix=<br />
The suffix the application package appends to its profiles.<br />
Connection=<br />
Defines the device type controlled by the application. It<br />
may be ACU, DIR, or OBM.<br />
Create=<br />
This is an optional field, depending upon the functionality<br />
supported by the application. It is the invocation sequence<br />
for the application to create a profile.<br />
Modify=<br />
This is also an optional field, depending upon the functionality<br />
supported by the application. It is the invocation<br />
sequence for the application to modify a profile.<br />
Setup=<br />
The standard invocation sequence for the package. The<br />
phone manager does the device "set-up" and dialing. The<br />
- 4 -<br />
�