Re: Activation Group and RCLACTGRP

Please point out to them that "RCLACTGRP ACTGRP(*ELIGIBLE)” should NEVER EVER be used in production code. Either that or please tell me the name of the vendor so that I can advise people to stay a million miles from their code.

That little beauty is so potentially lethal that IBM removed almost all references to it. Try and find it in the online help for instance - it’s not there. The reason is the number of really nasty “accidents” that occurred as a result of its use in production code.

This “feature” should only ever be used in development. And even then with caution and the knowledge that you may need to log off after usage.

There are as others have said some potential alternatives but good grief - the very idea that they should be telling you to do it int he first place is scary.

On Jan 25, 2016, at 6:03 PM, Hiebert, Chris <chris.hiebert@xxxxxxxxxxxxxx> wrote:

Does anyone know a good way to keep an activation group open, or to stop then ending of an activation group?

We have upgraded a vendor product and they have decided that their tool must run "RCLACTGRP ACTGRP(*ELIGIBLE)".

The worst command ever for a service program that stays open, but isn't "held" open.

Every single one of our service programs reside in a named activation group.

When we use this vendor's product, all of our named activation groups are destroyed.
This causes the remaining calls to the procedures inside the service program to generate the error "Tried to refer to all or part of an object that no longer exists."

I've been unable to find a way to stop the RCLACTGRP command from killing all of our activation groups.

I've tried to use the Register Activation Group Exit Procedure (CEE4RAGE) API to register a procedure, but that procedure only runs after the end request has already been made. And I haven't been able to figure out how to Stop the end request from completing.


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com