Return code 137 when trying to run FROMDSN command

Discussion of the Co:Z Toolkit Dataset Pipes utilities
Post Reply
Jim D
Posts: 1
Joined: Mon Jun 15, 2009 6:44 pm

Return code 137 when trying to run FROMDSN command

Post by Jim D »

Ran into a problem this weekend after building and ipling a new sysres set with the FROMDSN command. Several (every) job that tried to execute it either from a remote location (through Putty Plink) or From Z/os (oshell scripts) failed with the following message:

Server sent command exit status 137
Disconnected: All channels closed
I'm not sure I'm getting all that far into FROMDSN but not sure how to determine just what and where to look for the 137 exit status.

Thanks,
Jim
dovetail
Site Admin
Posts: 2022
Joined: Thu Jul 29, 2004 12:12 pm

Post by dovetail »

Just to double check - you running fromdsn remotely using the "-ssh" option, correct? If no, please explain and respond with the exact fromdsn command you are using.

If that is the case, there is probably something wrong with your sshd configuration on z/OS. Does it still have a line like this in "sshd_config" file:

Subsystem dspipes /usr/lpp/coz/bin/dspipes

which points correctly to the installed Co:Z directory?

If that's not the problem, you will need to get a trace. This is probably easier to do from a non-Windows (Putty) client. So try this from a remote z/OS client:

fromdsn -ssh -vvv user@zoshost HLQ.SOME.DATASET

From Windows where fromdsn will use the Putty plink client, you can do the same thing, only with "-v" instead of "-vvv", but the trace is not as detailed.
Post Reply