Hello again. When running a SFTP in batch mode from Zos, I get this error to one of our servers and yet SFTP to some other servers still runs ok and I'm not sure if the problem is on Zos or on the server that I send to .... see error at he bottom of the pasted job output ( [00405] Received message too long 1416128883)
1 J E S 2 J O B L O G -- S Y S T E M S Y S R -- N O D E S Y S S
0
09.24.53 JOB13487 ---- THURSDAY, 23 APR 2009 ----
09.24.53 JOB13487 ICH70001I FTPBATCH LAST ACCESS AT 09:20:44 ON THURSDAY, APRIL 23, 2009
09.24.53 JOB13487 $HASP373 IDMIZ999 STARTED - WLM INIT - SRVCLASS C2CR_NOR - SYS SYSR
09.24.53 JOB13487 IEF403I IDMIZ999 - STARTED - TIME=09.24.53
09.24.54 JOB13487 - --TIMINGS (MINS.)-- ----PAGING COUNTS---
09.24.54 JOB13487 -JOBNAME STEPNAME PROCSTEP RC EXCP CONN TCB SRB CLOCK SERV PG PAGE SWAP VIO SWAPS
09.24.54 JOB13487 -IDMIZ999 NONCAT2 CONTROLR 00 304 92 ****** .00 .0 82194 0 0 0 0 0
09.24.54 JOB13487 -IDMIZ999 S010 ........ 00 50 20 ****** .00 .0 3965 0 0 0 0 0
09.25.02 JOB13487 -IDMIZ999 S100 COZSFTP 255 758 9 ****** .00 .1 50666 0 0 0 0 0
09.25.02 JOB13487 IEF404I IDMIZ999 - ENDED - TIME=09.25.02
09.25.02 JOB13487 -IDMIZ999 ENDED. NAME-CONTROLM TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME= .1
09.25.02 JOB13487 -FNBACTRT - ESTIMATED TOTAL COST = R1.36 TOTAL SERVICE UNITS = 136K
09.25.02 JOB13487 $HASP395 IDMIZ999 ENDED
0------ JES2 JOB STATISTICS ------
- 23 APR 2009 JOB EXECUTION DATE
- 69 CARDS READ
- 331 SYSOUT PRINT RECORDS
- 0 SYSOUT PUNCH RECORDS
- 18 SYSOUT SPOOL KBYTES
- 0.14 MINUTES EXECUTION TIME
1 1 //IDMIZ999 JOB (IDMI,R,L,'HOS-MIGR'),'CONTROLM', JOB13487
..........
DtlSpawn[N]: Copyright (C) 2005-2006 Dovetailed Technologies LLC. All rights reserved.
DtlSpawn[N]: version 1.2.1 2009-01-23
DtlSpawn[D]: region size requested = 0K, Actual below/above limit = 10216K / 1277952K
DtlSpawn[D]: geteuid=921109991
DtlSpawn: executing progname=login-shell="-/bin/sh"
DtlSpawn[D]: stdin file opened: //DD:STDIN
DtlSpawn[D]: stdout file opened: //DD:STDOUT
DtlSpawn[D]: stderr file opened: //DD:STDERR
DtlSpawn[D]: spawning progname=/bin/sh
DtlSpawn[D]: argv[0] = -/bin/sh
DtlSpawn[D]: current environment:
DtlSpawn[D]: >LIBPATH=/lib:/usr/lib:.<
DtlSpawn[D]: >_EDC_ADD_ERRNO2=1<
DtlSpawn[D]: >HOME=/SYSR/u/ftp/ftpbatch<
DtlSpawn[D]: >_BPX_SHAREAS=MUST<
DtlSpawn[D]: >_BPX_SPAWN_SCRIPT=YES<
DtlSpawn[D]: >_BPXK_JOBLOG=STDERR<
DtlSpawn[D]: >PATH=/bin:/usr/bin<
DtlSpawn[D]: spawned /bin/sh (33882494)
DtlSpawn: returning with rc=exitcode=255
1Co:Z sftp version: 1.2.1 (5.0p1) 2009-01-23
Copyright (C) Dovetailed Technologies, LLC. 2008. All rights reserved.
[00405] Received message too long 1416128883
Error during DTLSPAWN batch: Received message too long
-
LeonBylsma
- Posts: 22
- Joined: Thu Apr 16, 2009 8:26 am
Can you use this server from another sftp client? I would guess that you will get the same error.
You are probably having this problem:
http://www.snailbook.com/faq/sftp-corruption.auto.html
This means that the target SSHD server's user has a profile script that is printing out some welcome messages. This is incompatible with using SSHD and sftp-server. If this is your problem, one solution is to check the terminal type before writing things out in your shell profile:
if [ ${TERM} != "dumb" ]; then
echo Welcome to our fine system
fi
You are probably having this problem:
http://www.snailbook.com/faq/sftp-corruption.auto.html
This means that the target SSHD server's user has a profile script that is printing out some welcome messages. This is incompatible with using SSHD and sftp-server. If this is your problem, one solution is to check the terminal type before writing things out in your shell profile:
if [ ${TERM} != "dumb" ]; then
echo Welcome to our fine system
fi
-
LeonBylsma
- Posts: 22
- Joined: Thu Apr 16, 2009 8:26 am
)-
LeonBylsma
- Posts: 22
- Joined: Thu Apr 16, 2009 8:26 am
-
LeonBylsma
- Posts: 22
- Joined: Thu Apr 16, 2009 8:26 am