|
From: Robert Rogerson <rogersonra@xxxxxxxxx><web400@xxxxxxxxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
Date: 12/14/2020 05:52 PMare
Subject: [EXTERNAL] Re: [WEB400] IWS and input parameters...
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>
@Nadir, your assumption is correct, pFilterDs is indeed input. So you
saying that I can have a data structure as input?field
Why must the "_lenght" be in upper case. I've never seen nor understand
this requirement.
Thanks,
Rob
On Mon, Dec 14, 2020 at 3:25 PM Nadir Amra <amra@xxxxxxxxxx> wrote:
Which parameters are input and which output?
And "_length" suffix should be "_LENGTH"
Assuming pFilterDs is input, you may want to define a length
in.for it as well so that you know how many entries are being passed
08:24:21
"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 12/14/2020
IAM:
From: Robert Rogerson <rogersonra@xxxxxxxxx><web400@xxxxxxxxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
Date: 12/14/2020 08:24 AM
Subject: [EXTERNAL] [WEB400] IWS and input parameters...
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>
I want to have a filter(s) for my api.
An individual filter is defined as
dcl-ds filterTmp template qualified;
type char(20);
value char(20);
end-ds;
But there may be multiple occurrences of filter. For example,
'Warehouse': '95,96,97'
'Type':'Shipments'
'DateRange': 'LastWeek'
I was hoping to do something like
dcl-pi *n;
pFilterDs likeds(filterTmp) dim(10) const;
transactionDs_length int(10);
transactionsDs likeds(transactionsTmp) dim(1000);
httpStatus like(httpStatusTmp);
httpHeaders like(httpHeadersTmp) dim(10);
end-pi;
But when I try this on Step 5 of 9 on the Deploy New Service Wizard
is anget
error
*Error:* ZUI_54411: The HTTP method must be PUT or POST when there
input parameter that is not being injected with a value.
How should I be doing this?
As an Amazon Associate we earn from qualifying purchases.
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.