I have different modules in my SRVPGM after following Nadir's link
https://developer.ibm.com/tutorials/i-rest-web-services-server3/ .

There is something wrong about URI template
I have 3 get modules which have different parameters and length.

Procedure name: GET3
HTTP request method: GET
URI path template for method: /GET3/{Key2}/{place}
HTTP response code output parameter: httpStatus
HTTP header array output parameter: httpHeaders
Allowed input media types: *JSON
Returned output media types: *JSON
Input parameter mappings:
Parameter name Data type Input source Identifier Default Value
Key int *PATH_PARAM Key2 *NONE
Place int *PATH_PARAM Place *NONE



Procedure name: GET2
HTTP request method: GET
URI path template for method: /GET2/{Key2}
HTTP response code output parameter: httpStatus
HTTP header array output parameter: httpHeaders
Allowed input media types: *JSON
Returned output media types: *JSON
Input parameter mappings:
Parameter name Data type Input source Identifier Default Value
Key int *PATH_PARAM Key2 *NONE

Procedure name: GET1
HTTP request method: GET
URI path template for method: *NONE
HTTP response code output parameter: httpStatus
HTTP header array output parameter: httpHeaders
Allowed input media types: *JSON
Returned output media types: *JSON
Input parameter mappings:
Parameter name Data type Input source Identifier Default Value
Key int *QUERY_PARAM Key *NONE
File char *QUERY_PARAM File *NONE



URI Template is supposed to help us identify which procedure to be called
for the Get operation.

GET1
https://xx/web/services/CUSDRIVER?Key=547&File=Headq

GET2
https://xx/web/services/CUSDRIVER/2345(key2 value) {Doesn't work}

GET3
What woudl be link for it ?

This thread ...

Follow-Ups:

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

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