### Example Admin File Configuration Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=files-admin-file This example shows how to configure several parameters in an admin file for package installation. The 'ask' value can be used for most parameters to prompt the installer, but not for 'mail' or in non-interactive installations. ```shell basedir=/usr/local mail= runlevel=nocheck conflict=quit setuid=nocheck action=nocheck partial=nocheck idepend=nocheck rdepend=nocheck space=quit ``` -------------------------------- ### Example ISTATES Parameter Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=files-pkginfo-file Defines the allowable run states for package installation. This example shows a common configuration for interactive installations. ```text ISTATES="S s 1" ``` -------------------------------- ### Example: List installed software with specific flags Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=lsiscs-listing-software-installed-standalone-client-spot-from-command-line This example demonstrates how to list installed software on 'spot1' using the 'La' flags for the lslpp command. ```bash nim -o lslpp -a lslpp_flags=La spot1 ``` -------------------------------- ### Example package lock entries Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=e-epkg-command This example shows how to lock 'bos.rte.lvm' always during installation and 'bos.games' only if it is installed. ```text bos.rte.lvm ALWAYS installp bos.games IFINST installp ``` -------------------------------- ### Update all filesets from a CD and log output Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=i-installp-command This example first lists all currently installed packages, filters the output to get package names, and then uses installp to update all filesets from a CD. The -e flag logs the output to a specified file. ```bash lslpp -lc | awk -F ":" '{print $2}' | tail -n +2 > /tmp/lslpp installp -agXd /dev/cd0 -e /tmp/install.log -f /tmp/lslpp ``` -------------------------------- ### Installp Summary Report Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=i-installp-command This is an example of the summary report generated by the installp command after an installation or update. It details the status of each software product processed. ```text Installp Summary ---------------- Name Level Part Event Result -------------------------------------------------------------------- bos.net.tcp.client 4.1.0.0 USR APPLY SUCCESS bos.net.tcp.client 4.1.0.0 ROOT APPLY SUCCESS bos.net.tcp.client 4.1.0.2 USR APPLY SUCCESS ``` -------------------------------- ### Overwrite Installation Summary Menu Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=system-using-bos-menus This summary window displays after selecting 'Start Install Now with Default Settings'. It allows confirmation of the installation method and options before proceeding. It also includes a warning about data loss on the destination disk. ```text Overwrite Installation Summary Disks: hdisk0 Cultural Convention: en_US Language: en_US Keyboard: en_US Graphics Software: Yes Desktop: CDE System Management Client Software: Yes TCP/IP ftp and telnet Software: No Enable System Backups to install any system: Yes Selected Edition: standard Optional Software being installed: >>> 1 Continue with Install +----------------------------------------------------- 88 Help ? | WARNING: Base Operating System Installation will 99 Previous Menu | destroy or impair recovery of ALL data on the | destination disk hdisk0. >>> Choice [1]: ``` -------------------------------- ### Example Xconfig Entries for Multiple Displays Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=environment-running-different-scripts-each-display This example demonstrates how to define different startup, setup, and reset scripts for two distinct displays, 'sysaaa_0' and 'sysaaa_1', within the Xconfig file. ```shell Dtlogin.sysaaa_0*startup: /etc/dt/config/Xstartup0 Dtlogin.sysaaa_1*startup: /etc/dt/config/Xstartup1 Dtlogin.sysaaa_0*setup: /etc/dt/config/Xsetup0 Dtlogin.sysaaa_1*setup: /etc/dt/config/Xsetup1 Dtlogin.sysaaa_0*reset: /etc/dt/config/Xreset0 Dtlogin.sysaaa_1*reset: /etc/dt/config/Xreset1 ``` -------------------------------- ### Example: Install Unconfigured NIM Client Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=uiiibosnc-using-installation-images-install-base-operating-system-nim-client-from-command-line This example demonstrates initiating a `bos_inst` operation for a client machine that is not yet a running, configured NIM client. It specifies `boot_client=no` because a manual network boot is required, along with the necessary `lpp_source` and `SPOT` resources. ```bash # nim -o bos_inst -a source=rte -a lpp_source=lpp_source1 \ -a spot=spot1 -a accept_licenses=yes -a boot_client=no machine1 ``` -------------------------------- ### Fileset.installed_list Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=concepts-packaging-software-installation This file is created by installp when a fileset is being installed and a previous version is already present. It lists the already installed fileset and its version. ```text storm.rain 1.1.0.0 ``` -------------------------------- ### Start Subserver Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=s-srcsrqt-r-subroutine This example starts a subserver identified by a code point. The subserver will only start if its parent subsystem is already active. Ensure the SRC socket file is correctly specified. ```c int cont=NEWREQUEST; int rc; short replen; short reqlen; struct char *handle; struct { struct srchdr srchdr; struct statcode statcode[20]; } statbuf; struct subreq subreq; subreq.action=START; subreq.object=1234; replen=sizeof(statbuf); reqlen=sizeof(subreq); rc=srcsrqt_r("", "", 987, reqlen, &subreq, &replen, &statbuf, SRC_NO, &cont, &handle); ``` -------------------------------- ### Example installp Status File Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=concepts-packaging-software-installation This example shows the format of a status file used by the installp command to indicate the success or failure of fileset installations. Each line represents a fileset with a status code. ```text s bos.net.tcp.client s bos.net.tcp.server f bos.net.nfs.client ``` -------------------------------- ### Start and Stop Processor Examples Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=subcommands-start-stop Demonstrates the usage of 'stop', 'start', and 'cpu' commands to manage processor states and view their status. Includes setting breakpoints and exiting the debugger. ```shell KDB(1)> stop 0 //stop processor 0 KDB(1)> cpu //display processors status cpu 0 status VALID STOPPED action STOP cpu 1 status VALID DEBUG KDB(1)> start 0 //start processor 0 KDB(1)> cpu //display processors status cpu 0 status VALID action START cpu 1 status VALID DEBUG KDB(1)> b sy_decint //set break point KDB(1)> e //exit the debugger Breakpoint .sy_decint+000000 mflr r0 <.dec_flih+000014> KDB(0)> cpu //display processors status cpu 0 status VALID DEBUG action RESUME cpu 1 status VALID DEBUGWAITING KDB(0)> cpu 1 //switch to processor 1 Breakpoint .sy_decint+000000 mflr r0 <.dec_flih+000014> KDB(1)> cpu //display processors status cpu 0 status VALID SWITCHED action SWITCH cpu 1 status VALID DEBUG KDB(1)> cpu 0 //switch to processor 0 KDB(0)> cpu //display processors status cpu 0 status VALID DEBUG cpu 1 status VALID SWITCHED action SWITCH KDB(0)> q //exit the debugger ``` -------------------------------- ### Fileset.installed_list with Multiple Filesets Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=concepts-packaging-software-installation Illustrates the Fileset.installed_list content when multiple filesets are found to be installed during the installation of a new package. ```text Pelly.obj 1.2.3.0 CedarBayou.stream 4.1.3.2 ``` -------------------------------- ### Install Subcommand Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=r-rdist-command The install subcommand copies out-of-date files and directories. Options can be specified to control the copy behavior, and the destination name can be altered. ```plaintext install -b -R Options[OptionalDestName]; ``` -------------------------------- ### Mount Volume Prompt Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=updates-completing-smit-installation-reading-status-messages This message indicates that you need to insert the specified installation media and press Enter to continue. ```text Mount volume 2 on /dev/cd0. Press the Enter key to continue. ``` -------------------------------- ### Display Software List Output Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=notes-aix-734-expansion-pack-release Example output from listing software on AIX media, showing fileset name, level, installation status (I/U), and content type. ```text fileset Name Level I/U Q Content ==================================================================== ICU4C.adt 2.8.0.0 I N usr # ICU Application Developer's Toolkit ICU4C.man.en_US 2.8.0.0 I N usr # ICU Manual Pages - U.S. English ``` -------------------------------- ### Start UIM/X Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=u-uimx-command Use this command to start the UIM/X user-interface management system. ```bash uimx ``` -------------------------------- ### Get User Attributes Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=g-getuserattrs-subroutine Demonstrates how to use the getuserattrs subroutine to retrieve user attributes like ID, admin status, and authentication system. Includes setup, function call, and output processing. ```c #include #include #define NATTR 3 #define USERNAME "foo" main() { dbattr_t attributes[NATTR]; int i; int rc; memset (&attributes, 0, sizeof(attributes)); /* * Fill in the attributes array with "id", "expires" and * "SYSTEM" attributes. */ attributes[0].attr_name = S_ID; attributes[0].attr_type = SEC_INT;; attributes[1].attr_name = S_ADMIN; attributes[1].attr_type = SEC_BOOL; attributes[2].attr_name = S_AUTHSYSTEM; attributes[2].attr_type = SEC_CHAR; /* * Make a call to getuserattrs. */ setuserdb(S_READ); rc = getuserattrs(USERNAME, attributes, NATTR); enduserdb(); if (rc) { printf("getuserattrs failed .... "); exit(-1); } for (i = 0; i < NATTR; i++) { printf("attribute name : %s \n", attributes[i].attr_name); printf("attribute flag : %d \n", attributes[i].attr_flag); if (attributes[i].attr_flag) { /* * No attribute value. Continue. */ printf("\n"); continue; } /* * We have a value. */ printf("attribute domain : %s \n", attributes[i].attr_domain); printf("attribute value : "); switch (attributes[i].attr_type) { case SEC_CHAR: if (attributes[i].attr_char) { printf("%s\n", attributes[i].attr_char); free(attributes[i].attr_char); } break; case SEC_INT: case SEC_BOOL: printf("%d\n", attributes[i].attr_int); break; default: break; } printf("\n"); } exit(0); } ``` ```text attribute name : id attribute flag : 0 attribute domain : files attribute value : 206 attribute name : admin attribute flag : 0 attribute domain : files attribute value : 0 attribute name : SYSTEM attribute flag : 0 attribute domain : files attribute value : compat ``` -------------------------------- ### installp -s Command Output Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=i-installp-command Example output from the `installp -s` command, which lists applied software fileset updates and available updates. ```text Installp Status --------------- Name Part Level State -------------------------------------------------------------------- bos.net.tcp.client USR 4.1.0.2 APPLIED bos.net.tcp.client ROOT 4.1.0.2 APPLIED bos.rte.commands USR 4.1.0.1 APPLIED bos.rte.misc_cmds USR 4.1.0.1 APPLIED bos.rte.tty USR 4.1.0.1 APPLIED ``` -------------------------------- ### Load System Configuration Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=h-hty-load-command Demonstrates how to load the system configuration using the hty_load command, specifying the device file and using the default driver configuration file. ```bash hty_load -d /dev/rhp0 ``` -------------------------------- ### Installed Requisite Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=concepts-packaging-software-installation Illustrates an installed requisite, where 'Super.msg.fr_FR.Widget' cannot be installed automatically if 'Super.Widget' is not installed. ```makefile *instreq Super.Widget 2.1.0.0 ``` -------------------------------- ### Example 1: Immediate Switch Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=s-swts-command This example demonstrates how to switch a thin server named 'lobo' to use the 'cosi2' common image immediately. ```APIDOC ## Example 1: Immediate Switch To switch the `cosi1` common image of a thin server named `lobo` to a common image named `cosi2`, enter: ```bash swts -c cosi2 lobo ``` The `lobo` thin server is re-initialized and `cosi2` is its new operating system. ``` -------------------------------- ### Install software and view summary report Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=i-installp-command Install software using the installp command. A summary report is provided at the end, listing the status of each software product installed. This summary is also saved in /var/adm/sw/installp.summary. ```bash installp -a -d /usr/sys/inst.images bos.net.tcp.client 4.1.0.0 installp -a -d /usr/sys/inst.images bos.net.tcp.client 4.1.0.2 ``` -------------------------------- ### Example wparexec output Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=wpars-creating-application-wpar This output shows a successful creation and startup of an application WPAR named 'wparname'. It also includes messages related to starting and stopping the WPAR. ```text wparexec: Verifying filesystems... wparexec: Workload partition wparname created successfully. startwpar: COMMAND START, ARGS: wparname startwpar: Starting workload partition 'wparname' startwpar: Mounting all workload partition file systems startwpar: Loading workload partition startwpar: Shutting down all workload partition processes rmwpar: Removing workload partition firstapp rmwpar: Return Status = SUCCESS startwpar: Return Status = SUCCESS ``` -------------------------------- ### BOOTP Specific Options Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=files-dhcp-server-configuration-file Example demonstrating the usage of BOOTP specific options like server address, home directory, and bootfile. ```shell option sa 1.1.2.2 option hd "/vikings/native" option bf "bootfile.asdg" ``` -------------------------------- ### Example of If Requisite Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=concepts-packaging-software-installation This example demonstrates an 'if requisite' for the 'plum.tree' fileset. It specifies that the '1.1.2.3' level should be installed only if 'plum.tree' is already installed at the '1.1.0.0' level. ```shell *ifreq plum.tree (1.1.0.0) 1.1.2.3 ``` -------------------------------- ### Specifying Alternate Client and Server with xinit Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=x-xinit-command This example shows how to specify an alternate client program and its arguments, followed by a double dash, and then the server program. Client and server names must start with a '.' or '/'. ```shell xinit /path/to/client -- /path/to/server :1 ``` -------------------------------- ### Get status of rpc.lockd daemon Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=control-getting-current-status-nfs-daemons This is an example of getting the status for the `rpc.lockd` daemon. ```bash lssrc -s rpc.lockd ``` -------------------------------- ### Typical .profile File Configuration Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=files-profile-file This example defines and exports PATH and epath variables, then launches a C shell. Use this to set up your environment variables and preferred shell upon login. ```shell PATH=/usr/bin:/etc:/home/bin1:/usr/lpp/tps4.0/user:: epath=/home/gsc/e3: export PATH epath csh ``` -------------------------------- ### Simplest setupterm Call Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=s-setupterm-subroutine Demonstrates the simplest way to call setupterm, using default values for terminal name, file descriptor, and error code. ```c setupterm((char*) 0, 1, (int*) 0) ``` -------------------------------- ### Example Response File Content Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=multiplatform-performing-silent-installation-using-response-files This is an example of the content found in a generated response file. It includes metadata about the installation and user-configurable options, such as the install location. Options can be modified directly in this file. ```ini ################################################################ # # InstallShield Options File # # Wizard name: Setup # Wizard source: setup.jar # Created on: Tue Jun 25 11:05:34 CDT 2002 # Created by: InstallShield Options File Generator # # This file contains values that were specified during a recent execution of # Setup. It can be used to configure Setup with the options specified below when # the wizard is run with the "-options" command line option. Read each setting's # documentation for information on how to change its value. # # A common use of an options file is to run the wizard in silent mode. This lets # the options file author specify wizard settings without having to run the # wizard in graphical or console mode. To use this options file for silent mode # execution, use the following command line arguments when running the wizard: # # -options "record.txt" -silent # ################################################################################ ################################################################################ # # My Product Install Location # # The install location of the product. Specify a valid directory into which the # product is installed. If the directory contains spaces, enclose it in # double-quotes. For example, to install the product to C:\Program Files\My # Product, use # # -P installLocation="C:\Program Files\My Product" ``` -------------------------------- ### LAPI_Xfer GET Operation Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=l-lapi-xfer-subroutine This example demonstrates how to use the LAPI_Xfer interface for a GET operation to retrieve data from a remote task. Ensure LAPI_Address_init is called to initialize the data buffer list. ```c { lapi_xfer_t xfer_struct; /* initialize the table buffer for the data addresses */ /* get remote data buffer addresses */ LAPI_Address_init(hndl,(void *)data_buffer,data_buffer_list); . . . /* retrieve data_len bytes from address data_buffer_list[tgt] on */ /* task tgt. write the data starting at address data_buffer. */ /* tgt_cntr and org_cntr can be NULL. */ xfer_struct.Get.Xfer_type = LAPI_GET_XFER; xfer_struct.Get.flags = 0; xfer_struct.Get.tgt = tgt; xfer_struct.Get.tgt_addr = data_buffer_list[tgt]; xfer_struct.Get.org_addr = data_buffer; xfer_struct.Get.len = data_len; xfer_struct.Get.tgt_cntr = tgt_cntr; xfer_struct.Get.org_cntr = org_cntr; LAPI_Xfer(hndl, &xfer_struct); } ``` -------------------------------- ### Sample pkginfo File Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=files-pkginfo-file This is an example of a typical pkginfo file, detailing package attributes. ```shell PKG="oam" NAME="OAM Installation Utilities" VERSION="3" VENDOR="AT&T" HOTLINE="1-800-ATT-BUGS" EMAIL="attunix!olsen" VSTOCK="0122c3f5566" CATEGORY="system.essential" ISTATES="S 2" RSTATES="S 2" ``` -------------------------------- ### Local Server Specification Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=x-xdm-command A typical entry for a local display number 0, specifying the display name, class, type, and the command to start the server. ```text :0 IBM-GT local /usr/bin/X11/X :0 ``` -------------------------------- ### Start Key Manager Tool Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=tool-creating-key-database Use this command to start the Key Manager tool for creating a key database. ```bash certmgr ``` -------------------------------- ### Initiate bos_inst Operation Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=uiiibosnc-using-installation-images-install-base-operating-system-nim-client-from-command-line Use this command to start the base operating system installation on a NIM client. Specify the source, lpp_source, SPOT, license acceptance, and whether to boot the client automatically. If the client is not already a configured NIM client, you may need to set `boot_client=no` and perform a manual network boot. ```bash # nim -o bos_inst -a source=rte -a lpp_source=Lpp_Source \ -a spot=SPOTName -a accept_licenses=yes -a boot_client=yes/no ClientName ``` -------------------------------- ### Install Versioned WPAR Images using installp Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=partitions-creating-versioned-wpar Alternatively, install WPAR images and filesets directly from the installation media using the installp command. This is an example for command-line installation. ```bash installp -qaXYd installation_device vwpar.images vwpar.sysmgt ``` -------------------------------- ### Confirm Overwrite Installation Summary Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=iaipe-installing-aix-using-media-device-install-partition-without-hmc Review the overwrite installation summary, including selected disks, language settings, and optional software, before starting the AIX installation. ```text Overwrite Installation Summary Disks: hdisk0 Cultural Convention: C Language: C Keyboard: C Graphics Software: Yes Desktop: CDE System Management Client Software: Yes TCP/IP ftp and telnet Software: No Enable System Backups to install any system: Yes Selected Edition: standard Optional Software being installed: >>> 1 Continue with Install 88 Help ? 99 Previous Menu >>> Choice [1]: ``` -------------------------------- ### Basic pkgproto Usage with Path Mapping Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=p-pkgproto-command This example demonstrates how to use pkgproto to map source directories to destination paths and generate a prototype file. ```bash $ pkgproto /usr/bin=bin /usr/usr/bin=usrbin /etc=etc f none bin/sed=/bin/sed 0775 bin bin f none bin/sh=/bin/sh 0755 bin daemon f none bin/sort=/bin/sort 0755 bin bin d none etc/master.d 0755 root daemon f none etc/master.d/kernel=/etc/master.d/kernel 0644 root daemon f none etc/rc=/etc/rc 0744 root daemon ``` -------------------------------- ### Start Key Manager Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=tool-requesting-digital-certificate Use this command to start the Key Manager tool if you are not already using it. ```bash runkm ``` -------------------------------- ### Fileset Build Date Comparison Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=updates-checking-fileset-build-dates Illustrates the concept of fileset build dates (YYWW format) and how they are used to determine installation eligibility. This table shows different Technology Levels (TL) and their corresponding fileset versions and build dates. ```text YYWW 0723 0746 0816 ------------------------------------------------ TL7 5.3.7.0 5.3.7.10 TL6 5.3.0.60 5.3.0.70 5.3.0.80 ``` -------------------------------- ### Mount SMB Client File System (Example) Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=protocol-server-message-block-smb-client-file-system An example demonstrating how to mount an SMB client file system with specific options for workgroup, port, signing, encryption, protocol version, and SPN. ```bash mount -v smbc -n llm140.xyz.com/cec102usr1/Passw0rd \ -o "wrkgrp=SMB_302.test,port=445,signing=required,encryption=required, \ secure_negotiate=desired,pver=auto,spn=cifs/llm140.xyz.com" /some_share /mnt ``` -------------------------------- ### Example INTONLY Parameter Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=files-pkginfo-file Indicates that the package should only be installed interactively. Setting this to any non-NULL value enforces interactive-only installation. ```text INTONLY=true ``` -------------------------------- ### Start NIM BOS Installation Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=aix-installing-client-using-nim Initiate the NIM BOS installation process from the NIM master using the SMIT interface. ```bash smit nim_bosinst ``` -------------------------------- ### Install Base OS using NIM Client Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=uiiibosnc-using-installation-images-install-base-operating-system-nim-client-from-command-line Use this command to initiate a base operating system installation on a NIM client. Specify the source type, lpp_source, spot, license acceptance, and whether to boot the client. ```bash nim -o bos_inst -a source=rte -a lpp_source=lpp_source1 -a spot=spot1 -a accept_licenses=yes -a boot_client=no machine1 ``` -------------------------------- ### Example of uuto Destination Path Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=u-uuto-command This example shows how to specify a remote system and a user on that system. ```bash remote_system!user_name ``` -------------------------------- ### NIM resolv.conf Example Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=n-nim-command Example content for a resolv.conf file used with NIM for name resolution services after a BOS installation. ```text nameserver 129.35.143.253 nameserver 9.3.199.2 domain austin.ibm.com ``` -------------------------------- ### View Files During Installation with installp Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=updates-installing-optional-software-products-service Use the `installp` command with the verbose option (-V2) to display the files being updated during an installation. This helps in monitoring the installation progress. ```bash installp -V2 ``` -------------------------------- ### Example .rhosts File Content Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=system-comparing-file-systems-different-machines An example of what the `.rhosts` file might look like after adding a new stanza. ```shell NIM.mycompany.com root nim.mycompany.com root host.othernetwork.com root orig_host.mycompany.com root ``` -------------------------------- ### Example: XREQ interim fix Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=e-epkg-command Example entry in the interim fix prerequisite file where 'oldefix4' is an XREQ, ensuring it is NOT installed. ```plaintext oldefix4 XREQ # Make sure oldefix4 is NOT installed ``` -------------------------------- ### Example File System Comparison Definition Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=system-comparing-file-systems-different-machines An example of the `compareFS` file content, specifying `/home/jane/*` on `juniper.mycompany.com` for comparison. ```shell /home/jane/* -> juniper.mycompany.com install -v ; ``` -------------------------------- ### Start Using Configuration Set Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=c-confsetcntrl-command Use this command to start using a specific configuration set. Ensure the configuration set name is correct. ```bash wlmcntrl -a -d confset1 ``` -------------------------------- ### Start yppasswdd Daemon Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=security-configuring-secure-network-file-system Use the startsrc command to start the yppasswdd daemon. This is part of the NIS setup for secure NFS. ```shell # startsrc -s yppasswdd ``` -------------------------------- ### Install Support Program Packages Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=program-installing-support-base-release-44 Use this command to initiate the installation process for all required software packages. Ensure you have the correct installation images and license agreements accepted. ```shell smitty install_all ``` -------------------------------- ### Start Dynamic Screen with Alternate Terminal Setup Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=d-dscreen-command Use this command to start the Dynamic Screen utility with a specific alternate terminal setup. This is helpful when default key actions conflict with application control sequences, such as in word processing applications. ```bash dscreen -t wy60-wp ``` -------------------------------- ### Preview License Agreements on Installation Media Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=updates-software-licensing Use this command to preview license agreements on the installation media before installation. This is useful for optional software installations. ```shell installp -El ``` -------------------------------- ### Install Software with geninstall Source: https://www.ibm.com/docs/en/aix/7.3.0?topic=g-geninstall-command Use this syntax to install software products using the geninstall command. Specify the media source and either a file containing the list of products to install or the product names directly. The 'all' keyword installs all products on the media. ```bash geninstall -d Media [ -I installpFlags ] [ -E | -T ] [ -t ResponseFileLocation ] [ -e LogFile ] [ -p ] [ -F ] [ -Y ] [ -Z ] [ -D ] { -f File | Install_List ] | all} ```