Hi Robert, is there a specific reason not to use IWS builtin capacity to
deliver parsed parameters to the called RPG *PGM/*SRVPGM?

Just curious about other developers' use of IWS.

Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco

Il giorno mar 28 lug 2020 alle ore 15:46 Robert Rogerson <
rogersonra@xxxxxxxxx> ha scritto:

Hi All,

I'm creating a REST webservice/api and using IWS. I'm then using Postman
to test the webservice. All the endpoints call procedures in a service

I have an endpoint /web/server/claims which will call the RPG procedure
GetAllClaims which returns all claims. I have tested this with Postman
and it works correctly.

My next step is to add a filter. So I call the same endpoint but this time
I pass a parameter of whid. So the endpoint now becomes
/web/server/claims/?whid=93 which will call the RPG procedure GetAllClaims
but this time I need to extract the parameter passed in the QUERY_STRING to
return only claims for warehouse 93.

Can someone point me to either documentation or an example of how to
specify and extract from the QUERY_STRING. I've done a lot of searching on
Google but I must not be searching on the correct terms because I can't
find anything on QUERY_STRING other than that you may specify it..


This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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