HP NonStop G-Series - Manual (Page 111)

Appendix H: Customizing OVNM Configuration Files 111
Appendix H: Customizing OVNM Configuration Files
This section describes the procedures to make custom changes to the OVNM configuration files that are not
supported via the OVNM Host Installation Client or the ALTROVNM routine. The Host Installation Client allows
you to change parameters like the filters and the collector to be used by OVNM to write the messages.
NOTE: Changes to these files should be performed only when you are instructed to do so by the Support Staff.
You should not make changes to these files unless the ramifications of the changes are known.
Whenever changes are made using the Host Installation Client, or via ALTROVNM, a TACL routine called
BUILDCNF is executed. This routine rebuilds certain configuration files from scratch. If manual changes are made
to those files, they are lost the next time BUILDCNF executes unless they are made correctly.
BUILDCNF will rebuild the following files:
• OVNMCONF
• OCCCONF
• ELKCONFA
• ELKCONFO
• MONCONF
• OSSCONF
• MAILCONF
For making changes in the OVNMCONF and OCCCONF, the best approach (if possible) is to make the
changes between the Start/End Customer Change lines. These are maintained by BUILDCNF and during
version upgrades.
153 -------------------------------------------------------
154 -- Please set your own values for the above params --
155 -- between Start/End Customer changes #1 --
156 -------------------------------------------------------
157 -- Start Customer Changes #1 --
158 -- End Customer Changes #1 –
Changes to any of the parameters that are defined above this comment can be applied by re-entering the SET
command between these two lines, for example, between line 157 and 158 above. The system will use
whichever SET command is processed last. The original line built by BUILDCNF can remain as it is. For example,
the following sample customer change will enable suppression of leading spaces in the EMS messages. By
default, the leading spaces are displayed in HPOM.
153 -------------------------------------------------------
154 -- Please set your own values for the above params --
155 -- between Start/End Customer changes #1 --
156 -------------------------------------------------------
157 -- Start Customer Changes #1 –
158 SET ADAPTER SUPPRESSLEADINGSPACES ON
159 -- End Customer Changes #1 –
When this is not possible, a TACL routine called CUSTCHGS must be created that will make the necessary
changes after BUILDCNF builds the configuration file. When BUILDCNF executes, if a file called CUSTCHGS
exists, it will execute it, passing the name of the configuration file that was recreated. A sample CUSTCHGS file
called SAMPCHGS has been provided along with the backend.