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



Not in a position to check but I think what you have probably missed is that on step 5 you need to map the parameter to the URL input. At the bottom of the page you have a parameter identifier for the input (i.e. the one you designated as being the input parm at step 4) alongside the parm name is a pull-down selection list and since you are passing color in the URL, you need to select *PATH_PARAM - from that pull-down. Once you do that 'color' (i.e. the name you used in the path) should be available as a pull down item in the "Identifier" box. Select that to match the URL entry with your parm and your error message should go away.

Jon Paris

On Oct 31, 2019, at 1:13 PM, Kelley <kelley.work@xxxxxxxxxxx> wrote:

Hi all,

I'm trying to deploy an IWS service for the first time using a service program that I created. The service program has two sub-procedures, both return production yield values. The first returns yield data by color code (which in our world is material). The second returns yield data by production line number. Both work normally when bound with an RPGLE program.

The service program is called WS100I, the two sub-procedures are called ColorYield and LineYield. The rest of this focuses on ColorYield as that's the one I'm working with.

The PR/PI of ColorYield looks as follows:

//-- Prototype Definition ----------
//--
Dcl-pr ColorYield;
Color_Code Zoned(3:0);
Color_Data Likeds(Yield_Info);
End-pr;

//-- Procedure Interface Definition ----------
//--
Dcl-pi ColorYield;
Color_Code Zoned(3:0);
Color_Data Likeds(Yield_Info);
End-pi;

Color_Code is the input and Color_Data is the output.

The DS Yield_Info looks as follows:

//-- Data Structures ----------
//--
Dcl-ds Yield_Info Template;
Color_Dsc_Short Char(5);
Color_Dsc_Long Char(10);
Num_Starts Zoned(5:0);
Num_Firsts Zoned(5:0);
Yield_Percent Zoned(5:2);
End-ds;

I'm using the Deploy New Service wizard on my 7.1 system. My issue starts when I'm specifying the name for the service (step 3 of 9 on my system).

I've set the resource name as WS100I and the service description as WS100I. But I'm not sure how to set the URI path template. Right now, it's looks like:

/{color:\d+}

When I get to step 5 of 9 (specifying resource method information), I get the following error:

ZUI_54411: The HTTP method must be PUT or POST when there is an input parameter that is not being injected with a value.

The Input Parameter Mappings look like:

Parameter Name: Color_Code
Data Type: Zoned
Input Source: *PATH_PARAM
Identifier: color
Default Value: *NONE

Parameter Name: Color_Data
Data Type Struct
Input Source: *NONE

For the second parameter, none of the fields are changeable, they do not allow input.

I'm not sure what I'm doing wrong at this point. Perhaps the error is related to not including the second parameter in the URI path template, but I can't figure out how to define the regular expression for a data structure.

For reference, I've been referring to web pages by Nadir Amra and Scott Klement.

Any ideas?

Thanks,

Kelley



--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
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-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.