Hi, Dan:

Here is a little RPG program to determine what parameters
are passed to an OPM program, and exactly how they are
arranged in the "calling" program's storage.

(I found this many years ago; not sure where; maybe from the
old Q38 Magazine BBS...):
==============================================
H    1
IPIDS    SDS                            500
I                                    *PARMS          #PARMS
I                                    *PROGRAM    PGMNAM
C        *ENTRY    PLIST
C                          PARM        PARM01225
C                          PARM        PARM01255
C                          PARM        PARM04255
C                          PARM        PARM05255
C*                         . . .
C* code at least as many PARMs as expected; use DSPPGM on
C* the program you are analyzing, and look at the minimum and
C* maximum number of parameters shown on the second screen.
C*
C                          DUMP
C                          SETON                            LR
C                          RETRN
==============================================

Compile this program, then put it in a library in front of the *LIBL,
rename it to the name of the program in question for which you need
to determine the parameters. Then call the program that calls it, and
examine the "dump" spool file (QPPGMDMP) that is produced.
This should help you to see exactly what is going on.

Regards,

Mark S. Waterbury





As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.