These responses are asynchronous to the command itself... Just how long
would you like the pipe to wait to be sure it has captured all the messages
produced by a command? There are no immediate responses to your secuser
commands, as indicated by the fact that the pipe found none.
Now, if you want to set up IUCV and message trapping, then you'd have a
party...
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OE-5-55 200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
On 11/8/07 10:30 AM, "Brian Nielsen" <[EMAIL PROTECTED]> wrote:
> 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
