Why don't the HCP messages from SET SECUSER or SET OBSERVER get captured 

when issued in a pipeline?

   pipe cp set secuser server01 * | hole
   HCPCFX6768I SECUSER of SERVER01 initiated.
   Ready; T=0.01/0.01 08:53:00
   pipe cp set secuser server01 off | hole
   SERVER01: HCPCFX6769I Your SECUSER terminated by BNIELSEN.
   HCPCFX6769I SECUSER of SERVER01 terminated.
   Ready; T=0.01/0.01 08:53:04

I don't expect the message from SERVER01's console to be captured, but I 

do expect the HCP messages on my own console to be captured.

All the HCPxxxE messages from various CP commands seem to be correctly 

captured.  And here is an example of an HCPxxxI message that gets capture
d:

   set cptrace for server01 reset
   HCPCFA1034I No SPECIFIC CP TRACE is in effect for SERVER01.
   Ready(01034); T=0.01/0.01 08:53:14
   pipe cp set cptrace for server01 reset | hole
   Ready(01034); T=0.01/0.01 08:53:18

Brian Nielsen

Reply via email to