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

01.01.2013 Views

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-

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 />

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!