MFASTC running with Java 17 has the below message BPXI039IBPXI039I SYSTEM LIMIT SHRLIBRGNSIZE HAS REACHED 85% OF ITS CURRENT CAPACITY OF 68157440 BPXI039I SYSTEM LIMIT SHRLIBRGNSIZE HAS REACHED 90% OF ITS CURRENT CAPACITY OF 68157440 BPXI039I SYSTEM LIMIT SHRLIBRGNSIZE HAS REACHED 100% OF ITS CURRENT CAPACITY OF 68157440
Questions:
1. What is the impact to the MFASTC task if we don't increase SHRLIBRGNSIZE ?
2. Is there any tuning possible, from an AAM perspective, to avoid SHRLIBRGNSIZE reaching 100% ?
MFASTC (AAM) running with Java 17
MFASTC task stays up and functional without interrupting other STCs behavior
Environment
1. Verify your current SHRLIBRGNSIZE in BPXPRM member by issuing D OMVS,L
Sample Output:BPXO051I 08.21.28 DISPLAY OMVS 980 OMVS 0010 ACTIVE OMVS=(50) SYSTEM WIDE LIMITS: LIMMSG=ALL CURRENT HIGHWATER SYSTEM USAGE USAGE LIMIT MAXPROCSYS 106 109 900 MAXUIDS 24 25 500 MAXPTYS 0 0 800 MAXMMAPAREA 439 439 40960 IPCMSGNIDS 11 13 500 IPCSEMNIDS 2 2 2000 IPCSHMNIDS 3 3 500 IPCSHMSPAGES 0 0 262144 IPCMSGQBYTES --- 708709 2147483647 IPCMSGQMNUM --- 112 10000 IPCSHMMPAGES --- 0 25600 SHRLIBRGNSIZE 68157440 68157440 68157440 SHRLIBMAXPAGES 0 0 4096 MAXUSERMOUNTSYS 0 0 0 MAXUSERMOUNTUSER 0 0 0 MAXPIPES 29 32 15360
2. For the above scenario, since the Current Usage has reached 100% of System Limit
Stay with Java 17, update the MFAPARMS member to add the below and restart MFASTC task.export _BPXK_DISABLE_SHLIB=YES
3. Issue D OMVS,L
from the output, you will notice that the SHRLIBRGNSIZE has shrunk back to a lot less than 100%.
From the output of D OMVS,L You will notice that the SHRLIBRGNSIZE has shrunk back to a lot less than 100%.