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-18
Printing Files From TACL
After moving an OSS format file to the Guardian environment, converting a file to EDIT
format is done with the Guardian utility CTOEDIT, as follows:
CTOEDIT fromfile, tofile
Printing Files From TACL
ASCII text files or EDIT-format files are printed by copying the file to a spool location. A
spool location normally is named $S, followed by a printer name: for example,
$S.#LASER.
The command to print the file $DATA01.REPORTS.JAN94 to the spool location
$S.#LASER is as follows:
FUP COPY $DATA01.REPORTS.JAN94, $S.#LASER
OSS Pathname and Guardian Filename
Conversions
Two utilities are available for you to translate OSS pathnames to Guardian filenames
and Guardian filenames to OSS pathnames. The gname utility converts OSS
pathnames into Guardian filenames; the pname utility converts Guardian filenames into
OSS pathnames.
The following gname command:
gname /bin/sh
results in the following output:
gname: /bin/sh ---> \KT22.$XPG.ZYQ00000.Z00005LS
The following pname command:
pname \$XPG.ZYQ00000.Z00005LS
results in the following output:
pname: $XPG.ZYQ00000.Z00005LS ---> /bin/sh
Use the ls utility in the OSS environment to list filenames in your OSS directories; use
the FILES command in the Guardian environment to list filenames in your Guardian
subvolumes.
To list process names associated with commands being executed, use the Guardian
STATUS command for both OSS and Guardian process names. See Guardian
Commands for the UNIX User on page 4-14 for a sample output of the Guardian
STATUS command. To obtain the status of only OSS processes, use the OSS ps
utility, discussed under OSS Commands for the Guardian User on page 4-10.
OSS processes are identified by the program filename, with subvolume names
beginning with ZYQ. The program filename for the OSS process can be translated