Debugging Event Actions on OpenVMS

From TDiWiki

DEBUGGING AUTOMATIC, ACKNOWLEDGE, OR PURGE ACTIONS

---

For the event in question, check one of the consoles that is being monitored for the event.

• Select Operations.
• Select Consoles.
• Select the console in question.
• Select Monitored Events.
• Select the event in question.
• Select Automatic, Acknowledge, or Purge Actions.
• Check to see if the console in question is highlighted.
• Check to see if the action name is checked.
• Check to see if the timeframe has been selected.
• For certain actions, determine if the parameter or contact fields have been filled in (mostly pertains to mailing or paging actions).
• Click on the selected action name (in blue).
• Read through the procedure to determine if the username or password prompts are used in the procedure.
• Determine if the username and/or password are valid for your CW invocation (often times the CONSOLE_MANAGER username is used, but the password has been changed).

If the steps above are correct, and you are running your CW server on a VMS box, then attempt the following.

Login to a properly privileged account (SYSTEM or other suitably privileged account).

At the VMS $ prompt, perform the following:

$ SHOW QUEUE/ALL/FULL SYS$BATCH

• if no queue is defined, you must create a queue and define the SYS$BATCH logical to point to it, or if there is an existing batch queue you wish to use, you must define the SYS$BATCH logical to point to it using the following command

$ DEFINE/SYSTEM/EXEC SYS$BATCH queue_name_to_be_used

• if a SYS$BATCH queue exists, check to see if it is paused or stopped.

If either, issue the following command: $ START/QUEUE SYS$BATCH

If the queue exists, and is running, you can perform the following additional steps to determine the problem.

• Issue the following command:

$STOP/QUEUE SYS$BATCH

• Enter CW though the browser and create and occurence of the event, either by creating a scheduled occurence, or connecting to the console and entering the pattern associated with the event.
• Exit the browser, and perform the following command:

$ SHOW QUEUE/ALL/FULL SYS$BATCH.

• You should see an associated entry in the batch queue corresponding to the action perform. The queued job should have an entry number associated with it.
• Enter the following command:

$SET ENTRY entry_number/LOG=SYS$LOGIN:/KEEP/NOPRINT

• Start the batch queue using the following command: $START/QUEUE SYS$BATCH
• The job should run to completion.
• Enter the following command : $ TYPE SYS$LOGIN:action_procedure_name.LOG
• Scan the .LOG file to determine if errors are occuring within the .LOG file.
• If possible, mail a copy of this .LOG file to support@tditx.com.

(Thanks to B.Moore)