You have two options to getting access to query string variable. The
recommended way is to inject the query string parameter into a parameter

The alternative way is to pass the entire query string as an environment
variable and within your code you would need to issue a getenv() call and
then parse the query string variable.

Obviously, injecting an input parameter with value of query string
variable is easiest. And this method allows you to specify a default
value as well if not specified.

"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 07/28/2020 08:45:55

From: Robert Rogerson <rogersonra@xxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
Date: 07/28/2020 08:46 AM
Subject: [EXTERNAL] [WEB400] IWS, REST and retrieving variables from
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

Hi All,

I'm creating a REST webservice/api and using IWS. I'm then using
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
I pass a parameter of whid. So the endpoint now becomes
/web/server/claims/?whid=93 which will call the RPG procedure
but this time I need to extract the parameter passed in the QUERY_STRING
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
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..

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.