Execution of Other Commands by Control Scripts

Every command executed by a control script is a potential source of failure because the command may not exist on the target system. Your script can use any command conditionally, if it checks first for its existence and executability, and if it does not fail when the command is unavailable.

If the target system(s) conform with the POSIX 1003.2 Shells and Utilities standard, then the Execution Environment Utilities of this standard will also be available.
If a fileset has a prerequisite dependency on another product/fileset, then most of the control scripts for the dependent fileset can use the commands of the required product/fileset, if the $ROOT_DIRECTORY is /. (All commands perform their tasks in prerequisite order).
Commands should be referenced relative to the path components specified in the PATH variable. (See the discussion of PATH and the SW_PATH environment variable above.)

Execution of Other Commands by Control Scripts

Technical documentation

» Table of Contents

» Glossary

» Index