This is a topic that comes up often internally. I can only speak from ICSF's perspective that we always try to compatibly ignore options that no longer are needed.
That said, I believe the other z/OS components have the same approach. We want to avoid incompatible changes to PARMLIB even if it means a little more work on our end. I will say that, yes, you should poke your sysprog to remove or at least comment out deprecated/obsoleted parms if only to make it clear that they no longer have an effect. Eric Rossman --------------------------------- ICSF Security Architect z/OS Security --------------------------------- -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of [email protected] Sent: Thursday, July 23, 2026 7:12 AM To: [email protected] Subject: [EXTERNAL] Obsolete parameters - problem ahead? Hi! It is frequent, for some configuration options of IBM products, to become obsolete. When the product is started, these options are normally detected as OBSOLETE and IGNORED. In your experience, is there a real risk that newer versions, instead of just recognizing them as obsolete, stop recognizing them and cause a real problem (for instance, not processing the configuration member from that specific line, or directly abending the start)? Just for the record, I have detected such obsolete options in SDSF and ICSF. Of course, the best way would be to address the problem by just deleting (or commenting) these obsolete options. But I am not the sysprog (I am a RACF admin). Thanks in advance for your help, Juan Mautalen ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
