Re: API data type prototyping

Pete,

You could also take a look at some books, for example "APIs at Work" by Pence & 
Hawkins, published by MC Press (www.mcpressonline.com)

It contains a disk with sample code.

Always a good idea to learn by example.

Regards,
Carel Teijgeler

*********** REPLY SEPARATOR  ***********

On 18-7-05 at 12:42 Pete Helgren wrote:

>Thanks Leif and Jonathan.
>
>Just what I was looking for!  I knew I had seen that somewhere before.
>
>We need more "Getting Started in ..." documents though.  Even though I 
>have been coding RPG for 20 years (yikes!) API's were NOT part of my 
>vernacular until very recently.  If we really want to get folks moving 
>to RPG IV I think "Getting Started in..." and "Nutshell" (to rip off 
>O'Reilly...) booklets would be an excellent way to do it.  Then post it 
>all in a more or less central place (like Midrange.com.....)
>
>Pete
>
>
>Leif Guldbrand wrote:
>
>>Hi Pete,
>>
>>Not sure, but could it be Barbara Morris's article ??
>>www.Think400.dk/adhoc_2.htm#eks0010
>>
>>Leif
>>----- Original Message ----- 
>>From: "Pete Helgren" <Pete@xxxxxxxxxx>
>>To: "RPG Midrange Discussion" <rpg400-l@xxxxxxxxxxxx>
>>Sent: 18. juli 2005 19:15
>>Subject: API data type prototyping
>>
>>
>>  
>>
>>>Seemed to me that there was a post, way back when, that had some 
>>>instructions for mapping API data types to RPG types.  Perhaps there is 
>>>an FAQ somewhere?
>>>
>>>What I would like is some general instructions on how to properly define 
>>>variables in my prototypes for system API calls.  For example, I am 
>>>working with QSZRTVPR API and it has the following format:
>>>
>>>1     Receiver variable     Output     Char(*)
>>>2     Length of receiver variable     Input     Binary(4)
>>>3     Format name     Input     Char(8)
>>>4     Product information     Input     Char(*)
>>>5     Error code     I/O     Char(*)
>>>
>>> Optional Parameter:
>>>
>>>6     Product information format name     Input     Char(8)
>>>
>>>What I would like is something that says:
>>>
>>>Binary(4) maps to 10I
>>>Char(*) maps to (? don't know)
>>>Char(8) to 8A
>>>
>>>Also whether or not the value keyword is needed. Anything special for 
>>>I/O vs Input or output.  That kind of thing.
>>>
>>>Yes, this is basic stuff and yes, I suppose a properly trained RPG 
>>>programmer would know this stuff, but I recently transitioned to RPG IV 
>>>(free form mostly) and some of this stuff is just tough to get your arms 
>>>around (especially when Java and C++ also intrude into the programming 
>>>mix on a daily basis).
>>>
>>>Perhaps an FAQ entitled "How to prototype and use system API's"?  
>>>Although I know we can't document all the API's, general "rules" about 
>>>how to do it would be helpful.  Perhaps it is already in a post.  If so 
>>>I'd gladly format them into an FAQ or stuff them in the Wiki.
>>>
>>>Seems that I have seen something like this somewhere in the past...if 
>>>so, sorry for the waste of time...could you point me to it.
>>>
>>>Pete Helgren
>>>
>>>-- 
>>>This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
>list
>>>To post a message email: RPG400-L@xxxxxxxxxxxx
>>>To subscribe, unsubscribe, or change list options,
>>>visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
>>>or email: RPG400-L-request@xxxxxxxxxxxx
>>>Before posting, please take a moment to review the archives
>>>at http://archive.midrange.com/rpg400-l.
>>>
>>>
>>>
>>>    
>>>
>>
>>
>>  
>>
>-- 
>This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
>To post a message email: RPG400-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
>or email: RPG400-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/rpg400-l.