Find every data set the portfolio names

Report each data set as a component of its own — what kind of file it is, the control card member whose IDCAMS DEFINE creates it, the jobs that allocate it new, and how many jobs, steps and programs touch it — and mark the DD cards and the DEFINE commands that make one. A data set is the one component of an estate with no source file: nothing declares it, the JCL names it on a DD without saying where it came from, and the COBOL names only the DD, so the object is built by joining all three. Two more tables come out of the same join: who touches each file, a row per job and program rather than a list in a cell, because a file an installation shares has hundreds of them; and the chain each file goes through in order, from the card that defines it through the job that creates it to the jobs that read it, ordered by what the dispositions say and by the order the Control-M conditions run the jobs in. AnalyzeDataSets answers the same question and changes nothing.