DataMuseum.dk

top - metrics - download

    Length: 3767 (0xeb7)
    Types: TextFile
    Names: »V«

└─⟦db1c56801⟧ Bits:30000748 8mm tape, Rational 1000, TESTMATE 2_2_0
    └─⟦866d14df1⟧ »DATA« 
        └─⟦97c804b2f⟧ 
            └─⟦this⟧ 

TextFile

package Remote_Command_Execution is

-- Required Information for running remote command
--      1) Test Driver.  Need this to resolve switch settings
--      2) Input Filename. The R1000 and the remote names.  Will put
--         this file to the remote name.
--      3) Output Filename. The remote and R1000 names.  Will get this file
--         from the remote.  Note that command execution will "temporarily"
--         redirect all output from the remote command execution to this
--         file on the R1000.  Then, after the command sequence has finished,
--         the remote output file if specified will overwrite the R1000; if
--         a remote name is not specified, then the command output will remain.
--      4) Remote_Results_Filename. Name of file to use on remote for remote
--         results file.  This file will be interrogated upon completion of the
--         sequence of remote command executions for status results.
-- Connection information will be cached such that once the connection has
-- been made with a remote, it will be maintained until either a different
-- connection is requested (via switching subsystem/views) or the test script
-- terminates (it is assumed that termination will result in automatic
-- closing of the connection by whatever powers that be controlling it).
--
-- The following logic dictates registering of the Test_Results:
--
--  if remote results file ok then
--      TMS.Register_Results (remote results file value)
--  elsif remote command execution failed then
--      TMS.Register_Results (Fail)
--  end;
--
-- Note that the remote command can be a sequence of lines, each of which is
-- executed as a "separate" command on the remote, which implies it can have
-- a status of its own.  Only the status from the last command executed is
-- used in determining failure status above.  All other command status's will
-- be ignored.


  procedure Run (Driver_Name : String;
                 Cmd : String;
                 Local_Input_File : String := "";
                 Remote_Input_File : String := "";
                 Local_Output_File : String := "";
                 Remote_Output_File : String := "";
                 Remote_Results_File : String := "TMSSTAT";
                 Cmd_Execution_Output_File : String := "";
                 Options : String := "");
  --
  -- Driver_Name : R1000 RCI Ada object name.  Used to setup context for
  --               executing the Cmd.
  --
  -- Cmd : literally the command to execute on the target.  For example,
  --       using the RS6000 customization, this would be "./hello.exe".
  --       This Cmd is resolved relative to the Object_Name target remote
  --       directory.  If multiline, each line will be executed as a separate
  --       command.
  --
  -- @_File         : the filename (relative to the context established by
  --                  Driver_Name) used to return remote results in.
  --                  Note that it is case sensitive, and must be a relative
  --                  name as the context is prepended to this name to form
  --                  a full pathname to workaround a problem with the RCI and
  --                  using relative pathnames to "File_Exists".  If specified
  --                  fully, then the file will be moved to/from the remote
  --                  at the appropriate time.
  --
  -- Remote_Results_File : Filename for returning remote results, same
  --                       restrictions as above. If "", then
  --                       will use the status back from the Cmd execution to
  --                       register results.

  procedure Close_Connection;
  -- force the closure of the connection established for the last command
  -- execution.

end Remote_Command_Execution;