[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: %scan() fails working in http_long_ParseUrl() (Thomas Raddatz)
Ed and I could not yet really figure out what the problem was. At least
there were a couple of different issues such as broken pipe errors and
blank URLs. However I could successfully call the web service from our
System i after having enabled SSL.
Hence there should not be any problems neither with HTTPAPI nor with WSDL2RPG.
Thomas.
Am 04.10.2011 19:09, schrieb EWaldschmidt@xxxxxxxxxxxxxxxxxxxxx:
>
> I did debug the program and on the third time the URL was blank.
> Plus the return code was -1 on the second iteration of the loop.
> Ed Waldschmidt, MBA
> Sr. Programmer/Analyst
> Brotherhood Mutual Insurance Company
> 260-481-5361
> ewaldschmidt@xxxxxxxxxxxxxxxxxxxxx
> From: ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
> To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Date: 10/04/2011 01:04 PM
> Subject: Ftpapi Digest, Vol 64, Issue 6
> Sent by: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> _________________________________________________________________
>
> Send Ftpapi mailing list submissions to
> ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> To subscribe or unsubscribe via the World Wide Web, visit
> [1]http://www.scottklement.com/mailman/listinfo/ftpapi
> or, via email, send a message with subject or body 'help' to
> ftpapi-request@xxxxxxxxxxxxxxxxxxxxxx
> You can reach the person managing the list at
> 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: %scan() fails working in http_long_ParseUrl() (Thomas
> Raddatz)
> ----------------------------------------------------------------------
> Message: 1
> Date: Tue, 04 Oct 2011 18:45:45 +0200
> From: Thomas Raddatz<thomas.raddatz@xxxxxxxxxxx>
> Subject: Re: %scan() fails working in http_long_ParseUrl()
> To: HTTPAPI and FTPAPI Projects<ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Message-ID:<4E8B3839.6070602@xxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Mike,
> I am not sure whether or not Ed noticed that. But certainly I did not
> notice that HTTPAPI was called three times.
> I wonder how or what did the last call to it. For sure the stub
> program
> called HTTPAPI two times. But I do expect that it called HTTPAPI three
> times. The first time it received the 302 error and the second time it
> received the SOAP error message. So actually that call finished
> successfully.
> Meanwhile I invited Ed to the mailing list. I assume that he gets this
> message and joins us. I also discussed with him how to debug the
> problem
> and I am waiting for his response.
> Thomas.
> Am 03.10.2011 23:42, schrieb Mike Krebs:
> > While this shouldn't error out where it did...Did Ed notice this?
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <soap:Envelope
> xmlns:soap="[2]http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="[3]http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="[4]http://www.w3.org/2001/XMLSchema">
> > <soap:Body>
> > <ExecuteOperationResponse
> xmlns="[5]http://www.aplicor.com/">
> > <ExecuteOperationResult><Error Code="4016"
> Details="BMICIntegrationService, invalid User/Password, access to the
> service denied." />
> > </ExecuteOperationResult>
> > </ExecuteOperationResponse>
> > </soap:Body>
> > </soap:Envelope>
> >
> > It might have nothing to do with it, but the service is working and
> returning an error.
> >
> > When they are hitting HTTPAPI for the third time, what url are they
> using?
> >
> >
> >
> >
> ----------------------------------------------------------------------
> -
> > This is the FTPAPI mailing list. To unsubscribe, please go to:
> > [6]http://www.scottklement.com/mailman/listinfo/ftpapi
> >
> ----------------------------------------------------------------------
> -
> >
> ------------------------------
> ----------------------------------------------------------------------
> -
> This is the FTPAPI mailing list digest. To unsubscribe, go to:
> [7]http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
> End of Ftpapi Digest, Vol 64, Issue 6
> *************************************
>
> ------------ IMPORTANT NOTICE ------------
> The information in this e-mail and in any attachments
> is the property of Brotherhood Mutual Insurance Company
> and is confidential. If you are not the intended recipient,
> you should delete this message from your system and
> immediately notify the sender. Unless otherwise indicated by
> Brotherhood Mutual Insurance Company, you may not copy
> or send this e-mail or any attachments to any other person
> nor disclose the contents to others if such action conveys
> confidential information to our competitors or is in any other
> way reasonably likely to be adverse to the interests of
> Brotherhood Mutual Insurance Company. This e-mail will
> not modify any insurance policy term or provision, nor will
> it evidence an intent to be bound by or to modify any
> contract or agreement.
>
> References
>
> 1. http://www.scottklement.com/mailman/listinfo/ftpapi
> 2. http://schemas.xmlsoap.org/soap/envelope/
> 3. http://www.w3.org/2001/XMLSchema-instance
> 4. http://www.w3.org/2001/XMLSchema
> 5. http://www.aplicor.com/
> 6. http://www.scottklement.com/mailman/listinfo/ftpapi
> 7. 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
-----------------------------------------------------------------------