DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Commands
8-8Busyout and Release Commands
8
■ Up to 3 maintenance commands issued from system access port (SAP) or
EPN Maintenance circuit pack logins can run concurrently. The other 2 are
reserved for the SYSAM and INADS ports.
■ Up to 5 administration commands can run concurrently.
■ In general, a maintenance object or other system entity can be acted upon
by only one command at a time. This restriction applies to such action
commands as:
— busyout
— change
— clear
—recycle
— release
—set
—test
■ In general, only 1 SPE component can be acted upon at one time by
commands such as those just mentioned.
■ When an action command is acting on a circuit pack, that circuit pack and
all maintenance objects located on it are unavailable for other commands.
■ Display-only commands such as the following generally do not conflict
with any other commands.
—display
—status
—get
— monitor
■ Certain system-wide actions such as
reset system
and
upgrade
software
cannot run concurrently with any other command.
■ Most commands require the use of shared system resources in order to
execute. When required resources are already in use, the command will
abort. For example,
save
,
restore
,
backup
, and
test disk
commands all
require the use of the Mass Storage System (MSS). Only one such
command can run at one time.
Busyout and Release Commands
The busyout command places the object of the command in a maintenance
busy state. In this state, the object is removed from active service and is not
available for use by call processing. Services dependent on the busied out
component are dropped. If the component supports a link, the link is dropped.
No scheduled or periodic background tests are run on the object while it is
busied out. Demand maintenance tests can be run on the object, though some
