Identify datasets related to Endevor

Products

• Endevor

Issue/Introduction

Given a C1DEFLTS table that defines an 'Endevor' (that is, a set of Endevor environments with their control datasets), is there any way to find out all the datasets related to this 'Endevor'?

Resolution

The datasets that relate to endevor fall into 3 categories

• Control datasets
• Libraries mentioned in type definitions (base, delta, source output and include)
• Datasets accessed by processors

Even though Endevor does not provide a comprehensive report, It is possible to obtain the names of the datasets for each one of the categories

1 - Control datasets

The control datasets are named in the C1DEFLTS table and print as part of the Endevor options report which is printed to ddname EN$TROPT if it is found to be allocated during Endevor initialization.

To take this report, run any Endevor batch job with //EN$TROPT DD SYSOUT=*,SPIN=NO added to the JCL step that runs program NDVRC1

To take the report with ISPF Endevor or Quickedit, the steps are:

• Get out of Endevor or logoff/logon
• TSO ALLOC FI(EN$TROPT) SYSOUT(X) SPIN(NO)
• Get into Endevor or quickedit up to the first panel and get out
• Find the report printed to ddname EN$TROPT among the JES2 outputs from the TSO session

The Endevor control datasets include

• Element Catalog
• Element Catalog Eindex
• Package Control File
• Endevor Macro Library
• CCID Validation Data Set (if used)
• ACM Query Root Data Set
• ACM Query Xref Data Set
• Admin Action Log Data Set (if used)
• Global Control File (if used)
• Endevor Parmlib Data Set
• Master Control file (MCF) for each stage 

Apart from the control datasets, the options report prints the site symbols table. The symbols in the table may be referenced in the dataset names in the type definitions and processors

2 - Libraries in type definitions

The DSNs are stored in the type definition records in the MCF datasets for each stage. They may be reported via standard Endevor report CONRPT07 (system definition profile)

Another option would be to use the LIST TYPE function of the CSV utility to extract a comma-separated list of the Endevor type definitions, which includes the libraries related to each type. This list may be later loaded into an Excel spreadsheet or you could format a report using the Endevor table tool utility ENBPIU00

Yet another option would be to specify OPTIONS NOCSV to extract a flat file and use whatever reporting tool available onsite with it. The flat file is mapped by the response structure of the LIST TYPE function of the Endevor API, distributed in copybooks ENHALTYP (assembler) and ECHALTYP (cobol)

The libraries that may be mentioned in a type definition are

• Base library
• Delta library
• Source Output library (optional)
• Include library (optional)

3 - Datasets accessed by processors

This is the hardest part. Endevor does not maintain information about these datasets. They are just mentioned in DD statements in the processors. To locate them, you can scan the processors for string DSN=. 

You can use Endevor search functions to scan the processors (which are stored in Endevor under type PROCESS). Alternatively, if the type PROCESS is defined with reverse delta format, you could scan directly the base library mentioned in the definition of type PROCESS