[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: http_close(): entered
Ahh...I didn't know that would happen in the job log.
On Tue, Mar 10, 2009 at 3:07 PM, Karl Woods
<[1]Karl.Woods@xxxxxxxxxxxxxx> wrote:
Actually, it's HTTP_URL_POST_XML. It just gets truncated in the job
log. GETEODROLL uses the HTTPAPI binding directory, StartOfElement
and EndOfElement procedures.
Karl B. Woods
Sr. Programmer/Analyst
Professional Services
1960 S. Milestone Dr., Ste B
Salt Lake City, UT 84104
S Tel: (801) 433-9426 (office)
( E-mail: karl.woods@xxxxxxxxxxxxxx
LiveSTRONG
....... __o Same Road
....... \<, Same Rules
.... ( )/ ( ) Same Rights
This e-mail contains proprietary information and may be confidential.
If you are not the intended recipient of this e-mail, you are hereby
notified that any dissemination, distribution or copying of this
message is strictly prohibited. If you received this message in error,
please delete it immediately.
-----Original Message-----
From: Michael Ryan [mailto:[2]michaelrtr@xxxxxxxxx]
Sent: Tuesday, March 10, 2009 1:00 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: http_close(): entered
Looks like program GETEODROLL may be using a 10 character variable for
calling a procedure with a longer name. I'll be that's supposed to be
HTTP_URL_POST.
On Tue, Mar 10, 2009 at 1:35 PM, Karl Woods
<[3]Karl.Woods@xxxxxxxxxxxxxx>wrote:
> >From module . . . . . . . . : QRNXMSG
> From procedure . . . . . . : InqMsg
> Statement . . . . . . . . . : 3
> To module . . . . . . . . . : QRNXMSG
> To procedure . . . . . . . : InqMsg
> Statement . . . . . . . . . : 3
> Message . . . . : The call to HTTP_URL_P ended in error (C G D
F).
> Cause . . . . . : RPG procedure GETEODROLL in program
> DTECHEODR1/GETEODROLL
> at statement 2181 called program or procedure HTTP_URL_P, which
ended in
> error. If the name is *N, the call was a bound call by procedure
pointer.
> Recovery . . . : Check the job log for more information on the
cause
> of
> the error and contact the person responsible for program
maintenance.
> Possible choices for replying to message . . . . . . . . . . . . .
. . :
> D
> -- Obtain RPG formatted dump. S -- Obtain system dump. G --
Continue
> processing at *GETIN. C -- Cancel. F -- Obtain full formatted
dump.
>
> Karl B. Woods
> Sr. Programmer/Analyst
> Professional Services
>
> 1960 S. Milestone Dr., Ste B
> Salt Lake City, UT 84104
> S Tel: (801) 433-9426 (office)
> ( E-mail: karl.woods@xxxxxxxxxxxxxx
> LiveSTRONG
> ....... __o Same Road
> ....... \<, Same Rules
> .... ( )/ ( ) Same Rights
>
>
> This e-mail contains proprietary information and may be
confidential.
> If you are not the intended recipient of this e-mail, you are hereby
> notified that any dissemination, distribution or copying of this
> message is strictly prohibited. If you received this message in
error,
> please delete it immediately.
>
>
>
>
> -----Original Message-----
> From: Michael Ryan [mailto:[4]michaelrtr@xxxxxxxxx]
> Sent: Tuesday, March 10, 2009 11:24 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: http_close(): entered
>
> anything in your job log?
>
> On Tue, Mar 10, 2009 at 1:11 PM, Karl Woods
<[5]Karl.Woods@xxxxxxxxxxxxxx
> >wrote:
>
> > Looking at the httpapi_debug log, I noticed that when I have a
> > successful request I see "http_close(): entered" at the end of the
> > log. There are times that "http_close(): entered" is missing from
> > the log and I receive "The call to HTTP_URL_P ended in error"
> > message from
> the program requesting the data.
> > Everything in the logs is the same except for this one line.
> >
> > Can anyone shed some light on this?
> >
> > Karl B. Woods
> > Sr. Programmer/Analyst
> > Professional Services
> >
> > 1960 S. Milestone Dr., Ste B
> > Salt Lake City, UT 84104
> > S Tel: (801) 433-9426 (office)
> > ( E-mail: karl.woods@xxxxxxxxxxxxxx LiveSTRONG ....... __o Same
> > Road
> > ....... \<, Same Rules
> > .... ( )/ ( ) Same Rights
> >
> >
> > This e-mail contains proprietary information and may be
confidential.
> > If you are not the intended recipient of this e-mail, you are
hereby
> > notified that any dissemination, distribution or copying of this
> > message is strictly prohibited. If you received this message in
> > error, please delete it immediately.
> >
> >
> >
--------------------------------------------------------------------
> > --
> > - 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. To unsubscribe, please go to:
> [7]http://www.scottklement.com/mailman/listinfo/ftpapi
>
----------------------------------------------------------------------
> -
>
-------------------------------------------------------------------
----
This is the FTPAPI mailing list. To unsubscribe, please go to:
[8]http://www.scottklement.com/mailman/listinfo/ftpapi
----------------------------------------------------------------------
-
References
1. mailto:Karl.Woods@xxxxxxxxxxxxxx
2. mailto:michaelrtr@xxxxxxxxx
3. mailto:Karl.Woods@xxxxxxxxxxxxxx
4. mailto:michaelrtr@xxxxxxxxx
5. mailto:Karl.Woods@xxxxxxxxxxxxxx
6. http://www.scottklement.com/mailman/listinfo/ftpapi
7. http://www.scottklement.com/mailman/listinfo/ftpapi
8. 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
-----------------------------------------------------------------------