Conference csc32::consolemanager

427.0. "CONSOLE WATCH LOOPS" by CX3PST::ANASAZ::J_BECKER (There's no substitute for a good boot) Tue Oct 11 1994 01:20

In vcs, a user could create a pseudo terminal and have the 
subprocess command file run the RECORD interface.  This 
would allow the user to repipe the console data from all
the nodes back into vcs.  The user used this mechanism to
watch for a particular peripheral's output.  The icon 
associated with this pseudo terminal would only change
color for this peripheral's events. In effect he could
monitor a peripheral from the data of all the nodes.

In PCM, the WATCH command does the same thing as the
VCS RECORD.  However in the psuedo terminal, the 
command file loops over and over

The same effect can be seen by entering at DCL

$CONSOLE WATCH/ALL/OUTPUT=SYS$OUTPUT

The output does not appear and the procedure exits.  When 
run in the pseudo environment (ie the system was added and
the command is the same as above), the above command is
looping.

Any ideas how to get around this?  Is there another way
to monitor a peripheral?

thanks

john becker

    John,
    
    >The output does not appear and the procedure exits.  When
    >run in the pseudo environment (ie the system was added and
    >the command is the same as above), the above command is
    >looping.
    
    This will be fixed in the next patch kit.
    
    >Any ideas how to get around this?  Is there another way
    >to monitor a peripheral?
    
    Phil can comment further on this one but there are hooks to allow
    event triggering against a peripheral that will probably be available
    in the next release.
    
    Regs,
      Dan

    Also, you can use /OUTPUT=TT as a workaround until the next
    patch kit.
    
    Regs,
      Dan