Re: Best practice for getting a PCML file describing a given API?

Thorbjørn Ravn Andersen wrote:

Is there perhaps some "header files" (just the input/output descriptions in RPG or Cobol or whatever) that can be read to generate the appropriate descriptor available somewhere in an optional package? Anything?

Here's a kludgy way to get the PCML struct for a data structure; it might save some time. Copy in the include file from QSYSINC, and code the name of the data structure you want as an entry parameter. Then CRTRPGMOD PGMINFO(*PCML) INFOSTMF(whatever).

If it's one of those structures that uses soft-coded offsets for some of the subfields, you'd have to do some cleanup on the struct after the compiler generated it.

/copy qsysinc/qrpglesrc,QWCRSSTS
C *entry plist
C parm QWCS0100
C return

It produces PCML like this (the ends of the lines are chopped off here).

<pcml version="4.0">
<struct name="QWCS0100">
<data name="QWCBAVL00" type="int" length="4" precision="31"
<data name="QWCBRTN00" type="int" length="4" precision="31"
<data name="QWCCDT" type="char" length="8" usage="inherit"
<data name="QWCSN" type="char" length="8" usage="inherit"
<data name="QWCUCSO" type="int" length="4" precision="31"
<data name="QWCUSO" type="int" length="4" precision="31"
...
</struct>
<program name="PCMLAPI" entrypoint="PCMLAPI">
<data name="QWCS0100" type="struct" struct="QWCS0100" </program>