Find the plans and packages the bind decks declare

Report the chain a bind deck writes down and mark every card that writes it: the plan, the packages its PKLIST may run, the collection each package lands in, the DBRM it is bound from and the program that DBRM was precompiled from, with the job whose step reads the deck. Nothing else in an estate holds the chain — the COBOL never names its package and the JCL never names its plan — and a deck bound in the job stream is read as one too. A second table reads the same binds from the package's side, so that which plans may run a package is a lookup rather than a search: a plan lists either the package outright or its whole collection with *, and only expanding the second says what a package change reaches. AnalyzeBindChain answers the same question and changes nothing.