Well, obsolete for one is not necessarily obsolete for all. There are home grown mods in code that need updating before you can just remove options. Especially with "legacy" code, how many of us support(ed) code with zero doc for the mods. It's like working with code Jenga - remove the wrong part and it all tumbles down.
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of [email protected] Sent: Thursday, July 23, 2026 6: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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
