3003 TIPS LIST 02/15/91 10:00 "3003 autoship" - Put this phrase in each pmr dealing with 3003 install/update problems. Put this in the body of the text. While you're talking to the customer you can simply do an addtxt. This document may change. You will not get another hard copy. Look on journey /u/hsim/other/3003/tips for any changes. Check the time stamp above to see if you're working with the latest copy. If you are unsuccessful in resolving install/update problems with an AutoShip or CorSvc customer you will end up giving the pmr to the COMMANDS group to handle. Keep in mind the potential for escalation if the problem is viewed by the customer is important. Also, be sure to put the number 3003 on the abstract line when you queue the pmr to the COMMANDS people. In all conversations we must know exactly what ACTIVE service release level the customer is at. Example, if there is a bos problem have customer run lslpp -h bos.obj. We need the ACTIVE 03.01.000x.00xx entry. If there is a tcpip problem have customer run two lslpp -h commands. lslpp -h bos.obj lslpp -h bosnet.tcpip.obj Location of helpful files on journey /u/hsim/other/xref - Cross Reference of lslpp -h info /u/hsim/other/3003/tips - This document /u/hsim/other/3003/ptfs - List of PTFs for pspp ordering /u/hsim/other/3003/docs/* - Actual soft copies of Release Notes /u/hsim/other/3003/apars/* - List of apars found in 3003. /u/hsim/other/3003/packaging - Helpful docs to understand packaging. 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 everyone else using updatep. Modify the bosinst scripts using sed. Modify the mkszfile script using sed. For 8MM drives, change block size to 512. Absolute minumum file space requirements. / 3.5 MBs This one was not clearly documented. /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. Customers who cannot deal with this must be handled case by case. See apar IX16832. '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. See apar IX16910. The fix is not software but is documentation. We tell all customers to modify the bosinst scripts BEFORE creating the Install/Maint diskettes. Clarification: we did fix the Install/Maint diskette that was auto shipped to each customer. So we should see few of these calls if any. .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 application companies 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 because we fixed 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. Ligted Keyboard and Dials not supported yet. Customers will have to wait for CorSvc 2004 for software drivers. CorSvc 2004 is expected to be available on March 15th, 1991. Xstation Manger enhancements not in 3003. Alot of SEs and Mkt Reps think 3003 has some Xstation enhancements. Such is not the case. CorSvc 2004 will have the significant changes. CorSvc 2004 is expected to be available on March 15th, 1991. Defective Media - Customer gets incomplete documentation or media is defective. AutoShips actually come from the Product side of ISMD so normally you would tell them to call the Boulder Hotline to have it reshipped. BUT such is not the case with AutoShip 3003. 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. We (L2) will need to ship a SevX copy to the customer asap. This means you will immediately tell the customer to ship the bad stuff back now and you will order the media of his choice (using pspp). Incorrect type of media shipped to customer. Some tape customers may incorrectly receive AutoShip 3003 on diskettes. This is unfortunate but there is little we can do for him. Tell him that you can ship him a copy on March 07, 1991 if he's willing to wait that long. Otherwise, that's all we can do. Let him know that the diskette process is not so bad. While it does require alot of feeding of diskettes, no diskette needs to be fed in more than once. 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. There is an 'unsupported' workaround for this. In the fax area is a 2 page document explaining why and how to recover. We don't support the letter or it's contents but you can fax it to the customer if they want it. 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 PTF U401279 This ptf is NOT shipped in the AutoShip 3003. It is only available via CorSvc (callup requests only). It is a replacement for 3003 X11rte.obj. It comes on 7 diskettes only. Some Informix customers and others may call in to specifically request it. Ship it SevX. 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 file are required in order to use the hft display. What happened? Probably, the customer created the mksysb on a system that had a NFS mount at the time of the mksysb. This is a known bug. To create a good mksysb (generally): Have NO NFS mounts at time of mksysb Have NO cdrom mounts at time of mksysb Have 8MBs free in /usr Have 8MBs free in /tmp If a customer calls in on this tell him to go back to the machine where he made the mksysb and remake it. Don't forget to tell the customer to be sure to have/make a set of boot diskettes that are at the same version of the system (GOLD, 3001, 3002, 3003). Note that this problem may be reported from Network Install customers. A network install customer may have taking the mksysb and put it on his network install server to attempt to install across the net. The same problem could result. Updating across the net Alot of customers say they're trying to update their systems across the net. This means many different things to different people. Get a clear understanding of what they mean. You can update across the net by having a remote mount mounted to your system. That remote mount could contain either/both 3003 update images or used by the updatep -t command. You can update using a network install server to get all your systems up to 3003. This is not really an update process. It's actually a reinstall process using a(some) install images. Do not pass this call off to anyone until you yourself can explain to someone else exactly what the customer is doing.