RE: Http_comp issue

[Walker Powell <Walker.Powell@xxxxxxxxx>]

Wow!  Thanks for pointing that out to me! I had put the comp message in my test so that I could see returning data. I absolutely forgot I would not need that in production!

Ahh, well, it is really gratifying to have someone with more experience guide the ignorant! I do appreciate it. Without you, and others, I would not have completed this task so quickly.

I've removed the code and all is well.

VBR,

Walker Powell
Pacer International IT
6805 Perimeter Dr.
Dublin, OH 43016
walker.powell@xxxxxxxxx
614.356.1257 office
614.923.1442 fax

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Mon, December 10, 2007 4:59 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Http_comp issue

Hi Walker,

Why on earth would you want to use a completion message in an auto-start job?!  Who would ever see the message?



Walker Powell wrote:
> All - We have been testing a call to a web service for a couple of
> weeks, and things have gone really well, thanks to some suggestions
> from this list.
>
> This past week-end we put the project into production and ran into an
> interesting situation. The program that is making the call is running
> in batch and I had been submitting a start up of the program from the
> job scheduler for testing.
>
> I had planned the production version to be an auto-start job.
> Everything went really good until the first web service call. :-0 Then
> we got the message "Value for call stack counter parameter not valid".
>
> Investigation revealed that the call to http_comp has hard coded a '1'
> in the call stack counter and I needed to send my completion message
> to the message queue of the entry specified by the call stack entry
> parameter, not the previous message queue because there is no previous
> message queue based on the way I set up the routing entry on the
> subsystem.
>
> I didn't want to change libhttp/http_com, so I created another
> procedure and put it outside of libhttp because I wanted to keep the
> lib "standard".
>
> This solved my problem. I realize I could have solved this in a number
> of ways, but I just wanted to let all know in case someone else has
> this issue when using an auto-start job.  I think this is most
> probably a rare case, though.

-----------------------------------------------------------------------
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
-----------------------------------------------------------------------