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-12
Editing Files From OSS
following table shows some common file operations, the OSS shell utility for those
operations, and examples of the same operations using a FUP command:
Editing Files From OSS
OSS has two primary editors: vi and ed utilities. vi is a screen-oriented editor; ed is a
line-mode editor. These editors are roughly equivalent to Guardian TEDIT and EDIT in
line mode. The Open System Services User’s Guide describes these OSS editors in
detail. Whenever possible, use the OSS (UNIX) editors for OSS files and the Guardian
editors for Guardian files.
Most OSS utilities can access Guardian type 101 files (EDIT files). These files can be
read from OSS and can also be written from OSS by using OSSTTY. You can use the
OSS editors to read and write Guardian type 180 files. If you want to edit a type 101
file using an OSS editor, you must first convert the file to type 180 with the Guardian
utility EDITTOC. If necessary, later convert it back to type 101 with the Guardian utility
CTOEDIT to use a Guardian editor. See Editing Files From TACL on page 4-16 for
more information on using EDITTOC and CTOEDIT.
Printing Files From OSS
You can use the OSS lp utility to print files, the lpstat utility to display the status of
print jobs, and the cancel utility to remove print jobs from the print queue. The
function of lp is equivalent to using FUP COPY to a spool location. lpstat is
equivalent to PERUSE. lpstat and cancel are equivalent to SPOOLCOM.
Examples
The following example prints the file testprog.c. The -d parameter specifies the
spool destination laser for the output:
lp -d laser testprog.c
Use the following command to list the status of all spool jobs in the print queue:
lpstat
Operation OSS Shell Utility FUP Command
Copies a file. cp report reprtsav FUP DUP REPORT, REPRTSAV
Displays filenames. ls FUP FILES
Displays file
attributes.
ls -l oldfile FUP INFO OLDFILE
Deletes file. rm oldfile FUP PURGE OLDFILE
Renames file. mv oldname newname FUP RENAME OLDNAME,
NEWNAME
Changes
protection.
chmod u=rwx testfile FUP SECURE TESTFILE, “OOOO”