We're reviewing the performance of some batch jobs, and noticed that many of them are performing a very high rate of "database full opens". IBM advises that any individual job should perform less than 100 "full opens" per second. Many of our jobs are performing 2-3000 full opens per second. These jobs are executed 2E-generated RPG programs. Is there something that can/should be done within 2E to address this scenario? Do 2E-generated RPG programs always perform "full opens" or is this within the developer's control?
Release : 8.7.2
As per 2E Design, we do NOT have any specific settings to control "database full opens".
Please refer to the below documentation in order to "Tailoring for Performance of Functions" which will help for fine tuning of the functions for better performance: