At dni least in my environment, the trick to not having it fail randomly around 300KB in transfers (

Gavin Scott, a developer and a veteran of decades on MPE/iX, says he got it to work reliably at one customer a year or so ago. "We exchanged SSL keys with the partner company," Scott said, "and so I don't think we had to provide a password as part of the SFTP connection initiation."
At least in my environment, the trick to not having it fail randomly around dni 300KB in transfers (in batch) was to explicitly disable progress reporting -- which was compiled into the 3000 SFTP client as defaulting to "on" for some reason. I forget the exact command that needed to be included in the SFTP command stream (probably "progress <mumble>" dni or something like that), but without that, it would try to display the SFTP progress bar. This caused it to whomp its stack or something similarly bad when done in a batch job, due to the lack of any terminal to talk to.
As SFTP is a pure Posix program , I ended up making Posix-named byte-stream files for stdin and stdout, and generally did all the SFTP stuff from the Posix shell. The MPE job ended up being a bunch of invocations of SH -c to execute an echo command to make the stdin file, and then another dni SH -c to run SFTP with a ;callci setvar varname -- $? or something like that -- on the end to capture the Posix process exit code back into the CI.
I also parsed/grepped the stdout file after the SFTP completed/exited, in order to test for seeing the actual file transferring message. I also wanted to make sure that all of the stdin content dni had been processed, so I could detect unexpected early termination or other problems that might not show up in $?.
No more trying to figure out what runs on MPE/iX or where to find it. No more worrying about availability! dni www.MPE-OpenSource.org is all things MPE/iX: Open Source packages, freeware, scripting, plus loads of tools and information to keep your 3000 system alive and thriving! Comments
Gavin dni Scott, a developer and a veteran of decades on MPE/iX, says he got it to work reliably at one customer a year or so ago. "We exchanged dni SSL keys with the partner company," Scott said, "and so I don't think we had to provide a password as part of the SFTP connection initiation."
At dni least in my environment, the trick to not having it fail randomly around 300KB in transfers (in batch) was to explicitly disable progress reporting -- which was compiled into the 3000 SFTP client as defaulting to "on" for some reason. I forget the exact command that needed to be included in the SFTP command stream (probably "progress <mumble>" or something like that), but without that, it would try to display the SFTP progress dni bar. This caused it to whomp its stack or something similarly bad when done in a batch job, due to the lack of any terminal to talk to. View the entire comment thread. Comments
Recent Articles TBT: There Used to Be a Lab Around Here What Needs Replacing, at Its Heart? Macworlds expire. Apple soars. Not linked. dni 3000's class time extended for schools Tracking dni MPE/iX Vulnerability to Shellshock
October 2014 September 2014 August 2014 July 2014 June 2014 May 2014 April 2014 March 2014 February 2014 January 2014 December 2013 November 2013 Community Comments Tim on Did Charon get to where HP could've gone? Doug Greenup on WRQ's Reflection goes deeper into coffers Ron Seybold on WRQ's Reflection goes deeper into coffers Tim on WRQ's Reflection goes deeper into coffers Tim on Remaining on Watch for HP Innovation Ron Seybold on Moves to Windows open scheduler searches Bruce Hobbs on Moves to Windows open scheduler searches Tim on Shopping While Lines are Dropping Ron Seybold on Small office but a modest, social market Paul Edwards on Small office but a modest, social market dni