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
The Development Environment
Open System Services Porting Guide—520573-006
2-8
Using Archiving Utilities
Use the ftp utility to access the OSS host system:
$ ftp oss_host
...
After the FTP prompt, change directory to your samples directory:
ftp> cd /home/nih00/samples
Still from the FTP prompt, copy the printargs.c file:
ftp> put printargs.c printargs.c
Quit FTP by entering the following at the FTP prompt:
ftp> quit
From your OSS window, compile the program as follows:
$ c89 -o printargs printargs.c
Still from your OSS window, test the program:
$ printargs arg1 arg2 arg3 arg4
Transferring Files Back to the Workstation
To transfer files back to your workstation, follow the steps below. These steps verify the
working directory at the OSS window and display the output from the pwd utility. Then
the source file is transferred back to the workstation. User input in this subsection
appears in courier type.
$ cd /home/nih00/samples
Use FTP to access the OSS host system:
$ ftp oss_host
logon nih00.user
Password: XXXXXXXX
At the FTP prompt, change the current directory to your samples directory:
ftp> cd /home/nih00/samples
Still at the FTP prompt, copy the file printargs.c to printargs.c:
ftp> get printargs.c printargs.c
Quit the FTP utility by entering the following at the FTP prompt:
ftp> quit
Using Archiving Utilities
Archiving utilities can simplify movement of large numbers of files between systems.
Open Systems Services supports tar, cpio, and pax (pax is the standard archiving
utility in the OSS environment). tar and pax are discussed in the following
subsections; cpio is not discussed in this guide because it is rarely used.