Updating an element and getting IMGR275E error - why is this error issued and how can it be resolved. : 

ELEMENT --   TYPE    NS ENVIRON  S SYSTEM   SUBSYS   VVLL PROCGRP  CUR DTE  

DCPST70      DB2CARD    NEWPROD  P NSECOMP  PRINTDOC 0101 NOGEN    28AUG19  

DCPST70      COBMVS     NEWPROD  P NSECOMP  STATMENT 0101 CB3NB    18OCT19  

C1G0202I  ACTION #1 / STMT #2                                                   

C1G0203I     ADD      ELEMENT DCPST70                                           

C1G0205I        FROM DSNAME:  CMT0.LOC.STMT.SETUP.DB2.CONTROL                   

C1G0204I        TO   ENVIRONMENT: DEVL     SYSTEM: NSECOM5  SUBSYSTEM: PRINTDOC 

C1G0232I        OPTIONS:  OVERRIDE SIGNOUT, UPDATE                              

C1G0232I                  CCID: TEST                                            

C1G0232I                  COMMENT: TEST                                         

IMGR257E  REG. ERROR: ELEMENT NAME ALREADY EXISTS AT:                           

C1G0506I     ENV: NEWPROD  SYS: NSECOMP  SBS: STATMENT  STGID: P  TYPE: COBMVS  

C1G0277I  ADD PROCESSING TERMINATED BECAUSE OF THE PREVIOUS ERROR               

C1G0200I  ELEMENT ACTION REQUEST PROCESSING COMPLETED, HIGHEST ENDEVOR RC WAS 00

END OF EXECUTION LOG - HIGHEST ENDEVOR RC = 0012                                

Release : 18.0 18.1

Component : CA Endevor Software Change Manager

IMGR257E  REG. ERROR: ELEMENT NAME ALREADY EXISTS AT:                           

C1G0506I     ENV: NEWPROD  SYS: NSECOMP  SBS: STATMENT  STGID: P  TYPE: COBMVS  

This is an element registration error, based in the system definition that you sent for SYSTEM NSECOMP you have Duplicate Name check activated at the “E” Security Level.

The message states:

IMGR257E  REG. ERROR: ELEMENT NAME ALREADY EXISTS AT Env/Stage - System/Subsystem

Reason:  Registration error. A duplicate Element found in a non-mapped location.

Action:  Duplicates are not allowed. Change the Element name.

Based on the scenario that a  batch job is showing an update to element DCPST70 at

  ENV: DEVL   SYS: NSECOM5 SUBS: PRINTDOC TYPE: DB2CARD                                                                                                                                           

The "E" level of duplicate name checking at the system level only allows one occurrence of an element name within the system.  Because the element already exists in subsystem STATEMENT (based on the error message), it is not allowing you to add/update in SUBSYSTEM PRINTDOC.

If you need both element, the way to lower the severity of the duplicate name checking at the system definition to C or W.  

IMPORTANT: Element registration settings in the system definition panel need to be kept consistent in all the stages where the system is defined. Otherwise element registration may behave in an unpredictable way. 

Based on the settings the error message you are receiving is correct. To review more information on Element registration please take a look at the documentation:

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/18-0/using/ca-endevor-quick-edit-option/operating-information/element-registration.html

Here is some information that may help you to better understand the options you have chosen:

DUPLICATE ELEMENT NAME CHECK IS ACTIVE  

Specifies whether the Element name registration feature is active.

 The following option applies to this clause:

• ERROR SEVERITY LEVEL

Specifies the message severity level for messages that result when errors are found during an Element name registration check. This clause is only valid if the Define System statement includes the clause DUPLICATE ELEMENT NAME CHECK IS ACTIVE

• . Valid values are:
  • W - Warning
  • C- Caution
  • E- Error - The default, if this clause is omitted.

DUPLICATE PROCESSOR OUTPUT TYPE CHECK IS ACTIVE  

Specifies whether the duplicate Processor output type check is active.

• If active, Endevor compares Element names across types and Processors groups for the same Processor output type. A conflict occurs if a user attempts to add or create an Element and an Element with the same name and Processor output Type exists in the same System, with a different Type.

The following options apply to this clause:

• ACROSS SUBSYSTEMS
  • Specifies whether the check extends to the Subsystems defined to this System. This clause is only valid if DUPLICATE PROCESSOR OUTPUT TYPE CHECK IS ACTIVE
• ERROR SEVERITY LEVEL
  • Specifies the message severity level for messages that result when errors are found during a duplicate Processor output Type check. This clause is only valid if the Define System statement includes the clause DUPLICATE PROCESSOR OUTPUT TYPE CHECK IS ACTIVE
• Valid values are:
  • W- Warning
  • C- Caution
  • E- Error - The default, if this clause is omitted.