Dealing with Endevor message IMGR253E
Article ID: 14221
Updated On:
Products
Issue/Introduction
During normal operation, Endevor may check its inventory (composed by the element catalog and the MCF datasets) for different reasons, like checking that the element being added is not already present, or to enforce element name registration.
It might happen that these inventory checks raise the following error message which would cause the action to fail
IMGR253E SEGMENT FOUND WITH INVALID INVENTORY <environment>/<stageid>/<system>/<subsystem>
How to do to find and correct the problem?
Cause
This error indicates that incorrect information has been found in the Endevor element catalog (ELMCATL dataset)
This dataset contains one to several records for each combination of element name and type name
Each record contains from 1 to 5 'catalog segments', each one representing one occurrence of the element/type combination into a particular inventory location (represented by environment name, stage ID, system name and subsystem name)
Message IMGR253E means that, for the element being processed, a catalog segment has been found in ELMCATL naming a location that is not defined in the corresponding MCF.
This can happen for a variety of reasons, including but not limited to:
- NOT backing up/restoring catalog and all related MCF's together
- Removing non-empty environments from C1DEFLTS (that is, environments whose MCFs still contain element records)
- Changing the environment names and/or stage IDs in C1DEFLTS while the MCFs contain element records
Resolution
The first way to solve this error is to run BC1JCSYN job. This utility ensures that each and every catalog segment has a corresponding element record in the MCF and vice versa. If run in VALIDATE mode, it will simply report any discrepancies it finds. If run in UPDATE mode, it will update the ELMCATL file so that its contents is consistent with that of the MCF datasets.
The utility cannot fix this error when the element name and stage ID shown in the message do NOT match any stage defined in the C1DEFLTS table. The reason is that, in this case, it cannot identify what is the MCF to be checked in order to verify and eventually correct the element catalog. What is worse is that the utility cannot even detect this situation so that it will leave the corruption in ELMCATL without issuing any error message.
This situation may happen, for example, if an environment has been removed from the C1DEFLTS table while any of its MCFs still contained element records. These element records have corresponding catalog segments which cause the error but BC1JCSYN cannot detect them.
An indication of this situation would be that the environment name and stage ID shown in message IMGR253E does NOT match any environment defined in C1DEFLTS
If you can recall having removed the env/stage indicated in IMGR253E from C1DEFLTS, then a possibility is to temporarily add the environment to the table and run BC1JCSYN with the updated C1DEFLTS. The added environment needs to have two associated MCFs, but they may be empty (just created with IDCAMS DEFINE)
The last resort to correct this error is to rebuild the element catalog from scratch using job BC1JXCNV
Feedback
