[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
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 <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: "ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx"
> <ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx>
> To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Sent: Friday, November 7, 2014 10:09 AM
> Subject: Ftpapi Digest, Vol 97, Issue 3
> 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: 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]sk@xxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[6]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: Longer Character Parameter
> Message-ID: <[7]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[9]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: RE: receive Dynamic XML
> Message-ID:
> <[10]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[12]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[14]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[16]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[18]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]http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [20]http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>
> ------------------------------
> Message: 3
> Date: Thu, 6 Nov 2014 19:41:23 +0000 (UTC)
> From: Donnie Barrow <[21]ddbarrow@xxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[22]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: receive Dynamic XML
> Message-ID:
>
> <[23]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[25]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[27]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[29]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[31]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[33]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]http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [35]http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
> ?
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [36]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[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: [1][39]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[2][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 <[3][41]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
> <[4][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: [5][43]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[6][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: [7][45]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[8][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:
> [9][47]http://www.scottklement.com/mailman/listinfo/ftpapi
>
> -----------------------------------------------------------------------
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [10][48]http://www.scottklement.com/mailman/listinfo/ftpapi
>
> -----------------------------------------------------------------------
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [11][49]http://www.scottklement.com/mailman/listinfo/ftpapi
>
> -----------------------------------------------------------------------
> References
> 1. mailto:[50]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 2. mailto:[51]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 3. mailto:[52]mkrebs@xxxxxxxxxxxxxxxxxx
> 4. mailto:[53]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 5. mailto:[54]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 6. mailto:[55]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 7. mailto:[56]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 8. mailto:[57]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 9. [58]http://www.scottklement.com/mailman/listinfo/ftpapi
> 10. [59]http://www.scottklement.com/mailman/listinfo/ftpapi
> 11. [60]http://www.scottklement.com/mailman/listinfo/ftpapi
> ------------------------------
> Message: 4
> Date: Thu, 6 Nov 2014 11:42:35 -0800
> From: raJerry Birch <[61]jerry.birch@xxxxxxx>
> To: "[62]ftpapi@xxxxxxxxxxxxxxxxxxxxxx"
> <[63]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Debugging TESTMIRIN
> Message-ID:
> <[64]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]sk@xxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[66]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: Debugging TESTMIRIN
> Message-ID: <[67]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]ddbarrow@xxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[69]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: receive Dynamic XML
> Message-ID:
>
> <[70]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]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[73]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[75]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[77]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[79]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[81]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]http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [83]http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
> ?
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.? To unsubscribe, please go to:
> [84]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]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects <[87]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[2][89]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]mkrebs@xxxxxxxxxxxxxxxxxx>
> To: HTTPAPI and FTPAPI Projects
> <[4][91]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[6][93]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]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:[8][95]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]http://www.scottklement.com/mailman/listinfo/ftpapi
>
> -----------------------------------------------------------------------
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [10][97]http://www.scottklement.com/mailman/listinfo/ftpapi
>
> -----------------------------------------------------------------------
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [11][98]http://www.scottklement.com/mailman/listinfo/ftpapi
>
> -----------------------------------------------------------------------
> References
> 1. mailto:[99]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 2. mailto:[100]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 3. mailto:[101]mkrebs@xxxxxxxxxxxxxxxxxx
> 4. mailto:[102]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 5. mailto:[103]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 6. mailto:[104]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 7. mailto:[105]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 8. mailto:[106]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 9. [107]http://www.scottklement.com/mailman/listinfo/ftpapi
> 10. [108]http://www.scottklement.com/mailman/listinfo/ftpapi
> 11. [109]http://www.scottklement.com/mailman/listinfo/ftpapi
> ------------------------------
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list digest. To unsubscribe, go to:
> [110]http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
> End of Ftpapi Digest, Vol 97, Issue 3
> *************************************
>
> References
>
> 1. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 2. http://scottklement.com/mailman/listinfo/ftpapi
> 3. mailto:ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
> 4. mailto:ftpapi-owner@xxxxxxxxxxxxxxxxxxxxxx
> 5. mailto:sk@xxxxxxxxxxxxxxxx
> 6. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 7. mailto:545BC968.7010509@xxxxxxxxxxxxxxxx
> 8. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 9. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 10. mailto:3DF08BA25872B644A1421B9F085B1829A0E5D9D035@xxxxxxxxxxxx
> 11. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 12. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 13. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 14. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 15. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 16. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 17. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 18. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 19. http://www.scottklement.com/mailman/listinfo/ftpapi
> 20. http://www.scottklement.com/mailman/listinfo/ftpapi
> 21. mailto:ddbarrow@xxxxxxxxx
> 22. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 23. mailto:1243368863.178054.1415302883258.JavaMail.yahoo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 24. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 25. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 26. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 27. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 28. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 29. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 30. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 31. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 32. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 33. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 34. http://www.scottklement.com/mailman/listinfo/ftpapi
> 35. http://www.scottklement.com/mailman/listinfo/ftpapi
> 36. http://www.scottklement.com/mailman/listinfo/ftpapi
> 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:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 51. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 52. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 53. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 54. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 55. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 56. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 57. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 58. http://www.scottklement.com/mailman/listinfo/ftpapi
> 59. http://www.scottklement.com/mailman/listinfo/ftpapi
> 60. http://www.scottklement.com/mailman/listinfo/ftpapi
> 61. mailto:jerry.birch@xxxxxxx
> 62. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 63. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 64. mailto:1415302955.20532.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 65. mailto:sk@xxxxxxxxxxxxxxxx
> 66. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 67. mailto:545BDFF6.1060207@xxxxxxxxxxxxxxxx
> 68. mailto:ddbarrow@xxxxxxxxx
> 69. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 70. mailto:2112098020.294575.1415372779589.JavaMail.yahoo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 71. http://www.webservicex.net/CurrencyConvertor.asmx'
> 72. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 73. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 74. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 75. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 76. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 77. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 78. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 79. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 80. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 81. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 82. http://www.scottklement.com/mailman/listinfo/ftpapi
> 83. http://www.scottklement.com/mailman/listinfo/ftpapi
> 84. http://www.scottklement.com/mailman/listinfo/ftpapi
> 85. http://www.webservicex.net/CurrencyConvertor.asmx'
> 86. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 87. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 88. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 89. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 90. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 91. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 92. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 93. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 94. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 95. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 96. http://www.scottklement.com/mailman/listinfo/ftpapi
> 97. http://www.scottklement.com/mailman/listinfo/ftpapi
> 98. http://www.scottklement.com/mailman/listinfo/ftpapi
> 99. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 100. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 101. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
> 102. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> 103. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 104. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 105. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 106. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> 107. http://www.scottklement.com/mailman/listinfo/ftpapi
> 108. http://www.scottklement.com/mailman/listinfo/ftpapi
> 109. http://www.scottklement.com/mailman/listinfo/ftpapi
> 110. 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
> -----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------