Read the schema the DDL creates, and who reaches each table

Record the DB2 schema the portfolio creates: each table with its columns, primary key, foreign keys and indexes, anchored at the member and line it is created on, from both places DDL is written — a member of a DDL library, and the SYSIN stream of the job that submits it. The summary joins each table to the programs whose EXEC SQL names it and to the packages and plans those programs are bound into, an unqualified name resolved against the qualifier its package was bound with, and a foreign key becomes a relationship between the two tables so the model diagram is the same graph everything else is drawn from. FindDb2Catalog answers the same question and marks each statement in the source; this one produces the tables and changes nothing.