HP NonStop G-Series User Manual
Page 112
Appendix H: Customizing OVNM Configuration Files 112
SAMPCHGS is just a sample, showing how this TACL routine can be coded. It includes samples of how to:
•
Change the CPU, LINKDEPTH, MAXSERVERS, Priority and Program File name assignments for the various
gateways
•
Change the Program used for EMSDIST, for example, to one that supports HighPin
•
Set various parameters in the MONCONF file
•
Set various parameters in the ELKCONFA file
You will have to review the code and make the necessary changes to the TACL routine to perform your specific
requirements. The Support Staff are available for assistance but customers are responsible for maintaining the
CUSTCHGS TACL routine.
NOTE:
You should have a basic understanding of the TACL programming language before cloning
SAMPCHGS to CUSTCHGS.
Use the following command to test your version of CUSTCHGS:
Run CUSTCHGS
When CUSTCHGS actually changes a file, it will display a message. An example has been provided below for
your reference.
Rename $TEMP.BTOVNM99.ELKCONFA, SAVEFILE.ELKCONFA
You should compare the contents of both of those files to make sure that only the changes you expect have been
applied.
NOTE:
OVNM is able to use Guardian security or Safeguard security for deciding which Guardian User ID
can perform what functions. You can use safeguard security by enabling the SAFESECINTV
in the OCCCONF file. To enable Safeguard checking, the value must be greater than zero. If the value is zero
(the default) then only Guardian security will be used.
To turn this feature on, you must create or update your CUSTCHGS file. The file SAMPCHGS has been
updated to show an example of how to do this. The value that is passed for this value determines the maximum
age of the Safeguard data that will be used when evaluating permissions. If you set this to a 1, it means that
once OVNM collects the data, it will use the ACL in its memory for at most, 1 hour before interrogating
Safeguard again.
If Safeguard is not available on the system, it will use guardian security even if the Safeguard parameter is set,
but it will generate EMS message for unavailability of Safeguard.
Customizing Node Monitoring Feature
In the previous OVNM versions, when you used the Object Configuration Client to turn Node Monitoring OFF,
the OVNM application would continue to consume EMS messages and react to them (if they were defined in an
EMS threshold) and send them to HPOM (if specified). With OVNM release 4.8, when you use the Object
Configuration Client to turn monitoring off/on for the entire node, you have the option of having this impact the
EMS traffic as well.
To invoke this new feature for EMS thresholds, you need to add this line to the OCCCONF file between the
CUSTOMER CHANGES #1 lines. If you add this command anywhere else, then you will lose the feature the next
time a change or upgrade is applied.
SET OCC MSTCTXFILE $vol.subvol.MSTCTX
Where $vol.subvol is the location of your OVNM subvolume. Do NOT specify the node name in this command.
The MSTCTX file is a control file used by the ORMMST program to record whether or not node monitoring has
been turned off or on.
To invoke this new feature in a way that will prevent EMS messages from going to HPOM when you turn node
monitoring off, add the following code to the OVNMCONF file, between the CUSTOMER CHANGES #1 lines. If
you add this command anywhere else, then you will lose the feature the next time a change or upgrade is
applied.
SET OVNM MSTCTXFILE $vol.subvol.MSTCTX
Where $vol.subvol is the location of your OVNM subvolume. Do NOT specify the node name in this command.
A
pp
en
di
x H