My reason for suggesting an APAR is that intrinsic inability to track down the source of an error message strikes me as a design failure. Furthermore, an APAR tied to a defect may get better (= quicker) resolution than an enhancement RFE.
In Ed's case, a syntax typo in the initialization options might be difficult capture succinctly. Nonetheless there are products that flag errors by 'line number' without trying to diagnose the error in depth. ISPF HILITE pointed to the problem, which was sufficient to fix it. HSM should be able to provide comparable guidance. Other products do. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: Friday, June 22, 2018 1:50 AM To: [email protected] Subject: (External):Re: ARC0104I INVALID INITIALIZATION COMMAND Jesse 1 Robinson wrote: >I'd say that this is such an egregious oversight that it should be APARable >even after all this time. There's no statute of limitations on bad design. Or ask for a thing to do Syntax Checking of ARCCMDxx just like the one for BPXPRMxx member (SETOMVS SYNTAXCHECK=(??) ). Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
