RE: Overflow in the activation mark counter (Smith, Dave)

Tom:  The work volume did not increase.  They do not explain the difference
at this point.  Their response is:  "I will update you as soon as the
developer calls and discusses this issue."

Vernon: It looks like the default for "Default activation Group" is *YES
which causes the program to act like an OPM program.  IBM had us check this
and in our case, because we are using such a mix of RPG II, III, and IV,
they reccomend that it should be *YES.

From: "Westdorp, Tom" <Tom.Westdorp@StationCasinos.com>
To: midrange-l@midrange.com
Subject: RE: Overflow in the activation mark counter
Date: Tue, 26 Mar 2002 13:52:26 -0800
Reply-To: midrange-l@midrange.com

given that they say:
"As of V4R5 and V5R1, at the SLIC level the counter is an 8-byte integer,
while at the
MI level only the 4 low-order bytes are used..."

How do they explain the difference?  Or did your work volume increase on the
r510 box?  They  claim the method to be the same for 450 and 510.

From: Vernon Hamberg <vhamberg@attbi.com>
Subject: Re: Overflow in the activation mark counter
Reply-To: midrange-l@midrange.com

Is IBM going to do anything about this? Seems like a bug. But this
'low-order' vs. full task ID has been around for a long time, I'd say, it
shows up in a lot of PEX reports.

But it's another good reason not to use the default for activation group,
*NEW. Why this is the default is beyond me., as it has performance
problems, and now it can even kill jobs, apparently. Make a copy of CRTPGM
into your own system library (above QSYS) and change its default.