Note: This information is online help text for the System Management Interface Tool (SMIT) and is not for general reading.
The system is represented in the customized device configuration database as a device named sys0 and is described as the System Object. Various parameters of the operating system appear as attributes to this device. You can view and modify these parameters.
The options in this submenu allow the 64-bit application environment to be enabled either immediately or at system restart.
Select this option to immediately enable the 64-bit application environment. This action is reversible only at system restart.
The options in this submenu alter the /etc/inittab file to specify whether or not the 64-bit application environment is enabled at system restart.
Select Yes to enable the 64-bit application environment at system restart. Select No to disable this option.
Allows you to implement an RMALLOC heap that you can tune. You can specify a value, in Kbytes, between 0 through 1048576. This corresponds to 0 KB to 1 GB, which is the maximum value. This value takes effect only after a reboot and bosboot (which must both happen, in this order).
You can also run the vmtune command to see the current usage of RMALLOC heap.
The maximum size, in 4KB blocks, that the ARG/ENV list is allowed when running exec subroutines. This prevents exec subroutines from failing if the argument list is too long. You can specify a value in the range of 256 through 1024. The default value is 256. Specifying a higher value may constrain system memory resources. This change takes affect immediately and is preserved over boot.
Starts or stops the operating system from using Dynamic Processor Deallocation. The default is "Disabled".
Dynamic Processor Deallocation allows the operating system to stop using a processor that is failing. On some machines, the firmware can detect and gather errors. When the processor error count reaches a threshold that the firmware recognizes could cause a component to fail, the firmware returns an error report to the operating system. The operating system then logs the report. For some failures, the operating system on a machine with many processors stops using the failing processor and deallocates it. Until the failing processor is replaced, the firmware flags the processor for persistent deallocation whenever the machine is rebooted.
The version of Run-Time Abstraction Services (RTAS) installed on this machine. RTAS acts as an interface between the operating system and the firmware provided by the platform. It allows the operating system to perform functions usually performed by the hardware, such as starting and stopping processors, independent of the particular platform on which it is installed.
The frequency of the system bus in cycles per second.
Starts or stops the operating system from using Dynamic Processor Deallocation. The default is "Disabled".
Dynamic Processor Deallocation allows the operating system to stop using a processor that is failing. On some machines, the firmware can detect and gather errors. When the processor error count reaches a threshold that the firmware recognizes could cause a component to fail, the firmware returns an error report to the operating system. The operating system then logs the report. For some failures, the operating system on a machine with many processors stops using the failing processor and deallocates it. Until the failing processor is replaced, the firmware flags the processor for persistent deallocation whenever the machine is rebooted.
Allows you to enable or disable CPU sparing.
Enable CPU sparing to automatically stop a failing CPU resource and replace it with a spare CPU. This action is not obvious to users and to user-mode applications. If you enable CPU sparing and a spare CPU is not available, the failing CPU will be stopped.
CPU sparing and CPU guard work together. Enable CPU sparing behaves slightly different when CPU Guard is disabled. If a spare CPU is available, the replacement succeeds. If a spare CPU is not available, it does not stop the failing CPU and the number of CPUs in the system remains the same.
Disable CPU sparing to avoid degrading system performance when installed applications sensitive to performance can run without a CPU and would be impacted by bringing a spare CPU online.
To set tuning parameters using tuning commands in scripts called during a reboot, select "Enable". Select "Disable" to force tuning parameters to be set to values in the /etc/tunables/nextboot file.
Provides options for displaying, specifying, or changing the parameters of lost I/O detection. This function detects processes that are waiting for local block I/O that do not terminate.
To run the system with Lost I/O Detection, select "enable". The default is "disable". The selected choice remains in effect until you change it. You must have root user authority to change this value.
The detection threshold associated with the different actions. You can specify a range between 1 through 50000 minutes. The default value is 10 minutes. A change goes into effect immediately and remains in effect until you change it again.
To display a warning message on the console specified as the terminal device, select "enable". The default is "disable". A change goes into effect immediately and remains in effect until you change it again.
The terminal device on which warning messages are displayed. The specified terminal can be the console or an available TTY. The default terminal is the console (/dev/console). A change goes into effect immediately and remains in effect until you change it again.
To create a system dump and reboot the system whenever lost I/O is detected, select "enable". This action only occurs if lost I/O detection is also enabled. The default is "disable". A change goes into effect immediately and remains in effect until you change it again.
To restore the default values for the lost I/O detection, select "enable". The default is "disable".
The granularity at which changes to entitled processor capacity can be made. This value is expressed as a fraction of a physical processor and can be between 0.01 and 1. The default value is 1.
Indicates whether the partition is capped. If the partition cannot receive additional execution cycles, the value is "true". If the partition can receive additional execution cycles, the value is "false". The default value is "true".
If the "Variable processor capacity weight" is set to 0, the partition is considered "soft-capped." The partition is capped, and overrides a value of "false" in the "Partition is capped" attribute.
Indicates whether the partition is dedicated. If the partition is not using shared processors, the value is "true". If the partition is using shared processors, the value is "false". The default value is "false".
The number of processor units this LPAR is entitled to receive. This value cannot be below 0.
The minimum entitled capacity needed to power on the partition. This value cannot be below 0.
The maximum entitled capacity that can be assigned to the partition. This value cannot be below 1.
The relative priority given to this partition, which controls how idle cycles are assigned to it. This value can be between 0 and 255. The default value is 0.
If the "Variable processor capacity weight" is set to 0, the partition is considered "soft-capped." The partition is capped, and overrides a value of "false" in the "Partition is capped" attribute.
The unique identifier for this system. This ID is generated during the boot process. On some systems, this value will be same as the Partition ID.
The unique identifier for each partition in a partitioned system. This ID is generated during the boot process. On some systems, this value will be same as the System ID.
The maximum length allowed for user or group names on the system. The value has a range of 9 to 256. The default value is 9. This value includes the trailing NULL character for the user or group name, therefore, the actual limit of printable characters is one less than the specified value. A reboot of the system is required for the change to take affect.
Indicates whether AIX has enabled Stack Execution Disable (SED) mode, which can be used to disable the execution of code in the various data areas of a process. SED protection is only supported on the 64-bit kernel. SED protection provides four system-wide modes of operation:
Indicates the mode of behavior for NFS4 ACLs for deletion bits. In secure mode, NFS4 ACLs will be generated with DELETE bits set. Compatibility mode does not generate these DELETE bits as some other implementations will not accept ACLs containing these bits. A reboot is required after modifying this mode before changes will take effect.
Federal Information Processing Standards Publications (FIPS PUB) 140-2 is a US government standard for implementations of cryptographic modules. When running in FIPS mode, operating system will use FIPS 140-2 validated cryptographic library, and only allow FIPS-approved algorithms. The options in this submenu can be used to view or change system cryptographic operational mode.
This option diplays the current system cryptographic operational mode setting in ODM database. It may or may not match the mode running in operating system kernel.
By selecting option "FIPS" or "NON_FIPS", you can change the system cryptographic operational mode setting in ODM database. You can change this mode setting at any time, and it only takes effect into kernel when system is rebooted.