× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2019

Re: Help With Getting HTTP Server running

Scott, the only way i was able to pull any log info was from the joblog in
QEZJOBLOG... here is what is happening - what do i have misconfigured?

MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
TCP45B8 Information 00 02/14/19 08:26:52.790663 QZSRAPR QHTTPSVR *STMT
QZSRCGI QHTTPSVR *STMT
From module . . . . . . . . : OS400TRACE
From procedure . . . . . . : apr_dump_trace
Statement . . . . . . . . . : 51
To module . . . . . . . . . : ZSRVHJOB
To procedure . . . . . . . : ExceptionHandler_Default
Statement . . . . . . . . . : 29
Message . . . . : Trace data for application *HTTP formatted: QSRV033096.
CEE9901 Escape 30 02/14/19 08:26:52.790773 QLEAWI QSYS *STMT QP0ZPCPN QSYS
*STMT
From user . . . . . . . . . : LSAMSSO
From module . . . . . . . . : QLETOOL
From procedure . . . . . . : Q LE AWIRaise
Statement . . . . . . . . . : 176
To module . . . . . . . . . : QP0ZPCPN
To procedure . . . . . . . : Qp0zNewProcess
Statement . . . . . . . . . : 278
Message . . . . : Application error. *N unmonitored by *N at statement *N,
instruction X'4000'.
Cause . . . . . : The application ended abnormally because an exception
occurred and was not handled. The name of the program to which the
unhandled exception is sent is *N *N . The program was stopped at the
high-level language statement number(s) *N at the time the message was sent.
If more than one statement number is shown, the program is an optimized ILE
program. Optimization does not allow a single statement number to be
determined. If *N is shown as a value, it means the real value was not
available. Recovery . . . : See the low level messages previously listed
to locate the cause of the exception. Correct any errors, and then try the
request again.
CPF24A3 Escape 40 02/14/19 08:26:52.798878 QMHSNDPM QSYS 0C79 QLEAWI QSYS
*STMT
From user . . . . . . . . . : LSAMSSO
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
try the request again. This value must be greater than or equal to 0 but
cannot be larger than the number of entries on the call stack.
CEE9901 Diagnostic 30 02/14/19 08:26:52.798904 QLEAWI QSYS *STMT QP0ZPCP2
QSYS *STMT
From user . . . . . . . . . : LSAMSSO
From module . . . . . . . . : QLETOOL
From procedure . . . . . . : Q LE CPF24A3_handler
Statement . . . . . . . . . : 9
To module . . . . . . . . . : QP0ZPCP2
To procedure . . . . . . . : _CXX_PEP__Fv
Statement . . . . . . . . . : *N
Message . . . . : Application error. CEE9901 unmonitored by QP0ZPCPN at
statement 0000000278, instruction X'0000'.
Cause . . . . . : The application ended abnormally because an exception
occurred and was not handled. The name of the program to which the
unhandled exception is sent is QP0ZPCPN QP0ZPCPN Qp0zNewProcess. The program

On Wed, Feb 13, 2019 at 5:00 PM Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
wrote:

Hi Jay,

I don't see anything in that article that discusses the YAJLCALLR
utility. (In fact, I'm not sure that I ever documented that utility...
but, you're welcome to use it if you like it.)

At any rate, if the program isn't being called, then what is
happening? Are you getting an error? Are there messages in the
/www/your-instance/logs/error_log.xxxxx files related to it?

-SK


On 2/13/2019 2:26 PM, Jay Vaughn wrote:
so had a configuration error - corrected - starts and runs now...

Continuing on this POC, I have deployed YAJL onto our system and also
compiled YAJLCALLR to YAJLREST.

Now I attempt to do the following from the browser, but it does not seem
to
reach our system and invoke YAJLCALLR *pgm.

http://ourSystem:port/rest/YAJLCALLR

Just to be sure I'm progressing down the correct logical path I'd expect
to
see the YAJLCALLR *pgm object with a last used date set - but it is still
blank.

Has anyone else utilized this yet? What am I missing and
misunderstanding?

Thanks

Jay





On Wed, Feb 13, 2019 at 3:14 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

awesome - that pointed me right to the error - now to examine the error
-
PROBABLY more to come... THANKS!

On Wed, Feb 13, 2019 at 3:11 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

1. Check for a joblog (QEZJOBLOG outq if you spool them).
2. Check the log files in the IFS dir for your server (usually
/www/serverNameHere/logs).



-----Original Message-----
From: Jay Vaughn [mailto:jeffersonvaughn@xxxxxxxxx]
Sent: Wednesday, February 13, 2019 2:02 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Help With Getting HTTP Server running

First off, our i is hosted.
Second off, there is nobody that really knows i server configuration
within our shop.

With that said, I just walked through the process of setting up the
http
server for use with yajl rest apis using Scott Klements guide
https://www.common.org/scotts-iland-blog/rpg-and-yajl/

The steps to setup were straightforward. However when I press the
green
server start button within the HTTP servers tab, it will not start - as
soon as you refresh it is stopped.

What am I missing?

Thanks in advance,

Jay

--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.