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-16
Managing Files From TACL
OSS utilities enhanced to access a Guardian process would specify /G/srvr or
/G/5,48 for the previous commands. The OSS command line would look like one of
the following:
kill -s GUARDIAN /G/SRVR
kill -s GUARDIAN /G/5,48
Managing Files From TACL
Within TACL, you use the FUP command to manipulate files. The following table
shows some FUP commands for a few common Guardian file operations:
Editing Files From TACL
ASCII text files in the OSS environment have the same format as these files have on a
UNIX system: a string of bytes with each line ending with a line-feed character (0X0A).
Most ASCII text files in the Guardian environment are in a special format, called “EDIT
format” or “type 101.” Normally, this file type is used for text input and text output. Refer
to the PS Text Edit and PS Text Format User’s Guide for information on editing TEDIT
or EDIT format files in the Guardian environment.
If you are not familiar with the Guardian editor, TEDIT, and are more comfortable using
OSS (UNIX) editors, you might want to move the EDIT-format file from the Guardian
environment to the OSS environment, edit the file with the vi utility, and then move the
file back to the Guardian environment. The following are descriptions of how to make
these conversions.
For detailed user information on using the vi utility in the OSS environment, refer to
the Open System Services User’s Guide, which contains tutorial and advanced user
information about the vi utility.
FUP Command Operation
FUP INFO REPORT, DETAIL Displays all information about the file REPORT.
FUP DUP REPORT, REPRTOLD Copies the file REPORT to REPRTOLD.
FUP RENAME TESTFILE, TESTSAVE Renames the file TESTFILE to TESTSAVE.
FUP PURGE REPRTSAV Purges the file REPRTSAV.
FUP PURGE $DATA01.OUTPUT.* Purges the complete subvolume OUTPUT on
volume $DATA01.
FUP SECURE TESTPROG, “AOAO” Changes file protection so that any user can read
or execute the file TESTPROG (only the owner
can write or purge the file). The order of
attributes is read, write, execute, and purge.