Endevor issues error message about stage 2 while doing an add/update at a stage 1.
Article ID: 124426
Updated On:
Products
Endevor
Endevor Natural Integration
Endevor - ECLIPSE Plugin
Endevor - Enterprise Workbench
Issue/Introduction
A user adds an element to stage 1 but the action fails with Error
"THIS TYPE HAS NOT BEEN DEFINED AT STAGE stage-id WITHIN SYSTEM system-id "
The stage stage-id is the stage 2 where the type is not defined.
The stage 2 is not intended for recording element, then no type has been defined, all element will be stored in stage 1 only.
"THIS TYPE HAS NOT BEEN DEFINED AT STAGE stage-id WITHIN SYSTEM system-id "
The stage stage-id is the stage 2 where the type is not defined.
The stage 2 is not intended for recording element, then no type has been defined, all element will be stored in stage 1 only.
Environment
All Endevor version
Cause
When the entry stage is 1, any type must be defined in both stages, i.e. 1 and 2.
Resolution
It is mandatory to define all types in stage 2 even you don't need this stage.
If you are using single-stage environments, it is possible to define the type in stage 2 only. To do so, define the stage 2 as the entry stage for the environment by coding the C1DEFLTS with parameter ENTRYSTG#=2.
But, if the stage 1 has already been populated and need the stage 2 to not be updated by any action from stage 1(Move or Transfer actions), ESI can be activated to protect the stage 2. But all type have to be defined in stage 2 anyway.
As a bypass, for the time required to implement ESI, you can define the type in stage 2 and define Base and Delta with a non allocated dataset.
This way, if a user tries to move or transfer an element from stage 1 to stage 2, Endevor will issue an error message C1E0116E and the move won't be performed. This is suggested as a temporary/transitional solution.
If you are using single-stage environments, it is possible to define the type in stage 2 only. To do so, define the stage 2 as the entry stage for the environment by coding the C1DEFLTS with parameter ENTRYSTG#=2.
But, if the stage 1 has already been populated and need the stage 2 to not be updated by any action from stage 1(Move or Transfer actions), ESI can be activated to protect the stage 2. But all type have to be defined in stage 2 anyway.
As a bypass, for the time required to implement ESI, you can define the type in stage 2 and define Base and Delta with a non allocated dataset.
This way, if a user tries to move or transfer an element from stage 1 to stage 2, Endevor will issue an error message C1E0116E and the move won't be performed. This is suggested as a temporary/transitional solution.
Feedback
Yes
No
Powered by
