Recursive program call static variables

It is very unlikely that IBM will add a new type of static storage, so this request is being closed.

However, if you use ACTGRP(*NEW) for the program, then every call to the program would have its own static variables.

If you need some static variables to be unique for each call to the program and other static variable to be shared by all calls to a program, then the way to do that is to define the shared variables in a service program with a named activation group and use getter and setter procedures to access them. The variables that should be unique for each call to the *NEW program would be defined as normal static variables in the program.

I give you, this is not a proper way to describe this. Let me try again.
Traditionally we handled recursive calls by copying the program to QTEMP and calling it there. That way global variables was local to the new object.
By using the native possibility to call recursively the global variables are Global/Global!
This means that the transition is not just to implement recursive calls. That would introduce serious errors!
Our new coding template is all about procedures and this helps to minimize the problem, but we are forced to use existing code for many years to come.

May be a keyword that indicates that this is a static variable on module level could help here.

We will be happy to deliver a code example if the above makes no sense!

Hello, Pete. You mentioned that this would minimize the difference to other languages. Could you give an example of how your requirement works in another language, with specific syntax for that language?