Quickedit rejects lowercase element names after upgrade and fall back
Article ID: 121358
Updated On:
Products
Issue/Introduction
Quickedit may reject element names containing lowercase characters with error message ENDE018E The element name specified is invalid having the short form message (in the upper right corner of the screen): Invalid Element Name. The element name needs to be entered in uppercase so that Quickedit accepts it
This may happen after returning to release 17.0 (or 18.0 without fix RO92892 which introduces long-name element support) when the endevor upgrade has been fallback for whatever reason. It may also happen after testing the new release and returning to the old release. The condition is that both releases used the same ISPF applid and therefore the same ISPF profile member (normally CTLIPROF)
Before performing the upgrade and fallback, Quickedit turned the element name into upper case so the element name was accepted
Environment
Release: 17.0 and 18.0
Component: ENDBAS
Cause
This happens when the new release has set the selection for "Case-sensitive elm name' field to Y. This is done by default in the newer releases for performance reasons because case-insensitive searches degrade the performance of element searches so they are enabled only when explicitly selected by the user.
This setting is stored in the ISPF profile under variable EEVMIXEL. This variable is used in the old release even though it does not display in any panel and is normally set to N, which causes the element name to be turned into uppercase.
After the new release has set it to Y, the element name is no longer turned into uppercase so the error arises as the old release cannot accept element names containing lowercase characters.
Resolution
The simplest way to resolve this problem is to visit the 'dialog options' panel after fallback to the old release and hit enter. There is no need to update any field. Panel ENDIEO00 (the dialog defaults panel) has logic to unconditionally set the variable EEVMIXEL to N in the ISPF profile which resolves the situation.
Since the ISPF profile is specific to the TSO user, this needs to be done by each user experiencing the problem
Feedback
