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



Hi Jay,

You don't have to reference the program object in your URI. Just
http://ourSystem:port/rest is enough.

In your http config you will need the following:

ScriptAlias /rest /QSYS.LIB/YAJLREST.LIB/YAJLCALLR.PGM
<Directory /QSYS.LIB/YAJLREST.LIB >
SetEnv QIBM_CGI_LIBRARY_LIST "YAJLREST;YAJL"
Require all granted
</Directory>

Hope that helps.
Regards,
-Arco

Op wo 13 feb. 2019 om 21:42 schreef Jay Vaughn <jeffersonvaughn@xxxxxxxxx>:

I'm setting out to establish a POC for our company using SK's guide at

https://www.common.org/scotts-iland-blog/rpg-and-yajl/

I have the http server created and running.
I have YAJL deployed to the i.
I have YAJLCALLR compiled into YAJLREST lib.

I'm trying to logically progress down the path in small steps so I can
understand the moving pieces.

When I invoke from the browser... http://ourSystem:port/rest/YAJLCALLR I
would expect to at least see the *pgm object of YAJLCALLR last used date
set to today instead of remaining blank?

I'm at a loss (early in the game unfortunately) as to what I'm missing.
The good news is that I have written many YAJL rpg pgms at another employer
who had already had the endpoint setup - though slightly different than
what Scott shows in his guide.

So if I can just get over this initial configuration hump, I'm thinking I
should be home free.

Any help would be appreciated,

Jay

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.