This section describes:
- The programming commands that are detected by the CICS® IA Collector and
what is reported for each type of command.
- The differences, if any, between what the Collector detects
and what the Load Module Scanner detects.
In general, the Load Module Scanner always
detects more, because it covers paths that might not get exercised
by the Collector,
and because it cannot see beyond the command argument 0 to eliminate
EXEC CICS commands that do
not cause dependencies or affinities.
Note: - In all cases, the Load Module Scanner reports
only the verbs detected, without the resource name or, where appropriate,
the SYSID.
- For some commands, the Collector does
not store the resource name. For example, on an EXEC CICS FEPI CONVERSE DATASTREAM CONVID command,
when the dependency is between a FEPI program and a FEPI conversation,
the Collector does
not store the ID of the conversation, because of its transitory nature.
When the resource name is not stored, the command is not saved in
the DB2® tables in the Dependency
database objects. The command is, however, reported by the Reporter.
This section contains these topics: