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



>>Maybe post the code in non-free format so we can compare a call that works
>>against a call that doesn't?

It also worked on at least 2 or our clients machines, under release V5R1M0
and V5R2M0.
Here is the modification I made this morning:
   §UPR = 'LLUA26R';
   //***** CallP(E) PgmDSIN(§§DSIN);
 /End-Free
C                   Call(E)   §UPR
C                   Parm                    §§DSIN
 /Free

(The use of § is no typo, we can use § instead of @ in our source code)

After modification of the caller program and recompiling,
it does not work on either of this 3 machines.
I have to add the modification did not touch this call at all.
None of the data structure subfields that is passed as parameter was
changed,
nor the physical file for the data structure was changed.

Our first thought was, we didnot compile it in the right way, or in a wrong
library.
So we recompiled everything on our test machine, but without success. The
call ended with MCH3601.
After replacing the CALLP statement I worked like a charm.

At least our machines are current with PTFs, with the clients machines I
don't know.

It's not the first time I get this failure.
But the last times I realized it when testing
and replaced the CALLP through a fixed format CALL.
But this time, nobody checked if the call ends successfully.
The failure was trapped by using an (E)-Extender on the CALLP statement,
but not handled.
... and like always in these situations the client called our manager
and he makes some trouble.

Birgitta

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]Im Auftrag von Paul Morgan
Gesendet: Donnerstag, 4. August 2005 17:07
An: rpg400-l@xxxxxxxxxxxx
Betreff: Re: Problems with Prototyping and Calling RPGIII Programs


Birgitta,

Did the original calls work on your test box?  (maybe your test box is out
of date on some PTFs?)

Did you do anything with activation groups?  Could the RPG IV programs be
running in a different activation group than before?

Maybe post the code in non-free format so we can compare a call that works
against a call that doesn't?

Paul

--
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333

Birgitta wrote

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



--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.




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.