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-7
Moving Source Code
page either online or in the Open System Services Shell and Utilities Reference
Manual.
Moving Code to the OSS Environment
The following example shows how to move source code from a UNIX workstation to
the OSS environment. (Commercial software, freeware, and shareware utilities are
available for Telnet terminal emulation and file transfer protocol, or FTP, use from a PC
running the Microsoft Windows operating system.)
For the purposes of the example, assume your user ID is “nih00.user”.
First, from your workstation prompt, use the telnet command to access the OSS
host system by name (oss_host). User input in this subsection appears in courier
type:
telnet oss_host
For more information about the telnet command, refer to the telnet(1) reference
page either online or in the Open System Services Shell and Utilities Reference
Manual.
Your system returns messages similar to the following:
Welcome to host_name.subdomain.domain.zone
[PORT $ZTC0 #23 WINDOW $ZTN0A.#PTAAAE3]
TELSERV - T9553H01 - (01OCT2004)
Available Services:
OSS TACL EXIT
Enter Choice>
Enter your choice after the prompt:
>TACL
Log on to the OSS system after the TACL prompt:
TACL1> logon nih00.user
Password: XXXXXXXX
Execute the Guardian osh utility to start a Korn-compatible OSS shell:
TACL2> osh
Create a directory named samples:
$ mkdir samples
Note that the OSS shell prompt might not be $.
Open another window on your workstation with terminal emulation and copy the source
for a program from your workstation to your OSS directory:
$ cd /home/nih00/samples