|
I believe you'll need some pointers,... Here's an example of what I've done:
0098.00 * Entry Parms via Prototype/Procedure Interface
0099.00 *-------------------------------------------------
0100.00 d Oe1007ri10 pi
0101.00 d OePsc000 Like(Psc000)
0102.00 d OePsc001 Like(Psc001)
0103.00 d OePsc002 Like(Psc002)
0106.00 *------------------------------------------------------------------
0107.00 d Psc000 e ds ExtName(Oeps00) Based(pPsc000)
0108.00 d RzlA 1 Overlay(Psc000) Dim(3)
0109.00 d S4Ent# 8 Overlay(Psc000:284)
0125.00 d Psc001 e ds Extname(Oeps01) Based(pPsc001)
0126.00 d Wkl2A 5 Overlay(Psc001) Dim(1500)
0127.00
0128.00 d Psc002 e ds Extname(Oeps02) Based(pPsc002)
0129.00 d Wkl3A 5 Overlay(Psc002) Dim(1500)
0229.00 d pPsc000 s * Inz
0230.00 d pPsc001 s * Inz
0231.00 d pPsc002 s * Inz
In your *INZSR or prior to referencing any field within the DS, assign the pointers.
0268.00 c Eval pPsc000 = %Addr(Oepsc000)
0269.00 c Eval pPsc001 = %Addr(Oepsc001)
0270.00 c Eval pPsc002 = %Addr(Oepsc002)
HTH,
Regards,
Jon A. Erickson
Sr. Programmer Analyst
800.COM Inc.
1516 NW Thurman St
Portland, OR 97209-2517
Direct: 503.944.3613
Fax: 503.944.3690
Web: http://800.com
-----Original Message-----
From: tomh@simas.com [mailto:tomh@simas.com]
Sent: Tuesday, November 07, 2000 1:05 PM
To: RPG400-L@midrange.com
Subject: Prototyping *ENTRY when the PLIST parm is a data structure
How do I prototype the *ENTRY when one of the parms is a data structure with multiple subfields? Is there a way to do it without listing each subfield in the prototype definition? An example of what I want to convert:
dparmo ds
d $rtcd 7
d $fast 1
c *entry plist
c parm parmo
I've tried the following, but it didn't work:
dcsr0033 pr extpgm('CSR0033')
d parmo 100
dcsr0033 pi
d parmo 100
dparmo ds
d $rtcd 7
d $fast 1
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.