Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Figure 20 (page 197) illustrates the behavior when OSSTTY is run as a server named $ZTTY before
starting an application program explicitly designed to use it, such as mysample3 in the following
command set:
RUN OSSTTY / NAME $ZTTY, IN $VHS,OUT $DATA.OSSLOG.EDITFIL,
TERM $VHS, NOWAIT / -server
OSH -p "/usr/mysample3"
For information about using OSSTTY through the OSH command, see the osh(1) reference page
either online or in the Open System Services Shell and Utilities Reference Manual. For an example
of a TACL script using OSSTTY, see the Open System Services Programmer’s Guide.
Figure 20 Redirecting All OSS Standard Files
Controlling the Maximum Number of Files
The fileset catalog determines the number of regular files and directories (the number of inodes) a
fileset can contain. The fileset catalog is kept in the PXINODE file described in “OSS Catalog Files”
(page 85) and “Changing the Fileset Catalog” (page 157).
When a fileset catalog reaches its configured maximum number of inodes, application program
errors might occur unless additional inode entries are allowed in the catalog. The fileset catalog
can reach its maximum even when space remains for new file creation on disk volumes in the
storage pool.
A catalog’s approximate maximum number of inodes for files is determined by the fileset
MAXINODES attribute. MAXINODE defaults to 500,000 inodes for a new fileset unless the SCF
ADD FILESET command was used to set it. For a fileset created under a version of the OSS Monitor
prior to G11, the MAXINODES value is determined by applying a formula to the number of inodes
currently in use; the formula usually allows at least a 10 percent increase in the number of inodes
before the maximum is reached.
The number of inodes in a catalog also affects fileset recovery time. The more inodes in a fileset,
the more time that fileset recovery takes when the SCF DIAGNOSE FILESET command is used. A
Controlling the Maximum Number of Files 197