I usually create the PCML separately and put it in a shared folder on the
IFS. I then use the PCML to create the web service. Also, you may want to
put the parms in a data structure - that is easier to manipulate by the
consumer of the web service
BTW PCML cannot convert iSeries date fields - we convert them to 10 string
fields. If they have date fields on the parm list then the wizard is
probably unable to create the PCML.
Have them run the following on their ISeries then you can look at the PCML
in the IFS.
CRTRPGMOD MODULE(mylib/ITIN)
SRCFILE(mylib/QRPGLESRC)
OPTION(*SHOWCPY)
DBGVIEW(*ALL)
BNDDIR(*LIBL/mybindingdir)
PGMINFO(*PCML)
INFOSTMF('/shares/mypcmls/this.pcml')
Regards
Faizulla Khan
Information Services
Grand Circle Travels
617-346-6058
"Jon Paris"
<Jon.Paris@Partne
r400.com> To
Sent by: <wdsci-l@xxxxxxxxxxxx>
wdsci-l-bounces@m cc
idrange.com
Subject
[WDSCI-L] Limit on number of parms
08/01/2007 02:08 in Web Service
PM
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>
Anyone know if there is a limit in the current web service generation
wizard
that limits the number of parameters that can be passed?
I have a customer trying to use a program that takes 52 parameters (yes
really) and it is blowing up with error messages that indicate that the
pcml
can't be found.
Jon Paris
Partner400
www.Partner400.com
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
midrange.com
