Jump to content


Photo
- - - - -

Kick off Unix bus and task from Windows


9 replies to this topic

#1 Vol Yip

Vol Yip

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 393 posts
  • Gender:Male
  • Location:Hong Kong

Posted 27 September 2017 - 08:33 AM

I am doing Gloiva consulting where it's PROIV version is 9.2.

 

There are situations where I use Windows' rsh to kick of a Unix base Glovia system's bus and task process.

 

Since rsh is not recommended by Microsoft and the latest Windows versions do not come with rsh, does anyone know what is the alternative way to start a PROIV bus and task process (in Unix) from a Windows client?

 

Thanks.

 

Vol



#2 Wim Soutendijk

Wim Soutendijk

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 211 posts
  • Gender:Male
  • Location:Netherlands

Posted 05 October 2017 - 06:15 AM

Hi Vol, 

 

on a windows server, you can use p4task.exe to start up a bus&task session. if you specify the ip address of the unix server, the task will be started on that server.

 

p4task /task:1.1.1.1:8837:TK_Z_TASKTEST /env:GloviaEnvironment /oper:TSK:TSK /codiv:PTI

 

wim 



#3 Vol Yip

Vol Yip

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 393 posts
  • Gender:Male
  • Location:Hong Kong

Posted 05 October 2017 - 07:07 AM

Thanks Win,

Do you mean I can execute p4task.exe in Windows and specific ip of Unix then I can start a proiv bus and task in Unix? Do I need to install a proiv environment in Windows or I just copy p4task.eXe to Windows will do?

Vol

#4 Wim Soutendijk

Wim Soutendijk

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 211 posts
  • Gender:Male
  • Location:Netherlands

Posted 05 October 2017 - 07:15 AM

Hi Vol, 

 

I don't know what's in your (unix) proiv distribution.

I only run on windows, and for me p4task.exe is supplied in C:\Program Files\NorthgateArinso\PROIV Version 8\VirtualMachine\busapi\sample

any windows (v8) installation will supply that to you, that's all you need to access the unix server

 

Wim 



#5 Vol Yip

Vol Yip

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 393 posts
  • Gender:Male
  • Location:Hong Kong

Posted 05 October 2017 - 08:07 AM

Hi Wim,

 

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

 

./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

 
I am looking for an alternate way to start the same Unix bus and task from Windows since rsh is no longer support.
 
Vol


#6 Wim Soutendijk

Wim Soutendijk

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 211 posts
  • Gender:Male
  • Location:Netherlands

Posted 05 October 2017 - 08:11 AM

I understand. You now use rsh to execute the unix version of p4task.

 

without rsh you need to have the windows version of p4task.exe, which you can start from a command prompt or .bat file on windows.

 

Wim 



#7 Vol Yip

Vol Yip

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 393 posts
  • Gender:Male
  • Location:Hong Kong

Posted 05 October 2017 - 08:16 AM

Thanks Wim,

 

Looks like I need to install a window version of proiv in order to run p4task.exe........

 

Vol



#8 Vol Yip

Vol Yip

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 393 posts
  • Gender:Male
  • Location:Hong Kong

Posted 05 October 2017 - 09:06 AM

Win,

 

I have one more question, in your example

 

p4task /task:1.1.1.1: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:

 

C:\Glovia\bus\apisample>p4task /task:192.168.0.4:5453:tk_sf_wo_completiion /env:
prod /user:prodapij:tsdjp123
doConnect: connect failed: Host '192.168.0.4', port 5453
 last WIN32 error 10061 / winsock error 10061: Connection refused
p4OpenPro4: sockOpen to bus daemon failed
 No error

 

p4OpenPro4 failed: Last Error 1, StatusCode 0, FailReason 0, SubError 0
 
When I changed the port to 23 (I believe it is a universal port for accessing the Unix server:
 
C:\Glovia\bus\apisample>p4task /task:192.168.0.4:23:TK_SF_WO_COMPLETION /env:pro
d /user:prodapij:tsdjp123 /codiv:GLO /oper:TSK:TSK
p4OpenPro4: recv Reply failed
 last WIN32 error 2 / winsock error 2: Unknown
p4OpenPro4 failed: Last Error 30, StatusCode 0 (OK), FailReason 0, SubError 0
 
 
I think I am close but I need some more helps....
 
Thanks,
 
Vol

 

 

 

 



#9 Vol Yip

Vol Yip

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 393 posts
  • Gender:Male
  • Location:Hong Kong

Posted 05 October 2017 - 09:29 AM

Wim,

 

I think I have found the solution. Thanks for your help. Much appreciated.

 

Vol



#10 Wim Soutendijk

Wim Soutendijk

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 211 posts
  • Gender:Male
  • Location:Netherlands

Posted 05 October 2017 - 09:40 AM

Hi Vol,

 

I have configured port 8837 on my windows server as the bus&task port. 

I think you should use your port 5435  (and not 5453)

 

wim 





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users