Build the resource side of the CRUD matrix

Report which programs and jobs reach each file, queue, DB2 table, data set and IMS segment, one row per resource and program carrying the letters of everything done to it. This is the matrix FindResourceCrud and FindBatchCrud build, turned on its side: theirs answers what one program touches, this one answers who else touches a store, which is the question asked before a file is changed or retired. The same rows are pivoted rather than the portfolio being read again, so a VSAM file read through CICS in one program, read natively in another and allocated by a job under its real data set name is three rows about one store — and every segment a DL/I call names carries its own letters, the last one written and the ones above it read to reach it.