|
Even after receiving Scott's reply this morning, I tried putting the parms in quotes. No pointer error, but nothing returned either.
Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of M. Lazarus
Sent: Monday, January 18, 2010 3:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: Passing Parameters Back to a S/36 Proc
Jerry,
Try enclosing the parms in quotes:
CALL PGM(PGMA) PARM('?1?' '?2?')
-mark
At 1/18/10 04:22 PM, you wrote:
>I have often passed parameters to a program from a /36 procedure, such as:
> CALL PGM(PGMA) PARM('PARM1' 'PARM2'), or
> CALL PGM(PGMA) PARM(?1? ?2?)
>where the parameter conditions something in the callee (PGMA).
>
>Now I would like to be able to receive information from the callee
>to condition something in the /36 procedure.
>
>I tried the second example, but the call resulted in a pointer error.
>
>Using the local data area works as an interface between the 36E and
>an RPG IV program, but not if the program (PGMA, for example) is
>called by another RPG IV program as the LDA is not updated until the
>caller ends.
>
>Why the gyrations? Well, I wrote a program a couple of years ago
>simply for the 36E. It updated the LDA and the OCL can interpret
>the results. Now, though, I have found a need to call this same
>program from within an RPG IV program.
>
>My best guess right now is to update both the LDA *and* pass a
>parameter. The former (LDA) for use by the 36E; the latter for use
>by a program.
>
>Jerry C. Adams
>IBM System i Programmer/Analyst
>--
>B&W Wholesale
>office: 615-995-7024
>email: jerry@xxxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
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.