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-14
Guardian Commands for the UNIX User
In the following example, the first and second command lines compile the C source
code files test1.c and test2.c. The -c flag specifies the creation of only object
files: test1.o and test2.o. The third command line binds the two object files
together to create an executable file. The -o flag specifies the name of the executable
file (tester) to produce:
c89 -c test1.c
c89 -c test2.c
c89 -o tester test1.o test2.o
The Guardian TNS/R native equivalent is similar to the following:
NMC /IN TEST1C, OUT LIST1/ TEST1o
NMC /IN TEST2C, OUT LIST2/ TEST2o
NLD -o TESTER TEST1o TEST2o
The Guardian TNS/E native equivalent is:
CCOMP /IN TEST1C, OUT LIST1/ TEST1o
CCOMP /IN TEST2C, OUT LIST2/ TEST2o
ELD -o TESTER TEST1o TEST2o
Using the Guardian TNS C compiler tools, the equivalent would be:
C /IN TEST1C, OUT LIST1/ TEST1o; WIDE
C /IN TEST2C, OUT LIST2/ TEST2o; WIDE
BIND /IN TESTERB/
The contents of the file TESTERB would be as follows:
SELECT CHECK PARAMETER OFF
ADD * FROM TEST1O
ADD * FROM TEST2O
SELECT SEARCH $SYSTEM.SYSTEM.CWIDE
SELECT RUNNABLE OBJECT ON
SELECT LIST * OFF
SET HEAP 20 PAGES
BUILD TESTER
Refer to the C/C++ Programmer’s Guide for detailed information on compiling and
binding programs in the OSS environment.
Guardian Commands for the UNIX User
This subsection is intended for UNIX users who may occasionally directly use
Guardian commands to manipulate Guardian objects. It contains information about
working with processes and files using Guardian commands from within a Guardian
environment. Appendix B, Equivalent Guardian Commands for OSS and UNIX Users,
contains a table of many common OSS shell commands and their functionally
equivalent Guardian commands.