Thanks Sharon for your respond
But still am facing some issues by triggering above command as
mentioned
=========
*ail_subject=BDC NSS Tests}*
*[testengine.Timer:run:20] Timer started for 7200 seconds*
*[testengine.lib.Iperf:runServer:225] "iperf -s"*
*[testengine.lib.Staf:startProcess:229] Command: 10.79.16.166 PROCESS START
SHELL COMMAND "iperf -s" STDOUT serverLog.txt STDERRTOSTDOUT WAIT*
*[testengine.lib.Log:errorAndExit:94] Failed to start process 10.79.16.166
RC: 10*
*Result: Could not create STDOUT directory (), OS RC: 2*
*Failed to start process 10.79.16.166 RC: 10*
*Result: Could not create STDOUT directory (), OS RC: 2*
*[testengine.lib.Exit$1:run:32] In exit hooks, will exit*
Thanks
Sribastab
On Wed, Oct 21, 2015 at 8:21 PM, Sharon Lucas <luc...@us.ibm.com> wrote:
> When you specify a command with parameters as the value for the COMMAND
> option (instead of specifying both the COMMAND and PARMS options), you must
> specify the SHELL option. And you should always specify values that
> contain spaces within double quotes to indicate where an option value
> starts and ends. And, if you want to wait for the command to complete you
> can specify the WAIT option and then if you want to see the output (stdout
> and stderr) from running the command, you can specify options such as
> RETURNSTDOUT and STDERRTOSTDOUT. For example, try:
>
> STAF devadmin-ThinkPad-L412 PROCESS START SHELL COMMAND "iperf -s -B
> 172.16.10.239 -u" WAIT RETURNSTDOUT STDERRTOSTDOUT
>
> The error message is telling you that it could not find an executable
> named "iperf -s -B 172.16.10.239 -u" (instead of trying to find an
> executable named "iperf") because you didn't specify the SHELL option.
> Another way you could specify this is using the COMAND and PARMS options
> such as:
>
> STAF devadmin-ThinkPad-L412 PROCESS START COMMAND "iperf" PARMS "-s -B
> 172.16.10.239 -u" WAIT RETURNSTDOUT STDERRTOSTDOUT
>
> Note that your example of a STAF service request that works was using a
> different STAF service, the PING service, instead of the PROCESS service.
> These services have different syntax.
>
> For more information on the PROCESS service's START request including
> examples, see section "8.13 Process Service" in the STAF User's Guide at
> http://staf.sourceforge.net/current/STAFUG.htm#HDRPROCSRV.
>
> --------------------------------------------------------------
> Sharon Lucas
> IBM Austin, luc...@us.ibm.com
> (512) 286-7313 or Tieline 363-7313
>
>
>
>
> From: S Sribastab <sribastab...@gmail.com>
> To: staf-users@lists.sourceforge.net
> Date: 10/21/2015 09:34 AM
> Subject: [staf-users] Error on STAF !!!
> ------------------------------
>
>
>
> Hi All,
>
> Whenever am running a Staf command on windows am getting below errors
>
>
> *C:\ntaf>staf devadmin-ThinkPad-L412 PROCESS START COMMAND iperf -s -B
> 172.16.10.239 -u*
> *Error submitting request, RC: 10*
> *Additional info*
> *---------------*
> *Command does not exist: iperf -s -B 172.16.10.239 -u*
>
>
> ========
> but it works with single character command like:
>
> *C:\ntaf>staf devadmin-ThinkPad-L412 ping ping*
> *Response*
> *--------*
> *PONG*
>
>
> --
>
> *Thanks & RegardsMr.Sribastab*
>
> ------------------------------------------------------------------------------
> _______________________________________________
> staf-users mailing list
> staf-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/staf-users
>
>
>
--
*Thanks & RegardsMr.SribastabChennai9790993357*
------------------------------------------------------------------------------
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
