Thx. But how do you configure to allow pgm to accept Parms? I’m ultimately not wanting to use yajlcallr


On Feb 13, 2019, at 4:35 PM, Arco Simonse <arco400@xxxxxxxxx> wrote:

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:

Require all granted

Hope that helps.

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

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,

This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support by shopping at with our affiliate link:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].