Ibm rpg activation group

Now any subsequent time the program is called it will run in the already extant group. Since the activation group is already running, start up time can be greatly diminished. As promised, this means faster performance. To illustrate this, let me tell a story on myself. There were lots of explanations for that scenario, and I think we tried every one we could think of, to no avail.

As I have frequently done in the past, I turned to an e-mail list for assistance. After going around the barn a few times, someone asked about the activation group specified when the CGI programs were created. That was a lot of overhead for something as simple as a Web page! Now, within each CGI job, once a page has been requested the activation group remains and is constantly reused. This provided a dramatic increase in performance.

Now, if you have programs in activation groups all using the same procedure in service program A, there will be activations of that service program. That could obviously hamper performance. To improve that, you could put your service program into a named activation group, so that all the calling activations are sharing the same service program activation.

This would be worth examining if you have a service program that is used extensively. As always, though, there is a caveat. Using a named activation group introduces another interesting feature: Any static or global variables you use in a service program with a named activation group are available across other activation group boundaries.

The getHowMany returns the number of times that the procedure has been called. Since howMany is defined outside of any procedures see the D-spec coded above the procedure prototype , it is considered static or global.

That means that on subsequent calls within the same activation, the value of howMany remains. If PGM A calls it 50 times, the returned value would be If PGM B calls it 75 times, the value will be Now, since there is only one activation of the service program, howMany only exists once.

The activities performed by the activation group are:. Automatic variables lose both their values and memory locations when the procedure that contains them ends.

Default activation group non-ILE activation group. Every job has a default activation group. It is automatically created when the job starts and destroyed when the job ends. You cannot manually create or destroy the default activation group. It is the only activation group that can run non-ILE programs. This is generally considered a poor practice, for several reasons. ILE activation group. Deleting an Activation Group When an activation group is deleted, its resources are reclaimed.

The resources includestatic storage and open files. Named activation groups such as QILE are persistent activation groups in that they are not deleted unless explicitly deleted or unless the job ends.

The storage associated with programs running in named activation groups is not released until these activation groups are deleted. Therefore, you should avoid having ILE programs that use large amounts of static storage run in the OPM default activation group, since the storage will not be reclaimed until the job ends.

The storage associated with a service program is reclaimed only when the activation group it is associated with ends. If the service program is called into the default activation group, its resources are reclaimed when the job ends.

Use this command to delete a nondefault activation group that is not in use. The command provides options to either delete all eligible activation groups or to delete an activation group by name.

The command works differently depending on how the program was created. For programs, the storage will be re-initialized; however, the storage will not be released.

For service programs, the storage will neither be re-initialized nor released. Ibm - Rpg Interview Questions. Ibm - Rpg Practice Tests. IT Skills. Management Skills. Communication Skills. Business Skills.