SCF Reference Manual for the Kernel Subsystem

Currently the maximum number of available TLEs is:
• 3600 per CPU For G-series systems
• 20000 per CPU For H and J-series systems
The value of n specified in the ALTER command should be between 101 and the maximum
available TLEs. Otherwise, the ALTER command will fail and the following error message will
be displayed:
KERNEL E00110 The value for TLE_LIMIT for $ZZKRN is out of
the accepted range of 101 to max-available TLE.
You cannot alter the TLE limit above maximum avalable TLEs.
To use this attribute, see “Changing the System TLE Limit Attribute” (page 36).
AUTO_RETRY_ON_ERROR_654 n
specifies how the system handles situations when a request buffer is modified. As of the J06.09
and H06.20 RVUs, depending on the value of the AUTO_RETRY_ON_ERROR_654 attribute,
the system either immediately reports file-system error 654 or retries sending the request up to
three times:
• A value of ON configures the system to retry sending the request up to three times whenever
the system detects that a request buffer has been modified. The message or I/O operation
completes successfully if a subsequent retry delivers the request to the server CPU without
indication that the request was modified again during the life span of that retry.
However, in abnormal situations in which a client repeatedly modifies the request buffer
and all retries fail due to request buffer modifications, the system will complete the message
with the file-system error 654. Therefore, enabling automatic retries when request buffers
are modified does not mean that the system never reports file-system error 654. This
alternative system behavior simply restricts the reporting of file-system error 654 to clients
that may modify a request buffer multiple times after starting a new request.
• A value of OFF configures the system to immediately report file-system error 654 whenever
the system detects that a request buffer has been modified. OFF is the default setting.
To use this attribute, see “Changing Software Data Integrity Checking” (page 37).
ALTER SUBSYS Considerations
• Wild cards are not supported for the ALTER SUBSYS command.
• If the ALTER command is not successful, SCF returns an error message saying the requested
operation was not completely successful. SCF also sends a warning message identifying each
failed operation. To correct or change an attribute in response to a warning message, enter
another ALTER command.
• If $ZZKRN cannot find a specified file on $SYSTEM.SYSTEM, it searches for the file on the
current $SYSTEM.SYSnn. This search algorithm allows you to change the operating system
version yet keep the same attribute values for a process.
• When specifying a file name, avoid including the system name (unless the file must reside on
a specific system). Omitting the system name allows the process to be system-independent.
ALTER SUBSYS Examples
• This example shows how to specify new EMS template files:
-> ALTER SUBSYS $ZZKRN, &
RESIDENT_TEMPLATE $SYSTEM.TEMPLATE.TNEW, &
NONRESIDENT_TEMPLATE $SYSTEM.TEMPLATE.NRTNEW
• This example shows how to set the time-zone offset for a location in California:
96 SCF Commands for the Kernel Subsystem