IBM manual Logics of DB2 fix pack mass deployment script, 80 DB2 Deployment Guide

Note: Our deployment script only checks for DB2 instance processes and not all associated DB2 processes. Also, it does not detect shared libraries in the memory. Therefore we recommend that you ensure that all the DB2 processes have been stopped prior to running our script.

The fix pack installer installFixPack also detects if all DB2 processes have been stopped.

For related information, refer to the section “Stopping all DB2 processes before deployment” on page 77.

￿After deployment has finished on one machine, unmount NFS and go to the next target host.

Figure 2-9shows the script logic flow.

Script Start

Parse command line options

		Read next hostname	Empty	Script End
		Try ssh connection
		Mount NFS on remote machine
	Failure	mountnfs ()
	Verify no db2 process in memory		Perform fixpack deployment
Failure	chkdb2proc ()		db2fp_dply ()
		Success
		Unmount NFS on remote machine
		umountnfs ()

Figure 2-9 Logics of DB2 fix pack mass deployment script

The command line syntax for the fix pack deployment script is:

db2fp_install -N NFSpath -H hostA,hostB,...,hostN

-b base_install_path -c nlpack_location -n

-f level -f db2lib -f NOTSAMP -f installupdate -l log_file -t trace_file

80DB2 Deployment Guide