TS/MP 2.5 System Management Manual

Defaults for file name expansion are based on values you specify for the CMDVOL command and
the SET PATHWAY NODEINDEPENDENT attribute. See the command descriptions in “CMDVOL
Command” (page 138) and “SET PATHWAY Command” (page 159).
create-spec
specifies one of these file creation attributes or open attributes:
DescriptionFile-creation or Open Attribute
Specifies the size of the file extents allocated to the file.
pri-extent-size and sec-extent-size can be integers
from 1 through 65,535.
EXT
Specifies the exclusion mode for logical-unit. The
exclusion mode determines how other processes can access
the file identified in logical-unit.
EXCLUSIVE
nl
SHARED
nl
PROTECTED
Specifies the access mode for logical-unit. The access
mode designates what file operations can be performed.
I/O INPUT OUTPUT
Assigns a file code to logical-unit. file-code can be
an integer 0 through 65535. If you omit file-code, the value
is 0.
CODE file-code
Specifies the length of the records in logical-unit. record-size
can be an integer from 1 through 4072.
REC record-size
Sets the size of the data blocks for logical-unit. block-size
can be an integer from 1 through 4096.
BLOCK block-size
For more information about the ASSIGN attribute, see the ASSIGN command in the TACL Reference Manual.
AUTORESTART number
specifies the number of times that the PATHMON process attempts to restart a server process within
a fixed 10-minute interval after an abnormal termination, such as a call to the Guardian ABEND
procedure.
number can be a value from 0 through 32,767. If you omit this attribute, the default is 0.
After an abnormal failure of a server process, the action caused by this option is equivalent to using
the START SERVER command and is effective for static server processes only.
This attribute is valid for Guardian and OSS server processes.
CPUS primary:backup | cpu | cpu (cpu-wt)
specifies the list of processors in which the server processes in this server class run. The processors
can be specified either as primary and backup processor pairs, or as a list of single CPUs; the two
types of lists cannot be mixed.
primary:backup
The PATHMON process uses this sequence of pairs in the order specified as it creates the server
processes. You can define a maximum of 16 pairs of processor numbers; processor numbers for
backup CPUs need not be unique.
If a primary processor is down, the PATHMON process exchanges the roles of the primary and
backup CPUs. For example, if you define these:
CPUS (0:1, 2:3, 4:5)
and processor 2 is down, the PATHMON process starts the servers in CPUs 0, 3, and 4.
cpu
The PATHMON process uses this sequence of individual CPUs in the order specified as it creates
the server processes. A processor can be specified only once in the list; you can define a maximum
of 16 processor numbers. The BACKUPCPU attribute is not included in a PARAM message if a single
processor list includes only one processor.
If a processor is down, the PATHMON process uses the next processor in the list. For example, if
you define these:
CPUS (1, 3, 5)
188 SERVER Commands