Co:Z Launcher rc=127

[marguccio]

Hello there,
we are starting to use Co:Z Launcher on our z/OS 1.13, unfortunately we get rc=127 running the sample job:

//STEP1 EXEC PROC=COZPROC,
// ARGS='-LD,t batchav§UPDATE-QS-02.lex-com.net' set (D)ebug
//STDIN DD *
# This is input to the remote shell
echo "We are running on: " `uname -sr`

The target toolkit has been installed on a Windows box, along with Cygwin.
The most significant part of the trace shows

/opt/dtl/bin/cozserver -sockfd 3
[15:03:51.436135] CoZLauncher[D]: Started CoZServer process: 14
[15:03:51.445319] CoZLauncher[D]: arg[0] = '-LD,t'
[15:03:51.445427] CoZLauncher[D]: agent_cmd...
/bin/ssh -l batchav UPDATE-QS-02.lex-com.net c:/cygwin64/opt/dovetail/coz/bin/cozagent -LD,t
[15:03:51.785861] CoZLauncher[D]: Started CoZAgent process: 109
[15:03:51.789751] CoZLauncher[D]: About to start target command: ''
[15:04:39.369512] CoZLauncher[D]: agentStdoutThread completed
[15:04:39.370632] CoZLauncher[D]: agentStderrThread completed
[15:04:39.377114] CoZLauncher[E]: batchav§UPDATE-QS-02.lex-com.net target command '<default shell>' ended with RC=127
[15:04:39.377223] CoZLauncher[D]: Killing child process CoZServer (14) with signal 15
[15:04:39.377491] CoZLauncher[D]: Waiting for CoZServer
[15:04:39.380212] CoZLauncher[D]: serverStderrThread completed
[15:04:39.385990] CoZLauncher[D]: CoZServer (14) ended with RC=0
[15:04:39.388432] CoZLauncher: CoZLauncher ended with RC=127

which, in my understanding, tells us that the default shell (bash) on the Windows box has a problem.
The PATH on the Windows box is correct, so I really don't know where the culprit is.

Any idea ?

Kind regards,

Valter Marguccio

[dovetail]

Hi Valter,

It looks like your ssh connection failed to this Windows server.

- have you tested making a simple ssh connection to this windows server?
See: http://dovetail.com/docs/coz/install_wi ... sktop_sshd
"4. Test cygwin ssh from z/OS"

- otherwise, enable ssh tracing to get more information:
//COZCFG DD *
ssh-options=-vvv
//

[marguccio]

Hello,
trying to ssh to the windows box using 'ssh -p 8040 myuser@mywindowsbox' fails.
If I omit the port parameter, it works.
I tried to set the ssh trace and got a very long output. I can read through the trace that the
keys exchange works, but eventually rc=127 shows up. Let me know if I can send the trace
to you per e-mail.

Kind regards

[dovetail]

It could be that the cozagent program isn't found.

The command that is failing from the launcher is:

ssh -l batchav UPDATE-QS-02.lex-com.net c:/cygwin64/opt/dovetail/coz/bin/cozagent -LD,t

does this work interactively? If not, is the program found in the path as supplied?

otherwise, you can send the trace output to info@dovetail.com and we'll take a look.

[marguccio]

Hello there,
I've sent you the trace to your e-mail address.
Kind regards,

[dovetail]

It is difficult to tell what is happening, but I believe that the problem is that the cozagent program is not found / cannot be executed.

Try running this command to verify that you can remotely run the cozagent program via ssh:

ssh -l batchav UPDATE-QS-02.lex-com.net c:/cygwin64/opt/dovetail/coz/bin/cozagent -LD,t

[marguccio]

Hello,
how do I run the ssh command interactively ? From OMVS doesn't work, it say the ssh client can't be run from OMVS.

[dovetail]

Log into a z/OS ssh shell session from your workstation. Then you can issue the ssh client command.

[marguccio]

Hello,
from my workstation I logged on z/OS using PuTTY. Then I tried to connect to the Windows box
using the long ssh command you suggested. After giving the password, I got back to the bash prompt:

