Find what the run books document

Report what a documentation library says about the estate around it: one relationship row per name a run book member writes that the portfolio answers to, typed by what the name turned out to be, and one coverage row per program and job saying which member documents it. A run book is prose written in upper case, so a name-shaped token in it is any word of eight characters or fewer and no rule tells MASTER in a sentence from MASTER in a library: what makes a name a reference is looking it up among the members, data sets, tables, databases and load modules the portfolio holds, which is a join rather than something one member says. The row for what a member is about carries its shape — DOCJOB, DOCPGM, DOCFICH, DOCAPPL or DOCOPER — as the action metadata, so the component it documents can be told from a name it merely mentions. Both directions are findings as well: a program with no run book, which is worth knowing before touching the program, and a run book whose subject nothing answers to, which is a member a rename left behind. Every line writing a name that resolved is marked, which is what a reader is looking for in a page of prose.