Hello and good morning,
our mainframe system engineers have watched that in GEN-applications (here typically used as subtransactional components)
the used heap-storage is obviously much higher than in non-gen-parts of the application.
These components are sets of ActionBlocks that are simply used via COBOL-dynamic call (we use the z/OS-compatibilty mode for all our
GEN-applications).
The system-engineers found that the gen-Runtime-modules very often call the LE-functions „Create Heap (CEECRHP)" and Discard Heap (CEEDSHP)".
A typcal result in a Batch is:
run through Counter: 1
Additional Heap statistics:
Successful Create Heap requests: 158
Successful Discard Heap requests: 158
Total heap storage used: 2.545.608
Successful Get Heap requests: 302
Successful Free Heap requests: 0
Number of segments allocated: 230
Number of segments freed: 230
run through Counter: 1.000
Additional Heap statistics:
Successful Create Heap requests: 142292
Successful Discard Heap requests: 142292
Total heap storage used: 2.147.455.064
Successful Get Heap requests: 270908
Successful Free Heap requests: 0
Number of segments allocated: 206600
Number of segments freed: 206600
From our system-engineers Point of view it is desirable (and should be possible) to rework the gen-Runtime in order to use alternative LE functions which are significiantly less CPU intensive.
Is there a chance to investigate into this direction?
best regards
Klaus