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-6
Moving or Accessing Source Files
•
D40 and later TNS/R native environment (OSS and Guardian)
•
G-series TNS/R native environment (OSS and Guardian)
•
H-series TNS/E environment (Guardian only)
The TNS/R native C compilation tools are available in the TNS/R and TNS/E native
environments. The TNS/E native C compilation tools are available only in the TNS/E
native environment.
Moving or Accessing Source Files
The following subsections describe:
•
Using Network and File Management Utilities on page 2-6
•
Moving Source Code on page 2-6
•
Using Archiving Utilities on page 2-8
You might be moving files to and from the OSS environment while cross-compiling.
Many choices are available, as detailed in Compilation Options for C and C++
Programs on page 2-3.
Using Network and File Management Utilities
Network utilities such as the Network File System (NFS), ftp, and telnet are used
for transferring files between systems and PCs or workstations and should be available
to you. For more information about NFS, refer to the Overview of NFS for Open
System Services; for more information on the ftp and telnet network utilities, refer
to the Telserv Manual.
Moving Source Code
Source code can either be worked on through NFS or be moved between systems
using the ftp utility.
The ftp Utility
The ftp utility is used to transfer files between two machines. It provides
subcommands for listing remote directories, changing the current local and remote
directory, transferring multiple files in a single request, creating and removing
directories, and escaping to the local shell to perform shell commands. The ftp utility
also provides security by sending passwords to the remote host and permitting
automatic login, file transfer, and logoff.
The syntax for the ftp utility is:
ftp [-dginv] [host]
For more information about using the ftp(1) utility, including many examples and the
required syntax when using the ftp subcommands, refer to the ftp(1) reference