A number of system messages are not being processed by the "* LOGTABLE" file as expected.
Any idea why?
The messages that are being "missed" are local console messages/responses and do not come to VM:Operator via the *MSG facility. This is why they are not being "trapped".
To enable local console messages/responses to be "routed" through the SYSTEM LOGTABLE as if they were received via the *MSG facility, you must use the CONSOLE ROUTE command to specify you want the local console messages to be sent to the $ROUTER process for potential action:
---> CONSOLE ROUTE _addr_ START/STOP
which is documented at: https://docops.ca.com/ca-vm-operator/3-1/en/administrating/subcommands/console-subcommand
Issuing the CONSOLE ROUTE _addr_ START command (where _addr_ is the address of the VM:Operator SYSTEM console) will cause *all* CP, CMS, and VMOPERATOR command responses to be routed/sent to the $ROUTER process for potential processing.
To ensure the command is issued each time VM:Operator is initialized, place the command in the PROFILE VMOPER macro (if it doesn't exist, create it). If the PROFILE VMOPER file is found, it is automatically executed every time (just after) VM:Operator completes initialization.
===== * * * Top of File * * * |...+....1....+....2....+....3....+....4....+....5....+....6....+ ===== /* Issue these commands each time VM:Operator is Initialized */ ===== ===== say 'Executing PROFILE VMOPER:' ===== ===== /* Route LOCAL Console CP Responses to $ROUTER */ ===== 'CONSOLE ROUTE 009 START' ===== ===== say 'PROFILE VMOPER processing has completed.' ===== ===== Exit ===== * * * End of File * * *
Also reference documentation topic "How Message Processing Works" for details describing Message Processing: