Installation Guide and Reference

bosinst.data File Stanza Descriptions

This section describes the contents of the bosinst.data file. Example files follow the stanza descriptions. (See bosinst.data File Example.)

control_flow Stanza

The control_flow stanza contains variables that control the way the installation program works:

Variable	Decription
CONSOLE	Specifies the full path name of the device you want to use as the console. If this value is Default, and you are performing a nonprompted installation, then the console is set to /dev/lft0, if this device exists. If /dev/lft0 does not exist, the console is set to /dev/tty0. (Instructions for which key to press are displayed on the screen.) If you change the PROMPT variable to no, you must specify a console here.
INSTALL_METHOD	Specifies a method of installation: migrate, preserve, or new and complete overwrite. The default value is initially blank. The installation program assigns a value, depending on which version of AIX was previously installed. See Introduction to Base Operating System Installation for more information. The default method of installation is migrate if a previous version of the operating system is on the machine. If no previous version exists, the default method is new and complete overwrite.
PROMPT	Specifies whether the installation program uses menus from which you make choices. The possible values are yes (default) and no. Note You must fill in values for all variables in the locale stanza if you set the PROMPT variable to no. Similarly, if PROMPT equals no, you must supply values for all variables in the control_flow stanza, with two exceptions: the ERROR_EXIT and CUSTOMIZATION_FILE variables, which are optional. Attention: Fill in values for all variables in the target_disk_data stanza if you set the PROMPT variable to no. The BOS installation program assigns target disks for blank variables. You can lose data if the installation program assigns a disk where you store data.
EXISTING_SYSTEM_OVERWRITE	Confirms that the installation program overwrites existing volume groups. This variable is applicable only for a nonprompted overwrite installation. The possible values are no (default), yes, and any. no (Default) Only disks that are not part of a volume group can be used for the installation. yes Disks that contain the root volume group is used first, and if additional disks are needed for the installation, then disks that contain no volume groups are used. any Any disks can be used for the installation. When the installation is nonprompted and the target_disk_data stanza is empty, the installation process uses the value of the EXISTING_SYSTEM_OVERWRITE field to determine the disks to install on. An error message informs you if there are not enough disks matching the criteria needed to complete the installation.
RUN_STARTUP	Starts the Configuration Assistant on first boot after the BOS installation completes, if the system has a graphical interface. Starts Installation Assistant if the machine has an ASCII interface. The possible values are yes (default) and no. The no value is valid only when ACCEPT_LICENSES is set to yes.
RM_INST_ROOTS	Removes all files and directories in the /usr/lpp/*/inst_roots directories. The possible values are no (default) and yes. The /usr/lpp/bos/inst_roots directories must remain if the machine is used as a network server. To save disk space, set this value to yes if the machine is not a network server.
ERROR_EXIT	Starts an executable program if an error occurs in the installation program. The default value is blank, which signals BOS installation to use a command that is shipped on the installation media. The command starts an error message routine when the installation program halts because of an error. As an alternative to the default, you can enter the path name of your own script or command for a customized error routine.
CUSTOMIZATION_FILE	Specifies the path name of a customization file you create. The default value is blank. The customization file is a script that starts immediately after the installation program concludes.
TCB	Specifies whether you want to install the Trusted Computing Base (TCB). When you install the TCB, the trusted path, the trusted shell, and system integrity checking are installed. The TCB must be installed and initialized when the operating system is installed. The TCB cannot be installed later. By not installing the TCB, installation time is reduced. The possible values are no (default) and yes.
BUNDLES	Specifies what software bundles to install. Type the full path name of each bundle file. Be sure there is sufficient disk space and paging space on the target machine for the software you specify in the BUNDLES variable. This list of bundle file names is limited to 139 bytes. If your list of bundle file names is longer than 139 bytes, use the cat command to combine the bundle files into a single custom bundle file and enter the name of your custom bundle file in this field. If you are installing from tape, to specify system-defined bundles on the product media, use the full path name of each bundle file as follows: /usr/sys/inst.data/sys_bundles/BundleFileName If you are using a bosinst.data diskette to define your own bundle files, specify the full path name of each bundle file as follows: `/../`DirectoryName`/`BundleFileName. For example, if you put a bundle file named `mybundle` in the root directory, the full path name would be `/../mybundle.` If you are using preservation installation, create bundle files before you start the installation. Create the files in /home and specify the full path name of each bundle file as follows: /home/BundleFileName
RECOVER_DEVICES	Specifies whether to reconfigure the devices. The default value is Default. For mksysb installations, the ODM configuration database is saved in the image. The device names and attributes are automatically extracted from the database, and the BOS installation program attempts to recreate the devices the same way they were on the machine the mksysb was created on. This is normal procedure for regular mksysb restores on the same system. However, for cloning (installing the mksysb image on another system), you may not want these devices configured this way, especially for network configuration. When the mksysb image is created, the CPU ID is saved. If you are reinstalling the same system, then the device information is recovered. If the mksysb image is used to install another system, device information is `not` recovered from the mksysb image. The Default value can be overwritten. For example, if your system had the planar replaced, or you upgraded to another system, you might want to recover devices. In these cases, you can select yes in the Backup Restore menu to recover devices.
BOSINST_DEBUG	Specifies whether to show debug output during BOS installation. The value yes sends set -x debug output to the screen during BOS installation. The possible values are no (default) and yes.
ACCEPT_LICENSES	Specifies whether to accept software license agreements during the BOS installation. The default is no. To automatically accept them, set this value to yes. When the software licenses agreements are not accepted during BOS installation, Configuration Assistant or Installation Assistant prompts you to view and accept them. During a BOS installation, if this value is blank, the default of no is assumed. For mksysb installations, when ACCEPT_LICENSES is no, the user is forced to re-accept the licenses before continuing to use the system. When ACCEPT_LICENSES is set to yes, the licenses are automatically accepted for the user. If blank, the state of the licenses is the same as from when the mksysb was created.
DESKTOP	Specifies the desktop to be installed. The choice of available desktops are CDE (the default), NONE, GNOME, and KDE. If you choose GNOME or KDE, you will be prompted for the `AIX Toolbox for Linux Applications` CD.
INSTALL_DEVICES_AND_UPDATES	When installing a mksysb image to a system with a different hardware configuration, one boots from product media in order to get any missing device drivers installed. In addition, if the product media is a later level of AIX than the mksysb, software in the mksysb image will be updated. To prevent either of these additional installs from occuring, set this field to no. The default is yes.
IMPORT_USER_VGS	Specifies whether you want any user volume groups to be automatically imported after the system has been installed. The choices are yes and no.
ENABLE_64BIT_KERNEL	Specifies whether you want to enable the 64-bit kernel. The choices are yes and no.
CREATE_JFS2_FS	Specifies whether you want to create enhanced journaled file systems. The choices are yes and no.
ALL_DEVICES_KERNELS	Specifies whether to install all device and kernel filesets. The choices are yes and no.If you select no, then your system will be installed with the devices and kernel specific to your system configuration. If you select yes, then when you create a system backup of your system, you are able to use that system backup to install any system.
GRAPHICS_BUNDLE	Specifies whether to install the graphics software bundle during the BOS installation. This software bundle contains the graphics support for the Web-based System Manager and Linux desktops. The choices are yes and no.
DOC_SERVICES_BUNDLE	Specifies whether to install the documentation services software bundle during the BOS installation. This software bundle contains the Documentation Library Service software, which is used for viewing and searching online documentation. The choices are yes and no.
NETSCAPE_BUNDLE	Specifies whether to install the graphics software bundle during the BOS installation. This software bundle contains the Netscape Communicator software. The choices are yes and no.
HTTP_SERVER_BUNDLE	Specifies whether to install the graphics software bundle during the BOS installation. This software bundle installs the HTTP Web server software. The choices are yes and no.
KERBEROS_5_BUNDLE	Specifies whether to install the graphics software bundle during the BOS installation. This software bundle installs the Kerberos 5 client software. The choices are yes and no.
SERVER_BUNDLE	Specifies whether to install the AIX server software bundle during the BOS installation. This software bundle installs additional networking software, performance tools, and accounting services software. The choices are yes and no.
ALT_DISK_INSTALL_BUNDLE	Specifies whether to install the alternate disk installation software during the BOS installation. The choices are yes and no.
REMOVE_JAVA_118	Specifies whether to remove the Java 1.1.8 software from the current system when performing a migration installation. The choices are yes and no.

target_disk_data Stanza

The target_disk_data stanza contains variables for disks in the machine where the program is to install BOS. The default bosinst.data file has one target_disk_data stanza, but you can add new stanzas to install BOS on multiple disks, one stanza for each disk.

Multiple target_disk_data stanzas can exist. They define the disks that are to contain the root volume group. Only one field (PVID, SAN_DISKID, CONNECTION, LOCATION, SIZE_MB, HDISKNAME) must be non-null for BOS installation to choose a disk. The order of precedence is PVID (Physical Volume ID), SAN_DISKID, then CONNECTION (parent attribute//connwhere attribute), then LOCATION, then SIZE_MB, and then HDISKNAME. The BOS installation process uses the following logic to determine how to use the target_disk_data stanza information:

If PVID is set, BOS installation checks to see if a disk matches the value. If so, other attributes are ignored.
If PVID is empty and CONNECTION is set, then BOS installation checks to see if the parent and connwhere attributes (separated by "//") match a disk. If they do, other attributes are ignored.
If either PVID or CONNECTION is set, and neither value matches a disk on the target system, and no other attributes are set, an error message is generated, and a disk must be explicitly selected.
If PVID is empty and SAN_DISKID is set, then, for fibre channel-attached disks, BOS install interprets the SAN_DISKID as a World Wide Port Name and a Logical Unit ID (separated by "//"). The World Wide Port Name (ww_name) and Logical Unit ID (lun_id) can be obtained on a running system from the lsattr command.
If the ww_name and lun_id match a disk, other attributes are ignored.
If either PVID or SAN_DISKID is set, and neither value matches a disk on the target system, and no other attributes are set, then an error message will be generated and a disk will have to be explicitly selected.
If PVID and SAN_DISKID are empty and CONNECTION is set, then BOS install will see if the parent and connwhere attributes (separated by "//") match a disk. If this is true, then other attributes are ignored.
If CONNECTION is set, the value does not match a disk on the target system, and no other attributes are set, then an error message will be generated and a disk will have to be explicitly selected.
If other attributes are specified, processing occurs as described below:
- If LOCATION is set, BOS installation ignores SIZE_MB and HDISKNAME.
- If LOCATION is not set and SIZE_MB is, BOS installation selects disks based on SIZE_MB and ignores HDISKNAME.
- If LOCATION and SIZE_MB are both empty, BOS installation chooses the disk specified in HDISKNAME.
- If all fields are empty, BOS installation chooses a disk for you.

Attention: If prompt=no, do not leave the target_disk_data stanzas empty, unless you do not care which disk BOS installation overwrites. This is because the algorithm that determines the default disk for the installation is not always predictable.

The SIZE_MB field can contain either a size or the word largest. If a size is listed, BOS installation does a "best-fit" on the disks. If the word largest is in that field, BOS installation selects the largest disk. If there is more than one target_disk_data stanza, BOS installation selects the two "largest" disks, and so on.

PVID	Specifies the 16-digit physical volume identifier for the disk.
SAN_DISKID	Specifies the World Wide Port Name and a Logical Unit ID for fibre channel-attached disks. The ww_name and lun_id are separated by two slashes (`//`). This information can be obtained on a running system from the lsattr command.
CONNECTION	Specifies the combination of the parent attribute and the connwhere attribute associated with a disk. The parent and connwhere values are separated by two slashes (`//`). If the parent value is `scsi0` and the connwhere value is `0,1`, then the CONNECTION value is `scsi0//0,1`. An example of the CONNECTION value for a SSA disk would be `ssar//000629CCC07300D`. In the example, the parent attribute is represented by `ssar` and the ConnectionLocation (15-character unique identity) of the disk drive `000629CCC07300D` is used for the connwhere attribute.
SIZE_MB	Specifies the formatted size of the disk, in megabytes, where the program is to install BOS. The default value is blank. You can specify the size of your target disk by typing the number of megabytes available on the formatted disk. Also, you can type `largest` if you want to use the largest disk (that has not already been selected) found by the installation program.
LOCATION	Specifies a location code for the disk where the program is to install BOS. The default value is blank. If you do not specify a value, the installation program assigns a value based on the next two variables. For more information about physical location codes, refer to the `Diagnostic Information for Multiple Bus Systems` guide.
HDISKNAME	Specifies the path name of the target disk. The default value is blank. To name a target disk, use the hdiskname format, where hdiskname is the device name of your disk (for example, hdisk0).

locale Stanza

The locale stanza contains variables for the primary language the installed machine is to use. Refer to Understanding Locale Categories in AIX 5L Version 5.2 National Language Support Guide and Reference, which provides information about locales and the format to use when editing variables.

BOSINST_LANG	Specifies the language that the installation program uses for prompts, menus, and error messages. The default value is blank.
CULTURAL_CONVENTION	Specifies the primary locale to install. The default value is blank.
MESSAGES	Specifies the locale for message catalogs to install. The default value is blank.
KEYBOARD	Specifies the keyboard map to install. The default value is blank.

large_dumplv Stanza

The optional large_dumplv stanza specifies characteristics used if a dedicated dump device is to be created on the systems. A dedicated dump device is only created for systems with 4 GB or more of memory. The following characteristics are available for a dedicated large dump device:

DUMPDEVICE	Specifies the name of the dedicated dump device.
SIZEGB	Specifies the size of the dedicated dump device in gigabytes.

If the stanza is not present, the dedicated dump device is created when required. A dedicated dump device is created in machines with at least 4 Gigabytes of real memory during an overwrite install. By default, the name of the dedicated dump device is lg_dumplv and its size is determined by the following formula:

4>=  RAM < 12       size of dump device= 1 GB
12>= RAM < 24       size of dump device= 2 GB
24>= RAM < 48       size of dump device= 3 GB
     RAM >= 48      size of dump device= 4 GB

dump Stanza

The dump stanza specifies the following system dump characteristics:

PRIMARY	Specifies the primary dump device to be set by sysdumpdev -P -p device.
SECONDARY	Specifies the secondary dump device to be set by sysdumpdev -P -s device.
COPYDIR	Specifies the directory to which the dump is copied at system boot.
FORCECOPY	Specifies whether the system boots into menus that allow copy of the dump to external media if the copy fails.
ALWAYS_ALLOW	Specifies whether the key mode switch can be ignored when a dump is requested.

If the stanza is not present in the bosinst.data file, no additional dump device handling occurs beyond what is already in place. Checking on the values of the fields is limited; if the device specified for a dump device is not valid, any error processing comes from the sysdumpdev command and is sent to the console and stored in the BOS installation log.

If FORCECOPY is specified and no COPYDIR is specified, the value field of the autocopydump attribute from /etc/objrepos/SWservAt is retrieved and used for the sysdumpdev -[d|D] copydir operation.
If only the COPYDIR is specified without FORCECOPY being specified, forcecopy defaults to yes. The sysdumpdev -d (FORCECOPY = no) or sysdumpdev -D (FORCECOPY = yes) is used to set the copy directory.
If ALWAYS_ALLOW=yes, run sysdumpdev -K. Otherwise, run sysdumpdev -k.
If any values other than yes and no are specified for FORCECOPY or ALWAYS_ALLOW, the default actions occur, and processing continues.
If no value is specified for a particular dump field, no analogous sysdumpdev operation is performed. This leaves the system values in the appropriate state, even for a migration or system backup image installation. If a COPYDIR is specified but FORCECOPY is not specified, the value of the forcecopydump attribute is retrieved from the /etc/objrepos/SWservAt file to determine the correct form of sysdumpdev to invoke.