Flow Map Manual

Selecting Objects
Flow Map Host
3–6 098935 Tandem Computers Incorporated
2. Ensuring certain entities take part in Flow Map processing.
3. Overriding or modifying the effects of the EXCLUDE command.
An entity referenced by INCLUDE is added to any relevant PROGRAM or FILE object
and is subject to DISCARD and thresholds.
If an EXCLUDE statement excludes too many PROCESSes, you can include some
PROCESSes by using an INCLUDE statement in conjunction with an EXCLUDE
statement. In the following example, the PROCESS named $S1A, which is run from
the Program SERV1, is specifically included in a diagram:
INCLUDE PROCESS NAME $S1A
Using EXCLUDE Any item referenced in an EXCLUDE command is unconditionally excluded from
further processing. Entities are not tested for exclusion if they are referenced in
GROUP or INCLUDE statements. You can exclude whole sets of entities by name
using the EXCLUDE command. If, for example, a system has multiple applications
running and only one needs to be mapped, use the EXCLUDE statement. Below is a
sample EXCLUDE statement:
EXCLUDE PROCESS
PROGRAM $*.*.FEND1
$*.*.TCPA
$*.*.SERV1
This specifically excludes all programs with a filename of FEND1, TCPA, and SERV1
from this diagram. All TPDC PROCESSes with the appropriate PROGRAM-
FILENAME are effectively ignored.
Non-Referenced Entities Entities that are not referenced by GROUP, INCLUDE, or EXCLUDE statements and
have not been discarded as transient participate in further Flow Map processing.
These entities have their counters added to the relevant Processing and Database
objects, and the resulting Processing and Database objects are subject to threshold tests
if APPLY-THRESHOLDS is YES.
Thresholds Thresholds are applied at various stages of processing depending on the object. For
PROCESSes and DISKFILEs, thresholds are applied when the entities are first
processed, but the counters of these discarded entities are first added to their parent
objects, Programs or FILEs. Group, Program, and FILE thresholds are applied after all
entities are processed. These thresholds are applied whether or not the objects are
attached to groups.
An application may contain many busy components and many components that are
idle for most of the time. This situation represents what is often called the 80/20 Rule.
The rule states that typically only 20% of the components of an application account for
80% of the work. The core activities can be seen clearly if the idle components can be
excluded. This exclusion of idle components can be accomplished through the use of
THRESHOLD statements.