HP NonStop G-Series - Manual (Page 123)

Appendix N: Log Success/Failure of User Defined Command for Recovery 123
Appendix N: Log Success/Failure of User Defined
Command for Recovery
This section explains the procedure to write the Tacl routines that will notify OVNM in a way so OVNM can
correctly determine if the Tacl execution was successful. A sample Tacl routine called SAMPTACL in OVNM
shows the correct way to code a Tacl routine. To test this feature, create Filesys/File thresholds for files with
certain key words in their filename and use the following user-defined command:
RUN $vol.OVNM.SAMPTACL %s%
• If the filename contains GOOD, it will be reported as a successful execution of the command.
• If the filename contains ZERO, OVNM will consider it as a failure.
• If the filename does not contain GOOD or ZERO, then it will be treated as a failure.
To log whether or not a recovery command has been successfully executed the user’s TACL macro must check the
results of the recovery attempt and perform the necessary output commands: Follow the steps given below to
execute the recovery process in OVNM:
Step 1: OVNM_user_cmd_status Starting: Informing OVNM to look for Successful message.
Step 2: OVNM_user_cmd_status Successful: Informing OVNM that the user’s tacl code was successfully executed.
Step 3: OVNM_user_cmd_status Failed: Informing OVNM that the results failed and will generate an EMS event
containing text in “Log-Failure text field”.
NOTE: OVNM assumes a failure if it does not receive the Successful message and only receives the Starting
message. If it finds the Starting message but never finds the Successful message, then it assumes that the user’s
tacl code had some problem and was not successful (failed). Since the Starting message is critical in this
process, that output command should be executed as quickly as possible in the Tacl program.
Example of creating an OBJECT monitoring threshold in OVNM OCC with a user-defined Automatic Recovery
Command.
1. Click the New Configuration option in the Threshold menu to open Threshold dialog box.
2. Select FILESYS subsystem. OVNM will generate an event if the file “$DSMSCM.OVNMTEST.GOODTEST”
does not exist.
Figure 8 OCC Threshold Dialog Box