× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. May 2008

Re: Quick OPM RPG question

James Lampert wrote:
I could have sworn that I'd tested this before.

I've got an OPM RPG program, that was recently modified to add a sixth parameter (a multi-occurrence data structure, no less!) And I only reference the parameter if ##PARM in the PGSDS tells me it was passed. Yet suddenly, I find that the program crashes if that sixth parameter isn't passed, and the error message references the PARM statement on the *ENTRY PLIST.

Even more bizarre, there's code already in the program such that it tolerates fewer than the original 5 parameters.

Anybody know what could be going on here? Is it something about passing a multi-occurrence data structure?

I think it is the multi-occurrence DS causing the problem. It looks like the compiler sets up the pointer to the first occurrence as part of program entry.

The RPG IV compiler doesn't have the same problem. If you need that parm to be a multi-occur DS, your best bet is probably to convert it to RPG IV.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.