Conference csc32::consolemanager

Joe,

  We missed this when we were doing the work to put VCS features into
  PCM!

  Let me get this right, do you want your input file to be a list of
  commands valid on the managed system, or a list of valid PCM
  MONITOR commands?

  If the former, we may be able to do something for you.

Cheers,
Phil

>  Let me get this right, do you want your input file to be a list of
>  commands valid on the managed system, or a list of valid PCM
>  MONITOR commands?


	I need to be able to enter PCM from a DCL comand procedure and 
execute DIALOG commands on a managed system then be returned to DCL.

	This is a critical need for things like MDF/BRS quorum adjustment
scripts.

Joe

Joe,

  OK, try the following:

  $ CONSOLE DIALOG /QUIET /FILE=FILE.cmd system

  The /QUIET qualifier will prevent anything appearing on your
  display.

  This isnt dicumented (yet) but I will try and get it documented
  before we release, it should work as its what we use when you
  perform a DIALOG from withing the monitor interface.

Cheers,
Phil

Phil,


>  $ CONSOLE DIALOG /QUIET /FILE=FILE.cmd system


	Seems to work most of the time. Some of the multiple send
commands I have are getting lost. VCS has a /RATE qualifier on the
CONNECT command to slow things down. Any way to do it on PCM?

Joe


  CONNECT

    /RATE

              {FAST      }
       /RATE= {MEDIUM    }
              {SLOW (D)  }

    is the rate at which characters are sent from the /INPUT file to
    the nodes. FAST indicates that the contents of the files will be
    transmitted as fast as possible to the node. MEDIUM indicates that
    the contents of the files will be transmitted to the node at about 8
    to 10 characters per second. SLOW indicates that the contents of the
    files will be transmitted to the node at about 1 to 3 characters per
    second.

    The /RATE qualifier does not change your baud rate. The /RATE
    qualifier is ignored if you do not specify the /INPUT qualifier.
 

  Hmm, what type of system are you sending to?

  There is no "RATE" qualifier, we didnt forsee the
  need for one, we do rely on the managed system
  performing XON and XOFF so that it controls the
  rate itself.

  Apart from that, I take it that this is achieving
  your aim.

  BTW, you may see some funny messages appearing from
  the DIALOG when used this way, we are attempting to
  fix these up at the moment.

Cheers,
Phil

>  Hmm, what type of system are you sending to?


	I sending to a piece of test equipment with an
RS232 port. I can probably work around the problem by
just doing a one line send in the dialog file and then
do my commands with multiple $console dialog commands
from DCL. 
	You should probably look at having the /RATE
feature somehow. This would probably be more useful on
non DEC systems than on DEC systems

Joe

 OK, what we have done is the following...

    You now have a RATE keyword within your dialog procedure, the rate
    keyword will accept an integer number of seconds as a paramter, this
    will cause the dialog to pause after a SEND for the specified number
    of seconds before continuing.

    So, specifying RATE 5 will cause a 5 second wait between your SEND
    commands, the side effect of this would be if you have a WAIT command,
    the timeout specified for the WAIT will be added to the RATE period,
    as the WAIT will only start after the RATE period has expired.

    NOTE: we dont wait for the RATE time between all dialog commands, just
          after a SEND.


 Now, we understand that this may need some more work (such as placing the
 delay between characters and allowing intervals of less than 1 second),
 but that would be too much for this release, so if it is necessary, we
 ask that you submit a phase 0 request.

Cheers,
Phil