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
Useful Porting Tools
Open System Services Porting Guide—520573-006
3-4
Open Systems Portability Checker (OSPC) Tool
GNU, and Zortech compilers. It supports the Windows, OS/2 2.1, HP-UX, SunOS,
Solaris, and VAX/VMS operating systems, and many other UNIX variants. Its
capabilities and features are comprehensive, and it is easy to use.
Open Systems Portability Checker (OSPC)
Tool
Open Systems Portability Checker (OSPC) is a programming tool developed by
Knowledge Software. A powerful program for the UNIX workstation, OSPC checks
source code for strict ISO/ANSI C compliance, more extensively than C compilers or
lint programs.
This checking tool processes both U.S. Government and European C validation suites.
OSPC is particularly valuable in high-integrity, security-critical applications. The OSPC
set of checking profiles covers the most important and popular standards: ISO/ANSI C,
POSIX.1, POSIX.2, POSIX.4, XPG3, OSF/1 NFS, and more.
This tool is easy to adopt into your current development environment. By adding a few
lines of code to an existing make file, you enable standards checking to take place
whenever the application is built. With OSPC’s configurability, you can create and add
new platform profiles and modify existing ones to comply with future development
requirements.
You can configure OSPC to check the portability of a program being moved from one
platform to another. You identify on which platform the application already runs and the
target platform. It can use two rule bases at once: a from and a to. This capability
allows OSPC to identify the exact delta between two specific environments.
OSPC accesses a database of platform profiles to remove warnings that do not relate
to the target platform. It also uses information about characteristics of the source
platform to filter out warnings on constructs that might be considered a problem on the
target platform.
Conformance checking by OSPC is done in three stages:
1. OSPC performs a thorough check of the application’s source code for standards
compliance. The degree of checking is configurable, made possible with over 100
command-line options relating to various processors, compilers, and operating
systems.
2. OSPC performs cross-unit checks for consistent interfaces between application
and system services. Here, object-type consistency, function parameters, and
macro definitions are checked.
3. OSPC performs dynamic checking, during which all calls to system services are
monitored with regard to portability standards.
OSPC has two main checkers, packaged separately: static and dynamic. The static
checker uses configuration files, which provide information on each standard. The
checking can be quite thorough, or you can choose less-stringent checking.