IEV90 is hardly "alive", unless you captured it at some point before it was discontinued. Maybe you could find some incompatibility with HLASM, but I doubt it. In any case, the notice is only about how to create an alias for IEV90.
If I were IBM, I think I'd withdraw the usermod, and tell anyone who insists on using it that they're on their own, like any other usermod. On the other hand, permanently adding the alias shouldn't be a problem. If there happens to be somebody who has to keep a copy of old IEV90, AND they want to keep it in SYS1.LINKLIB, well, too bad. That's unreasonable, but you can deal with it yourself. IBM has more important things to do. On Sat, Aug 13, 2016 at 6:09 AM, Elardus Engelbrecht < elardus.engelbre...@sita.co.za> wrote: > Jeremy Stone wrote: > > >We've been receiving PMRs for HLASM due to users using an SMP/E USERMOD > create an alias of IEV90 against HLASM's ASMA90. For historical reasons, > users still have JCL procedures and EXECs referring to IEV90 rather than > the newer ASMA90. Invariably problems arise due to the USERMOD process > when maintenance is applied. We have modified our sample to help reduce > issues, but we still receive PMRs. > >Because this appears to be source of continued problems we are > considering modifying our SMP/E JCLIN to create a permanent alias of IEV90 > for ASMA90 on z/OS. > >However, before we progress with this, we'd like to understand if this > could cause problems for anyone. > >If anyone has any comments or concerns with this proposal, we'd be > interested to hear - either on the forum or an email to me. > > IEV90 still alive? Perhaps there are some ancient programs which still > need IEV90 for compile/link due to some compatibility issue. > > Just do it! Please! Place in a formal IBM announcement that IEV90 is to be > discontinued at z/OS v?.? > > Get rid of the module (or rename it to IEV90# or so) and put in an alias > as described. > > Groete / Greetings > Elardus Engelbrecht > -- sas
