If you are unable to use wisely, wait until you are.
The best way to "tune" a program is to not do stuff which the program is doing but doesn't need to be doing.
You won't get much benefit from "tuning" a couple of data-items, but if you define everything optimally in all your programs, it will add up.
Don't just take from the documents at face-value. CALL STATIC VS DYNAM for instance. The more lines of generated code in the called program, the less you will notice the difference. The greater flexibility of DYNAM outweighs the strict "performance" issue in all but exceptional circumstances.
Compile option AWO. Don't use it. Don't be lazy. Use APPLY WRITE ONLY for each individual QSAM VB output file.
Remember, you can't just go changing compile options, either. If they generate code, be aware of possible consequences of running a whole bunch of programs with a mix of options which affect generated code. I'd not want to go there.
Stick to getting the code right, and doing that well. Blindly "tuning" at the code level will waste a lot of your time, and won't save the machine much.