The journals aren’t nearly as important as the journal receivers. Where do you create your receivers? If you look at receiver directories, do you see the receivers listed with “Saved” status? Which system journals are you interested in? What auditing options did you activate? Are you tracking job accounting?
SAVSYS is possibly irrelevant most weeks — it could probably be replaced with SAVSECDTA and SAVCFG, probably avoiding a need to go to restricted state. A SAVSYS from three months ago is usually as good as last night’s (excepting security and configuration data). SAVSYS plus SAVLIB *IBM is fully appropriate after significant events such as a cumulative PTF package. A full system save (GO SAVE, 21) is rarely needed, appropriate before major events such as operating system upgrades.
Similar to SAVSYS, a non-SYS SAVLIB has probable irrelevant elements. The IBM libraries from months ago are usually good enough. Saving them on the same schedule as SAVSYS works fine.
SAVDLO? I would hope that that’s totally wasted effort. After the past decade, there probably shouldn’t be anything left in DLOs that you’d miss.
Of course, if you can save more, by all means do it. It seems reasonable to me to save to as high a level as you can comfortably accommodate. The more you have collected together, the easier things can be to recover. And extra copies are also potentially useful. It’s also easier to plan and implement, and that can make it far more likely to get done.
In general, if you’re saving non-SYS, you can almost guarantee that you’re saving system journal receivers. Non-SYS library saves capture IBM and all user libraries. On most systems, there are no other places for journal receivers to be created.