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
Porting UNIX Applications to the OSS Environment
Open System Services Porting Guide—520573-006
7-30
Locales in OSS Client/Server Applications
locale(1) reference pages either online or in the Open System Services Shell and
Utilities Reference Manual and to the setlocale(3) and localeconv(3)
reference pages either online or in the Open System Services Library Calls Reference
Manual.
Locales in OSS Client/Server Applications
For homogeneous client/server applications in the OSS environment, Open System
Services provides the setlocale_from_msg() function to enable a server to receive
a client’s locale information, along with messages from $RECEIVE.
If a client that is not internationalized communicates with an internationalized server,
the only locale available is the C/POSIX default locale. If an internationalized client
communicates with a server that is not internationalized, the result is undefined.
To change a server’s locale to match the locale associated with a client’s message, the
server must specify that it is to receive locale information, with the following steps:
•
Use FILE_OPEN_ option <13> (locale support) when opening $RECEIVE. This
option specifies that data messages are to have locale information sent with them
and enables setlocale_from_msg() to adopt the locale of a client. After doing
a READUPDATE[X] operation on the $RECEIVE file, the server can adopt the
locale of a client from information sent with a WRITE or WRITEREAD message
from the client.
•
When the server processes a client’s request, call setlocale_from_msg() to
change the server locale to match that of the client before executing any other
locale-sensitive function.
Refer to the setlocale_from_msg(3) reference page either online or in the Open
System Services Library Calls Reference Manual for more information.
Interoperability Between OSS and Guardian Locales
Open System Services provides two functions that enable interoperability between the
OSS and Guardian locales. The set_env_from_defaults() and
set_defaults_from_env() functions preserve the locale information of a parent
process in one environment, and allow a child process in the other environment to
inherit the parent’s locale information.
To enable locale interoperability between the OSS and Guardian environments, HP
has enhanced the =_DEFAULTS DEFINE in the Guardian environment. The
=_DEFAULTS DEFINE attributes now include the locale environment variables defined
by the POSIX standards and the XPG4 specifications.
For more information about using the set_env_from_defaults() and
set_defaults_from_env() functions and the locale environment variables, refer to
the Software Internationalization Guide.