HP NonStop G-Series - Manual (Page 105)

Appendix G: Transporting Thresholds 105
ZTEXTRCT / ZTINSERT
The ZTEXTRCT and ZTINSERT tools are used together. The advantage of using these tools rather than MOVEDB is
that you can leave the OVNM systems running on both the sending node and the receiving node.
The first tool, ZTEXTRCT, is used to extract the thresholds from a node. The second tool, ZTINSERT, is used to
insert the thresholds into the second node.
To run ZTEXTRCT, switch to the OVNM subvolume and run it. For example:
32> volume $oss.ovnm
33> run ztextrct
Purge $OSS.OVNM.ORMEXTR
Fup Create $OSS.OVNM.ORMEXTR, type u, ext 20, maxextents 800
CREATED - $OSS.OVNM.ORMEXTR
Run Extract /in $OSS.OVNM.ORMCONF, out $OSS.OVNM.ORMEXTR/
Total Errors: 000
The extract job will create a binary file called ORMEXTR containing all the thresholds, in a format to be used with
ZTINSERT. This file needs to be moved from this node to the receiving node. You can use EXPAND or TCPIP.
The ZTINSERT utility will now verify that the data that it is attempting to insert came from a compatible OVNM
environment. Ideally, both OVNM environments should be the same (where ztextract and ztinsert are executed).
In some cases it is possible to take data from a different system and insert it into the current environment. This
feature was added in version 5.3 so this protection is not available in earlier versions. If you do use incompatible
releases, it is possible that you will end up corrupting the database on the system where ZTINSERT is executed.
To execute the insertion job, make sure that the OVNM application is running. It uses the LSTCOM process to
add records to the database. This is the same program that is used by the Object Configuration Client (OCC).
When adding records to the database, it will attempt to detect duplicate thresholds. To start the procedure,
switch to your OVNM subvolume and run ZTINSERT. Once you have executed ZTINSERT with all the files you
want to insert, you need to perform the following procedure to notify the monitoring program that new objects
have been added to the database:
• RUN BATCONF $OVLST
• START MONITORING
• EXIT
The following is an example and it shows what happens if you attempt to insert the same file into the same
node, twice.
37> Volume $oss.ovnm
38> run ztinsert
Run Insert /in $OSS.OVNM.ORMEXTR, out $BOLST/ $OSS.OVNM.ORMCONF
INSERT processing starting...
Processing CPU;CPU;CPU IS DOWN;*;0
Duplicate skipped
Processing CPU;CPU;CPU QUEUE LENGTH;*;0
Duplicate skipped
Processing CPU;CPU;LOW-PCBS IN USE;*;0
Duplicate skipped
Processing DISK;DISK;DISK IS DOWN;*;0
Duplicate skipped
Processing DISK;DISK;PERCENT FULL;*;0
Duplicate skipped
Processing EMS;EVENT;EXECUTE-DEFINED-ACTI;TANDEM.254.999;
Duplicate skipped