Changing The Log Output Level; Format; Operands; Example - HP XP P9500 Software User's Manual

Changing the log output level

To change the Business Continuity Manager agent log output level, use the MODIFY command
with SETINIT the LOGLEVEL parameter.

Format

If both the name of the cataloged procedure for startup and the identification name were specified
in the START command:
MODIFY
1[cataloged-procedure-for-startup-name.]identification-name
,SETINIT LOGLEVEL(output-level)
If only the name of the cataloged procedure for startup was specified in the START command:
MODIFY
1cataloged-procedure-for-startup-name
,SETINIT LOGLEVEL(output-level)

Operands

cataloged-procedure-for-startup-name
Used to specify the name of the cataloged procedure for startup that was specified
in the START command when a Business Continuity Manager agent was started.
identification-name
Used to specify the identification name that was specified in the START command
when a Business Continuity Manager agent was started.
SETINIT LOGLEVEL (output-level) ~ <1-digit-number> ((0 to 2))
Used to specify the new output level.
However, if the output level is 3, you cannot prevent Business Continuity Manager
log data from being output, even if you change the output level to 2, 1, or 0 by
using the MODIFY command. To prevent the Business Continuity Manager log data
from being output, change the value of the initialization parameter, and then restart
the Business Continuity Manager agent.
For details about the output level, see the description of the initialization parameter
LOGLEVEL in the HP P9000 for Business Continuity Manager Software Installation
Guide.

Example

To change the log output level to2 for a Business Continuity Manager agent that was started and
whose identification name is YK, enter the following command:
MODIFY YK,SETINIT LOGLEVEL(2)
YKY111I LOGLEVEL WAS CHANGED
YKY114I LOGLEVEL=2

Notes on updating configuration files

This section contains notes on updating a configuration file:
Do not perform an update on a configuration file from both Replication Manager and Business
Continuity Manager at the same time.
◦ If you update a configuration file from Business Continuity Manager, first stop the Business
Continuity Manager agent that is using that file to start up.
◦ If you attempt to simultaneously update or view a configuration file from both Replication
Manager and Business Continuity Manager, an error might occur from either Replication
Manager or Business Continuity Manager. If this happens, re-execute the update or view
operation. If an error occurs in an attempt to view the file from Replication Manager, the
548 Linkage with Replication Manager