.***************************************************************** .* * .* Copyright: IBM Corporation 1988 * .* All rights reserved. * .* * .* Security Classification: IBM INTERNAL USE ONLY * .* * .* Purpose: Master file for creation of Memo to users. * .* * .* Document/part number: None * .* * .* Product release level: Not Applicable * .* * .* Minimum BookMaster release level required: 2.0 * .* * .* Required style: Memonum Style * .* * .* Imbedded Script files: None * .* * .* Included page segments: None * .* * .* Notes: Use only BookMaster tags, reference Corporate * .* Standard 0-0145-021 and BookMaster User's Guide * .* The "memonum" is supplied by SPC or ISMD, leave * .* it blank. * .* * .* * .* Change status: 1.st version, sublevel 1, July 1989 * .* * .***************************************************************** .* .* Publications, you might find useful, during the work. .* .* SC34-5009 BookMaster, Users Guide. .* .* SC24-5220 System Product Editor, User's Guide (XEDIT) .* .* C-S 0-0145-021 Corporate Standard: .* Document Interchange for Customer and Service Information .* .***************************************************************** :userdoc. :prolog. .*********************************************************************** .* BOOKMASTER SKELETON FILE FOR CREATING A MEMO TO USERS .*********************************************************************** .* .* AUTHOR: Insert Program Number between the single quotes: .* .nameit symbol=progno text='5756-030'. .*********************************************************************** .* .* AUTHOR: Do you have Feature Codes to add, replace the xxx with YES .* between the single quotes, this controls the appearance of the .* text Features under subject. .* .nameit text='true' symbol='xxx' .* .* AUTHOR: Insert Feature Codes between the single quotes: .* .nameit symbol=feat text='????/????/????'. .*********************************************************************** .* .* AUTHOR: Insert Program Name between the single quotes .* .nameit symbol=progname text='AIX Version 3 for RISC System/6000' .* .*********************************************************************** .* .* AUTHOR: Insert Operating System under which the program is installed .* .nameit symbol=sysname text='AIX'. .*********************************************************************** .* .* AUTHOR: Insert Release Number between the single quotes: .* .nameit symbol=release text='01'. .*********************************************************************** .* .* AUTHOR: Insert Modification Level Number between the single quotes .* .nameit symbol=modifica text='00'. .*********************************************************************** .* .* AUTHOR: Next you have to choose which memo you want to make. .* You can choose between: .* .* 1 MEMO TO NEW LICENSEES (with enclosed program directory) .* 2 MEMO TO NEW LICENSEES (with no program directory enclosed) .* 3 MEMO TO CURRENT LICENSEES .* 4 PTF MEMO (without MRM) .* 5 PTF MEMO (with MRM) .* 6 BLANK FORM (you add all the text yourself) .* 7 READ THIS FIRST (you add all the text yourself) .* .* You just replace "n" in symbol='n' with the number "1,2,3 .* 4,5,6 or 7 .* .nameit text='true' symbol='7' .* .* AUTHOR: If you make a memo 6, you have to scroll back and add the .* addressee before the Program Name between the single quotes .* as follows: .* .* .nameit symbol=progname text='Current Licensee of .* program name' .* .*********************************************************************** .* .* AUTHOR: Specify which Distribution Center - SPC or ISMD - that is the .* current Primary Program Library - Do it by replacing SPC with .* ISMD between the two single quotes in the following line if .* needed. 'SPC' or 'ISMD' must be written in upper case .* .nameit symbol=DISTLIB text='ISMD' .* .* Do not change the following line .* .nameit text='true' symbol=&DISTLIB. .* .*********************************************************************** .* .* AUTHOR: For ISMD use only: Set the R&A Coordinator ID Code between the .* two single quotes .* .nameit symbol=racoord text='????' .* .*********************************************************************** .* .* AUTHOR: If you make a Memo To Current Licensees (3), you can add .* from 1 to 5 different Attachments: .* .* "att1" Summary of changes .* "att2" List of Program Material .* "att3" Statement of Program Support .* "att4" Ordering Information for Basic Material .* "att5" Ordering Information for Optional Material .* .* Replace the xxxx in the following symbols with .* att1, att2, and so on according to the number of .* attachments you will be adding. .* .* Do not change the symbols you will not be using. .* That is, leave them with xxxx. .* .nameit text='true' symbol='xxxx' .nameit text='true' symbol='xxxx' .nameit text='true' symbol='xxxx' .nameit text='true' symbol='xxxx' .nameit text='true' symbol='xxxx' .* .* Search for "Attachment att1" "Attachment att2" and so on .* later in this file to find where to place the text of .* your attachments. .* .*********************************************************************** .* .* AUTHOR: If you want to make a PTF Memo 4, scroll through the .* document until you reach the text: .* .* Add the PTF Sequence Number for Memo 4 .* .*********************************************************************** .* .* AUTHOR: If you want to make a PTF Memo 5, scroll through the .* document until you reach the text: .* .* Add the PTF and MRM Label Numbers for Memo 5 .* .*********************************************************************** .* .* AUTHOR: If you want to make a Memo 6 (you add the text yourself) .* scroll until you reach the text: .* .* Memo 6, Here you add your own text .* .*********************************************************************** .* .* AUTHOR: If you want to make a Memo 7 (READ THIS FIRST) .* scroll until you reach the text: .* .* Memo 7, Here you add your own text .* .*********************************************************************** .* .* AUTHOR: If you want to add some text to any of the standard memos .* scroll until you reach the text: .* .* Here you add the Additional Text .* .*********************************************************************** .* .* NOTE: Do not change anything from here to: .* .* Add the PTF Sequence Number for Memo 4 .* .*********************************************************************** .nameit symbol=memonum text='' :docprof style=memonum punct='' language=english. :revision id=first char='|' run=yes. :eprolog. :frontm. .* :body. :griddef id=header rules=none hunits='* * *'. .************************* Logo :grid refid=header. :gridseg. :gridarea. :artwork &ibml36. :gridarea.&rbl. .************************* Address SPC/ISMD :gridarea. .************************* Address SPC .config addre1 on .when 'SPC' insert :lines. Software and Publications Center Sortemosevej 21 DK-3450 Alleroed Denmark :elines. .config addre1 off .************************* Address ISMD .config addre2 on .when 'ISMD' insert :lines. :elines. .config addre2 off :egrid. .************************* Rule :artwork rule depth=medium. .************************* Set up Memorandum to/Subject .*.config memo7 on .*.when '7' delete :artwork depth=5. .getw symbol=memoto gmltype='hp2' text='Memorandum to: MM' :dl tsize=&memoto. :dt.Memorandum to: .************************* Title :dd. .config type1 on .when 'SPC' insert .************************* SPC, Memo 1 2, New Licensees of .config navn1 on .when '1 or 2' insert New Licensees of .config navn1 off .************************* SPC, Memo 3, Current Licensees of .config navn3 on .when '3' insert Current Licensees of .config navn3 off .************************* SPC, Memo 4 5, Licensees of .config navn45 on .when '4 or 5' insert Licensees of .config navn45 off .config type1 off .************************* ISMD, Memo 1 2 3 4 5, Licensees of .config type2 on .when 'ISMD' insert .config navn12345 on .when '1 or 2 or 3 or 4 or 5 or 7' insert Licensees of .config navn12345 off .config type2 off .************************* SPC/ISMD, Program name, Program number &progname. .*(&sysname.) .br;Program Number &progno. .************************* SPC/ISMD, Subject, Release, Modification Level :dt.Subject: :dd.Release &release., Modification Level &modifica. .************************* Features, yes or no .config feattea on .when '???' insert .config feattea off .config featteb on .when 'YES' insert .************************* Features text for memo 1, 2, 3, 6, 7 .config featte1 on .when '1 or 2 or 3 or 6 or 7' insert .br;Features &feat. .config featte1 off .************************* Features text for memo 4, 5 .config featte2 on .when '4 or 5' insert .br;PTF(s) for Features &feat. .config featte2 off .config featteb off :edl. .*:p.&rbl. .*:p.&rbl. .*.config memo7 off .************************* Main text of Memorandums starts here .************************* MEMO 1 .config memo01 on .when '1' insert :p.Thank you for your order. The Material you have received is listed on the enclosed Packing List. Please review the Packing List to ensure you have received all items listed. :p. .config center1 on .when 'SPC' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Delivery Report which is enclosed for your convenience. .config center1 off .config center2 on .when 'ISMD' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Distribution Questionnaire which is enclosed for your convenience. .config center2 off :p. :p.For further description of all available material, see the enclosed Program Directory. :p. .config memo01 off .************************* MEMO 2 .config memo02 on .when '2' insert :p.Thank you for your order. The Material you have received is listed on the enclosed Packing List. Please review the Packing List to ensure you have received all items listed. :p. .config center1 on .when 'SPC' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Delivery Report which is enclosed for your convenience. .config center1 off .config center2 on .when 'ISMD' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Distribution Questionnaire which is enclosed for your convenience. .config center2 off :p. .config memo02 off .************************* MEMO 3 .config memo03 on .when '3' insert :p.The material you have received is listed on the enclosed Packing List. Please review the Packing List to ensure you have received all items listed. :p. .config center1 on .when 'SPC' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Delivery Report which is enclosed for your convenience. .config center1 off .config center2 on .when 'ISMD' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Distribution Questionnaire which is enclosed for your convenience. .config center2 off :p. :p.Attached to this memorandum: .tabrack 'ul----Ordering Information for Optional Material. ' :ul. .config attac1 on .when 'att1' insert :li.Summary of Changes .config attac1 off .config attac2 on .when 'att2' insert :li.List of Program Material .config attac2 off .config attac3 on .when 'att3' insert :li.Statement of Program Support .config attac3 off .config attac4 on .when 'att4' insert :li.Ordering Information for Basic Material .config attac4 off .config attac5 on .when 'att5' insert :li.Ordering Information for Optional Material .config attac5 off :eul. :p. :p.Please refer to the attachment(s) for further description. .config memo03 off .************************* MEMO 4 .config memo04 on .when '4' insert :p.The material you have received is listed on the enclosed Packing List. Please review the Packing List to ensure you have received all items listed. :p. .config center1 on .when 'SPC' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Delivery Report which is enclosed for your convenience. .config center1 off .config center2 on .when 'ISMD' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Distribution Questionnaire which is enclosed for your convenience. .config center2 off :p. :p.The following is the only PTF(s) that is/are currently valid. It/they is/are enclosed with this memorandum. :p. :hp2.PTF No::ehp2. :ul. .************************************************************************ .************************************************************************ .* .* AUTHOR: Add the PTF Sequence Number for Memo 4 - .* after the first :li. .* :li. .* .* If you have more PTF Sequence Numbers, enter each one .* after a :li. and remove the .*** .* .***:li. .***:li. .***:li. .***:li. .************************************************************************ .*********************************************************************** .* .* NOTE: Do not change anything from here to: .* .* Add the PTF Sequence Number/MRM Label for Memo 5 .* .*********************************************************************** :eul. :p.This PTF is subject to the provisions of the Agreement for IBM Licensed Programs. By this Agreement, the customer has agreed not to provide or otherwise make available the PTF to any person other than the customer or IBM employees. :p. :p.If the customer wishes to dispose of the licensed PTF(s), which remains the property of IBM, the customer should destroy the PTF(s) and certify the destruction thereof to IBM in writing. :p. :p.The PTF may not be given to third parties, except during the period any such person is on the customer's premises with the customer's permission for the purposes specifically related to the customer's use of the PTF. :p. .config memo04 off .************************* MEMO 5 .config memo05 on .when '5' insert :p.The material you have received is listed on the enclosed Packing List. Please review the Packing List to ensure you have received all items listed. :p. .config center1 on .when 'SPC' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Delivery Report which is enclosed for your convenience. .config center1 off .config center2 on .when 'ISMD' insert :p.If there are any discrepancies between the package contents and the Packing List, please report these via the Software Distribution Questionnaire which is enclosed for your convenience. .config center2 off :p. :p.The enclosed Machine Readable Materials contain the only PTF(s) that is/are currently valid. The MRM label(s) show the following PTF sequence number(s). :p. .*text ptf mrm label :dl tsize=15 termhi=0. :dthd.PTF :ddhd.MRM Label .************************************************************************ .* .* AUTHOR: Add the PTF Sequence Number/MRM Label for Memo 5 .* Place the PTF Sequence Number after the first ":dt." .* below and the MRM Label after the first ":dd.". .* .* If you have more than one set - remove the ".***" and add .* the next set after the following ":dt./:dd." :dt. :dd. .***:dt. .***:dd. .***:dt. .***:dd. .***:dt. .***:dd. .************************************************************************ .*********************************************************************** .* .* NOTE: Do not change anything from here to: .* .* Memo 6, - Here you add your own text .* .*********************************************************************** :edl. :p. :p.This Program Temporary Fix (PTF) is subject to the provisions of the Agreement for IBM Licensed Programs. By this Agreement, the customer has agreed not to provide or otherwise make available the PTF(s) to any person other than customer or IBM employees. :p.If the customer wishes to dispose of the licensed PTF(s), which remains the property of IBM, the customer should destroy the PTF(s) and certify the destruction thereof to IBM in writing. :p.The PTF may not be given to third parties, except during the period any such person is on the customer's premises with the customer's permission for the purposes specifically related to the customer's use of the PTF. :p. .config memo05 off .************************* MEMO 6 .config memo06 on .when '6' insert .************************************************************************ .* .* AUTHOR: Memo 6, - Here you add your own text .* .* Enter your text after the ":p." below. .* If you want to activate another Paragraph, remove ".***" .* before the next ":p." and add your text. .* :p. .***:p. .***:p. .***:p. .***:p. .*---------------------------------------------------------------------* .config memo06 off .************************* MEMO 7 .config memo07 on .when '7' insert .*****Space for Artwork :artwork depth=30mm. :table cols='*' width=page rules=none align=center frame=none scale='3.6'. :row. :c.READ THIS FIRST :etable. :artwork depth=80mm. .************************************************************************ .* .* AUTHOR: Memo 7, - Here you add your own text .* .* .*****Space for Artwork :artwork depth=20mm. :table cols='*' width=page rules=none align=right frame=none scale='1.0'. :row. :c.P/N 31F4227 :etable. .pa .pa .*****Space for Artwork :artwork depth=18mm. :table cols='*' width=page rules=none align=left frame=none scale='1.8'. :row. :c.WARNING! SYSTEM BACKUPS MAY NOT BE USABLE UNLESS YOU DO THE FOLLOWING: :etable. System image backups using the smit startup menu or the mksysb command may not be usable unless you make these changes. These procedures include changes needed to correctly create diskettes used to boot the system and to correctly create system backups. :p.Once your machine has been installed and boots from your hard disk, enter: :xmp. lslpp -h bos.obj :exmp. If the ACTIVE service level is 03.01.0003.00xx, you must do the following (you need to do this only once): :p.A. Change the mkszfile script. :p. Step 1 Login as root. 2 Type the following: cd /usr/bin 3 Type the following: cp mkszfile mkszfile.save 4 Type the following: sed -e 's/$8/$7/' mkszfile :p.B. Change the bosint scripts prior to making boot diskettes. :p. Step 1 Login as root. 2 Type the following: cd /usr/lpp/bosinst 3 Type the following: cp bosmenus bosmenus.save 4 Type the following: cp bosrest bosrest.save 5 Type the following: sed -e 's/\.5 -p//' bosmenus 6 Type the following: sed -e 's/\.5 -C/ -C/' bosrest :p.C. For customers with 8MM tape drives - Verify/Change block size to 512-bytes. :p. Step 1 Login as root. 2 Type the following: smit chgtpe 3 Change the BLOCK size entry field to 512. 4 Press and exit smit. :p.D. Create Bosboot, BOS Install/Maint, and Display Diskettes. :p.Instructions can be found in the Installation Guide (SC23-2341-01), on page 6. .pa .pa .*****Space for Artwork :artwork depth=18mm. :table cols='*' width=page rules=none align=left frame=none scale='1.8'. :row. :c.ABOUT THIS MEMO :etable. :p.This is the READ THIS FIRST second edition (February, 1991). :p.The information in this memo consists of hints for using the system, help with functions that the new user may find difficult, and last minute updates to the existing documentation. :p.This memo contains the information that is included in the file /usr/lpp/bos/README, plus some updates which did not make it into that file. Items that are different from /usr/lpp/bos/README are marked with :q.|:eq. in the left margin. :p.Users should also refer to other README files which are installed with the software. For information on locating those files, see :hdref refid=rdme. in this document. .*****Space for Artwork :artwork depth=30mm. :table cols='*' width=page rules=none align=left frame=none scale='1.8'. :row. :c.HOW TO USE YOUR DOCUMENTATION :etable. :ol. :li.Read the following sections of this READ THIS FIRST document: Errata for Installation Guide, Notes on Installation and Update, Understanding Paging Space Requirements, SMIT, and User Notes for InfoExplorer. AS YOU READ, COPY THE CHANGES INTO THE "Installation Guide" MANUAL FOR AIX VERSION 3. :li.Read the Installation Guide manual and follow the procedures for installing software on your RISC System/6000. Note: During the install process you can skip the step that tells you to read the AIX base operating system README file. :li.After you have installed your software, read the remaining sections of this READ THIS FIRST document. :li.You can then learn more about your system by reading your other hardcopy manuals or by reading in InfoExplorer, a software hypertext library. The flip cards in your Quickstart Kit tell you how to start InfoExplorer. Also note that within InfoExplorer is InfoTrainer, InfoTrainer contains lessons and interactive exercises for new AIX users. :eol. :toc. :body. :h2.Notes on Installation and Update :h3.Base Operating System Installation Caveat NOTE: When installing the base operating system, ensure that the boot diskettes are the same level as the base operating system to be installed. :rev refid=first. :h3.Errata for Installation Guide :p.Before installing, make the following corrections to the Installation Guide. :h4.Procedure for Starting up a Preinstalled System On page 6, step #8, the sentence should end with "continue to step 1." :h4.Turning On The System Unit Reminder: When you turn on your system it is very important to turn on all external attached devices BEFORE turning the system unit power switch to the ON position. The attached devices must be on BEFORE the system unit so that the system unit can properly identify them during the boot process. The above procedure is discussed in the following locations in the "Installation Guide" manual: page 5 step #2(bottom 1/2 of page); page 15 step #2 (bottom half); page 29 step #3(bottom half); and page 44 step #3. :h4.Is A Display Adapter Installed? If you are not sure whether or not you have a display adapter installed consult your "About your System" printout. It lists the hardware that is included with your system. You need to know this information in the following locations in the "Installation Guide" manual: page 15, step #6; page 29, step #7; page 43, step #7; and page 44, step #5. :h4.Exiting System Startup Menus The function keys for the SMIT Startup menu are described on pages 8, 22, 36, 53 and 64 of the AIX Version 3 Installation Guide manual. On each of these pages you should change the "Exits SMIT" command to read "F10 or Esc+0". :h4.Reading BOS README If you use the pg command to read the readme file, you can type "q" at the ":" prompt to Quit reading the file. This procedure is described on page 6, step #5; page 20, step #12; page 34, step #15; and page 52, step #19. "pg README" will perform the same function as "cat README | pg". :h4.Moving Up in the README File To page up, you must press the Enter key after you press the -(minus) key. This procedure is discussed in the following locations in the "Installation Guide" manual: page 6, step #5; page 20, step #12; page 34, step #15; and page 52, step #19. :h4.Creating Bosboot, BOS Install/Maint, and Display Diskettes SPECIAL NOTICE FOR KANJI USERS: The bosboot, mkinstdskt, and mkdispdskt routines described in the AIX Version 3 Installation Guide, under the section "Creating Bosboot, BOS Install/Maint, and Display Diskettes" does NOT apply on KANJI systems. KANJI systems use the standard National Language Services diskettes to boot and install AIX Version 3. The procedures for creating these diskettes are described on pages 6 and 20 of the AIX Installation Guide manual. In each of these locations, you need to note the following changes to the procedures: :ol. :li.This procedure requires a minimum of 1.44 meg capacity diskettes. :li.Under step 1a, to format a blank diskette, just type "format" at the command line. :eol. :h4.Starting SMIT Startup On page 8, paragraph 1, you only need to type "smit startup" at a command line if you did NOT use the desktop procedures listed in step #10 to start SMIT. :erev refid=first. :h4.8mm Tape Install Procedure If you have an 8mm INTERNAL tape drive and you are going to do software installation from 8mm tape, then make the following changes to the Installation Guide: On page 15 under the heading "Procedure for Installation and Maintenance with Tape", replace steps 1-4 with the following steps: :ol. :li.Turn System Key to the SECURE position. :li.Turn on all attached devices, such as terminals and external drives. :li.Turn system unit power switch to ON. :li.Wait for the LED to show "200". :li.Press the 8mm tape drive eject button. Be patient, the door will open in 1 or 2 minutes. :li.Insert the tape labelled AIX Version 3 into the drive and close the door. If you have more than one tape, use the one labelled "Volume 1". :li.Turn the System key to the SERVICE position.(Note: NOT the SECURE position) When the LED shows the code "C31", continue with step 5 on page 15 of the Installation Guide. :eol. Again, these procedural changes are only necessary if you are using an INTERNAL 8mm tape drive. :rev refid=first. :h4.Installation In the Installation Guide, you need to cross out a sentence in the following locations: page 10, step #6 (bottom half); page 23, step #6; and page 37, step #6. The sentence that should be deleted is "Press F4 while on an OPTION name field, to view the table of contents.". Do not insert the CD-ROM until after you read the instruction booklet located in the plastic shipping case containing your CD-Rom Hypertext Information Base Library. The case's "label" is a manual that slides out. Inserting the CD is discussed in the following locations in the "Installation Guide" manual: page 13 step #3; page 26, step #3; page 40, step #3; and page 56, step #3. On page 37 of the Installation Guide, between steps 3 and 4, you should insert the Volume 1 diskette for the Optional Program Product that you want to install. Page 37 of the Installation Guide, note that steps 4-10 must be repeated for each separate Optional Program Product that you want to install. Remember to insert the Optional Program Product's Volume 1 disk before you begin step 4. On page 54 in the Installation Guide, the "/usr/lpp.install" filename should be changed to read: "/usr/lpp.install/" Add a '/' directly after lpp.install. :erev refid=first. :h4.Booting From Diskettes When it is time to switch diskettes, the diskette drive may not stop spinning. If you receive a message to change disks (on-screen or by LED code), it is OK to eject a diskette even if the drive is spinning. The above procedure is discussed in the following locations in the "Installation Guide" manual: page 29, step #6(bottom of page); and page 44, step #6. :rev refid=first. After booting from tape or diskette, any stale mirrors are not automatically resynchronized in the root volume group. To resynchronize volume group(s) enter the command: :xmp. syncvg -v rootvg vg00 :exmp. or any other volume group name in the system. :h3.Other Errata :h4.AIX GL Graphics Library The documentation for the GL subroutine pixmode() is incorrect. When the pixmode setting is: :xmp. pixmode (PM_FASTMODE, FALSE); :exmp. the RGB mode pixels are packed as 0xAABBGGRR, and NOT as 0x00RRGGBB. For further information relating to the GL Graphics Library, please refer to /usr/lpp/gl/README. :h3.Notes to RISC System/6000 users with preloaded 120mb and 240mb disks :h4.120mb disks Your system has been preloaded with a subset of AIX. It is fully installed and immediately usable. Depending on the selected options that were installed your free space could range from greater than 20mb to no free space. Options to add additional space are: :ul. :li.add additional disks :li.create space on a server and mount it into the local filesystem :li.overmount a local filesystem (/u would be a good candidate) from a server :li.create a directory in another filesystem and symbolically link to it :li.delete a file system and reallocate it smaller :eul. There are probably other options as well. :h4.240mb disks Your system has been preloaded with the full AIX plus any additional options that may have been ordered. A portion has been pre-installed and is immediately available for use. It is BOSRUN, BOS Messages, BOSNET. You may also have immediate access to X11rte and DES if selected in your order. All other parts of AIX as well as any optional LPPS have been preloaded on the system. This means that they are in a packed format ready for installation by the user. They are located in the directory /usr/sys/preload. For proper installation to occur, some of the unused/unneeded parts must be removed. This will allow for enough free space to contain the desired parts. You did not order enough disks to contain all of AIX in a usable form. To determine what files to remove, do the following: :xmp. cd /usr/sys/preload egrep "preload|En_US" .toc | cut -f1,6-12 -d" " | pg :exmp. The result is the names of the preload files, followed by a list of the contents. Use this listing to determine what to delete. After determining what to delete, copy the files to backup media to save for later installation if the need may arise. The command to use is: :xmp. ls ..... | backup -ivf/dev/xxxx :exmp. where file1, file2 etc are the names of the files, and xxxx is the name of the backup device (rmt0, rfd0, or a file). Then the files may be deleted. Use the following command: :xmp. del etc. :exmp. It will prompt you to ensure that you are deleting the correct files. SMIT will then have more space to work with to allow for installation. :erev refid=first. :h3.Reinstall When booting the machine from the installation diskettes or tape, the user is presented with a menu of options which allows the user to install. This menu is similar to the following: :xmp. AIX 3.1 INSTALLATION AND MAINTENANCE Choose the ID number of the desired item. ID Choice 1 Install AIX with Current System Settings 2 Reinstall AIX with Current System Settings 3 View/Change Current System Settings 4 Commit Changes to System Settings but DO NOT Install 5 Perform System Maintenance :exmp. Choosing option 1 will destroy all contents of the hard disks which are specified for installation. Choosing option 2 will only recreate the file systems of / and /usr. These two file systems correspond with the logical volumes of /dev/hd4 and /dev/hd2 respectively. All other user file systems or data will be retained. The record of these file systems is also retained in the file "/u/filesystems". If you wish to recover the data on file systems which you have created, you must first copy the file "/u/filesystems" to "/etc/filesystems". You may also need to run the "fsck" command on those file systems to be recovered before trying to mount them. :h3.Re-install From Factory (bootable) Installation Tape On a Model 320 with internal hard disks that has been installed successfully by any means, it may not be possible to boot from a factory (bootable) installation tape. The system will boot from the disk and ignore the tape. To work around this problem, reset the NVRAM boot device list with the following command: :xmp. bootlist -m service fd rmt badisk scdisk :exmp. This will set the boot sequence to floppy disk, tape, disk. It will then be possible to boot from the tape and install normally. :h3.Image Installation Caveat: Creating Installation Diskettes When using a backed-up image to install a machine, you must boot from diskette and choose the tape device from which to install. Booting from tape and switching the tape does not work at this time. When you make the backed-up image you should also create a boot diskette to use when installing the image. Any updates applied to the machine the image was made from may have altered information on the boot diskette. If a new boot diskette is not created and used, there may be consistency problems in the configuration database causing problems with ODM commands and diagnostics. Procedures for creating BOOT and INSTALL diskettes for a RISC System/6000 are contained in the "INSTALLATION GUIDE" MANUAL. Corrections to these procedures are in the :hp2.Errata for Installation Guide:ehp2. section :hp2.Creating Bosboot, BOS Install/Maint, and Display Diskettes:ehp2. subsection. :h3.Network Configuration The following procedures are discussed in the following locations in the "AIX Environment RISC/6000 Installation Guide": page 12, page 24, page 38, and page 54, step 5. How to configure and start TCP/IP: 1. Enter the command "smit startup" and press ENTER. 2. Move the cursor to "TCP/IP" and press ENTER. 3. Select the option "TCP/IP Startup". 4. A Pop-up will be displayed listing "Available Network Interfaces". Move the cursor to the name of the Network Interface you want to use and press Enter. Note: "en0" = Ethernet, standard, "et0" = IEEE 802.3 Network Interface, and "tr0" = Token-Ring. 5. In the next menu the cursor will be highlighting the selection "Hostname". You must enter the hostname and TCP/IP address for your machine. Optionally, (check with your system administrator), you may also enter the Network mask, Nameserver address and domain, and the default gateway address. If the system has not been rebooted since the bosnet.tcpip.obj software was installed, then press the tab key to select "yes" for the option "START TCP/IP daemons Now". When you have finished editing this screen, press Enter to execute the TCP/IP startup configuration. When the command has completed, press the F3 function key three times to return the TCP/IP menu. If you are using a nameserver, then TCP/IP is now ready to use. NOTE: The TCP/IP Startup menu is intended to be used once and once only - for startup. If additional changes are required after exiting the panel, use the "further configuration" panel under TCP/IP. 6. If you are NOT using a nameserver, you may have to set up hostnames (relate names to internet addresses) for each of the hosts you want to communicate with. After starting TCP/IP, return to the TCP/IP menu and select the option "Add the Hostname for a Remote Server". Then add the name and Internet address and then press ENTER for each of the other systems you wish to communicate with on your network. After this information is entered, TCP/IP is ready to use. How to mount an NFS File System: Note: NFS allows you to mount a remote file system across a network. Before making an NFS mount, you must configure and start TCP/IP as described above. 1. Enter the command "smit startup" and press ENTER. 2. Move the cursor to "NFS" and press ENTER. 3. In the next menu the cursor will highlight the selection "Start NFS"; press ENTER. 4. At the next prompt, press the F4 key to list you choices. If you want NFS to be active now and to also be activated after each reboot, select "both". If you want to use NFS for just this session, select "now". This way, NFS will only remain active until you reboot the system. After you have made your selection, press ENTER to execute the command. After the command has completed, press the F3 key twice to return to the NFS menu. 5. Move the cursor to "Add a File System for Mounting" and press ENTER. The required entries for this menu are "PATHNAME of mount point", "PATHNAME of remote directory", and "HOST where remote directory resides". For example, if the Installation Code Server you are mounting from has been configured using the directory suggested in the Installation Guide, then the screen would look like this when it was completed: (Note: these are only examples and may not be the correct names for your system - ask your network administrator.) Add a File System For Mounting Type or select values in entry fields. Press Enter AFTER making all desired changes. [TOP] [Entry Fields] PATHNAME of mount point [/usr/lpp.install] PATHNAME of remote directory [/inst.images] HOST where remote directory resides [servername] Note: For the HOST line where we show the phrase "servername" type in the name of the Code Installation Server in the /etc/hosts file or on the nameserver. After you have entered the information in the above 3 lines, you may use the defaults values for the remaining entries. 6. Press ENTER to mount the NFS file system. :rev refid=first. :h3.Installing AIX Xstation Manager/6000 v1.1 (System Management Guide) Page 1-1, #4, If you are installing from Tape, type the command "smit instupdt_inst", instead of "installp -X all". Page 1-2, #4, After you have installed all the x_st_mgr diskettes, type the "installp -X all" again and this time insert the "x_st_mLANGUAGE" diskette (where LANGUAGE is the name of the language you want to use). For example, "x_st_mEn_US" is United States English). :erev refid=first. :h3.Installing the AIX Personal graPHIGS/6000 Currently the Model 730 supports only one 3D process. A graPHIGS application using the private connection to a graPHIGS nucleus or a graPHIGS remote nucleus is considered a 3D process. Such a process CAN open multiple windows. A second process will not run. The following programs are prerequisites for the graPHIGS API: :ol compact. :li.libX11.a :li.libXext.a :li.libgai.a :eol. :h4.Selecting Environments If you do an installp -l a list of the AIX Personal graPHIGS /6000 environments will be displayed. You can choose which ones you want to install: :dl compact tsize=1i. :dt.graPHIGS.R :dd.Run time support ( includes C and Pascal header files ) NOTE: This option is required by all other options. :dt.graPHIGS.1 :dd.IBM Plotter Support :dt.graPHIGS.1C :dd.Calcomp Plotter Support &endash. requires IBM Plotter support :dt.graPHIGS.1V :dd.Versatec Plotter Support &endash. requires IBM Plotter support :dt.graPHIGS.2 :dd.Japanese Fonts :dt.graPHIGS.3 :dd.GKS-CO Run time support :dt.graPHIGS.4 :dd.graPHIGS Remote Nucleus :edl. :h2.Understanding Paging Space Requirements Every system should have an amount of paging space equal to or greater than the amount of real memory. For example, if a system contains 32 megabytes of real memory, it should have, at a minimum, 32 megabytes of paging space. The install procedure allocates paging space based upon both the amount of real memory and the amount of disk space in the system. For some system configurations, this paging space allocation may not be sufficient. For a configuration of 32 megabtyes of real memory and 120 megabytes of disk space, the install procedure will, for example, allocate only 16 megabytes of paging space. If the amount of paging space is less than the amount of real memory in the system then it is possible that the system will run out of paging space before running out of memory. This is due to the fact that the system implements early allocation of paging space. This means that when a page is referenced both a real memory page and a paging space block are allocated. If there are fewer paging space blocks then real memory pages, paging space could be exhausted before all of real memory is utilized. If an installed system does not have sufficient paging space (either the amount of paging space is less than the real memory size or it is less than the amount required for the applications running on the system), additional paging space should be allocated. Additional paging space may be allocated by creating a new paging space logical volume using the 'mkps' command or by extending an existing paging space logical volume using the 'chps' command. Paging space size may be determined by using the 'lsps' command. These commands may also be issued via smit. Enter 'smit pgsp' to go directly to the paging space functions. :h2.SMIT (System Management Interface Tool) :h4.SMIT and Commands AIX Version 3 System Management is stratified so that users may enter the system at the layer befitting their work situation. The top layer is the System Management Interface Tool (smit), an interactive, natural language interface to regular Version 3 commands and scripts. Please notice that SMIT is a read-only shell; by itself, it alters nothing on your system. Instead, it executes commands that do all the work. Therefore, execution of commands from SMIT gives the same results as execution from the command line. The choice is yours. SMIT is useful to a new user in a variety of ways: as a survey of available function, as a command tutor and executive, as a shell script generator, and for quick access to on-line documentation via the help facility. Experienced users will find that it helps with complex command syntax and presents many lists of valid values. In addition, the FastPath facility brings the user down to the work site without menu traversal. (Commands executed by SMIT are valid FastPaths.) Many commands have been added to address two problems: too much help and not enough help! In the first case, some previously available (AIX Version 2) management applications such as "devices", "minidisks" and "adduser" were interactive, making shell script execution difficult. These have been broken down into families of commands whose user interaction is in the SMIT layer. You can produce a script by using SMIT the first time and then reuse the script to reproduce the action "unattended". On the other hand, some management tasks suffered from the opposite problem: they were procedural, requiring arcane knowledge of multiple steps. You can now do many of these tasks, such as TCP/IP configuration, with commands or the SMIT interface. Although there are many new commands, the task of learning them is eased both by SMIT and by the predictability of the command names. For example, four high level, generic commands manipulate devices: lsdev, mkdev, chdev and rmdev. Many command families use this four-verb paradigm of "list", "make", "change" and "remove", allowing you to access new function more predictably. :h4.The ODM The Object Data Manager (ODM) controls much of the system data in Version 3. Physical and logical (LVM) device configuration, software Vital Product Data (VPD), and SMIT interface data are stored by the ODM. System data can be changed indirectly by executing commands which manipulate it, or directly, by using the ODMEditor. Only very experienced users should change system data directly. The ODM is extendable and has a documented programming interface. Although some subsystems are controlled entirely by ODM data, others are hybrids, like TCP/IP. Many of its previously-known ASCII files still exist and can be directly edited: the /etc/hosts, /etc/hosts.equiv, /etc/ftpusers, /etc/services and /etc/resolv.conf. These files can also be indirectly changed by using commands. Other data, such as the interface device driver configuration for communications adapters, the hostname, and routes, are kept in the ODM. If you configure using commands (or SMIT), configuration methods store your data in the ODM. Subsequent IPLs run device methods that, in turn, run the ifconfig program. If you choose not to use commands, you can comment out the configuration methods in /etc/rc.net and add your ifconfig, hostname and route commands. The point is, if you already knew how to configure TCP/IP, you can still work in much the same way. For those who never learned the old way, we think that SMIT + commands is the way to start. Experienced 4.3 system administrators will find a discussion of 4.3 BSD and AIXv3 differences in the /usr/lpp/bos/bsdadm file. :h4.SMIT and Installation All optional software can be installed in the same way, regardless of install media or software product. The command "instupdt" can be used for both original installations and subsequent updates (and is used by SMIT). It is a high level command which executes both "installp" and "updatep" as needed. While you can directly use either of the two low level commands in some cases, they do not take care of positioning tapes. Again, you have more function and more protection if you go to a higher level. :h2.User Notes For InfoExplorer :ul. :li.If InfoExplorer is run on an hft console screen in ASCII mode, hot links are present but not displayed. The active hot link is reverse video'd and other links can be accessed by the TAB, f, or b keys. Pressing the "Enter" key will select the active hot link. :li.If the bottom of an InfoExplorer window becomes inaccessable by the normal "Slider bar", cursor keys, up/down arrow buttons, or Page Up/Down keys, use the "Maximize" Motif button in the upper right corner to enlarge the window to cover the screen. When finished, return the window to normal size by selecting the "Maximize" button again. :li.When using the ASCII version of InfoExplorer, be sure to use the File "Save" command bar options for Bookmarks, Notes, History, Search, to save those entries in a file before exiting InfoExplorer. :li.If the ASCII version of InfoExplorer terminates abnormally, notes, history, bookmarks, and search queries not previously saved may be lost. Type "stty sane j" to reset the ASCII terminal characteristics to a usable state. :li.The cursor left and cursor down keys do not function for InfoExplorer on WYSE terminals. Additionally, the active hot link is not highlighted on these terminals. :li.The "Print References" function of InfoExplorer prints articles directly referenced in the current window. It does not print articles that are linked further down. The user must follow those links to print the underlying articles. :li.When starting InfoExplorer, if a message appears in a small window thats says "No Matches Found", the problem is that the InfoExplorer databases are not loaded. They must be loaded before InfoExplorer is fully functional. The "LIST OF BOOKS", "LIST OF COMMANDS", and "EDUCATION" buttons are not active until InfoExplorer databases are loaded. :eul. :h2.CD-ROM File System When a CD-ROM disk is ejected from the drive, the files on the CD-ROM can no longer be accessed. The file systems mounted from the CD-ROM must be unmounted before the files can be accessed again. Processes which have files open on these file systems should be exited or killed. Processes whose current directories are on the file systems should have their current directories changed to directories which are not on the file systems to be unmounted. If you cannot determine all the processes which are preventing you from unmounting the CD-ROM file systems, a forced unmount (using the "-f" flag to unmount) can be used to unmount file systems which still have open files on them. Note that this will not work for file systems which have the root directory of the file system opened by a process. InfoExplorer can become unresponsive when the files it uses are on a CD-ROM file system and the CD-ROM disk has been ejected. Re-inserting the CD-ROM disk will not fix the problem. All InfoExplorer processes (graphical or ASCII) should be killed and the file system should be forced unmounted and mounted again. InfoExplorer can be started again after this is done. :h2.Man Pages The man command for the RISC System/6000 has been extended to read the InfoExplorer information data bases which contain the AIX Operating System documentation. The search path has been extended to search in /usr/man/man, then /usr/man/cat and additionally /usr/lpp/info directory structure. There is no nroff source for the man pages; however, source for additional man pages may be put into the man directories and will be located and processed by the man command. If a man search returns "no match found in database", try InfoExplorer. For more information on man, please access InfoExplorer with the following command: :xmp. info -s man :exmp. When you using the man command, the default pager is more. This can be changed by issuing (depending on what shell you're in) PAGER=somepag er; export PAGER. When you do a quit, you have not quit from the man process but only from the more of that particular article. A ctrl-c (sigint) will get you completely out. Man using krs now gets several hits, so when you quit, you actually quit and man gets the next article. :h2 id=rdme.README Files :p.Many of the separately installable programs have their own README files. Look for those files in the /usr/lpp/ directories. A list of them may be obtained with this command: :xmp. ls /usr/lpp/*/*README* :exmp. :h4.BSD :p.Two documents are available for experienced 4.3 BSD users. These summarize differences between 4.3 BSD and AIXv3 from a program portability viewpoint, and a system administration viewpoint: :xmp. /usr/lpp/bos/bsdport /usr/lpp/bos/bsdadm :exmp. The troff source for these documents is in /usr/lpp/bos/bsdport.tr and /usr/lpp/bos/bsdadm.tr. To format and print these documents use: :xmp. troff -me -T filename | | qprt -dp :exmp. where is the formatting routine for the desired printer, for example, ibm3816 or hplj. These documents are installed with the bosadt package. :h4.Compilers :p.README files for the compilers are in the following locations: :xmp. /usr/lpp/xlc/bin/README.xlc C Compiler /usr/lpp/xlf/DOC/README.xlf Fortran Compiler /usr/lpp/xlp/lib/README.xlp Pascal Compiler /usr/lpp/COBOL/README.cobol Cobol Compiler :exmp. :h4.NLS :p.A README for National Language Support is found in the file /usr/lpp/bos/README.nls :h4.ECS :p.A README for Electronic Customer Support is found in the file /usr/lpp/bos/README.ecs. :h4.Service :p.The CEREADME file contains information about the diagnostics and service documentation. This information is normally used by the service representative. The path to the CEREADME file is /etc/lpp/diagnostics/data/CEREADME. :h2.Notes on Printing :h4.Configuring a Printer First, define and configure the printer port, using SMIT. Type "smit" at the command line select "Devices" select "Printer/Plotter Devices" select "Printer/Plotter Devices" again select "Add a Printer/Plotter" select the printer and interface type select the parent adapter enter the port number (for example "p" for the native parallel port, or "s2" for native serial port S2) review and change the other attributes as needed The message "lpx Available" (where "x" is 0,1,...) appears, indicating that the device is now configured. The device name "lpx" is used when configuring a virtual printer for the device, as described below. Next, configure a virtual printer for the device so that the qprt, lpr, and lp commands can be used to queue print jobs to the device. This can be done with SMIT: Type "smit" at the command line select "Devices" select "Printer/Plotter Devices" select "Manage Local Printer Subsystem" select "Virtual Printers" select "Add a Virtual Printer" A list of the available printer devices is displayed, and you are asked to enter a device name. Enter the device name of the printer device you added above. The default value is displayed in parentheses. Pressing the Enter key without providing a name will use the default name. The next entries concern header and trailer pages. Possible choices are displayed. Enter your selection, or just press the Enter key to accept the defaults of no header or trailer pages. The next entries concern the print queue, or queues, for the printer. If the printer supports multiple types of data streams (for example, it also emulates another printer), a queue is created for each data stream type. You are asked to enter a print queue name. The default is displayed in parentheses. You may use the default queue name by pressing the Enter key, or enter a another queue name. The first character of the queue name must be alphabetic, and the queue name may not exceed seven characters. If the queue does not exist, it is created. You are asked if this is to be the default queue. The default queue is assumed when a print request is entered without specifying the queue. For example, "qprt smit.log" prints the file smit.log on the default print queue. If the queue already exists, you are asked if you want to add this device to the others already defined for this queue. Multiple devices on a queue are normally used only when there are printers of the same type attached. If a queue has multiple devices and the first device is busy, the queue manager tests each of the devices to locate the first device that is not in use and submits the print job to that device. When entries for the print queue, or queues, are completed, a message of completion is displayed. Press the Enter key to return to the "Virtual Printers" menu. The printer is now available for use with the qprt, lpr, and lp commands. :h4.QMS ColorScript 100 The QMS ColorScript 100 Model 20 printer can print color PostScript files and, optionally, HPGL (Hewlett-Packard Graphics Language) files. The HPGL emulator used to print HPGL files is on a DOS diskette shipped with the printer. If only PostScript files are to be printed, enter ! as the print queue name for the HPGL data stream when making the virtual printers. If HPGL files are to be printed, perform the following: Do NOT reply ! for the HPGL data stream when making the virtual printers. Insert the 3 1/2 inch diskette labeled "HPGL Emulator" in the diskette drive and as the root user, enter: /usr/lpd/pio/etc/pioqms100 -Q to copy the HPGL emulator files from the DOS diskette to an AIX directory. When HPGL print files are submitted to the HPGL print queue, the system will download the HPGL emulator to the printer and select the emulator as needed. PostScript files may also be submitted to the HPGL print queue if they begin with the two character string %! so the system can recognize them as PostScript (instead of HPGL) files and print them accordingly. Each time the printer controller is powered on, be sure to enter splp -F! lpx (where lpx is the printer device name, such as lp0,...) so the system will know that the HPGL emulator needs to be downloaded to the printer again. Also, if the system is re-booted, power off the printer controller and then power it back on in order to reinitialize the printer. :h4.List of Configured Virtual Printers To see a list of all virtual printers that have been configured, select "Change/Show Characteristics of a Virtual Printer" from the SMIT "Virtual Printers" menu. Press the Enter key to return. :h4.Configuring an Unsupported Printer Unsupported printers can sometimes be configured and driven satisfactorily. If the unsupported printer has the same hardware interface (serial or parallel) and is functionally similar to a supported printer, configure it as the supported printer. Otherwise, define and configure the printer device as "osp" (other serial printer) or "opp" (other parallel printer). In this case, when "Add a Virtual Printer" is selected and the device name is entered, a menu of supported printer types is displayed. Choose the printer type that most closely matches the unsupported printer being configured. Note the generic printer types "PostScript Printer" and "ASCII printer". Some laser printers can process more than one type of print data stream. For example, the TI 2115 OmniLaser can process PostScript, HP PCL, HP GL, Diablo 630, and TI 855 data streams. If the unsupported printer to be configured can process only a subset of these data stream types, configure it as a TI 2115 and when adding the virtual printers, enter ! as the print queue name for all data streams except for the ones wanted. A queue name of ! indicates that configuration of the data stream is to be bypassed. If the unsupported printer does not print correctly after being configured, consult the manual provided by the printer manufacturer. Then, select "Change/Show Characteristics of a Virtual Printer" from the SMIT "Virtual Printers" menu. Select the virtual printer, and view or change its attributes as needed. For example, the ci attribute (printer initialization string) and the t0, t1, and t2 attributes may need to be set to a null string for some printers by entering "ci=" (without the quotes), "t0=", etc. For more detailed information, use InfoExplorer to search for the heading "Printer Overview for System Management". Changing the printer description displayed when "Change/Show Characteristics of a Virtual Printer" is selected from the SMIT "Virtual Printers" menu can be useful if an unsupported printer has been configured as a supported printer. To change the printer description, select "Change/Show Characteristics of a Virtual Printer", choose the virtual printer whose description is to be changed, and then enter "mL=description for XYZ 1234 printer" (without the quotes), where "description for XYZ 1234 printer" is the new printer description. Also enter "mt=abbreviated description", where "abbreviated description" is a short description of the printer, such as "xyz1234". Press the Enter key to return. :h2.Print Spooler Notes :ul. :li.When using RISC System/6000 (running AIX 3.1) as server and AIX/RT or AIX PS/2 as client, the function of submitting multiple files in a single print request is not supported. Users can submit one job at a time or cat files into one file before submitting the print request to bypass this problem. :li.When using AIX/RT or AIX PS/2 as client and RISC System/6000 (running AIX 3.1) as server, the options to the AIX 2.2.1 print command are not honored by AIX 3.1 spooler system. :li.In a remote print environment, the client configuration should always specify the remote queue name on the server. Using the default remote queue name may cause unpredictable results. :li.The status commands display (lpstat, lpq, enq -A, qstatus, etc.) will contain two entries for remote queues. The first entry will contain the client's local queue and local device name and its status information. The second entry will immediately follow and will contain the client's local queue name (again), followed by the remote queue name. Any jobs submitted to a remote queue will first be displayed on the local side, and will be moved to the remote device as the job is processed on the remote machine. Since the status commands communicate with remote machines, the status display may occasionally appear to hang while waiting for a response from the remote machine. The command will eventually time out if a connection cannot be established between the two machines. :li.There are some cases in which the spooler commands do not have error checking for invalid argument combinations. :li.The spooler daemon will be stopped if the spooler configuration file /usr/lpd/qconfig file is empty. :li.Entering "cancel -?" and "enable -?" will cause the following error messages to be displayed: :xmp. enq (fatal error): 0781-048: Bad queue or device name: -? :exmp. :li.SMIT dialogues do not list job numbers as a selection list for users to cancel or prioritize a job. :li.In remote print environment, if a client user does not specify a burst page option from the command line, the default is to print a header page and not to print a trailer page. :li.In the case of a DEV_WAIT state on a queue device, try issuing :xmp. enq -U -Pqueue. :exmp. If that does not work then remove all jobs in that queue, and then issue enq -G to flush the other queues and bring down the spooler daemon. Then restart the qdaemon. :eul. :h2.Command Notes :h4.at The usage statement is incomplete and incorrect; -k and -m are not mentioned, -qn is mentioned but is not a valid input to the command. :h4.backup The -C flag does not improve the performance of backup. :h4.bsh This shell does not support filename expansion based on equivalence classification of characters. :h4.chmod In absolute (octal) mode, the SGID bit on a directory can not be removed. For example, 'chmod 777 dirname' will not remove the SGID bit so the mode will actually be 2777, but 'chmod g-s dirname' will remove the SGID bit. :h4.cpio This command will not archive files with user and group id's greater than 65535 since this may lead to unpredictable results. For example, these files may be extracted to another user or group id. :h4.csh In csh, control-A will sometimes cause a core dump. This shell does not support filename expansion based on equivalence classification of characters. :h4.halt halt -l does not suppress accounting file update as it should. :h4.find The 4.3 BSD fast find syntax is not supported. :h4.init init does not behave correctly if the inittab file does not exist. It stops in single user mode as root, also run level is not prompted for. init accepts, and telinit sends, a signal that stops respawning. The telinit usage statement reflects the new input flag, but the documentation doesn't mention it. During boot up the first few messages sent to the console are sent at a 9600 baud rate. If the console is set to a different baud rate then these messages will be lost. :h4.ksh Problem: a=$(su - user -c "echo \$PATH") a gets filled with the PATH from /etc/environment. When filesystems become full, ksh will begin to fail silently. If it can't write to your history file, your current history is lost. If you redirect the output of a builtin command to a file in a full filesystem, the output will be lost. If /tmp becomes full, ksh will not process the 'r cmd' feature correctly. The input is ignored, and no error message is generated. The MAILMSG environment variable is not output as the mail message. Instead, a hardcoded value such as "You have mail in /usr/spool/mail/username" is displayed. The "kill -l" builtin will display error messages for signals that do not have names. This shell does not support filename expansion based on equivalence classification of characters. :h4.ld -b loadmap&colon.FileId .br The alternate flag is "-b l&colon.FileId" instead of "-b I&colon.FileId" (Lower case L instead of upper case i). -e .br The symbol "__start" instead of "start" is the default entry point symbol if the -e flag is not specified. -x .br The local symbols are not currently stripped. Use the command "strip -r filename" to get the equivalent function. :h4.leave The command is incorrectly printing "late" messages. When you are one minute late, the message, "You are 1 minute late" is printed. This same message is repeated every minute until minute 10, when the message "You are 2 minutes late" is displayed. The messages will be changed to "You are going to be late". :h4.lock The lock command will not accept the root user's password unless the root user set the lock to begin with. :h4.make The make command does not fully support NLS. Make will complain that it cannot find makefile if there is an empty makefile. :h4.ps The "v" option always shows 0% for memory utilization. RSS and SIZE contain incorrect data (with real memory greater than virtual memory) :h4.quiz The quiz game core dumps when doing Shakespeare or poetry. :h4.reboot The -l flag doesn't suppress accounting file update as it is supposed to. :h4.shutdown /etc/shutdown is executable only by root; non-root system group members cannot run shutdown. The shutdown command with the -r flag will halt the system but will not reboot the machine when invoked using the rsh command. However, it will work correctly if invoked from a rlogin shell. The "shutdown" command issued to a Model 930 will power down the system by default. This information is not currently in the shutdown command pubs. There is a -p flag documented for the shutdown command that is not supported in this release. :h4.vi The error messages given when /tmp is full do not describe the real problem. :h4.vmstat Fails to display the one-line summary of the virtual memory activity since boot. :h4.what what may fail to find sccsid strings in executables when they are declared in the source as static internal variables in the following format: static char sccsid&lbrk.&rbrk. = "string"; .br This occurs because the binder discards those strings when there are no references in the program to static internal data. The following format works correctly when the -qro flag is used on the cc command line: static char *sccsid = "string"; .br If you are using -qnoro, which is the default, then it may be necessary to include a reference to the sccs id in your program. :h4.writesrv If the 'writesrv' daemon is terminated abnormally (system crash, power failure, or kill -9), the /usr/spool/writesrv directory must be manually cleaned up to remove any files left behind by writesrv. :h2.Logical Volume Manager A message such as 'unable to update logical volume hd7' will sometimes appear when an importvg or varyonvg -m1 is done. This message is a warning. The message appears because the logical volume control block (block 0 or the first 512 bytes on the logical volume) has been overwritten by a user application or a dump. As a consequence of this some of the information in the device configuration database may get default values. You may wish to update type (or any other field) information with: :xmp. chlv -t sysdump hd7 :exmp. When a volume group with file systems is imported, /etc/filesystems will be updated with values for those logical volumes and mount points. The varyonvg command must be run for the volume group, and fsck must be run on the file systems before the file systems can be mounted. 'importvg' will change the name of a logical volume if the name already exists in the system. It will print a message along with the new name to standard error. File system information in /etc/filesystems will include the new logical volume name. A volume group which has a paging space volume on it cannot be varied off or exported when the paging space is active. Once a paging space is made active with the swapon command, it cannot be made inactive while the system is running. Thus, the varyoff and exportvg commands will fail for that volume group. To work around this, ensure that the paging space is not activated automatically at system initialization and then reboot the system. If a message is printed that says to 'run varyonvg -m1', varyoff (varyoffvg) the volume group (if possible, not for rootvg) export (exportvg), and then import (importvg) it and varyon again. This usually has better results than just varyonvg -m1. If a disk that has had a volume group on it is to be reused, make sure the old volume group name does not exist in the device configuration database. If the volume group name appears in an 'lsvg' listing, run 'varyoffvg vgname', 'exportvg vgname' and then run 'extendvg' or 'mkvg' to that disk. The 'extendvg' and 'mkvg' commands will not allow the user to extend or create a volume group on a disk that the device configuration database believes is being used by another volume group. If a volume group gets locked, to unlock it run: :xmp. putlvodm -K `getlvodm -v vgname` :exmp. (the getlvodm command is back-quoted). If a physical volume cannot be added to a volume group, because "the Physical Volume ID does not exist or cannot be read", then the following sequence of commands will solve the problem. :xmp. chdev -l -a pv=clear chdev -l -a pv=yes extendvg :exmp. When an unrecoverable physical volume (disk) failure occurs, the following is recommended to restore the volume group. Obtain a list of the logical volumes that were allocated on the disk. :xmp. lspv -l hdisk3 :exmp. It is probable that when a file system logical volume loses some of its partitions it will be unusable. If it is not, then try and backup the file system to another media (e.g., tape). Otherwise, use previous backups. After backing-up or determining it is not possible, remove all of the logical volumes that existed on that disk from the volume group. (This means partitions on other disks as well.) :xmp. rmlv lv00 or rmfs /u/data :exmp. reduce the volume group :xmp. reducevg vg00 hdisk3 :exmp. Bring in a new disk and configure it, then extend the volume group :xmp. extendvg vg00 hdisk4 :exmp. and recreate the logical volumes or file systems and restore. 'reducevg' has an option to remove only logical partitions that are on that particular disk. However, it leaves the logical volume in a state of partial reduction and it is not recommended. When a physical volume failure causes a loss of quorum and the volume group is subsequently varied on with the force option, if the disk is recovered it may be necessary to replace its volume descriptor area. To put a new descriptor area on the disk run: :xmp. chpv -v r hdisk2 (the recovered one) chpv -v a hdisk2 :exmp. This will make the disk usable. The 'remove volume group' option in smit is not an export function. It will remove a disk or disks and all data on those disks from a volume group. Problems may occur when creating a large logical volume or extending a logical volume using a large number of partitions (more than 800MB). This does not mean a logical volume can not be larger than 800MB. The work around for this is to extend in smaller pieces. However, the default maximum number of partitions for a logical volume is 128. To extend a logical volume more than 128 logical partitions use the command: :xmp. chlv -x maximum_number_of_partitions lvname :exmp. then extend the logical volume or file system. The maximum size of a logical volume with a file system is 2 gigabytes. A volume group cannot have more than 99 logical volumes at this time. If varying on a volume group with the force option fails with the following error mesage: "0516-052 lvaryonvg: Volume group cannot be varied on without a quorum...", Execute the same command again for the forced varyon to take effect. :rev refid=first. After booting from tape or diskette, any stale mirrors are not automatically resynchronized in the root volume group. To resynchronize volume group(s) enter the command: :xmp. syncvg -v rootvg vg00 :exmp. or any other volume group name in the system. :erev refid=first. :h2.Journaled File System :h3.Set-group-id directories In AIX V3, the group id of newly created files and directories is determined in part by the parent directory. If the set-group-id bit of the parent directory is set, then the new file gets the group id of the directory. Otherwise, the new file gets the group id from the effective group id of the process. Also, the set-group-id bit is inherited from the parent directory when a new directory is created. These two features are not correctly documented in InfoExplorer. :h3.How to Extend an Existing File System 1. Enter the command "smit chjfs" and press ENTER. 2. Select the File System Name and press ENTER. 3. Move the highlight bar to "SIZE of File System (in 512-byte blocks)". Type in the total number of blocks that you want the extended file system to have. This will be the total number of blocks required in that logical partition. Note: When extending a file system with chfs, there are certain boundary conditions that may cause the extend to fail. In particular, if the file system is full and the size is a multiple of 56 Mb, then the file system cannot be extended. As a workaround, remove a couple of files and retry the extend; it should succeed. 4. After you have typed in this number, press ENTER. If you should enter a number not evenly divisible by the Physical Partition size, the system will automatically round-up to a number that is. 5. After the command is finished, press the F10 Function key to leave smit. :h3.Multiple logs per volume group Though the design of the journaled file system does not preclude using multiple logs in a single volume group, that particular function is not fully implemented and therefore should be avoided. Using the smit interface will automatically create the log with the appropriate size and attributes when the first file system in a volume group is created. :h2.Kernel Services Documentation Corrections The uexblock kernel service documentation incorrectly describes the environment that this service can be called in. This service can only be called to block the execution of the currently active process. If called with a process id other than the active process, the system will crash. This service should only be used by a user mode exception handler registered with the uexadd kernel service. When utilizing the timeout, untimeout and timeoutcf kernel services, the libsys library must be bound with the pinned part of the kernel extension. These services disable interrupts for serialization and therefore must execute in a pinned environment. Device driver use of the i_sched kernel service: the i_sched kernel service, used by device drivers to schedule off-level interrupt handling, has two additional restrictions that callers must understand. First, the i_sched service will not re-register an intr structure that is already registered for offlevel handling. Since i_sched has no return value, the service will simply return normally without registering the specified structure if it was already registered. The kernel removes the intr structure from the registration list immediately prior to calling the offlevel handler specified in the structure. It is therefore possible to re-use the structure to register another offlevel interrupt request in the offlevel handler itself. The structure can also be used to schedule another off-level call by an on-level interrupt handler (slih) that interrupted the off-level processing immediately prior to the off-level handler's invocation or during it's execution. Users of this service should be aware of these timing considerations and program accordingly. Secondly, the flags field in the intr structure is utilized by the kernel to determine if an intr structure is already registered. This field should be initialized once before the first call to i_sched and remain unmodified for future calls to i_sched. :h4.Kernel Services for Device Drivers: :h4.Purpose The d_cflush kernel service was added to the kernel to support flushing the processor and IOCC data caches when utilizing the "long term" DMA_WRITE_ONLY mapping of DMA buffers approach to bus master device DMA. :h4.Syntax :xmp. This service has the following definition: int d_cflush (channel_id, baddr, count, daddr) int channel_id; caddr_t baddr; size_t count; caddr_t daddr; :exmp. :h4.Parameters The baddr parameter designates the effective address of the memory buffer involved in the transfer. The count parameter defines the length of the memory buffer involved in the transfer. The channel_id parameter defines the DMA channel that is involved in the transfer (obtained from d_init), and the daddr parameter is the device address corresponding to the transfer. :h4.Function This kernel service should be called after data has been modified in a buffer to be DMAed to a device where the buffer has already been mapped for device dma using the d_master kernel service with the DMA_WRITE_ONLY option. This d_cflush kernel service will flush the processor cache for the involved cache lines and will invalidate any pre-fetched data that may be in i/o controller (IOCC) buffers for the designated channel. This most frequently occurs when using long term buffer mapping for dma support to or from a device. This service is not required if the DMA_WRITE_ONLY option is not used or if the buffer is mapped before each dma by calling the d_master kernel service. :h4.Execution Environment This service can be called from the process or interrupt environment. :h4.Return Value This service returns 0 if no error is detected. If parameters are invalid this service will return EINVAL. :h4.Additional Information The long term dma buffer mapping approach is frequently utilized when a "pool" of buffers are defined for sending commands and obtaining responses from an adapter via bus master DMA. This is also used frequently in the area of communications where buffers may come from a common pool such as the mbuf pool or a pool used for protocol headers. When using a fixed pool of buffers, the d_master service is only used once to map the address and range of the pool. The device driver then modifies the data in the buffers, and must flush the data from the processor and invalidate the IOCC data cache involved in transfers with the device. The IOCC cache must be invalidated since the IOCC may have "prefetched" data due to the last DMA to or from the buffer area which has just been modified for the next operation, and that data in the IOCC cache is now stale. To do this a new service dma kernel service d_cflush has been added which flushes the processor cache and invalidates the required IOCC cache. The device driver should use this function after modifying the data in the buffer, and before sending the command to the device to start the DMA. Once the dma has been completed the device driver should call the d_complete function to check for errors and ensure that any data read from the device has been flushed to memory. :h2.Notes on xde :h3.Using xde with FORTRAN programs In order for xde to function correctly in the Variable window, you should not use any capital letters in the names of your FORTRAN files. The variable window will sometimes show compiler-generated symbols that can be identified as "%". These can be ignored. :h3.Key bindings Key bindings do not work in the Main window, certain parts of the Context and the Variable window, and in any of the dialogs. :h3.Focus If the Execution menu has focus, mnemonics will be enabled even though no underlines are visible. :h3.Attaching to programs When attaching to a running process that isn't in the current directory, you will not see external variables for the program. After attaching to a running process (using the load -a option ), be sure to issue the 'detach' command to detach from the current program before issuing another 'load' command. When attaching to a running process, the current program location indication (double arrow) will not appear in the File and Context windows until a 'next', 'step' or similar command is issued. :h3.Using the 'use' command If the executable does not reside with the current source, use the 'use' command to get the correct source into the file window. Sometimes xde requires an execution command (e.g. goto , or next) to get synchronized after a 'use' command. :h3.Case considerations when debugging The default case for the supported languages are: C: mixed FORTRAN: lower Pascal: lower Cobol: upper When debugging programs that are mixed case, the user must change to the appropriate case when referring to symbols in a language different from the language in the current context. The 'case' command changes the case. :h3.The Variable Window The external variable list in the Variable window may not be complete. The externals are listed on a file by file basis. To determine which file an external variable corresponds to, issue the 'whereis' command which will display the file name as part of the fully qualified variable name. :h3.Variable Window Dialogs If a format is selected in the format dialog which is not appropriate for the data type of the displayed variable, the format will not change. Assignments are not allowed for *( p + i ), *( *p + i ), or (p&lbrk.i&rbrk.)&lbrk.i&rbrk. formats. :h2.xmonitor x25 Application When using the xmonitor application, the display used to show the data must be able to keep up with the rate of data being received. If running on a slow display, such as an ASCII terminal, it is recommended that the xmonitor output be directed to a file. This will keep system resources from being depleted and terminating the data transfer. :h2.Plotter Support with 5080 The 5080 Attachment Adapter plotter backend is accessible via the 'enq' command after using SMIT to identify the plotters: :xmp. Enter 'smit spooler' Manage Local Printer Subsystem --> Local Printer Queues --> Add a Local Queue --> NAME of queue to add: plta NAME of device to add: plota BACKEND PROGRAM pathname: /usr/lpd/plotgbe -gswa 9600 Enter 'smit spooler' Manage Local Printer Subsystem --> Local Printer Queues --> Add a Local Queue --> NAME of queue to add: pltb NAME of device to add: plotb BACKEND PROGRAM pathname: /usr/lpd/plotgbe -gswb 9600 :exmp. :h2.Notes on Tape Drives :h3.Using ECC on 1/4 Inch Tape Setting the "Enable ECC" attribute for 1/4 inch tape drives to the yes value writes data to tape using ECC for error detection. Setting this attribute to the no value writes data to tape using CRC for error detection. ECC provides much better error detection and correction capabilities than CRC. However, it may be necessary to use CRC in order to interchange tapes with another system. :h3.Performance Tips 1/2 inch Tape Device: The performance of backup, restore, dd, cpio, and tar to the IBM 9348 Magnetic Tape Unit Model 12 can be improved by changing the default blocksize. The performance improvement can be very great, depending on the file being transferred. To change the blocksize enter the following command: :xmp. chdev -l -a block_size=32k :exmp. Tape Devices General: See the Command Reference Manual and/or online information for the individual commands for additional flags and parameters that will affect the performance of the respective tape operation. As an example, the performance of "backup" can be enhanced by piping the output to "dd" and "restore" can be enhanced by piping from "dd". :h2.Dump, Trace, Error Logging According to the System Problem Solving Guide, one can display the dump statistics which are saved in the error log by entering the following command: 'errpt -aN dump', this is incorrect, the correct command is : 'errpt -aN sysdump'. The trace subroutines: trchk(), trchkt(), trchkl(), trchklt(), trchkg(), and trchkgt() are actually implemented as macros defined in /usr/include/sys/trcmacros.h. According to the System Problem Solving Guide, you can copy a dump from the dump device to diskettes by booting the Install/ Maintenance diskette and running 'dd if=/dev/hd6 of=/dev/rfd0'. This is oversimplified, there are procedures to perform before issuing the dd command and you actually have to issue the dd command multiple times with different parameters to retrieve the dump. The following is the procedure for retrieving a dump from a model 320, where the dump was taken to paging space (/dev/rhd6): :ol compact. :lp.You must have 6 formatted 1.4 meg diskettes. Follow these steps: :li.Boot with the install/maintenance diskettes. :li.Select option 5 from the install menu. :li.Enter the following commands: :xmp. ln /dev/hdisk0 /dev/ipldevice importvg -y rootvg hdisk0 varyonvg rootvg :exmp. :li.To put the dump on the floppies use the following dd commands on successive diskettes: :xmp. dd if=/dev/rhd6 of=/dev/rfd0 bs=36b count=80 dd if=/dev/rhd6 of=/dev/rfd0 bs=36b count=80 skip=80 dd if=/dev/rhd6 of=/dev/rfd0 bs=36b count=80 skip=160 dd if=/dev/rhd6 of=/dev/rfd0 bs=36b count=80 skip=240 dd if=/dev/rhd6 of=/dev/rfd0 bs=36b count=80 skip=320 dd if=/dev/rhd6 of=/dev/rfd0 bs=36b count=80 skip=400 :exmp. :eol. The SMIT dialog for copying a dump to diskette only permits you to copy the last dump taken on the default primary dump device (/dev/hd7). Some combinations of options from the SMIT trace dialog cause the trace command script to hang, for example, selecting event group(s) and also including or excluding additional events. Keying Ctrl-C breaks out of the command. Users that are adding error logging to their programs should read the /usr/adm/ras/README.errlg file for information regarding the error logging message catalogs. :h2.Library Routines: printf and scanf The functionality for the %lc and %ls options of printf() and scanf() has been removed because of conflicts with SVID. :h2.Setting the maximum number of processes allowed per user The default maximum number of processes per user is 40. This may be too low for users desiring many windows in X. There is currently no smit interface to change this, but the chdev command can be used to change it, and it will always be set to the new value when the system is rebooted. The following example would change the maximum number of processes for every user to 100. :xmp. chdev -l sys0 -a maxuproc=100 :exmp. To view the current setting of this and other system attributes type: :xmp. lsattr -E -l sys0 :exmp. :pc.Other options that can be set with the 'chdev -l sys0 -a' command have a "True" value following the text description of the attribute. The maxmbuf attribute is an exception. Changing this value is not currently supported. :h2.8-Port Mil-188 Adapters The 8-port mil-188 adapters, P/N 59F4037 EC C26213, shipped in certain machines do not contain fail-safe circuitry. In the following cases, the card will fail to detect non-functionality of the printers and continue to transmit data. :ul compact. :li.Printer not powered on. :li.Cable to printer unplugged. :eul. :pc. To avoid loss of data, ensure that your printers are powered on and attached to the system. The fail-safe circuitry has been added for all external customer shipments, P/N 81F8105 EC C26469, and will not present any problems. :h2.Security Notes :h3.Commands :h4.acledit The EDITOR environment variable must be specified with a full pathname or acledit will fail. :h4.audit 'audit start' audit all users currently logged on. :h4.auditselect The values of the result field must be one of: OK (not SUCCESS as stated), FAIL, FAIL_PRIV, FAIL_AUTH, FAIL_ACCESS, or FAIL_DAC (new). :h4.chuser chuser can not set the fsize, data, or stack attributes below the minimum values: :xmp. stack 49 data 1272 fsize 8192 :exmp. :h4.lslicense lslicense will report the tier (range) that the maxlogins value in /etc/security/login.cfg falls into. :h4.mkuser All usernames must contain at least one lowercase letter since login does not support all uppercase usernames on ttys. The username does not have to be entirely lowercase as stated in the documentation. The mkuser command has been enhanced to accept user attributes as arguments. These attributes may be given on the command line to override the default values for each attribute. The new syntax is: :xmp. mkuser &lbrk.-a&rbrk. &lbrk.= | ...&rbrk. username :exmp. where attribute can be any of the attributes listed in the chuser command documentation. The SMIT inteface for the mkuser command has been changed to support all of these options. The option values will be displayed as blank. These values will be replaced by the default values from the appropriate files in /etc/security. This change permits system administrators to create new user accounts with specific values. :h4.passwd Root will be authenticated like all other users, i.e., if root is changing another user's password, the passwd command will still prompt for that user's old password, at which point root may enter the old password or enter root's password. A user's password may be set to NULL (blank) using the passwd command by pressing or CTRL-D when prompted for a new password. The passwd command will not verify the null password by asking the user to reenter or CTRL-D as it does when non-NULL passwords are entered. A message will be displayed saying the password was set to NULL. The maximum number of bytes in a password is PASS_MAX, defined in limits.h. All usernames must contain at least one lowercase letter since login does not support all uppercase usernames on ttys. The username does not have to be entirely lowercase as stated in the documentation. :h4.setgroups Whenever the real group is reset, the former real group is not removed from the concurrent groupset as stated in the documentation. :h4.su The su command will not accept any username > 8 characters, including network information service database users (yp users). Under session initialization, if '-' is not used, the directory will not change as stated in the documentation to PWD, HOME, or /. The directory will be the same as before you issued the su command. :h4.tsh While in the trusted shell, 'su ' changes your effective id to user's id and places you in another trusted shell. The su command does not exit from tsh and execute the user's default shell as stated in the documentation. :h4.usrck The usrck command verifies that each user name listed in /etc/passwd has a stanza in /etc/security/user, /etc/security/limits and /etc/security/passwd. Stanzas will be added for each missing user name as needed. The usrck command also verifies that each group name listed in /etc/group has a stanza in /etc/security/group. :h3.Files :h4./etc/passwd and /etc/group Certain system-defined group and user names are required for proper installation and update of system software. Care should be exercised before replacing either of these files to ensure that no system-supplied groups are removed. :h4./etc/security/login.cfg There is no default value of 0 for maxlogins as stated in the documentation. Each system will be shipped with a different maxlogin value depending on the type of license bought. The synonym value must be a specific channel, not a multiplexed file; e.g., /dev/hft/2 is ok while /dev/hft has no effect. :h4./etc/security/passwd The documentation for this file refers to the password stanza name being 'passwd' when it is actually 'password'. The ADMCHG flag indicates the password was last changed by either a member of group security or root. Normally this flag is set only implicitly when the pwdadm command (not the passwd command) changes another user's password. :h4./etc/security/user The tpath default value is 'nosak', not 'on' as stated in the documentation. Seven new fields have been added to a user's stanza: :xmp keep=5. time_last_login Time of this user's last successful login. tty_last_login Device on which the user's last successful login occurred. host_last_login The host from which this user's last successful login originated. time_last_unsuccessful_login Time of this user's last unsuccessful login. tty_last_unsuccessful_login Device on which the user's last unsuccessful login occurred. host_last_unsuccessful_login The host from which this user's last unsuccessful login originated. unsuccessful_login_count Number of unsuccessful login attempts that have occurred since the last successful login. :exmp. time_last_login, tty_last_login and host_last_login are inserted into /etc/security/user at the time of the user's first successful login. Subsequent successful logins by the user cause an update of these fields. time_last_unsuccessful_login, tty_last_unsuccessful_login and host_last_unsuccessful_login are inserted into /etc/security/user at the time of the user's first unsuccessful login attempt. Subsequent unsuccessful login attempts under the user's account cause an update of these fields. unsuccessful_login_count is inserted into /etc/security/user at the time of the user's first unsuccessful login attempt. Subsequent unsuccessful login attempts under the user's account cause the value of this field to be incremented. unsuccessful_login_count is zeroed out upon a successful login by the user. /bin/login informs the user of these times and locations upon login, warning the user of breakin attempts into or unauthorized use of the account. The host field is only printed out if it is non-local (rlogin, telnet). The ttys attribute is interpreted in the order given. The first matching tty name is used. If no matching tty name is found, the user will not be permitted to login on the terminal. The device /dev/console should not be used as it does not refer to an actual device, instead it uses the name of the device to which /dev/console is redirected. You may determine the actual device associated with /dev/console by using the lscons command. The rlogin attribute is implemented to determine if a user can rlogin or telnet into the machine. The telnet attribute is unused. :h4./etc/security/audit/config If binsize is set to 0, no bin switching will occur and all bin collection will go to bin1. The default for the streammode is off, not on as stated in the documentation. :h4.limits.h file PASS_MAX is 32, not 256 as documented. However, only 8 characters of password information are significant. :h3.SMIT :h4.Changing Group Attributes with SMIT The SMIT user interface now supports changing group attributes, such as group members and administrators, of user administered groups. This is done via the chgrpmem command which can be used to modify groups that were created by a non-administrative user. For more info, see the mkgroup, chgroup, and chgrpmem commands. :h4.Creating a New Group with SMIT The SMIT user interface for creating a new group has been modified to support the use of the -A flag of the mkgroup command. Previously a group which had been created by a non-administrative user could not be properly administered by that user. Now the group is created with the -A option so the creator of the group may add or delete group members and administrators. For more information, see the mkgroup command. :h3.Subroutines Note: Before using any of the subroutines in the libs.a security library, a call must be made to setlocale (LC_ALL,""). This will enable the routines to read extended byte characters. Please refer to the Calls and Subroutines Reference: Base Operating system for a description of the setlocale function and usage. :h4.IDtouser The uid parameter is not a pointer of type uid_t as stated. It is a variable of type uid_t: uid_t uid. :h4.putuserattr SEC_NEW will update all user database files, not group database files as stated in the documentation. :h4.getpenv The purpose of this subroutine is to read the current process environment, not the current process credentials as stated in the documentation. :h4.nextuser The search mode must be either S_LOCAL or S_SYSTEM; it cannot be one or 'more' as specified in the documentation. :h4.nextgroup The search mode must be either S_LOCAL or S_SYSTEM; it cannot be one or 'more' as specified in the documentation. :h4.ckuseracct To use this subroutine, login.h must be included instead of usersec.h as specified in the documentation, i.e.: :xmp. #include :exmp. :h4.kleenup If the lists that SigIgn and SigKeep point to are both NULL, kleenup does not set all signals to SIG_DFL as specified in the documentation. :h4.auditproc AUDIT_QEVENTS returns the list of auditclasses defined for the current process if the pid specified is 0. Otherwise, the list of auditclasses defined for the specified pid are returned. :h4.setreuid The real and effective user ID arguments to the setreuid subroutine may be -1. If an argument is -1, the actual value for that uid will be set to the corresponding current uid. This subroutine is present for BSD conformance. :h3.Command Auditevents The following commands cut audit records. Auditevent is the event name, and info is the relevant, key piece of information being audited. :xmp keep=5. Command: Auditevent: Info: cfgmgr DEV_Configure device chdev DEV_Change parameters bootlist (bosboot) NVRAM_Config device mkdev DEV_Create node device filename DEV_Configure device DEV_Start device nvload NVRAM_Config device rmdev DEV_Stop device DEV_Unconfigure device DEV_Remove device installp INSTALLP_Abort name INSTALLP_Name name INSTALLP_Exec name lvm_changelv LVM_ChangeLV name & flags lvm_changepv LVM_ChangeVG name & flags lvm_createlv LVM_CreateLV name & flags lvm_createvg LVM_CreateVG name & flags lvm_deletelv LVM_DeleteLV name & flags lvm_deletepv LVM_ChangeVG name & flags lvm_extendlv LVM_ChangeLV name & flags lvm_installpv LVM_ChangeVG name & flags lvm_reducelv LVM_ChangeLV name & flags lvm_varyoffvg LVM_VaryoffVG name & flags lvm_varyonvg LVM_VaryonVG name & flags cron/at at description job time at AT_JobAdd filename user time AT_JobRemove filename user cron cron_start description file time cron_finish name pid time enq ENQUE_admin queue device request operation qdaemon ENQUE_exec queue request host file operation sendmail SENDMAIL_Config command SENDMAIL_ToFile command mkserver SRC_Addserver action chserver SRC_Chserver action chssys SRC_Chssys action srcmstr SRC_Start action SRC_Stop action rmserver SRC_Delserver action addssys subroutine SRC_Addssys action rmssys SRC_Delssys action acledit FILE_Acl access_control_list aclput FILE_Acl access_control_list :exmp. :h3.Concepts :h4.Trusted Computing Base Overview vhangup() is not supported in AIX 3.1 and therefore is not in libbsd.a. The subroutines revoke() and frevoke() should be used instead. :h2.Creating an Inventory File for sysck Vendor created software packages must use an inventory file as input to the sysck command to create links, set file ownership and modes, and to verify size and contents. The sysck.cfg file format is used by the installation process to initialize access permissions and privileges on files during the installation and update process. The documentation for the sysck.cfg file can be found in the programmers manual or by using InfoExplorer. This note gives examples of how certain entries are to be used. ACL Attribute - :xmp. acl = "attributes:\nbase permissions\n owner ..." :exmp. This is a string in the same format as the command "aclget". It must be double quoted and have all newlines escaped as "\n". The read, write, and execute mode bits will be set from the values of the base permissions for owner, group, and other if this attribute is present. SUID, SGID, and SVTX modes are set here and override a "mode = " entry. For files in the trusted computing base (TCB), the "acl =" attribute replaces the "mode =" attribute when the mode involves extended ACL entries. MODE Attribute - :xmp. mode = &lbrk.MODE&lbrk.,MODE,...&rbrk.,&rbrk.--x--x--x :exmp. where MODE is one or more of SUID, SGID, SVTX, or TCB in a comma separated list followed by the "rwx" or octal-style file permissions. Only the low-order nine permission bits can be set using either the octal or "rwxrwxrwx" format. Some examples are: :xmp. mode = SUID,--x--x--x :exmp. a traditional set-UID program with execute permission only. :xmp. mode = rw-r--r-- :exmp. a file which has read-write permission for the owner, but is read-only for group and others. The modes may additionally be specified in octal as :xmp. mode = 755 :exmp. a file which has read-write-execute for owner, and read-execute for group and others. SYMLINKS and LINKS Attributes - Links are specified as an attribute of the file name. These links will be tested for and created as required. Both soft (symbolic) and hard links are supported. The hard links for /bin/mv might be given as :xmp. /bin/mv: type = FILE links = /bin/cp,/bin/ln :exmp. An installation script can also specify symbolic links, as in :xmp. /usr/ucb/more: type = FILE symlinks = /usr/bin/more :exmp. In both cases, the value is a comma separated list of absolute pathnames. The links are validated either by comparing the device and inumber for the hard link case, or by comparing the contents of the symbolic link file in the soft link case. Invalid links are removed, and missing links are created. SIZE and CHECKSUM Attributes - The "size =" and "checksum =" attributes are used to perform crude validity checking for the file. It is possible to specify a more rigorous checking program using the "program =" attribute if a more reliable test is required. The format of the size and checksum attributes are: :xmp. /bin/example: type = FILE size = 12345 checksum = "12345 6 " :exmp. where 'size = 12345' indicates the size of the file in bytes and 'checksum = "12345 6 "' indicates that "12345 6 " is the output of the command "/bin/sum -r < /bin/example". The size and checksum attributes to the sysck command are used to verify the contents of files at installation time, and later, are used by lppchk to verify the files in an LPP continue to have the correct contents. Certain files in AIX 3.1 may change either prior to the completion of the installation, or after the installation has been completed. Files which may change between the time the installation begins and the time sysck initially verifies these files are typically configuration files, such as ODM files, used by the base operating system while the system is being initialized. These files must have a size and checksum value of "size = NOSIZE" and "checksum = NOSIZE". This prevents mkinventory from outputting a size and checksum value in the inventory file. Files which are expected to change after the installation is completed are typically log files. A good example is /usr/adm/wtmp, a file whose size changes with every user login. This file must have a size and checksum value of "size = VOLATILE" and "checksum = VOLATILE". This prevents sysck from entering the size or checksum into the Software Vital Products Database. If a file is expected to change before sysck is run and it may change after install time, both attributes must be used together, for example, "size = VOLATILE,NOSIZE". It is very important that you carefully consider every changeable file and ensure the proper modifiers are added. The default behavior for sysck is to clear the Access Control List for any files whose size and checksum do not agree with the values in the database. The lppchk program will report an LPP as broken if any of the files belonging to that LPP do not have the correct size and checksum values. :h2.DES Subroutine Interfaces des_crypt.h and ecb_crypt, cbc_crypt, des_setparity Subroutines :h4.Purpose Fast DES encryption routines :h4.Library DES library (libdes.a) :h4.Syntax :lines. #include int ecb_crypt(key, data, datalen, mode) char *key; char *data; unsigned datalen; unsigned mode; int cbc_crypt(key, data, datalen, mode, ivec) char *key; char *data; unsigned datalen; unsigned mode; char *ivec; void des_setparity(key) char *key; :elines. :h4.Description ecb_crypt() and cbc_crypt() implement the NBS DES (Data Encryption Standard). ecb_crypt() encrypts in ECB (Electronic Code Book) mode, which encrypts blocks of data independently. cbc_crypt() encrypts in CBC (Cipher Block Chaining) mode, which chains together successive blocks. CBC mode protects against insertions, deletions and substitutions of blocks. Also, regularities in the clear text will not appear in the cipher text. :h4.Parameters :dl tsize=10. :dt.key :dd.the 8-byte encryption key with parity. To set the key's parity, which for DES is in the low bit of each byte, use des_setparity. :dt.data :dd.the data to be encrypted or decrypted. :dt.datalen :dd.the length in bytes of data, which must be a multiple of 8. :dt.mode :dd.This is formed by OR'ing together some things. For the encryption direction 'or' in either DES_ENCRYPT or DES_DECRYPT. For software versus hardware encryption, 'or' in either DES_HW or DES_SW. :dt.ivec :dd.This is the 8-byte initialization vector for the chaining. It is updated to the next initialization vector upon return. :edl. :h4.Return Values :dl tsize=2i. :dt.DESERR_NONE :dd.No error. :dt.DESERR_NOHWDEVICE :dd.Encryption succeeded, but done in software instead of the requested hardware. :dt.DESERR_HWERR :dd.An error occurred in the hardware or driver. :dt.DESERR_BADPARAM :dd.Bad parameter to routine. :edl. Given a result status :hp1.stat:ehp1., the macro DES_FAILED(stat) is false only for the first two statuses. :h4.Implementation Specifics These routines are not available for export outside the U.S. :h2.TTY Notes :ul. :li.The tcsendbreak(fildes, duration) function with zero duration will cause transmission of zero-valued bits for at least 250 milli-seconds, to generate a break condition. Non-zero duration will cause transmission of zero-valued bits for 'duration' milliseconds (or 10 milliseconds, which ever is more). This does not guarantee a break condition for all baud rates. :li.A background process attempt to read from or write to its controlling terminal will cause SIGTTIN or SIGTTOU to be sent to the process and will cause the process to be stopped. :li.Lines on ASYNC drawer may not recover after Power Line Disturbance (PLD). Battery Backup Unit (BBU) should be used on ASYNC drawer. :li.The stty command supports POSIX as primary line discipline; BSD fashion of command syntax and keywords may be altered. Refer to manual pages for the correct syntax and supported keywords. The iexten bit must be turned on to enable extensions to POSIX (such as lnext, werase, discard, and eol2 special characters). :li.Homologation discipline will be supported in an upcoming update. :eul. :h2.relseq Device Configuration Subroutine Please ignore all references to relseq. This is a documented, but unsupported subroutine. :h2.Configuration of Ethernet interface Configuration of a standard Ethernet interface requires additional steps if you are using SMIT to change the adapter type from thin (BNC) to thick (DIX), or vice versa. To change the Ethernet adapter properties using SMIT, use the following procedure: :xmp. 1. Type "SMIT" and press Enter. 2. Choose the following SMIT Menu selections: - Devices -- Communications --- Ethernet Adapter ---- Change/Show Characteristics of an Ethernet Adapter 3. Change the Adapter Type field to the proper setting. 4. Set the Apply Change to Database Only field to "yes." 5. Reboot the machine to apply the configuration change. :exmp. :h2.World Trade Considerations: Auto-call unit When trying to use a Auto-call unit, (supported only for France for the Transpac network), the modem lines are not controlled correctly for proper use. The DTR line (line 108) does not appear to be controlled as required to perform the auto-call function. This may be worked around by using the xmanage application to force the DTR line up when required. This may require attended operation at both ends of the transmission. :h2.Note to Users of 6150 Battery Backup Option Users of the 6150 Battery Backup Option should be aware that the configuration information of the system needs to be modified to assure uninterrupted operation of battery backed internal SCSI devices when primary power is lost. For proper operation, the 6150 Battery Backup Option should be connected to either all or none of the internal SCSI devices on a particular SCSI adapter. Typically, the internal SCSI devices in the rack-mounted system include CD-ROMs and tape devices, while the external devices are disks, tapes, etc., located in one or more drawers. The configuration should be changed for each SCSI adapter which has its internal devices battery backed. To change the configuration for such a SCSI adapter, issue the command: :xmp. chdev -l scsin -a bb=yes -P :exmp. where "n" is the SCSI adapter instance being changed (e.g. 0, 1, 2, etc.). The system must be shutdown and re-IPLed to make this change take effect. :h2.Creating a File System Log on a Dedicated Disk Creating a file system log on a separate and dedicated disk will increase file system performance in most cases. An example is outlined below with a SMIT procedure and an equivalent command procedure. This example will create a volume group with two disks, one of which will be the dedicated device for the file system log. In this example the log disk will be hdisk1 and the file system disk will be hdisk2. A similar procedure can be taken for the rootvg, except instead of creating a new volume group, extend rootvg (extendvg rootvg hdisk1), then continue with the mklv and chpv commands, and create the file systems on hdisk0, or other disks in the rootvg. :xmp. SMIT: Type 'smit lvm'. Go to the Volume Groups section and then go to the screen to Add a Volume Group. Enter the appropriate information and enter the physical volume names to create the log and file system on. Hit Enter. COMMAND: mkvg -y fsvg1 hdisk1 hdisk2 varyonvg fsvg1 SMIT: Go back two screens to Logical Volumes, then go to Add a Logical Volume. Enter the name of the newly created volume group (fsvg1) and hit enter, then in the following screen set the following attributes: Name of Logical volume: loglv1 Number of physical partitions: 1 Physical volume name: hdisk1 Logical volume type: jfslog Position on physical volume: center Then hit enter. COMMAND: mklv -y loglv1 -t jfslog -a c fsvg1 1 hdisk1 SMIT: Go back two screens to Physical Volumes, then go to the Change Characteristics of a Physical Volume, and enter the name of the disk with the file system log on it, hdisk1, then hit enter, and in the change the value of the Allow physical partition Allocation to 'no' (with the tab key), and hit enter. Then exit from smit back to the command line with the PF3 key. COMMAND: chpv -a n hdisk1 SMIT: Continue with creating a file system by typing 'smit fs'. Go to the Add/Change/Show/Delete a File System screen, and then Journaled File System, then Add a Journaled File System, then fill in the appropriate information about the volume group name, file system size in 512-byte blocks, and mount point. Volume group name: fsvg1 Size of file system (in 512-byte blocks): 32768 MOUNT POINT: /u/myfs Hit enter, then go back one screen and mount the file system. COMMAND: crfs -v jfs -g fsvg1 -a size=32768 -m /u/myfs -A yes mount /u/myfs :exmp. :h2.New screen Capture command added :h4.Purpose Allows terminal screens to be dumped to a file. :h4.Syntax capture &lbrk. -a &rbrk. &lbrk. file &rbrk. :h4.Description Capture allows a user to dump everything printed on their terminal. The screen is written to file, or appended to file if the -a option is given. It can be sent to the line printer later with lpr. If no file name is given, the dumped screens are saved in the file screen.out. This program is useful when using a crt and a hard-copy record of the dialog is desired, as for a customer calling into IBM InfoLink and would like to capture some of the data on the screens for further review. The capture command creates a shell that emulates a vt100 terminal and maintains a record of what is being displayed on the screen in order to dump the screen to a file. The TERM environment variable is set to vt100 and if a program is run while running capture, that requires the user to tell it what terminal type the user is using, the user must tell the program that he is on a vt100 terminal. The ^P (Ctrl-p) key is the default key stroke to cause a screen dump to be performed. This can be changed by setting the SCREENDUMP environment variable to the octal value of the screen dump key desired. SCREENDUMP specifies an alternate key stroke, other than the default Ctrl-p. To change the screen dump key stroke, set SCREENDUMP to the octal value of the character you want to use. Then export SCREENDUMP.... For example, set SCREENDUMP to 35 to change the screen dump key stroke to Ctrl-]. The capture ends when the forked shell exits. :h4.Limitations Capture only supports a limited set of terminals and always creates a vt100 environment shell. :h2.Mouse button functionality with Motif window manager in AIXwindows The default Motif configuration file (/usr/lib/X11/system.mwmrc) sets up actions (e.g. raise, move, ...) to occur upon receipt of button presses for only two states: :ol. :li.When no modifier keys (e.g. shift, Num_Lock, ...) are pressed. :li.When the meta (alt) key is pressed. :eol. If the user wants Motif to perform the same action for a button- press regardless of whether the Num_Lock key is pressed, it is is necessary to add this modifier combination to the system-wide /usr/lib/X11/system.mwmrc (or the user's private $HOME/.mwmrc) Motif configuration file. :rev refid=first. :h2.Hot Keying in AIXwindows Rapid multiple hot keying may cause AIXwindows server to die. :h2.Backing Store in AIXwindows X clients that set the window backing_store hint to "Always" (i.e. XWindowAttributes.backing_store=Always) will not get any expose events. This means that if you run the server without backing store (which is the default), the X client will not get backing store support nor will it get expose events. The solution is to either not set the backing_store hint to "Always" or to start the server with backing store (i.e. xinit -bs). :h2.$sigblock variable added to dbx A new debug variable, $sigblock, is added to dbx. Setting this variable changes the default signal processing of dbx. By default, signals received through dbx are sent to the source program, or ObjectFile. If $sigblock is set, signals received by dbx will not be passed to the source program. User must supply a signal as an operand to the "cont" subcommand if a signal is desired to be passed on to the source program. For example, in debugging the following program: :xmp. #include #include void inthand() { printf("\nSIGINT received\n"); exit(0); } main() { signal(SIGINT, inthand); while (1) { printf("."); fflush(stdout); sleep(1); } } Following is a sample session with dbx, comments are placed between angle brackets on the right: dbx version 3.1 for AIX. Type 'help' for help. reading symbolic information ... (dbx) run interrupt in sleep at 0xd00180bc 0xd00180bc (sleep+0x40) 80410014 l r2,0x14(r1) (dbx) cont SIGINT received execution completed (dbx) set $sigblock (dbx) rerun &lbrk. looper &rbrk. interrupt in sleep at 0xd00180bc 0xd00180bc (sleep+0x40) 80410014 l r2,0x14(r1) (dbx) cont interrupt in sleep at 0xd00180bc 0xd00180bc (sleep+0x40) 80410014 l r2,0x14(r1) (dbx) cont 2 SIGINT received execution completed (dbx) :exmp. Users can use this new feature to interrupt execution of program running under dbx, examine program status and/or add and delete breakpoints, before continuing the execution as usual. If the variable $sigblock was not set, interrupting execution this way would cause a SIGINT to be sent to the program, causing execution to branch to signal handler (if one exists) when continued. :h2.Installing AIX SNA Services/6000 Before applying updates to AIX SNA Services/6000, some users will create a backup copy of their SNA profiles. While making backups is never a bad idea, the SNA update process will not remove existing profiles. The update process may modify these profiles when problems have been fixed that require existing profile information to be changed. It is important that the user not simply overlay these modified profiles with the backup copy, as necessary changes will be removed. When working with backups of the SNA profiles, use exportsna/importsna. Copying the contents of /usr/lpp/sna/objrepos to another directory is not sufficient. By using exportsna/importsna, any changes made to profile configuration will be applied to the backup copy of the profiles. To create the backup: exportsna -f'filename' where filename is the full path name of the file which will contain the exported profiles To replace existing profiles with the backup copy: importsna -l'filename' where filename is the full path name of the file which contains the profiles previously exported :h2.Compiling HCON Fortran API Programs For those who have need of compiling HCON Fortran API programs, a new requirement has been added that is not described in any of the other current documentation (HCON README file, the manual set, or the On-Line documentation) which is: the explicit inclusion of the standard "c" library in the compile command statement (-lc). If a program called fprog.f were to be compiled and linked with the HCON Fortran API 3270 library, it would be done by the following command statement: :xmp. xlf fprog.f /usr/lib/hcon/autolog.o -o fprog -lc -lg3270f -lg3270 :exmp. This new requirement also implies that the HCON API compile script called "apilaf", which resides in the /usr/bin directory, must be changed. In the current "apilaf" script, the following line: :xmp. -f ) LANGLIB="-lg3270f -lg3270 -lxlf" :exmp. should be changed (edited by the user) to read as follows: :xmp. -f ) LANGLIB="-lc -lg3270f -lg3270 -lxlf" :exmp. (Note the inclusion of "-lc" in this statement.) :h2.Diagnostics Enhancement The diagnostics have been enhanced to provide daily error log analysis of disk errors. If potential disk problems are found, a warning message will be issued to the console and logged in the error log. :erev refid=first. .***:p. .***:p. .***:p. .*---------------------------------------------------------------------* .config memo07 off .*********************************************************************** .* .* AUTHOR: Here you add the Additional Text - to Memo 1,2,3,4,5 or 6 .* .* The text will appear just after the last paragraph, .* containing the last of the standard text. .* Just remove the ".***" in the following line and add .* your text after the ":p.". .* .***:p. .*---------------------------------------------------------------------* .config attach on .when '3' insert .***** .config atta1 on .when 'att1' insert :h1.Summary of changes .************************************************************************ .* .* AUTHOR: Attachment att1 .* .* Enter your text after the ":p." below. .* If you want to activate another paragraph, remove the .* ".***" before the :p. and add your text. .* :p. .***:p. .***:p. .***:p. .***:p. .* End attachment att1 here .*---------------------------------------------------------------------* .config atta1 off .* .config atta2 on .when 'att2' insert :h1.List of Program Material .************************************************************************ .* .* AUTHOR: Attachment att2 .* .* Enter your text after the ":p." below. .* If you want to activate another paragraph, remove the .* ".***" before the :p. and add your text. .* :p. .***:p. .***:p. .***:p. .***:p. .* End attachment att2 here .*---------------------------------------------------------------------* .config atta2 off .config atta3 on .when 'att3' insert :h1.Statement of Program Support .************************************************************************ .* .* AUTHOR: Attachment att3 .* .* Enter your text after the ":p." below. .* If you want to activate another paragraph, remove the .* ".***" before the :p. and add your text. .* :p. .***:p. .***:p. .***:p. .***:p. .* End attachment att3 here .*---------------------------------------------------------------------* .config atta3 off .config atta4 on .when 'att4' insert :h1.Ordering Information for Basic Material .************************************************************************ .* .* AUTHOR: Attachment att4 .* .* Enter your text after the ":p." below. .* If you want to activate another paragraph, remove the .* ".***" before the :p. and add your text. .* :p. .***:p. .***:p. .***:p. .***:p. .* End attachment att4 here .*---------------------------------------------------------------------* .config atta4 off .config atta5 on .when 'att5' insert :h1.Ordering Information for Optional Material .************************************************************************ .* .* AUTHOR: Attachment att5 .* .* Enter your text after the ":p." below. .* If you want to activate another paragraph, remove the .* ".***" before the :p. and add your text. .* :p. .***:p. .***:p. .***:p. .***:p. .* End attachment att5 here .*---------------------------------------------------------------------* .config atta5 off .config attach off .************************************************************************