Jump to content
Vol Yip hasn't added any friends yet.
05 October 2017 - 09:29 AM
I think I have found the solution. Thanks for your help. Much appreciated.
05 October 2017 - 09:06 AM
I have one more question, in your example
p4task /task:220.127.116.11:8837:TK_Z_TASKTEST /env:GloviaEnvironment /oper:TSK:TSK /codiv:PTI
I believe 8837 is the port which opens for Windows to access Unix?
When I install Unix bus and task, I use the port 5435 and therefore my script is
./p4task /task:g2:5435:TK_SF_WO_COMPLETION /env:prod /user:prodapij:tsdjp123 /codiv:GLO /oper:TSK:TSK /params:CCN=$1,MAS_LOC=$2,WO_NUM=$3,WO_LINE=$4
In order to use Windows p4task.exe to start Unix task, do I replace my 5354 to your 8837?
I just installed a windows p4task.exe, I got the following error when execute:
05 October 2017 - 08:16 AM
Looks like I need to install a window version of proiv in order to run p4task.exe........
05 October 2017 - 08:07 AM
I think I need to clarify a bit. I have a proiv installation in Unix. What I want is so start a bus and task in Unix from a windows command prompt.
I used to use rsh in windows. In windows command prompt, I do:
C:\Documents and Settings\Administrator>rsh.exe G2 -l prodapij -n /g2/glovia/pro4bin/p4bus/task_wocomp.sh TS0007 TJE 26841 1
which will then start Unix script task_wocomp.sh, this script in fact will start
05 October 2017 - 07:07 AM
Community Forum Software by IP.Board