HP XP Cluster Extension Software Administrator Guide
CLI commands
This section describes the following CLI commands:
• “clxrun” (page 41)
• “clxchkmon” (page 42)
clxrun
Check disk set
Description
clxrun can be used to manually prepare the application service's disk set before an existing
application service start procedure is invoked. When using clxrun, the status of the associated
RAID Manager device/copy group is checked to ensure that access to the disk set will occur under
data consistency and concurrency situations only.
clxrun must be invoked before the application service disk set can be activated; it is considered
an online-only program. However, the CLI features provide the same disaster tolerance features
as the integrated versions of XP Cluster Extension.
NOTE: Execution of clxrun does not start the pair/resync monitor.
Syntax
clxrun [-version] [-forceflag] app_name
Arguments
–version Displays the XP Cluster Extension version
–forceflag Forces startup
app_name The application name configured in the user configuration file (UCF.cfg)
The clxrun program expects only one parameter as the default setting. This parameter is used
to uniquely identify the application service in the APPLICATION section of the user configuration
file.
clxrun first checks for the –forceflag option. When using clxrun, it is not necessary to create
an application_name.forceflag file. This option, however, must be specified first if used.
CAUTION:
The forceflag option is implemented as an emergency switch to manually activate your disk
set. If the forceflag option has been specified, XP Cluster Extension will not check any consistency
or concurrency rules before activating the disk set.
Return codes
clxrun exits with one of the following return codes:
0 OK
Application service can be started.
1 ERROR_GLOBAL
Application service should not start on any system in either site on either disk array.
2 ERROR_DC
Application service should not start on any system in the local site on the local disk array.
3 ERROR_LOCAL
Application service should not start on this system.
CLI commands 41