The mccomp command is the executable that calls the Knowledge Base compiler. The only required command option is the path to the manifest.kb file.

mccomp syntax

The following is the syntax for mccomp:

mccomp [-h|?] [-z] [-l <HomeLocation>] [-v [VERBOSE|INFORM|WARNING|ERROR|FATAL]]
[-e <ErrorLogFile>] [-n <CellName> | <ManifestKBFilePath>]

The following table lists the command-specific options for mccomp. For a list of common command options that apply to all CLI commands, see Event management common command options.

mccomp options



-e ErrorLogFile

Redirects error messages to a user-specified file; used primarily in scripts

-n CellName |ManifestKBFilePath

Specifies to use installationDirectory/pw/server /etc/CellName/kb/manifest.kb as the KB manifest file.
This option is ignored if ManifestKBFilePath is specified explicitly.


Sets the verbosity level of messages. Only messages of the specified level or higher are printed. If -v is not used, the default level is INFORM. If -v is used without a level specified, the default level is VERBOSE.

Restarting the cell

The knowledge base compiler compiles a Knowledge Base into executable code that can be loaded by a cell.

After running mccomp, if the compilation is successful, you must restart the cell to load the newly compiled Knowledge Base. For information about starting a cell, see mcell.

Rule tracing and collecting profiling data

The compiled Knowledge Base contains tracing and profiling instructions that help you to debug and optimize rules.

You can configure rule tracing using the Trace parameters in the mcell.conf file. For more information about the Trace parameters in mcell.conf, see Cell configuration parameters in mcell.conf.

Rule tracing is turned off by default to optimize performance.

You can dynamically enable, disable, and adjust the level of rule tracing while the cell is running by using the mcontrol CLI. You also can use the mcontrol CLI to request the collection of rule profiling data. This data includes the amount of time spent on each rule and the number of times each rule has been triggered. For more information about mcontrol trace rule controls, see mcontrol.

You can retrieve the profiling data collected by the mcontrol CLI by using the mgetinfo profiling CLI. For more information about mgetinfo, see mgetinfo.

mccomp examples

The following figure shows an example of mccomp.

mccomp example

mccomp -t manifest.kb

This command produces output similar to the example shown in the following figure:

Example output for mccomp

BMC-IMC120051I: Verifying file lib/sim_decl.wic
BMC-IMC120051I: Verifying file lib/sim_base.wic
BMC-IMC120051I: Verifying file lib/sim_validation.wic
BMC-IMC120051I: Verifying file lib/sim.wic
BMC-IMC120041I: File collectors/pom_byuser_collectors.mrl Compiled
BMC-IMC120041I: File collectors/mc_bystatus_collectors.mrl Compiled
BMC-IMC120041I: File collectors/mc_evr_collectors.mrl Compiled
BMC-IMC120041I: File collectors/bii4p_collectors.mrl Compiled
BMC-IMC120041I: File collectors/ibrsd_collectors.mrl Compiled
BMC-IMC120041I: File collectors/mc_sm_collectors.mrl Compiled
BMC-IMC120010I: Compilation ended successfully

mccomp return codes

There are no command-specific return codes for mccomp. For a list of common return codes that apply to all CLI commands, see Event management return codes.

Was this page helpful? Yes No Submitting... Thank you