00:MIF 001001 AI60 U401394 X 11308 UMF 2AI60 FAMILY PTF DOC 0101 X 3001001P1403 F 80 80 6 X *DATA*14560519910409 X .ti ~ 05 .tp add 1.9i MEMORANDUM TO:~~Licensees of AIX 3.1.5 ~~Program Number 5756-030 .sk 1 SUBJECT:~~AIX Version 3 Release 1 Modification 5 Kanji ~~RELEASE NOTES For U401394 ~~Corrective Service 2007 .tp delete 1.9i .sk 2;.fo on :hp2.INITIAL COMMENTS:ehp2. :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 contains Corrective Service 2007 updates which may be applied on top of AIX Version 3.1.5 or 2006 update for the RISC System/6000 and Optional Program Products. :p.:hp2.Notice to Xstation users::ehp2. Check your current level of x_st_mgr.obj and x_st_mgrmEn_US.msg by following command: :xmp. lslpp -h x_st_* :exmp. :p.If this command returns 1.2 for x_st_mgr.obj and 1.1 for x_st_mgrmEn_US.msg, you will need to install Manager/6000 version 1.2 messages(x_st_mgrmEn_US.msg) using this 2007 PTF tape before you will be able to successfully apply the update to Xstation Manager messages included on this 2007 PTF tape. :p.:hp2.Notice to AIX X-Windows 3270 Emulator users::ehp2. The following must be done BEFORE updating AIXwindows Runtime/6000: :xmp. cp /usr/lpp/fonts/fonts.alias /usr/lpp/fonts/fonts.alias.orig cp /usr/lpp/fonts/fonts.dir /usr/lpp/fonts/fonts.dir.orig When you have finished updating AIXwindows Runtime, copy the originals back: cp /usr/lpp/fonts/fonts.alias.orig /usr/lpp/fonts/fonts.alias cp /usr/lpp/fonts/fonts.dir.orig /usr/lpp/fonts/fonts.dir :exmp. :p.:hp2.Notice to FORTRAN users::ehp2. Because there are two versions of FORTRAN contained on the media, your update status field will show "failed" if you update FORTRAN. This does not mean that the whole update failed! Error messages similar to the following will be shown for both xlfrte.obj and xlfcmp.obj: :xmp. 0504-025 The version or release of the update to LPP option xlfrte.obj is greater than the version or release of the installed option. You must install the newer release to apply thus (sic) update. 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.PLEASE check the SMIT update messages and use lslpp -h to make sure the other LPP's were updated successfully. :p.:hp2.Notice to ESSL users::ehp2. You have to update BOS before you update ESSL. :p.:hp2.Notice to X11kanji users::ehp2. There is a problem with 2007 reject not restoring the Kanji fonts back to the previous level. All Kanji fonts become unaccessible although everything was back to the correct level after the reject of 2007 update. The problem was caused by the reject process not runing the "mkfontdir" commnad. A recovery is run following commands: :xmp. cd /usr/lpp/fonts/16; mkfontdir cd /usr/lpp/fonts/24; mkfontdir :exmp. :hp2.Check Your Package:ehp2. :p.Please verify you have received the appropriate media listed below. If your package is incomplete please contact the appropriate support organization. Refer to :hp2.Problem Reporting Numbers:ehp2. for more information. :p.1/4-Inch Cartridge Tape: :ul compact. :li.One 6150(QIC-120) 1/4-inch Data Tape Cartridge :eul. :p.8mm Tape: :ul compact. :li.One 8mm Data Tape Cartridge :eul. :hp2.BEFORE INSTALLATION:ehp2. :p.This section contains information you should be aware of before installing this corrective service. :hp2.Correct Level Boot Diskettes:ehp2. :p.Retain your previous version level 3.1.5 BOS BOOT, Display and BOS Install/Maintenance diskettes for use with this release. :hp2.System Image Backup Installation And Creation:ehp2. :p.When using a system image backup 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. :p.System image backup creation requires you to define your block size to 512 bytes. This is because the boot diskettes will configure your tape drive at a block size of 512 bytes. Use the "smit chgtpe" command to verify/change the tape block size. :p.A system image backup tape may be created using the "smit startup" Backup System menu or the "mkszfile" and "mksysb" commands. :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. :hp2.Verify The Tape Block Size:ehp2. :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 processes. Use the "smit chgtpe" command to verify/change the tape block size. :hp2.Backup Your System:ehp2. :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 corrective service. :hp2.The Update Process:ehp2. :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 Notes For 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. :hp2.Applying Selective Updates:ehp2. :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 boskj.obj can be applied first, and at a later time, updates to xlfcmp.obj can be applied. However, if updates to bosnet.tcpip.obj were applied, all previously applied updates to all program products would have to be committed, before bosnet.nfs.obj could be updated. :hp2.Displaying Corrective Service Contents:ehp2. :p.You can generate a list of all programs for which updates exist on the corrective service. In displaying the contents 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. :hp2.UPDATING WITH LIMITED DISK SPACE:ehp2. :p.In order for the update tools to provide apply/commit/reject capability, previous versions of the files being updated are saved. Some machine configurations with limited free space will experience difficulties 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. :hp2.Temporary Space Update:ehp2. :p.The "updatep" and "instupdt" commands accept a "-t" option that allows the user to identify a directory where additional space is available. This space can reside in another file system (/u for instance), 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 "updatep/instupdt" commands will query the directory to insure adequate space for the saved files. It also remembers where the saved files are located so that commit/reject can be executed at a later time. :p.These file systems must be writeable by root for the update to occur. This is especially important in the NFS case since the default owner for an NFS mounted file system is 'nobody'. The file system should be exported with root access authority. :p.In addition, the server must provide protection so that the saved files for the client are not overwritten by another client. A suggestion would be to establish a large file system on the server (i.e. /tempspace) and make a directory with the client's host name (i.e. /tempspace/client01). The server would export a /tempspace/clientxx for each client being supported. The client would mount /tempspace/client01 as /save. On the updatep command line, the option specified would be "-t /save". :hp2.Unprotected Mode Update:ehp2. :p.The "updatep" and "instupdt" commands accept "-N" option that directs the program to not save any previous versions of the files to be updated. 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. :hp2.Possible Files To Delete:ehp2. :p.While temporary space update reduces the need for file system space, the "updatep" command still uses some space on /usr. If the /usr space is not adequate, the next option is the unprotected mode update. This option uses the absolute minimum amount of file system space. If unprotected mode will not work, the only options left are to remove code in the file system or to obtain additional hard disks. :p.A good candidate for backing up on removable media is the file /usr/lpp/info/$LANG/aixmin/aixmin.rom (where $LANG is the language environment variable). This file will save around 2.7 MB and will not affect the operation of update except for help popups when using SMIT. :p.If space on / (root) is required, some files will need to be backed up and removed to make space available. Possible file candidates are identified below. :p.AIX contains unique support code for models 730 and 930 of the RISC System/6000. This code can be removed permanently on non-730/930 machines. The files are: ~/etc/drivers/eudd ~/etc/drivers/gemdd ~/etc/methods/cfg6193 ~/etc/methods/cfggem ~/lib/libgem3dm2.a ~/etc/microcode/8ffdc2.00.01 ~/etc/microcode/8ffdgt.00.01 ~/etc/microcode/8ffdgu.00.01 ~/etc/microcode/8ffdsh.00.01 ~/etc/microcode/GEMBATS.BIN :p.The files in the following list can be removed temporarily if a High Performance 3D Graphics Display adapter is not present in the machine. ~/etc/drivers/geadd ~/etc/methods/cfgsab ~/etc/microcode/8ee6.00.01 ~/lib/libsab3dm2.a :hp2.PREREQUISITES AND PRECONDITIONS:ehp2. :p.The Active Service level for (boskj.obj)must be at 03.01.0005.0012 or 03.01.0006.0008. To determine the ACTIVE Service level of the Base Operating System use the following command: lslpp -h boskj.obj :p.:hp2.Base Operating System (boskj.obj):ehp2. :p.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. :hp2.AIXwindows Runtime Users (X11rte.obj):ehp2. :ul. :li.AIXWINDOWS RUNTIME MUST BE UPDATED TO CORRECTIVE SERVICE 2007 IF you update the Base Operating System. :li.You should put AIXwindows Runtime updates on PRIOR to updating the Base Operating System. If you update the Base Operating System first and then update AIXwindows Runtime, you may have to execute the following command as root: :xmp. /usr/lpp/X11/bin/X.rebind :exmp. :eul. :hp2.PC Simulator (pcsim):ehp2. :ul. :li.You cannot update PC Simulator while AIXwindows is running. :eul. :hp2.AIX DOS Server (pci):ehp2. :ul. :li.All pci users should execute the following command before installing this update. Failure to do so will result in link errors. :xmp. rm -rf /usr/pci/3 :exmp. :eul. :hp2.DISK SPACE REQUIREMENTS:ehp2. :p.Use the "df" and "lsvg" commands to determine the existing free space available in your file systems and volume groups. :hp2.Space Requirements To Begin Process:ehp2. :p.This information is provided primarily for those customers that have limited disk space. .ti ~ 05 .tp add 1.9i 3.0 MB ~~/ (root) 3.0 MB ~~/usr 7.5 MB ~~/tmp :hp2.Space Requirements For Identified Licensed Programs:ehp2. :p.Using all Update Images at Once: :p.The following space requirements are for those customers who choose to apply ALL the updates at once as opposed to selectively applying 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. APPLY or APPLY/COMMIT UNPROTECTED MODE :ul compact. :li. 10.5 MB / (root) 9.5 MB / (root) :li. 65.0 MB /usr 3.5 MB /usr :li. 7.5 MB /tmp 7.5 MB /tmp :eul. :p.Base Operating System (boskj.obj) ONLY: :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. APPLY or APPLY/COMMIT UNPROTECTED MODE :ul compact. :li. 8.0 MB / (root) 8.0 MB / (root) :li. 21.5 MB /usr 3.5 MB /usr :li. 7.5 MB /tmp 7.5 MB /tmp :eul. :p.AIXwindows Run Time (X11rte.obj) ONLY: :ul compact. :li. 3 MB / (root) :li. 14.0 MB /usr :li. 7.5 MB /tmp :eul. :hp2.Space Requirements For Rejecting Identified Licensed Programs:ehp2. :p.All Licensed Program Updates :ul. :li. 4.5 MB / (root) :li. 2.5 MB /usr :li. 7.5 MB /tmp :eul. :hp2.PROCEDURES:ehp2. :ol. :p.:hp2.Note::ehp2. :ul. :li.Use only the root account to install or update. :li.Tape block size must be 512 bytes. :li.Quiesce the system. :eul. :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 suggestions will stop all but the necessary processes. :ul. :li.Unmount any nfs mounted filesystems. :li.sh /etc/nfs.clean (to kill NFS processes) :li.sh /etc/tcp.clean (to kill TVP/IP processes) :li.killall - (Note this is killall with the minus sign.) :li.nohup /etc/syncd 60 > /dev/null& (Restarts the syncd daemon.) :eul. : :li.To reinstall AIXwindows Runtime. :p.Insert the Tape. :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. :li.To update Base Operating System and other Optional Program Products, AIXwindows Development, Personal Computer Simulator, 3278/79 Emulator, System Network Architecture, Network Manager. :eol. :ul. :li.Execute: smit instupdt_apply_commit :li.List (F4) and select the DEVICE name. :li.List (F4) and Select (F7) the update image you wish to apply. Press Enter when finished selecting. :ul compact. :li.To apply but not commit, position the cursor on the "APPLY or APPLY/COMMIT?" entry and change the 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.To override the apply process, change the "SAVE Replaced Files?" entry field to "No". Warning: This is an unprotected process. If an update fails for any reason, you may have to reinstall that program and attempt the update again. :li.To have the apply process save the old files in a directory other than /usr/inst_updt, specify a directory in the entry field for "SAVE Directory". :eul. :li.Press Enter to begin the install process. :li.Exit SMIT (F10). :li.Shutdown and reboot your system. This is mandatory after updating Base Operating System (boskj.obj). Use the "shutdown -Fr" command. :eul. :hp2.ADDITIONAL REMARKS:ehp2. :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.InfoExpolorer ispaths file :p.The ispaths.full file has been changed in this 2007 update. The effects of the change will not be implemented unless you do following commands: :xmp. cd /usr/lpp/info/data mv ispaths ispaths.old cp ispaths.full ispaths :exmp. :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.A message will indicate a successful update such as the following example for boskj.obj: :xmp. updatep: The UPDATE of LPP bos with the following options was successful. boskj.obj :exmp. :p.In rare cases, the system will fail on a specific optional program product and reject the update. The command status field of SMIT will indicate failed and a message will be displayed similar to the following example for boskj.obj: :xmp. 0504-048: The UPDATE of LPP boskj with the following options has failed. The LPP is being rejected. boskj.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.Users should reread the README files for updated optional program products. :li.The update scripts for BOS will delete the default umask setting in /etc/profile. :li.The default and individual umask settings are maintained in /etc/security/user. :eol. :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.