Configuring Custom Actions3-16 Express5800/320Ma: Active Upgrade™ User’s GuideRelated Topics• “Programming Notes for Custom Actions” on page 3-15• “Configuring Custom Actions” on page 3-12Using Active Upgrade Environment VariablesYou can optionally use the environment variables specified in Table 3-5 in any programthat you write for a custom action. These environment variables are useful if you wantto write a conditional statement in your program that, for example, runs only on aparticular side of the system or only during a particular stage of the Active Upgradeprocess.By default, these environment variables are available to any child process of the ActiveUpgrade console, including executable files for custom actions. However, if necessary,you can also pass the environment variables to your executable files as arguments.For example, to pass only the ACTIVE_UPGRADE_SIDE variable to an executablefile, append the following string to the Arguments for the custom action on the CustomActions page:%ACTIVE_UPGRADE_SIDE%Table 3-5. Environment Variables for Custom ActionsEnvironment Variable DescriptionACTIVE_UPGRADE_SIDE Describes the side of the system on which the programis running.Values: Production, UpgradeACTIVE_UPGRADE_STATE Describes the current upgrade state.Values: Idle, PrepareSplit, Split, PrepareMerge, Merge,Commit, AbortACTIVE_UPGRADE_REQUEST Describes the current task that the Active Upgradeconsole is executing.Values: Idle, CheckReadiness, PrepareSplit,ExecuteSplit, PrepareMerge, ExecuteMerge, Commit,Abort, Start, Stop, BackupACTIVE_UPGRADE_HW_SPLIT Describes whether or not the system is running in splitmode.Values: Yes, No
