Wildcard Behavior Change in Endevor V18 Batch ADD

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench

Issue/Introduction

Under v17, the Element Name field could be wildcarded (e.g. XXX*). Wildcarding this way is not allowed under v18. Why?

This was/is a tremendous time-saver over having to select one element at a time to ADD.

PF1 expanded message:
 DISPLAY LIST OPTION "N" OR NAME MASKING NOT ALLOWED ON "TO" FIELDS. 

Environment

z/OS
CA Endevor V18

Resolution

Wildcarding is still allowed in the Member field in the  FROM ISPF LIBRARY:  section --

FROM ISPF LIBRARY:             
  PROJECT     ===> hlq         
  LIBRARY     ===> mlq         
  TYPE        ===> library     
  MEMBER      ===> a*          
                               

Or in the FROM OTHER ISPF DATA SET: section -- 

FROM OTHER ISPF DATA SET:                   
  DATA SET    ===> 'hlq.mlq.your.other.libr(a*)'