Endevor C1DEFLTS table names the MCF datasets that hold the control data for each stage defined in the table.
Given an MCF dataset, would it be possible to determine to which stage it corresponds?
Each MCF dataset contains a 'stage record' which is populated with information from the C1DEFLTS table the very first time that endevor opens the MCF. Printing that record shows information that may help to relate the MCF dataset with its C1DEFLTS table.
First step would be to print the stage record, which has a record key of 28 blanks (X'40'). This can be done, for example, with the IDCAMS utility:
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
PRINT IDS(your.MCF.dataset.name) -
FROMKEY(' ') -
COUNT(1) -
DUMP
/*
The stage record contains the following information in the following columns:
The above list refers to previous stage, current stage and next stage. Their meanings depend on whether the stage to which the MCF being listed belongs is stage 1 or stage 2 in its environment.
In both cases, "current stage" means the environment to which the MCF belongs, and then:
The below example corresponds to IDCAMS PRINT of the MCF datasets belonging to the 2 stages of the same environment:
1IDCAMS SYSTEM SERVICES TIME: 10:35:29 03/17/23 PAGE 2
-LISTING OF DATA SET -PUBLIC.I3382506.STG1.MCF
0KEY OF RECORD - 40404040404040404040404040404040404040404040404040404040
000000 40404040 40404040 40404040 40404040 40404040 40404040 40404040 40404040 * *
000020 40404040 40404040 40404040 40404040 40404040 40404040 40404040 40404040 * *
000040 40404040 40404040 40404040 40404040 E2E3C7F1 40404040 D7E4C2D3 C9C34BC9 * STG1 PUBLIC.I*
000060 F3F3F8F2 F5F0F64B E2E3C7F1 4BD4C3C6 40404040 40404040 40404040 40404040 *3382506.STG1.MCF *
000080 40404040 E2E3C7F2 40404040 D7E4C2D3 C9C34BC9 F3F3F8F2 F5F0F64B E2E3C7F2 * STG2 PUBLIC.I3382506.STG2*
0000A0 4BD4C3C6 40404040 40404040 40404040 40404040 40404040 F1E2E3C1 C7C540F1 *.MCF 1STAGE 1*
0000C0 40404040 40404040 40404040 40400028 40404040 40404040 40404040 40404040 * .. *
0000E0 40404040 40404040 40404040 40404040 40D7E4C2 D3C9C34B C9F3F3F8 F2F5F0F6 * PUBLIC.I3382506*
000100 4BC5D3D4 C3C1E3D3 40404040 40404040 40404040 40404040 40404040 40 *.ELMCATL *
0IDC0005I NUMBER OF RECORDS PROCESSED WAS 1
1IDCAMS SYSTEM SERVICES TIME: 10:35:29 03/17/23 PAGE 4
-LISTING OF DATA SET -PUBLIC.I3382506.STG2.MCF
0KEY OF RECORD - 40404040404040404040404040404040404040404040404040404040
000000 40404040 40404040 40404040 40404040 40404040 40404040 40404040 E2E3C7F1 * STG1*
000020 40404040 D7E4C2D3 C9C34BC9 F3F3F8F2 F5F0F64B E2E3C7F1 4BD4C3C6 40404040 * PUBLIC.I3382506.STG1.MCF *
000040 40404040 40404040 40404040 40404040 E2E3C7F2 40404040 D7E4C2D3 C9C34BC9 * STG2 PUBLIC.I*
000060 F3F3F8F2 F5F0F64B E2E3C7F2 4BD4C3C6 40404040 40404040 40404040 40404040 *3382506.STG2.MCF *
000080 40404040 40404040 40404040 40404040 40404040 40404040 40404040 40404040 * *
0000A0 40404040 40404040 40404040 40404040 40404040 40404040 F2E2E3C1 C7C540F2 * 2STAGE 2*
0000C0 40404040 40404040 40404040 40400028 40404040 40404040 40404040 40404040 * .. *
0000E0 40404040 40404040 40404040 40404040 40D7E4C2 D3C9C34B C9F3F3F8 F2F5F0F6 * PUBLIC.I3382506*
000100 4BC5D3D4 C3C1E3D3 40404040 40404040 40404040 40404040 40404040 40 *.ELMCATL *
0IDC0005I NUMBER OF RECORDS PROCESSED WAS 1