The example is a standard set up the BC1TNEQU table. This set up will check 2 datasets. The first check (standard) will check the Environment, System and Subsystem. The Second check (extension) will check the action.
For example:
NAMEQU ACTION_INITIATION,
L1=('C1'),
L2=(ENVIRONMENT),
L3=(SYSTEM),
L4=(SUBSYSTEM)
NAMEQU ACTION_INITIATION,
L1=('C1'),
L2=(MENUAUTH)
I would like to limit who can add, delete, etc to a specific stage of Endevor. How can I do this?
You can add the stage to the second "NAMEQU ACTION_INITIATION" as follows.
NAMEQU ACTION_INITIATION,
L1=('C1'),
L2=(STAGEID),
L3=(MENUAUTH)
This would change the second check to include the stage id. So if the actions was ADD and the stage ID is P, the dataset built would be C1.P.ADD
Note: When adding in the L2, the stage ID may be numeric. If it is, it is not a valid dataset qualifier. An alternative would be to use STAGENAME or add a character to the beginning as follows:
NAMEQU ACTION_INITIATION,
L1=('C1'),
L2=('S',STAGEID),
L3=(MENUAUTH)