× 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.



Your "MyPgm" variable cannot be a variable on the ExtPgm keyword.
It can be a named constant or a literal.

-Bob Cozzi
www.RPGxTools.com
If everything is under control, you are going too slow.
- Mario Andretti

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Hauser, Birgitta
Sent: Thursday, August 04, 2005 2:12 AM
To: 'rpg400-l@xxxxxxxxxxxx'
Subject: Problems with Prototyping and Calling RPGIII Programs

Hi,

I had some strange problem calling RPGIII programs through CALLP and
Prototypes.
Until today our application consists of about 50% of RPGIII Programs.
All our RPGIII programs only have 1 parameter (a externally described data
structure that is embedded as copy member in the I-specs).
The call to these programs looks as follows:

To call these programs from RPGIV free format we created a prototype that
looks as follows:
 /If Not Defined(DSIN)
 /DEFINE DSIN
D DSIN          E DS                  EXTNAME(LLDSIN)  
 /ENDIF

D MyPGM           S                   like(RefPGM) 

D PgmDSIN         PR                  ExtPGM(MyPGM)     
D   ParmDSIN                          like(DSIN)     
                                                   
Calling RPGIII program with CallP causes a failure with MCH3601. 
(Even after recompiling the RPGIII programs and the calling RPGIV, 
and restarting the session. Library list is ok and there is only 1 version
of the program)
Calling RPGIV with the same prototype causes no problems.

The call looks as follows:
/Free
  MyPGM = 'LL4711R';
  Monitor;
     PgmDSIN(DSIN);
  On-Error;
  EndMon;
/End-Free

If I change the call to an CALL in non Free-Format, 
the RPGIII program is executed without problems.

It seems that some modifications and recompiles of the calling RPGIV
procedures cause this problem.
Originally these calls worked.

Has somebody had comparable problems?
What can we do (with the exception of converting the RPGIII programs) to
prevent this failures?

Birgitta


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.