Re: CPF9897 HTTP/1.1 500 Internal Server Error Causes Hard Halt of Program

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

   Hi Laura,
   When you call the network routines in HTTPAPI (the HTTP_post_xxx or
   HTTP_get_xxx routines) they will return a return value that can have
   these values:
   1 = success
   0 = timed out
   -1= error detected inside HTTPPAI
   any number>1 = error/warning/notification reported by HTTP server
   You can then call the http_error() routine to get an error message.
   -or- you can call http_crash() to ask HTTPAPI to send an *ESCAPE
   message with CPF9897.
   To prevent the *ESCAPE message -- simply call http_error() instead of
   http_crash().   You can read the comments in the HTTPAPI_H member to
   see what each of the different API calls do.
   -SK

   On 12/13/2012 7:15 PM, Laura Hamway (PHOENIX) wrote:

   Hi,

   I am receiving CPF9897 HTTP/1.1 500 Internal Server Error,  this is
   mostly happening when incorrect data is sent.  Edits have now been put
   in and should cover 99% of the issues.  What I wanted to know is there
   a way to monitor for this message ?  When this message occurs the
   program that initiates the program with http process crashes and will
   sit in active jobs in MSGW status.  Is there a way to have this error
   not cause a hard halt?


   Thanks,

   Laura Hamway

   757-754-1334

   [1]www.phoenixbcinc.com


-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
[2]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------

References

   1. http://www.phoenixbcinc.com/
   2. 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
-----------------------------------------------------------------------