No commands were read from stdin

[Steve.Harman]

A problem began in the middle of the week last week. SFTP jobs began to get RC=1 with the error message in the subject.

I don't think it's Co:Z sftp per se, but I'm not sure what's going on. What's weird, the job runs successfully on another system in the JESPlex. Here's the log from a failing job:

Copyright (C) Dovetailed Technologies, LLC. 2011. All rights reserved.
**********************************************************************
* You are about to enter a private computer network. If you do not *
* have authority to use this network, please disconnect at this *
* time. Violators will be subject to legal remedies. *
* *
**********************************************************************
fromdsn(@DVG143.TMP.JCL(ATPW)).N.: 1 records/80 bytes read; 9 bytes written in 0.007 seconds (1.256 KBytes/sec).
No commands were read from stdin
CoZBatch.I.: returning rc=exitcode=1

Each of the systems has a separate USS environment, but everything else is shared. I've compared the scripts, ssh config, etc and nothing's changed in months. I restarted the daemon. Not sure what else to try. Anyone seen this problem?

Thanks,

[Steve.Harman]

I accidentally found what was causing this problem. Log files are directed the the /tmp folder... which was full. I cleared out some garbage and now everything is working again.

[dovetail]

You can configure $TMPDIR or $COZ_LOG to point to your log files.

Be warned that z/OS Unix shell scripts can also fail if /tmp is full. It is a good practice to manage /tmp with full threshold alerts and to schedule skulker to keep it cleaned up.

[Steve.Harman]

/tmp filled up because of a DB2 error file. It wasn't SFTP logs, those do age off. Co:Z was a victim, not a culprit. Thanks,