Re: IWS REST GET Variable Length PATH_PARM Input

Yes, you have to build combined PCML.

Example:

<pcml version="6.0">
<program entrypoint="CONVERTTEMP1" name="CONVERTTEMP1"
parseorder="TEMPOUT"
path="/QSYS.LIB/QSYSDIR.LIB/QIWSSAMPLE.SRVPGM" threadsafe="false">

<data length="10" name="TEMPIN" type="char" usage="input"/>
<data length="10" name="TEMPOUT" type="char" usage="output"/>
</program>

<program entrypoint="CONVERTTEMP2" name="CONVERTTEMP2"
parseorder="TEMPOUT"
path="/QSYS.LIB/QSYSDIR.LIB/QIWSSAMPLE.SRVPGM" threadsafe="false">

<data length="10" name="TEMPIN" type="char" usage="input"/>
<data length="10" name="TEMPOUT" type="char" usage="output"/>
</program>
</pcml>


"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 04/16/2019 11:48:13
AM:

From: Stephen Piland <Stephen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
To: "web400@xxxxxxxxxxxxxxxxxx" <web400@xxxxxxxxxxxxxxxxxx>
Date: 04/16/2019 11:48 AM
Subject: Re: [WEB400] IWS REST GET Variable Length PATH_PARM Input
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

Has anyone ever used PCML stmf on ifs for multiple procedures/
modules rolled up into a single SRVPGM? Aside from Varchar on 7.1
issue, it worked fine for me when Pcml data was in module (not ifs
file). I'm assuming if you have ABC001 and ABC002 modules in
ABCSRVPGM, you'd have to build a combined PCML on IFS of the
contents of both of their individual STMFs. If that is true, does
anyone have an example of how that would look?

Thanks again!