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
Migrating Guardian Applications to the OSS
Environment
Open System Services Porting Guide—520573-006
8-9
Equivalent OSS Commands for Compiling Guardian
Programs
Table 8-2. Common Guardian Compiler Tasks and How Similar Tasks Are
Achieved in the OSS Environment (page 1 of 2)
Guardian TNS Environment
Action Equivalent OSS Action
OSS Native c89 Flags to
Use
Run Accelerator (G-series) or
Object Code Accelerator (H-
series) program
Optimize a program file -O
Run C compiler without
specifying a RUNNABLE
pragma
Compile, but do not link,
specified source files
-c
Display detailed information
from the C compiler, Binder,
and Accelerator (G-series) or
Object Code Accelerator (H-
series)
Display minimal information
by default
(none)
Specify arguments on
Accelerator (G-series) or
Object Code Accelerator (H-
series) command line
Specify an optimization level -Woptimize=N
Specify arguments in a
Binder command file
Pass an argument string to
the linker
-Wnld=args (TNS/R non-
PIC object file)
-Wld=args (TNS/R PIC
object file)
-Weld=args (TNS/E object
file)
Specify a pragma on the C
compiler command line
Pass an argument string to
the C compiler
-Wansistreams
Run the SQL/MP compiler Invoke the SQL/MP compiler
by running the c89 utility
with the -Wsqlcomp flag
-Wsqlcomp=args
Run the SQL/MX compiler Invoke the SQL/MX compiler
by running the c89 utility
with the -Wmxcmp flag
-Wmxcmp=args
Compile Guardian module by
default
Specify that the module is to
be compiled as a Guardian
module
-Wsystype=guardian
Select static binding (default) Select static linking (default
is dynamic)
-WBstatic
Produce specified executable
file
Specify output file by name -o outfile
Use C compiler command
line to define option
Define preprocessor symbol -D symbolname
[=value]