Guardian User's Guide

Displaying Version and System Information
Guardian User’s Guide—425266-001
18-2
Task 2: Select Files for VPROC Processing
The following example shows how, from the TACL program, to find the object file for
the version of the File Utility Program (FUP) that you use:
In this example, the file your system refers to when starting FUP is
$SYSTEM.SYS00.FUP. Now you should stop this FUP process, as shown:
Related product files should also be in the same subvolume as the FUP object file.
Task 2: Select Files for VPROC Processing
VPROC can display information about product files with the following file codes:
Most of the time you will be interested in the object files for a product. An object file is
a program file on disk, such as FUP, TEDIT, or c89, that you can run as a process.
Files in the OSS file system can have only the file codes listed previously, so you need
not select OSS product files based on their file code. To determine the file code of a file
in the Guardian file system, use the FILEINFO command from a TACL prompt, as
described in Section 3, Managing Files With TACL
.
Files can be stored either singly or in sets called ar-format archive files. An ar-format
archive file is normally used only in the OSS file system and on UNIX systems. If you
request version information for an ar-format archive file that contains no Binder-format
object files, VPROC returns only the timestamp of the most recently modified file in the
archive file.
1> fup /nowait, name $stein/
2> status $stein
System \FORTY
Process Pri PFR %WT Userid Program file Hometerm
$STEIN 9,145 135 P 000 6,66 $SYSTEM.SYS00.FUP $ZTN1.#PTY0A9Q
Swap File Name: $GERT.#0295
3> stop $stein
File Code Content
0Binary files
100 Executable (TNS or TNS/R COFF format) nonnative object files
180 Guardian C data files, or OSS regular files containing text
510 Standard microcode files
700 TNS/R native (COFF or ELF format) relinkable or executable object files
860 TNS/R millicode files
870 TNS/R millicode files
880 TNS/R millicode files