RE: MCH3402 on second run of program

It really depends on your Activation Group... Check your service program to see what it's ACTGRP is. If using a named AG, simply issue a RCLACTGRP for that AG after you run.

Using AG(*NEW) adds ILE overhead, but ensures that resources will be automatically reclaimed after the module ends. Perhaps the recommended usage might be to compile CALLER as AG(*NEW) and SRVPGM as AG(*CALLER). This would cause the procedure to activate into the same AG as the CALLER, and once CALLER completes, all activated resources will be reclaimed...

There are hundreds of variations on this theme, and without more details, there's little to really recommend.

-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Wednesday, November 13, 2013 4:08 PM
To: Midrange Systems Technical Discussion
Subject: MCH3402 on second run of program

I think I've seen this on MIDRANGE before. Tried sraeching but found lots
of other hits.


I wrote an RPGLE program. A function is used in a service program. When
all data has been processed, *INLR is set on.

Run the program and it works. Run a second time, and MCH3402 is received.
Sign off and back on, and program works fine again.

Do I need to change program to include something to get rid of the error?

This is more of a curiousity question, as program likely won't be run very
often - and won't be run by anybody else.

Something about activation group is in my mind.

Just curious why it popped up.

John McKee