[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Getting started
I couldn't imagine not using FTPAPI. I did the IBM client->parse output
thing. FTPAPI is much easier.
On Thu, Sep 11, 2014 at 9:27 AM, Gary Thompson
<[1]gthompson@xxxxxxxxxxx> wrote:
Ron,
FWIW I started on that same path.
I created a pgm to scan for text and had some success.
Although we always connect to the same server for 'EDI'
send/receive, I saw differences in message texts,
as I had been advised by others on this list.
At that point, I re-considered and am now exploring FTPAPI;
currently on README Steps 4/5
-----Original Message-----
From: [2]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[3]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Ron
Koontz
Sent: Thursday, September 11, 2014 7:01 AM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Getting started
I'm sure it is a nice tool to use as he has many I use.� I do not
use this one but all we do is read the log file after the program
sends.� If an error occurs it Queues the batch again.� Only 2
programs.� One CL for the FTP process and one RPGLE program to read
the log file.� Maybe I'm not seeing the "big" picture here..
I even went as far as writing an exit program to monitor a specific
output file/log the FTP process created and queued the data again
based on what was in the output file..
Thanks
Ron Koontz
-----Original Message-----
From: [4]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[5]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Thursday, September 11, 2014 8:38 AM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Getting started
You can, but in Scott's words...
"*With OS/400 IBM ships a wonderful FTP client that allows you to� I do both interactive and batch file transfers. After attempting to
write a few programs that send files in "batch" mode, I discovered
that properly detecting errors in batch mode was not fun.*
*For my own project, I needed a way to reliably send data to a
customer every day. When this failed, or anything went wrong in the
process I needed an easy way to alert the I.S. department before the
customer noticed.*
*From these requirements, the FTP API was born. It uses socket calls
to implement the FTP protocol. If anything goes wrong, it will
report the error, and give the program the ability to retrieve the
error message. I use it both to send/receive files from my
customers, and also (as a separate job) to log on later and check
that the file is actually there.*
*�
*I would strongly recommend �PAPI over scripting the built in
client any day of the week and twice on Sunday.*
*Charles*
On Wed, Sep 10, 2014 at 4:40 PM, Ron Koontz <[6]rkoontz@xxxxxxxxx>
wrote:
>� � You don't have to use the API.. You can do this through
regular FTP on
>� � the 400.. We send thousands of EDI transactions over FTP
everyday...
>� � Send me an email if you want to know how. I can send you some
sample
>� � code if you want..
>
>
>
>� � Thanks
>
>
>� � [1]Continental Express
>
>� � Ron Koontz | IT Manager | Continental Express, Inc
>
>� � (: Direct: [7](937) 419.8118| (: Tel [8](800) 497.2100
x118|� Fax (937)
>� � 498.2155
>
>� � *: [2][9]rkoontz@xxxxxxxxx� Visit us on the web:� [3][10]www.ceioh.com
>� � [4][11]http://www.ceioh.com/Facebook-Like.jpg
>
>
>
>� � -----Original Message-----
>� � From: [12]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>� � [mailto:[13]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf
Of Gary
>� � Thompson
>� � Sent: Wednesday, September 10, 2014 2:01 PM
>� � To: [14]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
>� � Subject: Getting started
>
>
>� � Back in January, I joined this list (at least I think I did)
and
>� � downloaded ftpapi.savf
>
>
>� � Today I received orders to install asap due to issues we have
with our
>� � EDI 856 ASN process.
>
>
>� � If there are any notes/instructions that help with using the
save file,
>� � I will very much appreciate getting a copy or being pointed
in the
>� � right direction.
>
>
>� � (I've this feeling I've misplaced and/or forgotten something)
>
>
>� � Thanks all.
>
>
>
> __________________________________________________________________
>
>� � The information contained in this e-mail is intended only for
the
>� � individual or entity to whom it is addressed. Its contents
(including
>� � any attachments) may contain confidential and/or privileged
>� � information. If you are not an intended recipient you shall
not use,
>� � disclose, disseminate, copy or print its contents. If you
receive this
>� � e-mail in error, please notify the sender by reply e-mail and
delete
>� � and destroy the message. Continental Express, Inc. and its
subsidiaries
>� � and affiliates will not be held liable for the unintended or
>� � unauthorized use of any information contained in this email
or as a
>� � result of any additions or deletions of information
originally
>� � contained in this email.
>
> References
>
>� � 1. [15]http://www.ceioh.com/
>� � 2. mailto:[16]rkoontz@xxxxxxxxx
>� � 3. [17]http://www.ceioh.com/
>� � 4.
>
[18]https://www.facebook.com/plugins/like.php?href=https://www.faceb
ook.co
> m/pages/Continental-Express-Inc/394970290582855?fref=ts/
>
>
--------------------------------------------------------------------
--
> - This is the FTPAPI mailing list.� To unsubscribe, please go to:
> [19]http://www.scottklement.com/mailman/listinfo/ftpapi
>
--------------------------------------------------------------------
--
> -
>
>
________________________________
The information contained in this e-mail is intended only for the
individual or entity to whom it is addressed. Its contents
(including any attachments) may contain confidential and/or
privileged information. If you are not an intended recipient you
shall not use, disclose, disseminate, copy or print its contents. If
you receive this e-mail in error, please notify the sender by reply
e-mail and delete and destroy the message. Continental Express, Inc.
and its subsidiaries and affiliates will not be held liable for the
unintended or unauthorized use of any information contained in this
email or as a result of any additions or deletions of information
originally contained in this email.
--------------------------------------------------------------------
---
This is the FTPAPI mailing list.� To unsubscribe, please go to:
[20]http://www.scottklement.com/mailman/listinfo/ftpapi
--------------------------------------------------------------------
---
--------------------------------------------------------------------
---
This is the FTPAPI mailing list.� To unsubscribe, please go to:
[21]http://www.scottklement.com/mailman/listinfo/ftpapi
--------------------------------------------------------------------
---
References
1. mailto:gthompson@xxxxxxxxxxx
2. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
3. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
4. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
5. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
6. mailto:rkoontz@xxxxxxxxx
7. tel:%28937%29%20419.8118
8. tel:%28800%29%20497.2100%20x118
9. mailto:rkoontz@xxxxxxxxx
10. http://www.ceioh.com/
11. http://www.ceioh.com/Facebook-Like.jpg
12. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
13. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
14. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
15. http://www.ceioh.com/
16. mailto:rkoontz@xxxxxxxxx
17. http://www.ceioh.com/
18. https://www.facebook.com/plugins/like.php?href=https://www.facebook.co
19. http://www.scottklement.com/mailman/listinfo/ftpapi
20. http://www.scottklement.com/mailman/listinfo/ftpapi
21. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------