Why it happens that CASE-SENSITIVE ELM NM field is always set to Y, not keeping the value set by the user at the last session?
In the background of the question we have that, with CASE SENSITIVE ELM NM set to N, customers experience performance problems when building element lists. This is because case-insensitive searches cause much more overhead than case-sensitive ones. Since the default for this option was N, it resulted in generalized complaints about performance.
To address this situation, we issued fix RO95476. This fix forces the option to be unconditionally set to Y at the start of each new session. The user can set it to N but the value will be kept only during the current session, and will be forced again to Y at the next session.
Since we introduced the fix in the panel definitions (instead of the executable programs), interested sites could revert to the old logic by updating some endevor panels.
IMPORTANT: The endevor panels are maintained by SMP/E. If they are just edited, any changes may be eventually overwritten during maintenance. This effect may be prevented by introducing the changes via an SMP/E usermod.
When applying maintenance, SMP/E will refuse to replace a panel which has been replaced by an usermod. This will allow sites to restore the usermod, apply the maintenance, redo the usermod with the updated panel and apply it again.
The panels to be changed are C1SD10NA, C1SD1000, C1SFA000, C1SFB000, C1SFC000, C1SF2000, C1SF3000, C1SF4000, C1SF5000, C1SF6000, C1SF7000 and C1SF9000. They are distributed in the CSIQPENU library and are SMP/E entries of type PNL
The change to be made is in the )INIT section of the panels. To revert to the old logic, the following lines need to be commented out:
IF (&ETMPCASE = ' ')
&VNTSCASE = 'Y'
&ETMPCASE = 'Y'