00:MIF 001001 AI60 U401322 11308 2AIX PTF DOCUMENTATION FILE 3001001P1403 F 80 80 *DATA*01010019900920 .ti ~ 05 .tp add 1.9i MEMORANDUM TO:~~Licensees of AIX Version 3 Release 1 ~~Program Number 5756-030 .sk 1 SUBJECT:~~AIX Version 3 Release 1 Modification 5 ~~RELEASE NOTES For U401322 ~~Corrective Service 3005 .tp delete 1.9i .sk 2;.fo on :h3.INITIAL COMMENTS :p.:hp2.Notice::ehp2. The procedures for applying updates have changed significantly. :hp2.Warning::ehp2. Failure to meet documented disk space requirements may cause unpredictable results. :p.The enclosed tape media is called stacked tape. It contains corrective service update and install images, stacked one after another on the media. The first image on the media is a bootable image, equivalent to the BOS Boot and Display diskettes. The second image is equivalent to an Inst/Maint diskette. The third image is the table of contents (TOC). The remaining images are replacement and update images. :p.You will not be booting from this tape to install/update your system with this corrective service. :p.After installing all the images in this package, your system will be at AIX Version 3 Release 1 Modification 5 (AIX 3.1.5). :h5.Check Your Package :p.Please verify you have received the appropriate media. If not, please contact the appropriate support organization. Refer to :hp2.Problem Reporting Numbers:ehp2. for more information. :p.1/4-Inch Cartridge Tape Drive: :ul compact. :li.Two 6150 (QIC-120) 1/4-inch Data Tape Cartridges. :eul. :p.8mm Tape Drive: :ul compact. :li.Two 8MM Data Tape Cartridges. :eul. .pa :h3.GENERAL COMMENTS :p.This section contains information you should be aware of before installing this corrective service. :h5.IBM 150 MB 1/4-inch Cartridge Tape Drive :p.Error Correction Code (ECC) on the internal or external IBM 150 MB 1/4-inch Cartridge Tape Drive is no longer supported. SMIT has been updated to remove the ability to enable the ECC capability of the IBM 150 MB 1/4-inch Cartridge Tape Drive. :p.All AIX users not electing to install AIX Version 3.1.5 at this time, should set ECC on attached IBM 150 MB 1/4-inch Cartridge Tape Drives to "Off" using the current level of SMIT. :p.All RISC System/6000 customers of record, with the installed IBM 150 MB 1/4-inch Cartridge Tape Drives, will be notified of recommended procedures regarding tapes previously written while using ECC. :h5.Hardware Configuration Check During System Boot :p.This level of AIX has been enhanced to provide additional hardware configuration checking to warn users when a system hardware configuration has been detected which could result in improper operation of the system. This configuration check is performed automatically during each system boot by the system configuration procedure. If a hardware configuration is detected with which the system may not function properly, a warning message will appear on the system console during system boot. The message will instruct the user concerning the corrective action required. Also, an error log entry will be written to the system error log for additional service information. :p.The warning message written to the console will be similar to: :xmp. WARNING! A POTENTIAL CONFLICT EXISTS IN YOUR HARDWARE CONFIGURATION. OPERATING YOUR SYSTEM WITH THIS CONFIGURATION MAY RESULT IN UNDETECTED DATA LOSS. PLEASE CONTACT YOUR IBM SERVICE REPRESENTATIVE WITH SERVICE REQUEST NUMBER: XXX-XXX. :exmp. :h5.Machine Identifier Change :p.If the ACTIVE service release level is lower than 03.01.0003.0013, the value of the machine identifier that is returned by the "uname" command and the uname() and unamex() subroutines will change with this modification level from the machine identifier value that was previously returned. This change may affect applications that use the machine identifier to license program access. For example, new password(s) are required for any IBM Program Product currently running under RLM (Resource License Manager 5621-027). To see this identifier, issue the "uname -m" command. Application support organizations should be contacted for applications that are affected by this change. :p.To determine the ACTIVE service level of the Base Operating System, use the following command: :xmp. lslpp -h bos.obj :exmp. :h5.Correct Level Boot Diskettes :p.After installing and updating the Base Operating System, create BOS Boot, Display and BOS Inst/Maint diskettes to match AIX Version 3.1.5. Retain your previous versions of these diskettes for use with previous versions of AIX. For information on creating these diskettes, refer to the Installation Guide. :h5.System Image Backup Install And Creation :p.When using a system image backup tape to install a machine, you MUST boot from diskette and choose the tape device from which to install. Booting from an IBM bootable tape and then switching to a system image backup tape will not work. Create BOS Boot, Display and Inst/Maint diskettes when you create the system image backup. :p.If the ACTIVE service level is lower than 03.01.0003.0013, creating a system image backup tape requires the block size to be 1024 bytes for 8mm tape drives. If the ACTIVE service level is 03.01.0003.0013 or higher, creating a system image backup tape requires the block size to be 512 bytes. :p.To determine the ACTIVE service level of the Base Operating System, use the following command: :xmp. lslpp -h bos.obj :exmp. :p.Use the "smit chgtpe" command to verify/change the tape block size. A system image backup tape may be created using the "smit startup" Backup System menu or the "mksysb" command. :p.With this level of AIX you no longer have to unmount your NFS file systems and/or CDROM compact disc during the creation of your system image backup. :p.:hp2.Be sure to have at least 6.5MB of free space in the /tmp file system prior to creating your system image backup.:ehp2. This is needed to rebuild the boot logical volume. :h5.Verify The Tape Block Size :p.If you are using an 8mm tape cartridge, you should verify the 8mm tape drive is using a block size of 512 bytes during the installing and updating process. Use the "smit chgtpe" command to verify/change the tape block size. :h5.Backup Your System :p.Backup your system and important data. As with any process that modifies your operating system, the prudent course is to have a backup copy of your system before applying any updates. See System Image Backup Install for additional information. :h5.The Update Process :p.The installation of the software updates can be accomplished in 1 or 2 steps. You can apply the updates first, giving you the ability to reject the updates later. Alternatively, you can apply and commit the updates in one step. Once you commit the updates you cannot reject them. :p.The update process determines if there is adequate space available before an update is applied. If there is insufficient free space, the update process will notify you and processing of the update will stop. If you instruct the update process to automatically extend the logical volume partitions to accommodate the update, no notification will be given and the update will proceed. For customers with limited disk space, refer to Updating With Limited Disk Space. :p.If you have never installed corrective service updates on a RISC System/6000 before, we suggest you become familiar with the details of the process by reviewing the "updatep" and "instupdt" commands in InfoExplorer. :h5.Applying Selective Updates :p.With AIX for the RISC System/6000 you are able to apply all the updates found on the corrective service, or apply only selected options of the Licensed Program Products. :p.Major components of the operating system and Optional Program Products can have updates applied separately. However, options of a particular program product must be applied at the same time to use this feature. If an update to an option is required at a later time, for a program product with previous updates applied, all previously applied updates must be committed first, before the required option be updated. :p.For example, updates to bos.obj can be applied first, and at a later time, updates to xlfcmp.obj can be applied. However, with updates to bosnet.tcpip.obj applied, all previously applied updates to all program products will have to be committed, before bosnet.nfs.obj can be updated. :h5.Displaying Corrective Service Contents :p.You can generate a list of all programs for which updates exist on the corrective service. When doing this no update is attempted. You can also generate a list of all customer problem report numbers and summaries fixed by the specified program or program options. Use SMIT to generate these lists. .pa :h3.UPDATING WITH LIMITED DISK SPACE :p.For the update tools to provide apply/commit/reject capability, previous versions of the files being updated are saved. Some machine configurations will experience problems because of insufficient space in the /usr file system. :p.Two procedures have been developed to address limited /usr file system space problems. These procedures are: temporary space update and unprotected mode update. :h5.Temporary Space Update :p.The "updatep" and "instupdt" commands accept a "-t" option that identifies a directory where additional space is available. This space can reside in another file system (e.g. /u), another logical volume file system or in an NFS mounted file system. The "-t" option is invoked via SMIT in the "SAVE Directory" Entry Field. :p.The update process will query the directory to insure adequate space for the temporary files. Information about the file system where the saved files are located is kept so the commit or reject processing can occur at a later time. This file system must still exist for the reject or commit processing to complete successfully. :p.These file systems must be writeable by the root user for the update to occur. This is especially important when using NFS file systems, since the default owner for an NFS mounted file system is 'nobody'. The file system should be exported with root access authority. :p.The NFS server must provide protection so the saved files for the client are not overwritten by another client. A suggested way would be to establish a large file system on the server (e.g. /tempspace) and make a directory with the client's host name (e.g. /tempspace/client01). The server would export a /tempspace/clientxx for each supported client. The client would mount /tempspace/clientxx as /save. On the command line, the option specified would be "-t /save". :h5.Unprotected Mode Update :p.The "updatep" and "instupdt" commands accept a "-N" option to specify the current version of the files to be updated will NOT be saved. There is NO protection for an unsuccessful update using this option. If an update fails for any reason, you may have to reinstall that program and attempt the update again. The "-N" option is invoked via SMIT in the "SAVE Replaced Files?" Entry Field. :h5.Access to the -N or -t options :p.If the ACTIVE service level is lower than 03.01.0003.0013, the "smit" command does not have the new function supporting the "-t" and "-N" options of the "updatep" and "instupdt" commands. Applying and committing the Base Operating System update will allow you to apply additional updates using these new options in SMIT. On the SMIT menus "Install Optional Program Products with Updates" and "Update Optional Program Products", invoke the "-N" option by changing the "SAVE Replaced Files?" Entry Field to "No". Invoke the "-t" option by specifying a directory in the "SAVE Directory" Entry Field. :p.To determine the ACTIVE service level of the Base Operating System, use the following command: :xmp. lslpp -h bos.obj :exmp. :h5.Possible Files To Delete :p.While temporary space mode or unprotected mode reduces the need for file system space, the update process still uses some space on /usr and /(root). For some, even the unprotected mode is not enough. For those systems with extremely limited disk space, the remaining options are to remove code in the file system or to obtain additional hard disks. :p.:hp2.The / (root) file system:ehp2. :p.The following files and directories can be backed up and removed. Keep these backups safe. You may want to restore them after the update is completed. :ul compact. :p.Model 730 and Model 930. Only if your system is not a 730 or 930. :li./etc/drivers/eudd :li./etc/drivers/gemdd :li./etc/methods/cfg6193 :li./etc/methods/cfggem :li./lib/libgem3dm2.a :li./etc/microcode/8ffdc2.00.01 :li./etc/microcode/8ffdc2.00.02 :li./etc/microcode/8ffdgt.00.01 :li./etc/microcode/8ffdgt.00.02 :li./etc/microcode/8ffdgu.00.01 :li./etc/microcode/8ffdgu.00.02 :li./etc/microcode/8ffdgv.00.02 :li./etc/microcode/8ffdsh.00.01 :li./etc/microcode/8ffdsh.00.02 :li./etc/microcode/8ffdvp.00.02 :li./etc/microcode/GEMBATS.BIN :p.High Performance 3D Graphics Display adapter. Only if you do not have this adapter currently in your system. :li./etc/drivers/geadd :li./etc/methods/cfgsab :li./etc/microcode/8ee6.00.01 :li./lib/libsab3dm2.a :p.Hardware Diagnostics - Key Files. Be sure to restore these files after the update is complete. :li./etc/lpp/diagnostics/da/dgvars :li./etc/lpp/diagnostics/bin/diagipl :li./etc/lpp/diagnostics/bin/diagrpt :eul. :p.The following files can be removed from the system entirely because the update process replaces them. Warning: We suggest you back them up anyway in case the update process fails. :ul compact. :p.Hardware Diagnostics. These files are replaced by the update process for bos.obj. Be sure to separately backup the Key Files mentioned in the above list. :li./etc/lpp/diagnostics/da/* :li./etc/lpp/diagnostics/bin/* :p.TCPIP Applications. These files are replaced by the update process for bosnet.tcpip.obj :li./etc/ftpd :li./etc/gated :li./etc/named :li./etc/rexecd :li./etc/rlogind :li./etc/routed :li./etc/rshd :li./etc/rwhod :li./etc/telnetd :li./etc/timed :p.The Kernel. This file is replaced by the update process for bos.obj. Warning: If the update process fails, the reject process will also fail. You will likely need to run the "bosboot -a" command after the failure. If you use the Unprotected Mode, you may have to reinstall the bos.obj. :li./unix :eul. :p.:hp2.The /usr file system:ehp2. :p.The following files and directories can be backed up and removed. Keep these backups safe. You may want to restore them after the update is completed. :ul compact. :p.InfoExplorer Minimum data base file. This file is 2.7MB in size. :li./usr/lpp/info//aixmin/aixmin.rom :ul compact. :li.Where is the national language selected for messages. :eul. :p.TCPIP Application Samples. :li./usr/lpp/tcpip/samples/* :eul. :p.The following files can be removed from the system entirely because the update process replaces them. Warning: We suggest you back them up anyway in case the update process fails. :ul compact. :p.AIXwindows Run Time files. :li./usr/lpp/X11/bin/*.Z :li./usr/lpp/X11/bin/X :eul. .pa :h3.PREREQUISITES AND PRECONDITIONS :p.Use the "lslpp -l" and "lslpp -h" commands to examine what products are installed and what level the products are at. :p.:hp2.Base Operating System (bos.obj):ehp2. :ul compact. :li.Your paging space must be larger than your real memory if you update the Base Operating System while AIXwindows is running. We strongly recommend you NOT run AIXwindows during the update process. In addition to requiring more page space, you will also need more temporary space in /(root) and /(usr) if AIXwindows is running. :eul. :p.:hp2.AIXwindows Runtime (X11rte.obj):ehp2. :ul compact. :li.A version of AIXwindows Runtime must already be installed on your system. :eul. :p.:hp2.3270 Host Connection Program (hcon.obj):ehp2. :ul compact. :li.A version of 3270 Host Connection Program must already be installed on your system. :li.You must update Base Operating System (bos.obj) and Base Profiling Support (bosadt.prof.obj) prior to or in conjunction with 3270 Host Connection Program. Please refer to InfoExplorer for further information. :li.You must reconfigure after reinstalling the AIX 3270 Host Connection package. :eul. :p.:hp2.Xstation Manager (x_st_mgr.obj):ehp2. :ul compact. :li.A version of Xstation Manager must already be installed on your system. :li.You must reconfigure after reinstalling the Xstation Manager package. Please refer to the /usr/lpp/x_st_mgr/README file for further information. :eul. :p.:hp2.PC Simulator (pcsim):ehp2. :ul compact. :li.You cannot update PC Simulator while AIXwindows is running. :eul. :p.:hp2.Text Formatting System (txtfmt.tfs.obj, txtfmt.ts.obj, txtfmt.xpv.obj, txtfmt.bib.obj):ehp2. :ul compact. :li.A version of Text Formatting Services (txtfmt.tfs.obj) must already be installed on your system. :li.A version of Base Application Development Toolkit (bosadt.bosadt.obj) must be installed prior to installing the TranScript Tools option (txtfmt.ts.obj). :li.A version of AIXwindows Runtime (X11rte.obj) and AIXwindows Font Files (X11dev.fnt) must be installed prior to installing the Troff Xpreviewer option (txtfmt.xpv.obj). :li.A version of Text Formatting Services (txtfmt.tfs.obj) must be must be installed prior to or in conjunction with installing the Troff Xpreviewer option (txtfmt.xpv.obj) or the Bibliography Support option (txtfmt.bib.obj). :eul. :p.:hp2.XL FORTRAN Compiler (xlfcmp.obj, xlfrte.obj) and Run Time (xlfrte.obj):ehp2. :h5.Version 1 XL FORTRAN :ul compact. :li.You must update Base Operating System (bos.obj) and Base Profiling Support (bosadt.prof.obj) prior to or in conjunction with both the Compiler and Run Time. :li.You must update XL FORTRAN Run Time prior to or in conjunction with the Compiler. :eul. :h5.Version 2 XL FORTRAN (a separately orderable product) :ul compact. :li.You must update Base Operating System (bos.obj) prior to or in conjunction with both the Compiler and Run Time. :li.You must update XL FORTRAN Run Time prior to or in conjunction with the Compiler. :li.Contact your local IBM Branch Office or IBM Authorized Representative to order this version of XL FORTRAN. :eul. :p.:hp2.VS COBOL Compiler (cobolcmp.obj, cobolrte.obj) and Run Time (cobolrte.obj):ehp2. :ul compact. :li.You must update Base Operating System (bos.obj) prior to or in conjunction with both the Compiler and Run Time. :li.You must update VS COBOL Run Time prior to or in conjunction with the Compiler. :eul. :p.:hp2.XL Pascal Compiler (xlpcmp.obj, xlprte.obj) and Run Time (xlprte.obj):ehp2. :ul compact. :li.You must update Base Operating System (bos.obj) prior to or in conjunction with both the Compiler and Run Time. :li.You must update XL Pascal Run Time prior to or in conjunction with the Compiler. :eul. :p.:hp2.DOS Server (pci.obj):ehp2. :ul compact. :li.You must update TCPIP Applications (bosnet.tcpip.obj) prior to or in conjunction with DOS Server. :eul. .pa :h3.DISK SPACE REQUIREMENTS :p.Use the "df" and "lsvg" commands to determine the existing free space available in your file systems and volume groups. Please refer to InfoExplorer for information on these commands. :h5.AIXwindows Run Time (X11rte.obj) ONLY :p.X11rte.obj has different space requirements depending on the service level currently running on the system. :p.If the current service level for X11rte.obj is 03.01.0003.0012 or higher, the following space is required: :ul compact. :li. 3 MB / (root) :li.13.5 MB /usr :li. 7.5 MB /tmp :eul. :p.If the current service level for X11rte.obj is LOWER than 03.01.0003.0012, the following space is required: :ul compact. :li. 3 MB / (root) :li.22 MB /usr :li. 7.5 MB /tmp :eul. :h5.Base Operating System (bos.obj) ONLY :p.bos.obj has different space requirements depending on the service level currently running on the system. :p.The first column states space requirements needed to APPLY or APPLY/COMMIT in protected mode. The second column states space requirements needed to update using the UNPROTECTED MODE. :p.If the current service level for bos.obj is 03.01.0003.0013 or higher, the following space is required: :p. APPLY or APPLY/COMMIT UNPROTECTED MODE :ul compact. :li. 8.5 MB / (root) 8.5 MB / (root) :li. 39 MB /usr 3.5 MB /usr :li. 7.5 MB /tmp 7.5 MB /tmp :eul. :p.If the current service level for bos.obj is LOWER than 03.01.0003.0013, the following space is required: :p. APPLY or APPLY/COMMIT UNPROTECTED MODE :ul compact. :li. 9.5 MB / (root) Feature Not Available :li. 39 MB /usr :li. 7.5 MB /tmp :eul. :p.:hp2.WARNING: While the system may ask you to provide 6.1MB of free space for the /(root) file system in order to update the Base Operating System (bos.obj), you will actually need 8.5MB or 9.5MB depending on your current service release level. If you do not provide for this space requirement, the system may indicate a successful update when an error has actually occurred. You must review your /smit.log file for any libraries that may have failed to rebuild successfully. Search on the key word "archive:". Failure to follow these steps may require a reinstallation of your AIX operating system. SMIT will NOT notify you of this particular failure. Furthermore, the vital product data (VPD) information will not reflect this failure.:ehp2. .pa :h5.Using ALL Update Images At Once. :p.The update images have different space requirements depending on the service level currently running on the system. The following space requirements are for those customers who choose to apply ALL the updates at once as opposed to selectively apply the updates. :p.The first column states space requirements needed to APPLY or APPLY/COMMIT in protected mode. The second column states space requirements needed to update using the UNPROTECTED MODE. :p.If the current service level for bos.obj is 03.01.0003.0013 or higher, the following space is required: :p. APPLY or APPLY/COMMIT UNPROTECTED MODE :ul compact. :li. 8.5 MB / (root) 8.5 MB / (root) :li. 103.0 MB /usr 3.5 MB /usr :li. 7.5 MB /tmp 7.5 MB /tmp :eul. :p.If the current service level for bos.obj is LOWER than 03.01.0003.0013, the following space is required: :p. APPLY or APPLY/COMMIT UNPROTECTED MODE :ul compact. :li. 9.5 MB / (root) Feature Not Available :li. 103.0 MB /usr :li. 7.5 MB /tmp :eul. :p.:hp2.WARNING: While the system may ask you to provide 6.1MB of free space for the /(root) file system in order to update the Base Operating System (bos.obj), you will actually need 8.5MB or 9.5MB depending on your current service release level. If you do not provide for this space requirement, the system may indicate a successful update when an error has actually occurred. You must review your /smit.log file for any libraries that may have failed to rebuild successfully. Search on the key word "archive:". Failure to follow these steps may require a reinstallation of your AIX operating system. SMIT will NOT notify you of this particular failure. Furthermore, the vital product data (VPD) information will not reflect this failure.:ehp2. :h3.CHANGES TO USER CONFIGURABLE FILES :hp2.Files Replaced::ehp2. The following files are replaced due to functional enhancements and/or fixes. Please save these files before updating your system if you have changed them. After completing system updates, compare the saved files to the new versions, and make any necessary changes. Do NOT overwrite the new versions of the files with the saved files. :ul compact. :li./etc/brc :li./etc/qconfig :li./usr/lib/font/devibm3812 :li./usr/lib/font/devhplj :li./usr/lib/sendmail.cf * :li./usr/spool/cron/crontabs/uucp :p.* If your ACTIVE service release level is 03.01.0003.0013 or higher, this is the ONLY file replaced. :eul. :hp2.Files Modified::ehp2. The following file has been modified to provide functional enhancements and/or fixes. The modifications should not affect any user changes to this file. :ul. :li./etc/rc.tcpip :eul. .pa :h3.PROCEDURES :ol. :p.NOTE: Login as the root user to install or update. :p.NOTE: Tape block size must be 512 bytes. :p.:hp2.Step 1.:ehp2. Retrieve the "installp" command from the IBM supplied tape by issuing the following commands: :ul compact. :li.cd / :li.Insert the tape labelled volume 1. :li.restore -f/dev/rmt0.1 -qvxs4 ./etc/installp :li.chgrp bin /etc/installp :li.chown root /etc/installp :li.chmod 4500 /etc/installp :eul. :p.:hp2.Step 2.:ehp2. For systems with 3270 Host Connection installed, issue the following command: :ul compact. :li.lppchk -cu hcon.obj :eul. :p.:hp2.Step 3.:ehp2. Quiesce the system. :ul compact. :p.The more processes you have running, the more temporary free disk space is required to update your system. This is especially true of AIXwindows Runtime. The following bullets will stop all but the necessary processes. :li.Unmount any nfs mounted filesystems. :li.sh /etc/nfs.clean :li.sh /etc/tcp.clean :li.killall - (Note this is killall with the minus sign.) :li.nohup /etc/syncd 60 > /dev/null& (Restarts the syncd daemon.) :eul. :p.:hp2.Step 4.:ehp2. To reinstall AIXwindows Runtime, Text Formatting Services, Xstation Manager and Messages, 3270 Host Connection Program and Messages. :ul. :li.Execute "smit instupdt_install" :li.List (F4) and select the DEVICE name. :li.Position the cursor on the "OPTION name" entry field, press List (F4) and Select (F7) the install images you wish to replace. Press Enter when finished selecting. :li.Position the cursor on the "OVERWRITE newer version?" entry field and change it to "Yes" by pressing the Tab key. :li.If you do not want the system to automatically extend the / (root) and /usr file systems, change the "EXTEND logical disk partitions?" entry field to "No" by pressing the Tab key. :li.Press Enter to begin the install process. :li.Exit SMIT (F10). :p.NOTE: AIXwindows Runtime will not be usable until Base Operating System has been updated. :eul. .pa :p.:hp2.Step 5.:ehp2. To update Base Operating System and other Optional Program Products AIXwindows Development, Personal Computer Simulator, 3278/79 Emulator, System Network Architecture, Network Manager, AIX VS COBOL Run Time Environment, AIX VS COBOL Compiler, AIX XL FORTRAN Run Time Environment, AIX XL FORTRAN Compiler, AIX XL Pascal Run Time Environment, AIX XL Pascal Compiler. :ul. :p.:hp2.WARNING: While the system may ask you to provide 6.1MB of free space for the /(root) file system in order to update the Base Operating System (bos.obj), you will actually need 8.5MB or 9.5MB depending on your current service release level. If you do not provide for this space requirement, the system may indicate a successful update when an error has actually occurred. You must review your /smit.log file for any libraries that may have failed to rebuild successfully. Search on the key word "archive:". Failure to follow these steps may require a reinstallation of your AIX operating system. SMIT will NOT notify you of this particular failure. Furthermore, the vital product data (VPD) information will not reflect this failure. See Disk Space Requirements.:ehp2. :li.Execute "smit instupdt_apply_commit" :li.List (F4) and select the DEVICE name. :li.Position the cursor on the "OPTION name" entry field, press List (F4) and Select (F7) the update images you wish to apply. Press Enter when finished selecting. :li.If you want to apply, but not commit the update, change the "APPLY or APPLY/COMMIT?" entry field to "Apply only" by pressing the Tab key. :li.If you do not want the system to automatically extend the / (root) and /usr file systems, change the "EXTEND logical disk partitions?" entry field to "No" by pressing the Tab key. :li.If you want to use unprotected mode update, change the "SAVE Replaced Files?" entry field to "No" by pressing the Tab key. :ul compact. :li.WARNING: If an update fails for any reason, you may have to reinstall that program and attempt the update again. :eul. :li.To have the apply process save the old files in a directory other than /usr/inst_updt, specify a directory in the "SAVE Directory" entry field. :li.Press Enter to begin the install process. :li.Exit SMIT (F10). :li.Shutdown and reboot your system, after updating the Base Operating System only, by issuing the following command: :xmp. shutdown -Fr :exmp. :eul. :eol. .pa :h3.ADDITIONAL REMARKS :ol. :li.Logical Volume Mirrors :p.After booting from tape or diskette, any stale mirrors are not automatically synchronized in the root volume group. To synchronize the root volume group enter the command: :xmp. syncvg -v rootvg :exmp. :li.Xstation Manager Users :p.Users of Xstation Manger 1.1 should be aware that this update contains Xstation manger 1.2. Refer to the /usr/lppp/x_st_mgr/README file for instructions to allow the Xstation 120s to boot using the Xstation Manger 1.2 server. :p.Xstation Manager 1.2 requires the Xstation 120 to have a minimum of 1.5MB of system memory (DRAM). Users having Xstation 120s with minimum memory (.5MB) who wish to use Xstation Manager 1.2 are responsible for meeting this requirement. :li.AIX SNA Services/6000 Profiles :p.Before applying updates to AIX SNA Services/6000, some users may create backup copies of their SNA profiles. Making backups is never a bad idea, but the SNA update process does not remove existing profiles. It may modify these profiles to fix problems that require existing profile information to be changed. It is important the user DOES NOT overlay these modified profiles with the backup copies, as necessary changes will be overwritten. :p.When creating backups of the SNA profiles, use the "exportsna" and "importsna" commands. Copying the contents of /usr/lpp/sna/objrepos to another directory is not sufficient. By using the "exportsna" and "importsna" commands, any changes made to profile configuration will be applied to the backup copy of the profiles. :p.To create the backup: :hp1.exportsna -f :ehp1. :p.To replace existing profiles with the backup copy: :hp1.importsna -l :ehp1. :li.Display PostScript Users :p.The permissions of the new Display PostScript fonts will not allow general user access. To fix this, login as root and execute the following commands: :xmp. chmod +r /usr/lpp/DPS/fonts/outlines/* chmod +r /usr/lpp/DPS/fonts/prebuilt/* chown bin /usr/lpp/DPS/fonts/outlines/* chown bin /usr/lpp/DPS/fonts/prebuilt/* chgrp bin /usr/lpp/DPS/fonts/outlines/* chgrp bin /usr/lpp/DPS/fonts/prebuilt/* :exmp. :li.A message will indicate a successful update such as the following: :xmp. updatep: The UPDATE of LPP bos with the following options was successful. bos.obj :exmp. :p.In rare cases, the system will fail on a specific optional program product and reject the update. The command field of SMIT will indicate failed and a message will be displayed similar to the following: :xmp. 0504-048: The UPDATE of LPP bos with the following options has failed. The LPP is being rejected. bos.obj :exmp. :p.Simply rerun the update on the specific failing Optional Program Product. :li.An attempt to update an optional program product that is not installed will fail. The following error message will appear: :xmp. 0504-016 updatep: The updatep command cannot complete. The system programs are at the correct level already or the specified programs are not on this diskette or the programs on the diskette are not on the system. :exmp. :p.If the update involves several optional program products, the failure reflects only the optional program products that are not installed. This error message will be displayed for each optional program product that is not installed. Installed optional program products will update successfully unless a different error condition is detected. To verify apply/commit activity, SMIT can be used to list the history of an optional program product from the "Inventory / Vital Product Data" menu. :li.If the update of a specific optional program product fails and rejects successfully, the COMMAND STATUS Command field may indicate "OK". Examine the update results carefully to determine the update status. Or, verify apply/commit activity using SMIT to list the history of an optional program product from the "Inventory / Vital Product Data" menu. :li.After updating an optional program product, 'lppchk' might indicate "wrong length" and "wrong checksum" for some updated files. Typically, this should not be a concern. :li.The InfoExplorer database files have been updated to reflect the new function shipped in this package. :li.Users should reread the README files for updated optional program products. :eol. .ti ~ 05 .tp set 5m 7m :h3.PROBLEM REPORTING NUMBERS :p.U.S. Domestic Customers: ~HowTo or Installation/Configuration ~~HowTo or Installation/Configuration problems should be directed ~~to your local IBM Branch Office or IBM Authorized ~~Representative. ~AIX Software Defect Problems ~~Contact IBM Austin's Software Defect Support at 1-800-237-5511 ~RISC System-6000 Hardware Problems ~~Contact IBM hardware support at 1-800-IBM-SERV ~SystemXTRA Customers ~~Contact IBM SystemXTRA at 1-800-IBM-XTRA. For World Trade Customers: ~Contact your country IBM Support Structure.