HPUX : PACKAGE EXECUTION STEPS IN SG

During Run Script Execution
Once the package manager has determined that the package can start on a particular node, it
launches the script that starts the package (that is, a package’s control script or master control
script is executed with the start parameter). This script carries out the following steps:
1. Executes any external_pre_scripts
2. Activates volume groups or disk groups.
3. Mounts file systems.
4. Assigns package IP addresses to the NIC on the node (failover packages only).
5. Executes any customer-defined run commands (legacy packages only
6. Starts each package service.
7. Starts up any EMS (Event Monitoring Service) resources needed by the package that were
specially marked for deferred startup.
8. Exits with an exit code of zero (0).



 During Halt Script Execution
Once the package manager has detected the failure of a service or package that a failover package
depends on, or when the cmhaltpkg command has been issued for a particular package, the
package manager launches the halt script. That is, a package’s control script or master control
script is executed with the stop parameter.



1. Halts any deferred resources that had been started earlier.
2. Halts all package services.
3. Executes any customer-defined halt commands (legacy packages only) or external_scripts.
4. Removes package IP addresses from the NIC on the node.
5. Unmounts file systems.
6. Deactivates volume groups.
7. Exits with an exit code of zero (0).
8. Executes any external_pre_scripts