.* TIMESTAMP 08/14/90 .sp 2 .rf on .df 1 font x0pr12 .bf 1;.sp 2 .hr left right SHELF/REPRO: XXX BIN XXXXXXXX PTFU401164 PRODNUM 00/00/89 .rf off .* .im NEWTOP MEMORANDUM TO:&tab.LICENSEES OF AIX VS COBOL RUN TIME ENVIRONMENT/6000 &tab.&tab.&tab.&tab.&tab.PROGRAM PRODUCT,5601-259 .sk 1 :table cols='10m *' rules=none frame=none. :row. :c.SUBJECT: :c.AIX VS COBOL Run Time Environment/6000 :row. :c. :c.Corrective Service # U401164 :row. :c. :c.Cumulative PTF Release Notes :etable. .sk 1 .sk 2;.fo on :hp2.A: Apar Abstracts:ehp2. :sl compact. :li.IX12044 Segmentation violation in ACCEPT for args > 112. :li.IX11118 Highlighting would remain on after being set. :li.IX11457 Screen attributes where incorrectly passed. :esl. :hp2.B: Prerequisites:ehp2. :p.The user must have installed the base code. :hp2.C: General Comments:ehp2. :p.The AIX Corrective Service media in this package contains updates to AIX VS COBOL Run Time Environment for the RISC System/6000. :p.When examining customer problem reports for this PTF, please note that Apar IX11456 is not actually included in this PTF. :hp2.CHECK YOUR KIT:ehp2. :p.Check the contents of your PTF kit as soon as you receive it to verify that you have received all of the items necessary to apply and subsequently commit the software updates contained in this PTF ship. The following paragraphs list the items that should be contained in each type of PTF kit. If anything is missing, please call the IBM Software Defect Support Line at (800) 237-5511. :p.3.5-Inch Diskette PTF Kit: Each RISC System/6000 has a 3.5-inch diskette drive as standard equipment. If you received the 3.5-inch diskette PTF kit you should have received the following items: :ul compact. :li.3.5-inch diskettes. :li.This document. :eul. :hp2.BEFORE YOU APPLY/COMMIT THIS PTF:ehp2. :p.Before you begin the apply and/or commit of this PTF, please read the rest of these installation instructions. :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 this PTF. :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 at a later date. Alternatively, you can apply and commit the updates in one step. Once you commit the updates you cannot reject them. SMIT can be used to commit or reject applied updates from the "Install and Update Optional Program Products" menu. :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 disk partitions to accommodate the update, no notification will be given and the update will proceed. For information on the update process in which space is severely limited, refer to the UPDATING WITH LIMITED DASD section in this document. :p.If you have never installed PTF updates on a RISC System/6000 before, we suggest you become more acquainted with the details of the process by reviewing the updatep and instupdt commands in InfoExplorer. :hp2.APPLYING SELECTIVE UPDATES:ehp2. :p.With AIX Version 3.1 for the RISC System/6000 you have the ability to install all the updates found on the PTF or, if you so choose, install only selected subcomponents of the operating system and optional program products. :hp2.DISPLAYING PTF CONTENTS:ehp2. :p.You can generate a list of all programs for which updates exist on the PTF. 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 or the command line to view these summaries. :hp2.PTF INSTALLATION INSTRUCTIONS:ehp2. :hp1.Note::ehp1. The following procedures step you through the installation of this PTF via SMIT. For command line syntax refer to InfoExplorer. :hp1.Note::ehp1. These procedures are guidelines that should be sufficient enough for most AIX V3.1 environments. For those customers that have special needs and requirements not covered in these instructions, please refer to InfoExplorer for more details. :p.We are assuming that you wish to apply the software updates first, before committing them to permanent use. After you have applied your updates and have determined if you want to make these changes permanent you can use SMIT later to commit them or reject them, freeing up space in the process. :ol. :li.If the bos update (bos ptf not included in this package) has not been applied, sufficient free space must be available in /usr for a successful compiler update. If compiler update fails, increase free space in /usr and repeat update process. :li.Insert your media in the appropriate drive. :li.Login as root. :li.Unmount any NFS mounts and stop all processes. :p.Many of the optional program products can be stopped via SMIT but not all. Refer to InfoExplorer. Specifically, we recommend that you find the process id of the sync daemon (/etc/syncd) and use the kill command to stop the process. The process id is found by entering "ps -e | grep syncd". In addition, one command that is very effective in stopping all but the neccessary processes is the 'killall - ' command. The downside to using the killall command is that some processes may require special cleanup procedures before they can be stopped. Others may require special cleanup procedures before they can be restarted. Please use this command with care. :li.Enter smit updatep :p.You should be at the Install and Update Optional Program Products menu. :li.Select Update Optional Program Products :p.You should be at the Update Optional Program Products menu. :li.Hit F4 to display a list of devices to choose from. :li.Choose the appropriate device. :p.After you make your choice, the Update Optional Program Products menu will look similar to this: :table cols='2* * *' rules=none frame=none. :row. :c. :c.&lbrk.Entry Fields&rbrk. :c. :row. :c. DEVICE name :c./dev/rmt0.1 :row. :c. OPTION name :c.&lbrk.all&rbrk. :c.+ :row. :c. APPLY or APPLY/COMMIT? :c.Apply and Commit :c.+ :row. :c. EXTEND logical disk partitions? :c.Yes :c.+ :row. :c. Create BACKUP-FORMAT file? :c.No :c.+ :row. :c. BYPASS special instructions? :c.No :c.+ :row. :c. REMOVE Preload BFF? :c.No :c.+ :etable. :li.Position the highlighted cursor on the "APPLY or APPLY/COMMIT?" entry and change the entry field to "Apply only" by hitting the Tab key. :sl. :li.&lbrk.all&rbrk. is the default and recommended choice for the OPTION name field. However, specific components may be selected by entering F4 at the OPTION name field. Follow directions displayed to choose components. From this screen, components may be applied individually. However, components that are applied must be committed before additional components can be applied. :li.You may also optionally choose to change other fields. Refer to InfoExplorer for details. :esl. :li.Press Enter key to begin the installation of this PTF. :eol. :p.When finished, you can simply reboot your system with the 'shutdown -Fr' command or you can restart your processes and re-establish your NFS mounts. :hp2.NOTES FOR UPDATING WITH LIMITED DASD:ehp2. :p.In order for the update tools to provide apply/commit/reject capability, it is necessary to save the previous versions of the files being updated. In some machine configurations, this will cause problems due to insufficient space in the /usr filesystem. This note will address some options to reduce the usage of /usr to a minimum level. :p.Two procedures have been developed to address limited /usr filesystem space problems. They are: temporary space update and unprotected mode update. They are described in the following sections. :hp3.Temporary Space Update:ehp3. :p.The updatep and instupdt commands accept a -t parameter that specifies a directory where additional space is available. This space can reside in another file system (/u for instance), another logical volume filesystem or an nfs mounted filesystem. :p.Updatep/instupdt will query the directory to insure adequate space for the temporary files. It also remembers where the saved files are located so that commit/reject can occur at a later time. :p.These filesystems must have root access for the update to occur. This is especially important in the nfs case since the default owner and group for an nfs mounted filesystem is nobody. The filesystem must 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 filesystem on the server (i.e. /tempspace) and make a directory with the client's hostname (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 update command line, the option specified would be -t /save. :hp3.Unprotected Mode Update:ehp3. :p.Updatep/instupdt have been modified to accept a -N flag. This flag directs the program to not save any previous versions of the files to be updated. There is no protection for an unsuccessful update for this option. The only avenue for recovery is a re-install of the root volume group code. :hp3.General Comments:ehp3. :p.While temporary space update reduces the need for filesystem space, it still requires some extra space on /usr. There will be cases where this will not be adequate. In this case, the next option is the unprotected mode update. It uses an absolute minimum amount of filesystem space. If unprotected mode will not work, the only option is to remove code in the filesystem or to obtain additional local dasd. :p.A good candidate for backing up on diskette 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 smit helps. :hp3.Accessing the Modified Update Tool:ehp3. :p.In order to access the above new functions, the update for bsmEn_xx.msg (where xx denotes the language to be updated) must be run. This will bring in the changed update tools, and make them available for the next invocation of updatep/instupdt. bsmEn_xx.msg is part of the bos update. The bos update must be ordered to receive the modified update tool. :hp2.D: Additional Instructions:ehp2. :ol. :li.During the update process, we recommend that the sync daemon be turned off. Use the kill command to stop the daemon (/etc/syncd) before starting the update. :p.Error messages, similar to the following, may be seen during the bos.obj or boskj.obj update: :xmp. umount: 0506-349 Cannot unmount /dev/hd5: A device is already mounted or cannot be unmounted. dd: 0511-040 2+0 records in. dd: 0511-041 2+0 records out. mkfs: mkfs: 0506-210 The filesystem is currently mounted. mount: mount: 0506-324 Cannot mount /dev/hd5 on /blv: A device is already mounted or cannot be unmounted. :exmp. -or- :xmp. umount: error unmounting /dev/hd5: Device busy 2+0 records in 2+0 records out mkfs: Filesystem is currently mounted. mount: /dev/hd5 on /blv: Device busy :exmp. :p.Typically, the AIX update process recovers and results in a successful installation. In this instance, the messages should be of no concern. A message will indicate a successful update such as the following: :xmp. updatep: The UPDATE of LPP boskj 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 field of SMIT will indicate failed and a message will be displayed similar to the following: :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.During the update process, an attempt to update an option 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. :li.If the update involves several optional program products, the failure reflects only the optional program products that are not installed. This error message should be displayed for each optional program product that is not installed. Installed optional program products should 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. :eol. :p.Problem reporting numbers are as follows: Software Defect Support Line at (800) 237-5511, Hardware Support at (800) IBM-SERV, System XTRA customers at (800) IBM-XTRA. Howto or installation/configuration problems should be directed to your local IBM Service Representative or IBM authorized representative.