[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ftpapi Digest, Vol 97, Issue 6
Yes I was using F10 to step through. In all the times I had used
STRDBG, F10 had always allowed me to see where problems occured. I did
not know F22 existed and had never taken the time to explore all the
cmd keys' functions. Thanks for teaching me something new!
Thanks Mike for expanding on the answer by showing the time saving
method.
I will try it out this evening since this is a project I am working on
after hours.
Also, I'm sorry for taking up mailing list space for trivial answers
but I had just never encountered that type debugging situation and
could not see why the files were not getting transferred. This should
let me see what's going on.
Thanks to all,
Jerry
From: "ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx"
<ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx>
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Sent: Friday, November 7, 2014 11:45 AM
Subject: Ftpapi Digest, Vol 97, Issue 6
Send Ftpapi mailing list submissions to
[1]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
[2]http://scottklement.com/mailman/listinfo/ftpapi
or, via email, send a message with subject or body 'help' to
[3]ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
[4]ftpapi-owner@xxxxxxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ftpapi digest..."
Today's Topics:
1. RE: Message 5 - Debugging TESTMIRIN (Mike Krebs)
----------------------------------------------------------------------
Message: 1
Date: Fri, 7 Nov 2014 10:45:21 -0600
From: Mike Krebs <[5]mkrebs@xxxxxxxxxxxxxxxxxx>
To: HTTPAPI and FTPAPI Projects <[6]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Message 5 - Debugging TESTMIRIN
Message-ID:
<[7]3DF08BA25872B644A1421B9F085B1829A0E5D9D192@xxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
STRDBG mainpgm
F10 (step)
Call mainpgm
When it breaks on the first statement, press F14
Add the service program to the work with Module List
Opt Program/module Library Type
1 ftpapir4 *LIBL *SRVPGM
Use 5 on the module that has do_dir
Add a breakpoint.
F12 to continue
Will save a little time wading through the program using F22.
-----Original Message-----
From: [8]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[9]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Michael
Ryan
Sent: Friday, November 7, 2014 10:17 AM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Message 5 - Debugging TESTMIRIN
Are you Shift-F10 (step into) instead of F10 (step over)?
Sent from my iPhone
> On Nov 7, 2014, at 7:42 AM, raJerry Birch <[10]jerry.birch@xxxxxxx>
wrote:
>
> Jerry,
> FTPAPI is just a service program that you call from your own RPG
> programs. Likewise, TESTMIRIN, is just a regular RPG program
compiled
> with the normal RPG compiler from IBM.
> You can debug it the same way you'd debug anything else.
> Is that what you're asking?
> Scott,
>
> Thanks for your reply. I am still having to use SEU so I am using
> STRDBG. I set the DEBUG up for TESTMIRIN and was stepping through it
> but when it went to each of the CALLP statements, it did not step
> through the subprocedures and I need to see what is happening inside
of
> the "do_dir" subprocedure. Do I need to do something else in the
> STRDBG setup or the compile for it to be able to step through the
> subprocedures?
>
> Thanks,
> Jerry
> From: "[11]ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx"
> <[12]ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx>
> To: [13]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Sent: Friday, November 7, 2014 10:09 AM
> Subject: Ftpapi Digest, Vol 97, Issue 3
> Send Ftpapi mailing list submissions to
> [1][14]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> To subscribe or unsubscribe via the World Wide Web, visit
> [2][15]http://scottklement.com/mailman/listinfo/ftpapi
> or, via email, send a message with subject or body 'help' to
> [3][16]ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
> You can reach the person managing the list at
> [4][17]ftpapi-owner@xxxxxxxxxxxxxxxxxxxxxx
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ftpapi digest..."
> Today's Topics:
> 1. Re: Longer Character Parameter (Scott Klement)
> 2. RE: receive Dynamic XML (Mike Krebs)
> 3. Re: receive Dynamic XML (Donnie Barrow)
> 4. Debugging TESTMIRIN (raJerry Birch)
> 5. Re: Debugging TESTMIRIN (Scott Klement)
> 6. Re: receive Dynamic XML (Donnie Barrow)
>
----------------------------------------------------------------------
> Message: 1
> Date: Thu, 06 Nov 2014 13:18:00 -0600
> From: Scott Klement <[5][18]sk@xxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[6][19]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: Longer Character Parameter
> Message-ID: <[7][20]545BC968.7010509@xxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Arturo,
> A VARYING field (like your xml_Data example) consists of two parts,
(1)
> a length (2) the actual data. However, the WEBFORM_postData()
rotuine
> does not return it in that format. Instead, it just points directly
to
> the data. It does return a length, but it's in a completely separate
> field.
> So you are confusing RPG by pointing a VARYING field at it. It's
trying
> to use part of the data string as the length portion, and that's
> definitely going to cause problems.
> If you really need to read this data yourself (instead of just
passing
> it on to another HTTPAPI routine) then please use a fixed-length
> variable (rather than VARYING) and restrict it's length using
%SUBST.
> -SK
>> On 11/6/2014 8:11 AM, Arturo wrote:
>> Thanks guys! Much appreciate your response.
>>
>>
>> Your suggestion worked! I'm fairly new to the pointer world, as I
>> haven?t really had to use. I will create my own procedure and not
>> modify HTTPAPI. Again, great suggestion!
>>
>>
>> Having another pointer issue. I want to get the value from the
> pointer
>> postPtr from the following call: WEBFORM_postData(form :postPtr
>> :postDataSize ) but get error RNX0115 when I do the following:
>>
>>
>> p_PostData = postPtr;
>>
>> wXML = 'Value of uri: ' + xml_Data;
>>
>>
>> The definitions are:
>>
>> D p_PostData S *
>>
>> D xml_Data S A Len(500000) Varying
>>
>> D
>> Based(p_PostData)
>>
>>
>> What am I doing wrong, that I am getting the RNX0115 error? When I
>> debug, and hit F11 on xml_Data, I see actual data in the field,
> which
>> is why this error is confusing me.
> ------------------------------
> Message: 2
> Date: Thu, 6 Nov 2014 13:28:57 -0600
> From: Mike Krebs <[8][21]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[9][22]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: RE: receive Dynamic XML
> Message-ID:
> <[10][23]3DF08BA25872B644A1421B9F085B1829A0E5D9D035@xxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
> Sounds like you are on the right track.
> If you have problems writing INCOMING, share some XML and there are
a
> bunch of us that can help out. But with multiple data elements, you
> will have to use some global variables or data structures to keep
track
> of the results.
> -----Original Message-----
> From: [11][24]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[12][25]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Donnie
> Barrow
> Sent: Thursday, November 6, 2014 11:57 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: receive Dynamic XML
> Thank you for you response?Here is what I am doing. I getting item
> info/availability from a webservice. since it will involve multiple
> warehouses the xml will return lists aka arrays of warehouse item
> availability.[UGHHH] ?So I took?a bit of EXAMPLE16 &?EXAMPLE17 and
used
> it since it was parsing the return data. In my case it will be a
huge
> chunk of data to parse especially with the arrays....SO I didn't
want
> to write it to the IFS [like in EXAMPLE17] but rather parse send the
> data back into the program parms.
> From: Mike Krebs <[13][26]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[14][27]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 12:15 PM
> Subject: RE: receive Dynamic XML
>
> I think http_url_post_xml allows you to work with the returned data
> directly. EXAMPLE16 is showing this by calling INCOMING for each
> element in the returned xml.
> -----Original Message-----
> From: [15][28]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[16][29]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Scott
> Mildenberger
> Sent: Thursday, November 6, 2014 10:29 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: RE: receive Dynamic XML
> I have used both the _raw and _xml procedures for either
> http_url_get/post depending on what you are using, they allow you to
> specify a procedure that gets called when data is received.? They
are
> used in some of the provided examples if you search for them.
> Scott
> -----Original Message-----
> From: [17][30]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[18][31]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Donnie
> Barrow
> Sent: Wednesday, November 05, 2014 4:59 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: receive Dynamic XML
> ?i need some guidanceMy rpgle free program is calling a webservice.
I
> used Scott Klement's example17?but I do not want to write the
response
> soap to the IFS. Is there anyway to receiveand parse?the response
xml
> in the program without writing to the IFS Donovan BarrowDBarrow
> Consulting
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [19][32]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [20][33]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
----------------------------------------------------------------------
> -
>
> ------------------------------
> Message: 3
> Date: Thu, 6 Nov 2014 19:41:23 +0000 (UTC)
> From: Donnie Barrow <[21][34]ddbarrow@xxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[22][35]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: receive Dynamic XML
> Message-ID:
>
>
<[23][36]1243368863.178054.1415302883258.JavaMail.yahoo@xxxxxxxxxxxxxx.
ne1.
> yahoo.com>
>
> Content-Type: text/plain; charset="utf-8"
> I am using?data structures. the?challenge for me will be to keep
track
> of the array elements in the list as I can receive multiple
warehouses.
> Gonna watch the program run?in debug to see how it plays out and
then
> yell for help afterwards LOL.....so stay tuned!? thanks for your
help.
> ? From: Mike Krebs <[24][37]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[25][38]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 2:28 PM
> Subject: RE: receive Dynamic XML
>
> Sounds like you are on the right track.
> If you have problems writing INCOMING, share some XML and there are
a
> bunch of us that can help out. But with multiple data elements, you
> will have to use some global variables or data structures to keep
track
> of the results.
> -----Original Message-----
> From: [26][39]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[27][40]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Donnie
> Barrow
> Sent: Thursday, November 6, 2014 11:57 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: receive Dynamic XML
> Thank you for you response?Here is what I am doing. I getting item
> info/availability from a webservice. since it will involve multiple
> warehouses the xml will return lists aka arrays of warehouse item
> availability.[UGHHH] ?So I took?a bit of EXAMPLE16 &?EXAMPLE17 and
used
> it since it was parsing the return data. In my case it will be a
huge
> chunk of data to parse especially with the arrays....SO I didn't
want
> to write it to the IFS [like in EXAMPLE17] but rather parse send the
> data back into the program parms.
> ? ? ? From: Mike Krebs <[28][41]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[29][42]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 12:15 PM
> Subject: RE: receive Dynamic XML
> ?
> I think http_url_post_xml allows you to work with the returned data
> directly. EXAMPLE16 is showing this by calling INCOMING for each
> element in the returned xml.
> -----Original Message-----
> From: [30][43]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[31][44]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Scott
> Mildenberger
> Sent: Thursday, November 6, 2014 10:29 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: RE: receive Dynamic XML
> I have used both the _raw and _xml procedures for either
> http_url_get/post depending on what you are using, they allow you to
> specify a procedure that gets called when data is received.? They
are
> used in some of the provided examples if you search for them.
> Scott
> -----Original Message-----
> From: [32][45]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[33][46]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Donnie
> Barrow
> Sent: Wednesday, November 05, 2014 4:59 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: receive Dynamic XML
> ?i need some guidanceMy rpgle free program is calling a webservice.
I
> used Scott Klement's example17?but I do not want to write the
response
> soap to the IFS. Is there anyway to receiveand parse?the response
xml
> in the program without writing to the IFS Donovan BarrowDBarrow
> Consulting
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [34][47]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [35][48]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
> ?
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [36][49]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
----------------------------------------------------------------------
> -
>
> -------------- next part --------------
> I am using data structures. the challenge for me will be to keep
> track
> of the array elements in the list as I can receive multiple
> warehouses.
> Gonna watch the program run in debug to see how it plays out and
then
> yell for help afterwards LOL.....so stay tuned! thanks for your
> help.
>
__________________________________________________________________
> From: Mike Krebs <[37][50]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[38][51]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 2:28 PM
> Subject: RE: receive Dynamic XML
> Sounds like you are on the right track.
> If you have problems writing INCOMING, share some XML and there
are a
> bunch of us that can help out. But with multiple data elements,
you
> will have to use some global variables or data structures to keep
> track
> of the results.
> -----Original Message-----
> From: [1][39][52]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[2][40][53]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
Behalf Of
> Donnie
> Barrow
> Sent: Thursday, November 6, 2014 11:57 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: receive Dynamic XML
> Thank you for you response Here is what I am doing. I getting item
> info/availability from a webservice. since it will involve
multiple
> warehouses the xml will return lists aka arrays of warehouse item
> availability.[UGHHH] So I took a bit of EXAMPLE16 & EXAMPLE17 and
> used
> it since it was parsing the return data. In my case it will be a
huge
> chunk of data to parse especially with the arrays....SO I didn't
want
> to write it to the IFS [like in EXAMPLE17] but rather parse send
the
> data back into the program parms.
> From: Mike Krebs <[3][41][54]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
> <[4][42][55]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 12:15 PM
> Subject: RE: receive Dynamic XML
> I think http_url_post_xml allows you to work with the returned
data
> directly. EXAMPLE16 is showing this by calling INCOMING for each
> element in the returned xml.
> -----Original Message-----
> From: [5][43][56]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[6][44][57]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
Behalf Of
> Scott
> Mildenberger
> Sent: Thursday, November 6, 2014 10:29 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: RE: receive Dynamic XML
> I have used both the _raw and _xml procedures for either
> http_url_get/post depending on what you are using, they allow you
to
> specify a procedure that gets called when data is received. They
are
> used in some of the provided examples if you search for them.
> Scott
> -----Original Message-----
> From: [7][45][58]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[8][46][59]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
Behalf Of
> Donnie
> Barrow
> Sent: Wednesday, November 05, 2014 4:59 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: receive Dynamic XML
> i need some guidanceMy rpgle free program is calling a
webservice.
> I
> used Scott Klement's example17 but I do not want to write the
> response
> soap to the IFS. Is there anyway to receiveand parse the response
xml
> in the program without writing to the IFS Donovan BarrowDBarrow
> Consulting
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [9][47][60]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
>
----------------------------------------------------------------------
> -
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [10][48][61]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
>
----------------------------------------------------------------------
> -
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [11][49][62]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
-----------------------------------------------------------------------
> References
> 1. mailto:[50][63]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 2. mailto:[51][64]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 3. mailto:[52][65]mkrebs@xxxxxxxxxxxxxxxxxx
> 4. mailto:[53][66]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 5. mailto:[54][67]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 6. mailto:[55][68]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 7. mailto:[56][69]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 8. mailto:[57][70]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 9. [58][71]http://www.scottklement.com/mailman/listinfo/ftpapi
> 10. [59][72]http://www.scottklement.com/mailman/listinfo/ftpapi
> 11. [60][73]http://www.scottklement.com/mailman/listinfo/ftpapi
> ------------------------------
> Message: 4
> Date: Thu, 6 Nov 2014 11:42:35 -0800
> From: raJerry Birch <[61][74]jerry.birch@xxxxxxx>
> To: "[62][75]ftpapi@xxxxxxxxxxxxxxxxxxxxxx"
> <[63][76]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Debugging TESTMIRIN
> Message-ID:
>
<[64][77]1415302955.20532.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
> I am new to FTPAPI and I'm trying to use the TESTMIRIN program to
get
> all the files from an FTP server directory to a specific IFS
directory
> on an i system. Is there a way to step through the recursive call of
> the do_dir subprocedure with debug to see what is happening or can
you
> only examine FTP return codes to try to see what is happening?
> Best Regards,
> Jerry L. Birch
> -------------- next part --------------
> I am new to FTPAPI and I'm trying to use the TESTMIRIN program to
get
> all the files from an FTP server directory to a specific IFS
> directory
> on an i system. Is there a way to step through the recursive call
of
> the do_dir subprocedure with debug to see what is happening or can
> you
> only examine FTP return codes to try to see what is happening?
> Best Regards,
> Jerry L. Birch
> ------------------------------
> Message: 5
> Date: Thu, 06 Nov 2014 14:54:14 -0600
> From: Scott Klement <[65][78]sk@xxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[66][79]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: Debugging TESTMIRIN
> Message-ID: <[67][80]545BDFF6.1060207@xxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Jerry,
> FTPAPI is just a service program that you call from your own RPG
> programs. Likewise, TESTMIRIN, is just a regular RPG program
compiled
> with the normal RPG compiler from IBM.
> You can debug it the same way you'd debug anything else.
> Is that what you're asking?
>> On 11/6/2014 1:42 PM, raJerry Birch wrote:
>> I am new to FTPAPI and I'm trying to use the TESTMIRIN program to
> get
>> all the files from an FTP server directory to a specific IFS
> directory
>> on an i system. Is there a way to step through the recursive call
> of
>> the do_dir subprocedure with debug to see what is happening or can
> you
>> only examine FTP return codes to try to see what is happening?
>> Best Regards,
>> Jerry L. Birch
> ------------------------------
> Message: 6
> Date: Fri, 7 Nov 2014 15:06:19 +0000 (UTC)
> From: Donnie Barrow <[68][81]ddbarrow@xxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[69][82]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: receive Dynamic XML
> Message-ID:
>
>
<[70][83]2112098020.294575.1415372779589.JavaMail.yahoo@xxxxxxxxxxxxxx.
ne1.
> yahoo.com>
>
> Content-Type: text/plain; charset="utf-8"
> with that example there is only one variable being passed back.rc =
> http_url_post_xml(
>
'[71][84]http://www.webservicex.net/CurrencyConvertor.asmx':%addr(SOAP)
+
> 2 : %len(SOAP) : *NULL : %paddr(Incoming) : %addr(rate)?please give
me
> a suggestion on?how to handle a data structure where I am using an
> external file definition. Would?I incorporate the routine in ex17?
> ? From: Mike Krebs <[72][85]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[73][86]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 2:28 PM
> Subject: RE: receive Dynamic XML
>
> Sounds like you are on the right track.
> If you have problems writing INCOMING, share some XML and there are
a
> bunch of us that can help out. But with multiple data elements, you
> will have to use some global variables or data structures to keep
track
> of the results.
> -----Original Message-----
> From: [74][87]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[75][88]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Donnie
> Barrow
> Sent: Thursday, November 6, 2014 11:57 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: receive Dynamic XML
> Thank you for you response?Here is what I am doing. I getting item
> info/availability from a webservice. since it will involve multiple
> warehouses the xml will return lists aka arrays of warehouse item
> availability.[UGHHH] ?So I took?a bit of EXAMPLE16 &?EXAMPLE17 and
used
> it since it was parsing the return data. In my case it will be a
huge
> chunk of data to parse especially with the arrays....SO I didn't
want
> to write it to the IFS [like in EXAMPLE17] but rather parse send the
> data back into the program parms.
> ? ? ? From: Mike Krebs <[76][89]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[77][90]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 12:15 PM
> Subject: RE: receive Dynamic XML
> ?
> I think http_url_post_xml allows you to work with the returned data
> directly. EXAMPLE16 is showing this by calling INCOMING for each
> element in the returned xml.
> -----Original Message-----
> From: [78][91]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[79][92]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Scott
> Mildenberger
> Sent: Thursday, November 6, 2014 10:29 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: RE: receive Dynamic XML
> I have used both the _raw and _xml procedures for either
> http_url_get/post depending on what you are using, they allow you to
> specify a procedure that gets called when data is received.? They
are
> used in some of the provided examples if you search for them.
> Scott
> -----Original Message-----
> From: [80][93]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[81][94]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
Donnie
> Barrow
> Sent: Wednesday, November 05, 2014 4:59 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: receive Dynamic XML
> ?i need some guidanceMy rpgle free program is calling a webservice.
I
> used Scott Klement's example17?but I do not want to write the
response
> soap to the IFS. Is there anyway to receiveand parse?the response
xml
> in the program without writing to the IFS Donovan BarrowDBarrow
> Consulting
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [82][95]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [83][96]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
> ?
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [84][97]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
----------------------------------------------------------------------
> -
>
> -------------- next part --------------
> with that example there is only one variable being passed back.
> rc = http_url_post_xml(
> '[85][98]http://www.webservicex.net/CurrencyConvertor.asmx'
> : %addr(SOAP) + 2
> : %len(SOAP)
> : *NULL
> : %paddr(Incoming)
> : %addr(rate)
> please give me a suggestion on how to handle a data structure
where I
> am using an external file definition. Would I incorporate the
routine
> in ex17?
>
__________________________________________________________________
> From: Mike Krebs <[86][99]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
<[87][100]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 2:28 PM
> Subject: RE: receive Dynamic XML
> Sounds like you are on the right track.
> If you have problems writing INCOMING, share some XML and there
are a
> bunch of us that can help out. But with multiple data elements,
you
> will have to use some global variables or data structures to keep
> track
> of the results.
> -----Original Message-----
> From: [1][88][101]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[2][89][102]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
Behalf Of
> Donnie
> Barrow
> Sent: Thursday, November 6, 2014 11:57 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: receive Dynamic XML
> Thank you for you response Here is what I am doing. I getting item
> info/availability from a webservice. since it will involve
multiple
> warehouses the xml will return lists aka arrays of warehouse item
> availability.[UGHHH] So I took a bit of EXAMPLE16 & EXAMPLE17 and
> used
> it since it was parsing the return data. In my case it will be a
huge
> chunk of data to parse especially with the arrays....SO I didn't
want
> to write it to the IFS [like in EXAMPLE17] but rather parse send
the
> data back into the program parms.
> From: Mike Krebs <[3][90][103]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
> <[4][91][104]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, November 6, 2014 12:15 PM
> Subject: RE: receive Dynamic XML
> I think http_url_post_xml allows you to work with the returned
data
> directly. EXAMPLE16 is showing this by calling INCOMING for each
> element in the returned xml.
> -----Original Message-----
> From: [5][92][105]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[6][93][106]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
Behalf Of
> Scott
> Mildenberger
> Sent: Thursday, November 6, 2014 10:29 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: RE: receive Dynamic XML
> I have used both the _raw and _xml procedures for either
> http_url_get/post depending on what you are using, they allow you
to
> specify a procedure that gets called when data is received. They
are
> used in some of the provided examples if you search for them.
> Scott
> -----Original Message-----
> From: [7][94][107]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[8][95][108]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
Behalf Of
> Donnie
> Barrow
> Sent: Wednesday, November 05, 2014 4:59 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: receive Dynamic XML
> i need some guidanceMy rpgle free program is calling a
webservice.
> I
> used Scott Klement's example17 but I do not want to write the
> response
> soap to the IFS. Is there anyway to receiveand parse the response
xml
> in the program without writing to the IFS Donovan BarrowDBarrow
> Consulting
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [9][96][109]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
>
----------------------------------------------------------------------
> -
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [10][97][110]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
>
----------------------------------------------------------------------
> -
>
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [11][98][111]http://www.scottklement.com/mailman/listinfo/ftpapi
>
>
-----------------------------------------------------------------------
> References
> 1. mailto:[99][112]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 2. mailto:[100][113]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 3. mailto:[101][114]mkrebs@xxxxxxxxxxxxxxxxxx
> 4. mailto:[102][115]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 5. mailto:[103][116]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 6. mailto:[104][117]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 7. mailto:[105][118]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 8. mailto:[106][119]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 9. [107][120]http://www.scottklement.com/mailman/listinfo/ftpapi
> 10. [108][121]http://www.scottklement.com/mailman/listinfo/ftpapi
> 11. [109][122]http://www.scottklement.com/mailman/listinfo/ftpapi
> ------------------------------
>
-----------------------------------------------------------------------
> This is the FTPAPI mailing list digest. To unsubscribe, go to:
> [110][123]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
> End of Ftpapi Digest, Vol 97, Issue 3
> *************************************
>
> References
>
> 1. mailto:[124]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 2. [125]http://scottklement.com/mailman/listinfo/ftpapi
> 3. mailto:[126]ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
> 4. mailto:[127]ftpapi-owner@xxxxxxxxxxxxxxxxxxxxxx
> 5. mailto:[128]sk@xxxxxxxxxxxxxxxx
> 6. mailto:[129]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 7. mailto:[130]545BC968.7010509@xxxxxxxxxxxxxxxx
> 8. mailto:[131]mkrebs@xxxxxxxxxxxxxxxxxx
> 9. mailto:[132]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 10.
mailto:[133]3DF08BA25872B644A1421B9F085B1829A0E5D9D035@xxxxxxxxxxxx
> 11. mailto:[134]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 12. mailto:[135]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 13. mailto:[136]mkrebs@xxxxxxxxxxxxxxxxxx
> 14. mailto:[137]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 15. mailto:[138]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 16. mailto:[139]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 17. mailto:[140]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 18. mailto:[141]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 19. [142]http://www.scottklement.com/mailman/listinfo/ftpapi
> 20. [143]http://www.scottklement.com/mailman/listinfo/ftpapi
> 21. mailto:[144]ddbarrow@xxxxxxxxx
> 22. mailto:[145]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 23.
>
mailto:[146]1243368863.178054.1415302883258.JavaMail.yahoo@xxxxxxxxxxxx
il.n
> e1.yahoo.com
> 24. mailto:[147]mkrebs@xxxxxxxxxxxxxxxxxx
> 25. mailto:[148]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 26. mailto:[149]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 27. mailto:[150]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 28. mailto:[151]mkrebs@xxxxxxxxxxxxxxxxxx
> 29. mailto:[152]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 30. mailto:[153]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 31. mailto:[154]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 32. mailto:[155]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 33. mailto:[156]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 34. [157]http://www.scottklement.com/mailman/listinfo/ftpapi
> 35. [158]http://www.scottklement.com/mailman/listinfo/ftpapi
> 36. [159]http://www.scottklement.com/mailman/listinfo/ftpapi
> 37. mailto:[160]mkrebs@xxxxxxxxxxxxxxxxxx
> 38. mailto:[161]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 39. mailto:[162]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 40. mailto:[163]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 41. mailto:[164]mkrebs@xxxxxxxxxxxxxxxxxx
> 42. mailto:[165]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 43. mailto:[166]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 44. mailto:[167]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 45. mailto:[168]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 46. mailto:[169]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 47. [170]http://www.scottklement.com/mailman/listinfo/ftpapi
> 48. [171]http://www.scottklement.com/mailman/listinfo/ftpapi
> 49. [172]http://www.scottklement.com/mailman/listinfo/ftpapi
> 50. mailto:[173]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 51. mailto:[174]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 52. mailto:[175]mkrebs@xxxxxxxxxxxxxxxxxx
> 53. mailto:[176]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 54. mailto:[177]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 55. mailto:[178]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 56. mailto:[179]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 57. mailto:[180]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 58. [181]http://www.scottklement.com/mailman/listinfo/ftpapi
> 59. [182]http://www.scottklement.com/mailman/listinfo/ftpapi
> 60. [183]http://www.scottklement.com/mailman/listinfo/ftpapi
> 61. mailto:[184]jerry.birch@xxxxxxx
> 62. mailto:[185]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 63. mailto:[186]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 64.
mailto:[187]1415302955.20532.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 65. mailto:[188]sk@xxxxxxxxxxxxxxxx
> 66. mailto:[189]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 67. mailto:[190]545BDFF6.1060207@xxxxxxxxxxxxxxxx
> 68. mailto:[191]ddbarrow@xxxxxxxxx
> 69. mailto:[192]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 70.
>
mailto:[193]2112098020.294575.1415372779589.JavaMail.yahoo@xxxxxxxxxxxx
il.n
> e1.yahoo.com 71.
[194]http://www.webservicex.net/CurrencyConvertor.asmx'
> 72. mailto:[195]mkrebs@xxxxxxxxxxxxxxxxxx
> 73. mailto:[196]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 74. mailto:[197]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 75. mailto:[198]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 76. mailto:[199]mkrebs@xxxxxxxxxxxxxxxxxx
> 77. mailto:[200]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 78. mailto:[201]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 79. mailto:[202]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 80. mailto:[203]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 81. mailto:[204]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 82. [205]http://www.scottklement.com/mailman/listinfo/ftpapi
> 83. [206]http://www.scottklement.com/mailman/listinfo/ftpapi
> 84. [207]http://www.scottklement.com/mailman/listinfo/ftpapi
> 85. [208]http://www.webservicex.net/CurrencyConvertor.asmx'
> 86. mailto:[209]mkrebs@xxxxxxxxxxxxxxxxxx
> 87. mailto:[210]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 88. mailto:[211]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 89. mailto:[212]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 90. mailto:[213]mkrebs@xxxxxxxxxxxxxxxxxx
> 91. mailto:[214]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 92. mailto:[215]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 93. mailto:[216]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 94. mailto:[217]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 95. mailto:[218]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 96. [219]http://www.scottklement.com/mailman/listinfo/ftpapi
> 97. [220]http://www.scottklement.com/mailman/listinfo/ftpapi
> 98. [221]http://www.scottklement.com/mailman/listinfo/ftpapi
> 99. mailto:[222]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 100. mailto:[223]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 101. mailto:[224]mkrebs@xxxxxxxxxxxxxxxxxx
> 102. mailto:[225]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 103. mailto:[226]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 104. mailto:[227]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 105. mailto:[228]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 106. mailto:[229]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 107. [230]http://www.scottklement.com/mailman/listinfo/ftpapi
> 108. [231]http://www.scottklement.com/mailman/listinfo/ftpapi
> 109. [232]http://www.scottklement.com/mailman/listinfo/ftpapi
> 110. [233]http://www.scottklement.com/mailman/listinfo/ftpapi
>
----------------------------------------------------------------------
> - This is the FTPAPI mailing list. To unsubscribe, please go to:
> [234]http://www.scottklement.com/mailman/listinfo/ftpapi
>
----------------------------------------------------------------------
> -
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[235]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list digest. To unsubscribe, go to:
[236]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
End of Ftpapi Digest, Vol 97, Issue 6
*************************************
References
1. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
2. http://scottklement.com/mailman/listinfo/ftpapi
3. mailto:ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
4. mailto:ftpapi-owner@xxxxxxxxxxxxxxxxxxxxxx
5. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
6. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
7. mailto:3DF08BA25872B644A1421B9F085B1829A0E5D9D192@xxxxxxxxxxxx
8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
9. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
10. mailto:jerry.birch@xxxxxxx
11. mailto:ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
12. mailto:ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
13. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
14. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
15. http://scottklement.com/mailman/listinfo/ftpapi
16. mailto:ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
17. mailto:ftpapi-owner@xxxxxxxxxxxxxxxxxxxxxx
18. mailto:sk@xxxxxxxxxxxxxxxx
19. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
20. mailto:545BC968.7010509@xxxxxxxxxxxxxxxx
21. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
22. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
23. mailto:3DF08BA25872B644A1421B9F085B1829A0E5D9D035@xxxxxxxxxxxx
24. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
25. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
26. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
27. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
28. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
29. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
30. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
31. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
32. http://www.scottklement.com/mailman/listinfo/ftpapi
33. http://www.scottklement.com/mailman/listinfo/ftpapi
34. mailto:ddbarrow@xxxxxxxxx
35. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
36. mailto:1243368863.178054.1415302883258.JavaMail.yahoo@xxxxxxxxxxxxxx.ne1.
37. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
38. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
39. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
40. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
41. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
42. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
43. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
44. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
45. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
46. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
47. http://www.scottklement.com/mailman/listinfo/ftpapi
48. http://www.scottklement.com/mailman/listinfo/ftpapi
49. http://www.scottklement.com/mailman/listinfo/ftpapi
50. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
51. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
52. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
53. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
54. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
55. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
56. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
57. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
58. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
59. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
60. http://www.scottklement.com/mailman/listinfo/ftpapi
61. http://www.scottklement.com/mailman/listinfo/ftpapi
62. http://www.scottklement.com/mailman/listinfo/ftpapi
63. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
64. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
65. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
66. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
67. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
68. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
69. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
70. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
71. http://www.scottklement.com/mailman/listinfo/ftpapi
72. http://www.scottklement.com/mailman/listinfo/ftpapi
73. http://www.scottklement.com/mailman/listinfo/ftpapi
74. mailto:jerry.birch@xxxxxxx
75. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
76. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
77. mailto:1415302955.20532.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
78. mailto:sk@xxxxxxxxxxxxxxxx
79. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
80. mailto:545BDFF6.1060207@xxxxxxxxxxxxxxxx
81. mailto:ddbarrow@xxxxxxxxx
82. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
83. mailto:2112098020.294575.1415372779589.JavaMail.yahoo@xxxxxxxxxxxxxx.ne1.
84. http://www.webservicex.net/CurrencyConvertor.asmx':
85. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
86. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
87. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
88. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
89. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
90. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
91. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
92. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
93. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
94. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
95. http://www.scottklement.com/mailman/listinfo/ftpapi
96. http://www.scottklement.com/mailman/listinfo/ftpapi
97. http://www.scottklement.com/mailman/listinfo/ftpapi
98. http://www.webservicex.net/CurrencyConvertor.asmx'
99. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
100. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
101. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
102. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
103. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
104. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
105. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
106. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
107. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
108. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
109. http://www.scottklement.com/mailman/listinfo/ftpapi
110. http://www.scottklement.com/mailman/listinfo/ftpapi
111. http://www.scottklement.com/mailman/listinfo/ftpapi
112. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
113. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
114. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
115. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
116. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
117. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
118. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
119. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
120. http://www.scottklement.com/mailman/listinfo/ftpapi
121. http://www.scottklement.com/mailman/listinfo/ftpapi
122. http://www.scottklement.com/mailman/listinfo/ftpapi
123. http://www.scottklement.com/mailman/listinfo/ftpapi
124. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
125. http://scottklement.com/mailman/listinfo/ftpapi
126. mailto:ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
127. mailto:ftpapi-owner@xxxxxxxxxxxxxxxxxxxxxx
128. mailto:sk@xxxxxxxxxxxxxxxx
129. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
130. mailto:545BC968.7010509@xxxxxxxxxxxxxxxx
131. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
132. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
133. mailto:3DF08BA25872B644A1421B9F085B1829A0E5D9D035@xxxxxxxxxxxx
134. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
135. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
136. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
137. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
138. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
139. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
140. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
141. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
142. http://www.scottklement.com/mailman/listinfo/ftpapi
143. http://www.scottklement.com/mailman/listinfo/ftpapi
144. mailto:ddbarrow@xxxxxxxxx
145. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
146. mailto:1243368863.178054.1415302883258.JavaMail.yahoo@xxxxxxxxxxxxxx.n
147. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
148. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
149. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
150. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
151. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
152. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
153. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
154. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
155. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
156. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
157. http://www.scottklement.com/mailman/listinfo/ftpapi
158. http://www.scottklement.com/mailman/listinfo/ftpapi
159. http://www.scottklement.com/mailman/listinfo/ftpapi
160. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
161. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
162. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
163. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
164. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
165. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
166. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
167. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
168. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
169. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
170. http://www.scottklement.com/mailman/listinfo/ftpapi
171. http://www.scottklement.com/mailman/listinfo/ftpapi
172. http://www.scottklement.com/mailman/listinfo/ftpapi
173. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
174. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
175. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
176. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
177. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
178. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
179. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
180. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
181. http://www.scottklement.com/mailman/listinfo/ftpapi
182. http://www.scottklement.com/mailman/listinfo/ftpapi
183. http://www.scottklement.com/mailman/listinfo/ftpapi
184. mailto:jerry.birch@xxxxxxx
185. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
186. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
187. mailto:1415302955.20532.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
188. mailto:sk@xxxxxxxxxxxxxxxx
189. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
190. mailto:545BDFF6.1060207@xxxxxxxxxxxxxxxx
191. mailto:ddbarrow@xxxxxxxxx
192. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
193. mailto:2112098020.294575.1415372779589.JavaMail.yahoo@xxxxxxxxxxxxxx.n
194. http://www.webservicex.net/CurrencyConvertor.asmx'
195. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
196. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
197. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
198. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
199. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
200. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
201. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
202. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
203. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
204. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
205. http://www.scottklement.com/mailman/listinfo/ftpapi
206. http://www.scottklement.com/mailman/listinfo/ftpapi
207. http://www.scottklement.com/mailman/listinfo/ftpapi
208. http://www.webservicex.net/CurrencyConvertor.asmx'
209. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
210. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
211. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
212. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
213. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
214. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
215. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
216. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
217. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
218. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
219. http://www.scottklement.com/mailman/listinfo/ftpapi
220. http://www.scottklement.com/mailman/listinfo/ftpapi
221. http://www.scottklement.com/mailman/listinfo/ftpapi
222. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
223. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
224. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
225. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
226. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
227. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
228. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
229. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
230. http://www.scottklement.com/mailman/listinfo/ftpapi
231. http://www.scottklement.com/mailman/listinfo/ftpapi
232. http://www.scottklement.com/mailman/listinfo/ftpapi
233. http://www.scottklement.com/mailman/listinfo/ftpapi
234. http://www.scottklement.com/mailman/listinfo/ftpapi
235. http://www.scottklement.com/mailman/listinfo/ftpapi
236. 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
-----------------------------------------------------------------------