Re: Prototypes for System APIs

[Brian Parkins <goodprophet.bp@xxxxxxxxx>]

Jon, I stand to be corrected, but I don't think QSYSINC provides any 
prototypes for calling APIs. I took a look at QUSLRCD - no call 
Prototype that I could see. My understanding has been that QSYSINC 
provides Data Structures, (and non-free format ones at that) mostly for 
Retrieve and List APIs. In other words, declaring the variables needed - 
but not the call Prototypes.

The QUSRJOBI member is a good example. Data Structures are provided for 
decoding the (retrieved) information - but no help for coding the call 
Prototype. (There is always a confusing comment similar to the following,

D******************************************************************
     D*Prototype for calling Retrieve Job Information API (QUSRJOBI)
D******************************************************************
     D QUSRJOBI        C                   'QUSRJOBI'

- which is no help at all!)

I would suggest your clients will need to create all the required call 
Prototypes, (hopefully in /COPY members). Perhaps some kind soul has 
already done the grunt work and made the source available?

Brian.

On 30/11/2018 22:16, Jon Paris wrote:
> Anyone know what the IBM rules are for when a proto is supplied in QSYSINC ?  Going through them a lot are supplied (such as QUSLRCD for example) but others such as QUSPTRUS are not there.  I'm trying to come up with a way for clients to determine which ones they have and which they need to potentially create.
>
>
> Jon Paris
>
> www.partner400.com
> www.SystemiDeveloper.com