bash-2.03# ssh -l batchav UPDATE-QS-02.lex-com.net c:/cygwin64/opt/dovetail/coz/bin/cozagent -LD,t
batchav@update-qs-02.lex-com.net's password:
bash-2.03#

If the cozagent wouldn't be found, I'd have got an error message. Still, looking at the behaviour above, I can't
understand whether it works or not.

[dovetail]

Since you are running the cozagent program with the "-LD,t" option, you should have gotten a bunch of trace output if it ran.
It should look something like this:

Code: Select all

zos>ssh -l myuser  myserver c:/cygwin/opt/dovetail/coz/bin/cozagent -LD,t                                                   
myuser@myserver's password: 
cozagent[N]: version: 1.1.2 2013-03-19
[10:57:17.262392] cozagent[I]: version: 1.1.2 2013-03-19
[10:57:17.263394] cozagent[I]: Copyright (C) Dovetailed Technologies, LLC. 2006. All rights reserved.
[10:57:17.263394] cozagent[D]: cozagent dir: c:/cygwin/opt/dovetail/coz/bin
[10:57:17.263394] cozagent[D]: cwd: /home/goetze
[10:57:17.264394] cozagent[D]: PATH:
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/WINDOWS/system32
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/WINDOWS
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/WINDOWS/System32/Wbem
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/WINDOWS/System32/WindowsPowerShell/v1.0
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/Users/goetze/bin
[10:57:17.264394] cozagent[D]: 	/usr/bin
[10:57:17.264394] cozagent[D]: 	/opt/dovetail/coz/bin
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/Program Files (x86)/Windows Live/Shared
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/Program Files (x86)/Intel/OpenCL SDK/3.0/bin/x86
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/Program Files (x86)/Intel/OpenCL SDK/3.0/bin/x64
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/android/sdk/tools
[10:57:17.264394] cozagent[D]: 	/cygdrive/c/android/sdk/platform-tools
[10:57:17.264394] cozagent[D]: 	/bin
[10:57:17.264394] cozagent[D]: 	c
[10:57:17.264394] cozagent[D]: 	/cygwin/opt/dovetail/coz/bin
[10:57:17.264394] cozagent[D]: Waiting for configuration commands...

Can you even run the cozagent command locally on Windows with these options and get this output?

[dovetail]

I should also mention that the target toolkit package for Windows was built with 32-bit cygwin.
We have not tested with 64-bit cygwin.

There are some known incompatabilities:
http://stackoverflow.com/questions/1832 ... gwin-64bit

if you can't get the cogagent program to run under 64-bit cygwin, you might try installing 32-bit cygwin in a separate directory and try that.

I don't really see a requirement for 64-bit cygwin unless you are using programs that need huge memory spaces.

[marguccio]

Hello there,
if I run the above command on the Windows box, I get the same results as with z/OS, that is, nothing.
No output, no trace, nothing. The systems asks for the password, and afterward I get back to the bash.

[marguccio]

Hello there,
if I logon on the Windows box, go to the directory where the binaries are installed and type i.e. cozagent, I get back
nothing. I assume I should get a message, shouldn't I ?

[dovetail]

If you type:

cozagent -LD,t

you should get the output as above. If not, then the program is not working properly. Since it was built with 32-bit cygwin libraries, you might try to install cygwin 32 in an alternate directory and try that.

[dovetail]

As mentioned before, we have not tested the 32-bit cygwin binaries for the target toolkit under 64-bit cygwin.

We will look at building 64-bit cygwin builds for Windows and possibly distribute these as well.

In the mean time, you will probably have to install 32-bit cygwin if you want to use the 32-bit build of the Co:Z Target toolkit for Windows. This will work fine under 64-bit Windows.

FWIW, 64-bit cygwin is quite new. My suggestion is that unless you have a good reason to use 64-bit cygwin, that you install 32-bit cygwin - even on 64-bit Windows systems.

Here is some more information:

http://stackoverflow.com/questions/1832 ... gwin-64bit

http://cygwin.com/faq.html