system reboots using the shutdown
When this service aid is run from standalone diagnostics, the flash update image file is copied to the file system from diskette or from the NIM server. Using a diskette, the user must provide the image on backup format diskette because the user does not have access to remote file systems or any other files that are on the system. If using the NIM server, the microcode image must first be copied onto the NIM server in the /usr/lib/microcode directory pointed to the NIM SPOT (from which you plan to have the NIM client boot standalone diagnostics) prior to performing the NIM boot of diagnostics. Next, a NIM check operation must be run on the SPOT containing the microcode image on the NIM server. After performing the NIM boot of diagnostics one can use this service aid to update the microcode from the NIM server by choosing the /usr/lib/microcode directory when prompted for the source of the microcode that you want to update. If not enough space is available, an error is reported, stating additional system memory is needed. After the file is copied, a screen requests confirmation
before continuing with the flash update. When you continue with the update, the system reboots using the reboot
current flash image is not saved.
You can use the update_flash command in place of this service aid. The command is located in the /usr/lpp/diagnostics/bin directory. The command syntax is as follows:
update_flash
update_flash
update_flash
Flag Description
Attention: The update_flash command reboots the entire system. Do not use this
command if more than one user is logged on to the system.
Chapter 6. Introducing Tasks and Service Aids 147