HP XP P9000 Command View Advanced Edition Suite Software 7.5.0-00 Administrator Guide (Web Version) (TB581-96346, July 2013)

Related topics:
Prerequisite environment for using the configuration definition file, page 241
Notes on using the configuration definition file, page 254
agent.rm.horcmInstance, page 405
agent.rm.horcmService, page 405
server.agent.rm.temporaryInstance, page 416
server.agent.rm.temporaryPort, page 416
server.agent.rm.horcmSource, page 419
Configuration definition file parameters supported Device Manager
If you use a parameter not supported by Device Manager, the configuration definition file is assumed
to be invalid and processing is not performed normally.
Device Manager supports the following parameters:
HORCM_MON
HORCM_CMD
HORCM_DEV
HORCM_LDEV
HORCM_INST
HORCM_INSTP
#
HORCM_CTQM
#
#
These parameters are supported by Device Manager agent version 6.2 or later. Note that when
you create or use a copy pair, even if HORCM_INSTP or HORCM_CTQM information is defined in
the configuration definition file, the Device Manager agent will operate while ignoring the
definition. The Device Manager agent does not add the HORCM_INSTP or HORCM_CTQM definitions
to the configuration definition file, nor does it add a pair group to the existing definitions. However,
when you delete a pair, any definitions of that pair group that exist in the HORCM_INSTP or
HORCM_CTQM definitions will also be deleted.
Related topics:
Description conventions for the configuration definition file, page 243
HORCM_MON parameter description format, page 244
HORCM_CMD parameter description format, page 246
HORCM_DEV parameter description format, page 247
HORCM_LDEV parameter description format, page 249
HORCM_INST parameter description format, page 251
HORCM_LDEVG parameter description format, page 252
HORCM_ALLOW_INST parameter description format, page 253
Description conventions for the configuration definition file
If a configuration definition file is not created in accordance with the description conventions, Device
Manager assumes that the configuration definition file is invalid.
Create a configuration definition file in accordance with the following conventions.
Administrator Guide (Web Version) 243