×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




You COULD create an exe on the PC that runs the script
with output redirected to a .txt, then scan the file for
return codes.

ftp host -s:script > output.txt

Or maybe DOS batch files can scan - it's been awhile.

Alternatively, this could be a candidate for FTP exit
program use - no need then to SBMJOB. I'm not sure,
though, about notification of failure to the PC.
> I've got a strange one that began after installing V5R1 a few weeks ago.
>
> In brief, we have a PC running DOS 6.22 that receives orders from our
> sales reps laptops.  The PC is connected to the AS/400 via ethernet.
> These orders are put into a text file ("TORDER.DAT") and FTP'ed to the
> IFS.  Immediately after the FTP PUT command, the PC issues a SBMJOB
> command to the AS/400 that processes these orders.
>
> The first thing the submitted job does is a RNM of "TORDER.DAT" to
> "Jnnnnnn.DAT" where nnnnnn is the AS/400 job number.  This happens at
> least 30 times _per day_.  About 2-3 times per week the RNM will fail
> with CPFA0A9 Object not found meaning TORDER.DAT does not exist.  If I
> look at the IFS it is indeed not there.  This would likely indicate to
> me the FTP PUT command failed.  I don't know any way to capture at that
> PC if the PUT has failed and I'm never there to see it.
>
> Can anyone think of something that may have changed with V5R1 that would
> cause almost random FTP failures?  Changing from V4R5 to V5R1 is the
> only thing different, so I'm presuming that is the first place to look.
>
> Thanks.
>
> --
> Jeff Crosby


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.