Preface

The manual VOS Communications Software: Defining a Terminal Type (R096) documents the format of a terminal-type-definition file (TTP), which provides the VOS operating system with the information it requires to interact with a terminal device of a specific type. It also documents the commands used to compile the TTP into a form usable by the operating system and to install this compiled result in the terminal-type table for a Stratus module. Finally, it describes a collection of subroutines that an application program can call to access directly the information contained in a terminal-type table.

This manual is intended for system-support or application programmers who need to connect non-standard terminals to Stratus systems or to access terminal information from application programs.

Before using the manual VOS Communications Software: Defining a Terminal Type (R096), you should be familiar with the following manuals:

  • VOS System Administration: Configuring a System
  • VOS Communications Software: Asynchronous Communications (R025). Note that this manual is available only on VOS StrataDOC for VOS Release 14.7.1 and earlier.

Manual Version

This manual is a revision. Change bars, which appear in the margin, note the specific changes to text since the previous publication of this manual. Note, however, that change bars are not used in new chapters or appendixes.

This revision incorporates the following changes.

  • A new appendix containing information about the Latin alphabet No. 9
  • Various documentation fixes throughout the manual
  • The removal of information that is no longer relevant
  • The addition of errata information

Manual Organization

This manual has ten chapters and eight appendixes.

Chapter 1 provides an overview of terminal-type support.

Chapter 2 describes the overall structure and syntax of a TTP.

Chapter 3 explains how to specify general terminal characteristics and setup options for a terminal type in the configuration section of a TTP.

Chapter 4 explains how to define the mapping between the VOS internal character-coding system and the encoding of character sets for a terminal type in the character-translation section of a TTP.

Chapter 5 explains how to specify the keyboard characteristics for a terminal type in the keyboard section of a TTP.

Chapter 6 explains how to specify in the input sections of a TTP the way in which generic requests recognized by the VOS operating system and some applications are entered at the keyboard for a terminal type.

Chapter 7 explains how to specify in the output section of a TTP the sequences that must be transmitted to a terminal type to perform common functions, such as clearing the display.

Chapter 8 explains how to specify in the attributes section of a TTP the properties of attributes that affect the way in which characters are displayed (for example, intensity) and the sequences that must be transmitted to a terminal type to set these attributes.

Chapter 9 describes the two commands used to compile and install TTPs.

Chapter 10 describes the subroutines that allow application programs to obtain the information needed to interact directly with a terminal type. (This information is obtained from the terminal-type table on a Stratus module.)

Appendix A presents two sample TTPs.

Appendix B contains sample programs that illustrate the use of some of the subroutines documented in Chapter 10.

Appendix C presents a table that shows the VOS internal version of Latin alphabet No. 1.

Appendix D shows the formal syntax for capability expressions described in Chapter 7.

Appendix E presents the symbolic names, defined in system include files, that represent the VOS operating system internal codes for generic input requests and output capabilities.

Appendix F explains how to write TTPs for printers.

Appendix G describes the way in which the current terminal-type support software interprets TTPs written in the format required by the previous version of the software.

Appendix H presents the C language calling sequences for the subroutines described in Chapter 10.

Appendix I provides terminal-type-related information about the Latin alphabet No. 9 character set.

Related Manuals

Refer to the following Stratus manuals for related documentation.

  • VOS System Administration: Configuring a System
  • VOS Commands Reference Manual
  • VOS Reference Manual
  • VOS Word Processing User's Guide
  • VOS Forms Management System manuals:

VOS PL/I Forms Management System

VOS COBOL Forms Management System

VOS FORTRAN Forms Management System

VOS Pascal Forms Management System

VOS C Forms Management System

  • VOS Subroutines manuals:

VOS PL/I Subroutines Manual

VOS COBOL Subroutines Manual

VOS FORTRAN Subroutines Manual

VOS Pascal Subroutines Manual

VOS C Subroutines Manual

Notation Conventions

This manual uses the following notation conventions.

  • Italics introduces or defines new terms. For example:

The master disk is the name of the member disk from which the module was booted.

  • Boldface emphasizes words in text. For example:

Every module must have a copy of the module_start_up.cm file.

  • Monospace represents text that would appear on your terminal's screen (such as commands, subroutines, code fragments, and names of files and directories). For example:
change_current_dir (master_disk)>system>doc
  • Monospace italic represents terms that are to be replaced by literal values. In the following example, the user must replace the monospace-italic term with a literal value.
list_users -module module_name
  • Monospace bold represents user input in examples and figures that contain both user input and system output (which appears in monospace). For example:
display_access_list system_default 

%dev#m1>system>acl>system_default

w  *.*

Key Mappings for VOS Functions

VOS provides several command-line and display-form functions. Each function is mapped to a particular key or combination of keys on the terminal keyboard. To perform a function, you press the appropriate key(s) from the command-line or display form. For an explanation of the command-line and display-form functions, see the manual Introduction to VOS .

The keys that perform specific VOS functions vary depending on the terminal. For example, on a V105/V109 EPC terminal, you press the key on the numeric keypad to perform the INTERRUPT function.

Note: Certain applications may define these keys differently. Refer to the documentation for the application for the specific key mappings.

The following table lists some VOS functions and the keys to which they are mapped on commonly used Stratus terminal types. For information about the key mappings for a terminal that is not listed in this table, refer to the documentation for that terminal.

 
VOS Function
 
V105/V109 EPC
full_xterm, putty, putty8, putty_aws, tinyterm
CANCEL
 †
<0> † or
CYCLE
 †
 † or - or right arrow key
CYCLE BACK
†
† or - or left arrow key
DISPLAY FORM
 † or -<PageUp>
