3003 TIPS
                                03/07/91



General flow of updating to 3003.

  Update AIXwindows Runtime Environment using installp.      (X11rte.obj)
  Update InfoExplorer databases using installp.              (*****.info)
  Retreive and run the ./RUME script from DISPLAY diskette.
  Update bos.obj and other OPPs using updatep.
  Modify the bosinst scripts using sed.
  Modify the mkszfile script using sed.
  For 8MM drives, change block size to 512.
  Shutdown and reboot.
  Apply the additional updates (4 diskettes).


Absolute minumum file space requirements.

  /     3.5 MBs
  /usr  2.5 MBs
  /tmp  6.5 MBs


Problem installing X11rte on Model 320s with 120MB hard disks.

  A Preloaded 320 with 120MB hard disks contains following LPs:

    bos.obj
    bsmEn_US.msg
    bosnet.tcpip.obj
    bosnet.nfs.obj
    bosnet.snmpd.obj
    bosnet.ncs.obj
    X11rte.obj (optional)   
    X11mEn_US.msg (optional)        

  As long as the customer has not put anything else on that system, 
  then he should be able to completely update this system.
  One big catch here - X11rte.obj requires 23MBs in /usr before he'll
  start the reinstall.

 
'Media surface errors' when USING a system backup (mksysb) on 1/4" tape.

  If customer did not modify the bosinst scripts and created their own 
  Install/Maint diskette they may see this on 1/4" tape backups.
  See Release Notes step 14 which tell all customers to modify the
  bosinst scripts BEFORE creating the Install/Maint diskettes.
  The Install/Maint diskette that was auto shipped to each customer
  will not exhibit this problem.


.fs.size file not found or invalid when USING a system backup (mksysb).

  If customer did not modify the mkszfile BEFORE making the system
  backup he will always get the above error.  See Release Notes page 1.


Licensed applications may not work after apply bos.obj updates.

  Some vendors license a customer to use their application by having the
  customer call them to get a license password.  The customer needs this
  password to install the application (like PCADAM).
        
  Customers who have an application they have been using all along and 
  have just put 3003 bos.obj on may find that they are no longer licensed
  to run that application.  

  This is caused by a fix to the uname command.  The uname command is
  used to return a unique machine name (number) but prior to 3003 it
  did not.
        
  Have the customer contact his application support number to get 
  relicensed.  See Release Notes Section C: Additional Instructions #2.


Lighted PF Keys and Dials not supported yet.  

  Software drivers for these features will not be available until 
  CorSrv 2004.


Xstation Manger enhancements not in 3003.               

  Performance enhancements for the X-Station 120 server will not be
  available until CorSrv 2004.


Defective Media - Customer gets incomplete documentation or media is defective.

  AutoShips actually come from the Product side of ISMD.  Replacements
  would normally be obtained by calling the Boulder Hotline, as they are
  for defective installation media.  Such is not the case with AutoShip
  3003 Corrective Service.

  Have the customer ship the ENTIRE package back to ISMD.  Provided with
  the ship is a postage free stickem.  This MUST be done so IBM can 
  analyze the media and correct process problems and identify purvasive 
  problems.

  The customer can call 800-237-5511 for a replacement copy.


LED 552 if customer does not reboot after CorSvc 3003 or AutoShip 3003

  Customers who fail to follow directions or forget to reboot their
  system after putting on bos.obj of 3003 who in turn immediately apply
  ptf U401273 (Additional Updates 3003) will always get a solid 552 LED
  on the next IPL.


PTF U401273

  This ptf is shipped with all AutoShip 3003 and CorSvc 3003 automatically
  The documentation (Release Notes) calls it Additional Updates 3003.
  The labels call it MPP UPDATE.

  This ptf is on 4 diskettes only.  It contains 32 fixes in updatep format
  Fixes are in:

    bos
    bosadt
    bosext1
    bosnet
    bsmEn_US
    X11dev


System backups (mksysb) and console being mapped to /dev/null

  This is not 3003 specific but needs to be addressed to everyone.
  Customers have called to say that after they reinstalled a system
  using a mksysb tape, the console never comes up but the machine is
  actually up.  

  This usually is because /usr/lpp/fonts/* files are missing.  These files
  are required in order to use the hft display.

  What happened?  Probably, the customer created the mksysb on a system
  that had an NFS or CD-ROM mount at the time of the mksysb.  This is a
  known bug, fixed on CorSrv 2004.

  To create a good mksysb (generally):

    Have NO NFS mounts at time of mksysb
    Have NO CD-ROM mounts at time of mksysb
    Have 8MBs free in /usr
    Have 8MBs free in /tmp