Open System Services Porting Guide (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to Porting
- 2 The Development Environment
- 3 Useful Porting Tools
- 4 Interoperating Between User Environments
- Purpose of Interoperability
- The OSS User Environment
- OSS Commands for the Guardian User
- Guardian Commands for the UNIX User
- OSS Pathname and Guardian Filename Conversions
- Running the OSS Shell and Commands From TACL
- Running Guardian Commands From the OSS Shell
- Running OSS Processes With Guardian Attributes
- Using OSS Commands to Manage Guardian Objects
- 5 Interoperating Between Programming Environments
- 6 OSS Porting Considerations
- 7 Porting UNIX Applications to the OSS Environment
- 8 Migrating Guardian Applications to the OSS Environment
- General Migration Guidelines
- C Compiler Issues for Guardian Programs
- Using New and Extended Guardian Procedures
- Using OSS Functions in a Guardian Program
- Interoperating With OSS Programs
- Starting an OSS Program From the Guardian Environment
- C Compiler Considerations for OSS Programs
- Porting a Guardian Program to the OSS Environment
- How Arguments Are Passed to the C or C++ Program
- Differences in the Two Run-Time Environments
- Which Run-Time Routines Are Available
- Use of Common Run-Time Environment (CRE) Functions
- Replacing Guardian Procedure Calls With Equivalent OSS Functions
- Which IPC Mechanisms Can Be Used
- Interactions Between Guardian and OSS Functions
- 9 Porting From Specific UNIX Systems
- 10 Native Migration Overview
- 11 Porting or Migrating Sockets Applications
- 12 Porting Threaded Applications
- A Equivalent OSS and UNIX Commands for Guardian Users
- B Equivalent Guardian Commands for OSS and UNIX Users
- C Equivalent Inspect Debugging Commands for dbx Commands
- D Equivalent Native Inspect Debugging Commands for dbx Commands
- E Standard POSIX Threads Functions: Differences Between the Previous and Current Standards
- Glossary
- Index
Interoperating Between User Environments
Open System Services Porting Guide—520573-006
4-7
Factors Affecting Shell Operation
Functions are similar to scripts, but without the overhead of searching the file system
for the script file. A function provides the ability to use the command-line parameters
from its invocation and to use any built-in or program. The currently defined functions
can be listed using the typeset -f command.
The following are examples of aliases and functions you can use in the OSS
environment:
stty Settings
The stty command allows you to specify terminal-control character values such as
backspace, linebreak, and End-of-File. The control character values can be printed
using the stty -a command. The following are sample stty commands:
stty eof ^D sets the End-of-File (EOF) control character to Ctrl-D.
stty erase ^H sets the erase character or backspace control character to Ctrl-H.
Line and History Editing
The OSS shell provides two command-line editing modes: escape activated and fc
(FIX command) activated. The following paragraphs describe editing command lines
and history files. For a tutorial-style discussion of editing command lines and history
files, refer to the Open System Services User’s Guide.
VISUAL or EDITOR Variables
When you press the Escape key, the built-in, shell command edit mode is activated.
The editor used is vi, emacs, or GNU emacs (gmacs). In this editing mode, either the
current command or a command from the history file can be edited and then executed.
You can activate this facility either by setting one of the vi, emacs, or gmacs options
with the set command, or by setting the VISUAL or EDITOR variables.
Alias or Function Description
alias h=history
Establishes the h alias for the command
history.
alias rename= ’mv’
Establishes an alias, specifying rename as
a new name for the mv command.
function ll {ls -l $@ ;} Establishes the ll function, which
produces a long listing for the files
specified in the command line.
function lm {ls -l $@ | more ;} Establishes the lm function, which
produces a long listing for files specified in
the command line and directs output to the
more command.
Note. The OSS shell has a default setting for the stty End-of-File (EOF) value of ^Y. On
most UNIX systems, the default value is ^D.