Re: Address of Variable in Service Program Exported Procedure -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Address of Variable in Service Program Exported Procedure
From: Brian Parkins <goodprophet.bp@xxxxxxxxx>
Date: Mon, 7 Nov 2022 21:00:50 +0000
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

As well as passing parameters, there are other options available to you involving the use of shared Objects:

- *USRSPC (which can be manipulated using based variables and pointers)
- *DTAQ
- *MSGQ
- *MSGF

Just a thought.
Brian.

On 07/11/2022 20:48, Vinay Gavankar wrote:

The reason it was being done was the variable is 32K bytes. I guess it
shouldn't matter as RPG would internally pass the pointer, so there would
be no effect on program performance.

Follow-Ups:

Re: Address of Variable in Service Program Exported Procedure , Charles Wilt

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