Re: One HTTP Instance started failing today

[Brad Stone <bvstone@xxxxxxxxx>]

Seems internal...  I'd contact IBM.  That's weird for sure.

I had some HTTP server instances just fail a couple months ago as well out
of the blue.  I tracked it down to the SSL application name and how I
didn't have it the same case.  It ran for years that way and one day
decided to stop.

On Tue, Jun 2, 2020 at 8:56 AM Art Tostaine, Jr. <atostaine@xxxxxxxxx>
wrote:

> This happened last night. No PTF's or anything changed that we are aware
> of. Google hasn't turned up much, getting ready to submit to IBM
>
> Message ID . . . . . . :   HTP8082       Severity . . . . . . . :   30
>
> Message type . . . . . :   Information
>
> Date sent  . . . . . . :   06/02/20      Time sent  . . . . . . :
> 08:31:39
>
>
> Message . . . . :   HTTP Server instance DC@PGMLIB job
>
>   080494/QTMHHTTP/DC@PGMLIB failed.
>
> Cause . . . . . :   There are one or more jobs associated with the server
>
>   instance DC@PGMLIB. One of the HTTP server instance DC@PGMLIB jobs
> failed.
>   If there are other server jobs active for instance DC@PGMLIB, they will
>
>   continue processing requests and another job is also created
> automatically
>   to replace the failed job. See the job log for 080494/QTMHHTTP/DC@PGMLIB
> for
>   more information.
>
> Recovery  . . . :   Receipt of this message usually indicates there is a
>
>   problem that needs to be resolved. Correct the problem identified in the
> job
>   log for 080494/QTMHHTTP/DC@PGMLIB.
>
> This error appears in the joblog,
>
> CPF1892    Escape                  40   06/01/20  23:00:06.335272  QDMDSPOV
>     QSYS        1912     QWCCDSJC    QSYS        05A7
>                                      Message . . . . :   Function DSPOVR
> not allowed.
>              Cause . . . . . :   Function DSPOVR is not allowed in a job
> which is capable                          of running with multiple
> threads.
>
> And this:
>
> CPF24A3    Escape                  40   06/01/20  23:00:06.345650  QMHSNDPM
>     QSYS        0C9E     QLEAWI      QSYS        *S
>                                      To module . . . . . . . . . :   QLEDEH
>
>                                      To procedure  . . . . . . . :   Q LE
> leDefaultEh2
>                                      Statement . . . . . . . . . :   175
>
>                                      Message . . . . :   Value for call
> stack counter parameter not valid.
>                                      Cause . . . . . :   The value 3,
> specified for call stack counter parameter,
>                                        is not valid. The value was
> specified in parameter number 7 on the API.
>                                        Recovery  . . . :   Correct the
> value for call stack counter parameter and
>
> any help appreciated.
>
> --
> Art Tostaine
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com