HELP
-
-
INSERT DEFAULT
-
 † or -
INSERT SAVED
 † or -
INTERRUPT
†
--
NO PAUSE
-
† or -
†Press this key on the numeric keypad only, not on the regular keyboard.

Format for Commands and Requests

Stratus manuals use the following format conventions for documenting commands and requests. (A request is typically a command used within a subsystem, such as analyze_system.) Note that the command and request descriptions do not necessarily include each of the following sections.

name
The name of the command or request is at the top of the first page of the description.

Privileged
This notation appears after the name of a command or request that can be issued only from a privileged process.

Purpose
Explains briefly what the command or request does.

Display Form
Shows the form that is displayed when you type the command or request name followed by -form or when you press the key that performs the DISPLAY FORM function. Each field in the form represents a command or request argument. If an argument has a default value, that value is displayed in the form.

The following table explains the notation used in display forms.

The Notation Used in Display Forms

Notation
Meaning

Required field with no default value.

The cursor, which indicates the current position on the screen. For example, the cursor may be positioned on the first character of a value, as in ll.
current_user
current_module
current_system
current_disk
The default value is the current user, module, system, or disk. The actual name is displayed in the display form of the command or request.

Command-Line Form
Shows the syntax of the command or request with its arguments. You can display an online version of the command-line form of a command or request by typing the command or request name followed by -usage.

The following table explains the notation used in command-line forms. In the table, the term multiple values refers to explicitly stated separate values, such as two or more object names. Specifying multiple values is not the same as specifying a star name. When you specify multiple values, you must separate each value with a space.

The Notation Used in Command-Line Forms

Notation
Meaning
argument_1
Required argument.
argument_1...
Required argument for which you can specify multiple values.
 
Î Ï
 
Set of arguments that are mutually exclusive; you must specify one of these arguments.
[argument_1]
Optional argument.
[argument_1]...
Optional argument for which you can specify multiple values.
 
 
Set of optional arguments that are mutually exclusive; you can specify only one of these arguments.
Note: Dots, brackets, and braces are not literal characters; you should not type them. Any list or set of arguments can contain more than two elements. Brackets and braces are sometimes nested.

Arguments
Describes the command or request arguments. The following table explains the notation used in argument descriptions.

The Notation Used in Argument Descriptions

Notation
Meaning
There are predefined values for this argument. In the display form, you display these values in sequence by pressing the key that performs the CYCLE function.
Required
You cannot issue the command or request without specifying a value for this argument.
 
If an argument is required but has a default value, it is not labeled Required since you do not need to specify it in the command-line form. However, in the display form, a required field must have a value—either the displayed default value or a value that you specify.
(Privileged)
Only a privileged process can specify a value for this argument.

Explanation
Explains how to use the command or request and provides supplementary information.

Error Messages
Lists common error messages with a short explanation.

Examples
Illustrates uses of the command or request.

Related Information
Refers you to related information (in this manual or other manuals), including descriptions of commands, subroutines, and requests that you can use with or in place of this command or request.

Format for Subroutines

Stratus manuals use the following format conventions for documenting subroutines. Note that the subroutine descriptions do not necessarily include each of the following sections.

subroutine_name
The name of the subroutine is at the top of the first page of the subroutine description.

Purpose
Explains briefly what the subroutine does.

Usage
Shows how to declare the variables passed as arguments to the subroutine, declare the subroutine entry in a program, and call the subroutine.

Arguments
Describes the subroutine arguments.

Explanation
Provides information about how to use the subroutine.

Error Codes
Explains some error codes that the subroutine can return.

Examples
Illustrates uses of the subroutine or provides sample input to and output from the subroutine.

Related Information
Refers you to other subroutines and commands similar to or useful with this subroutine.

Online Documentation

The VOS StrataDOC Web site is an online-documentation service provided by Stratus. It enables Stratus customers to view, search, download, print, and comment on VOS technical manuals via a common Web browser. It also provides the latest updates and corrections available for the VOS document set.

You can access the VOS StrataDOC Web site at http://stratadoc.stratus.com. A copy of the VOS StrataDOC CD-ROM is included with this release. You can also order additional copies from Stratus.

This manual is available on the VOS StrataDOC Web site.

For information about ordering the VOS StrataDOC CD-ROM, see the next section, "Ordering Manuals."

Ordering Manuals

You can order manuals in the following ways.

  • If your system is connected to the Remote Service Network (RSN™), issue the maint_request command at the system prompt. Complete the on-screen form with all of the information necessary to process your manual order.
  • Contact your nearest Stratus sales office, Stratus Customer Assistance
    Center (CAC) office    , or distributor.

Manual orders will be forwarded to Order Administration.

Commenting on This Manual

You can comment on this manual by using the command comment_on_manual. To use the comment_on_manual command, your system must be connected to the RSN. Alternatively, you can email comments on this manual to comments@stratus.com.

The comment_on_manual command is documented in the manual VOS System Administration: Administering and Customizing a System and the VOS Commands Reference Manual . There are two ways you can use this command to send your comments.

  • If your comments are brief, type comment_on_manual, press or , and complete the data-entry form that appears on your screen. When you have completed the form, press .
  • If your comments are lengthy, save them in a file before you issue the command. Type comment_on_manual followed by -form, then press or . Enter this manual's part number, R096, then enter the name of your comments file in the -comments_path field. Press the key that performs the CYCLE function to change the value of -use_form to no and then press .

Note: If comment_on_manual does not accept the part number of this manual (which may occur if the manual is not yet registered in the manual_info.table file), you can use the mail request of the maint_request command to send your comments.

Your comments (along with your name) are sent to Stratus over the RSN.

Stratus welcomes any corrections and suggestions for improving this manual.