HP Serveur lame HP ProLiant BL465c Gen8 - Manual (Page 186)

For an item that can be omitted, the default value is used for operation.
After creating the host environment settings file, in the created server execute the check tool
(
EX_DRM_HOST_DEF_CHECK ) for the host environment settings file as follows:
On the file or database server:
EX_DRM_HOST_DEF_CHECK -db -f host-environment-settings-file
On the backup server:
EX_DRM_HOST_DEF_CHECK -bk -f host-environment-settings-file
If an error is found, revise the contents of the file, and then re-execute the check tool.
Creating operation IDs
An operation ID is a unique character string given to each resource that is to be the processing target
of an extended command.
You must define beforehand the information that the extended command will reference during execution
in the operation definition file. This operation definition file must be created at a certain location in
the "_operation-ID
.dat " format. By passing the operation ID in an argument to an extended command,
you can allow the extended command to reference the contents of the operation definition file.
Before setting up an extended command, determine a name that uniquely identifies the target on any
server involved in execution of the extended command.
An example of specifying an operation ID is provided below.
" server-name-of-operation-target " + " resource-name-to-be-operated "
An operation ID can have up to 64 ASCII characters.
The operation ID string can contain the following special characters:
! , # , $ , % , & , ' , ( , ) , + , _ , - , ^ , @ , , , .
Note however that the following restrictions are placed on using these special characters:
• You cannot create an operation ID that begins with a hyphen (-).
• You cannot create an operation ID using a period (.) by itself.
• If an operation ID contains an ampersand ( & ) or a caret ( ^ ), the operation ID must be enclosed in
double quotation marks ( " ).
Operation IDs are not case sensitive.
Note the following when using an operation ID:
• You cannot specify the same operation ID for multiple extended commands and execute these
commands in parallel. If you do, the extended commands may terminate with an error or the
backup catalog that is the target of the extended commands may be damaged.
However, you can execute an
EX_DRM_SQL_TLOG_BACKUP command in parallel that is specifying
the same operation ID as another extended command.
• To rename or stop using a created operation ID, you must delete the temporary directory for ex-
tended commands that has been generated automatically.
For information on how to delete the temporary directory for extended commands, see “
Deletion
of unnecessary files ” on page 183.
Preparation for using Application Agent 186