Find what runs a variable

Report every way a variable reaches the scheduler — the copybook that declares it, each program that uses it, the load module the program is bound into, the procedure and job step that run that module, and the Control-M definition that submits the job — and mark each source at the link it contributes. Six sources have to be joined to answer it and each holds only its own link: the copybook does not know its programs, the program does not know its module, the module does not know its job, and the job does not say when it runs. A chain that stops short is reported as far as it got, so a field that reaches no batch job is a row saying so rather than a gap. AnalyzeVariableChain answers the same question and changes nothing.