get rid of the script and use Scott's FTPAPI...

But download the beta version as it is the most recent (I'd take Scott's
beta code over most vendor's production code, beside the only reason it's
still "beta" is that he want to update the examples)

Join the mailing list for support


On Mon, Jan 27, 2014 at 3:22 PM, Gary Thompson <gthompson@xxxxxxxxxxx>wrote:

I am working on an EDI 856 ASN project.

We're currently in pilot phase (delivering product to
a few, selected customers requiring ASN) and this
weekend had a problem where the service handing
ASN document transfers to our customers started

"Cannot connect to host at address."
"Try again later."

(double quotes mine)

The ftp script in question has been running reliably the
past few weeks and had run successfully about 7:30 pm
yesterday, Sunday, Jan 26th.

At about 10:15 pm, we started "receiving" the cannot
connect message.

Our ASN document service is also looking into the issue,
but they don't yet see a cause for failed FTP connections.

Question: is there a fairly eash way to "catch" an FTP
"Cannot connect" message and then either continue
the transfer or "re-schedule" ?

My operations manager said he had recommended the
purchase of a "Managed FTP solution" but was turned-
down due to cost.

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page