Use the Region Configuration Menu panel
CIU200 to specify the API and SPI commands to be monitored.
These two types of dependency-related CICS® commands can be collected:
- To specify which API commands are to be monitored on a particular CICS region, type action code 3 at
the top of the Resource Options panel, CIU290,
shown in Figure 1. Press
Enter.
The CICS Resources Options panel, CIU240,
shown in Figure 1, is displayed.
- To specify which SPI commands are to be monitored on a particular CICS region, type action code 4 at
the top of the Resource Options panel, CIU290,
shown in Figure 1). Press
Enter.
The CICS Resources Options panel, CIU245,
shown in Figure 2, is displayed.
Note: - If you specified ALL on the Region Configuration
Menu, the initial values of the fields on the CICS Resources
Options panel are set to those of the first "real" CICS region listed on the Region
Configuration Menu; that is, the values are taken from the first region
listed after the special ALL and DEFAULT applids.
Both the CICS APPLID and the
SYSID are shown as ALL.
- If you specified DEFAULTS on the Region
Configuration Menu, the initial values of the fields on the CICS
Resources Options panel are the defaults, taken from the CICS IA control
file, CIUCNTL.
The CICS APPLID is shown as
DEFAULTS and the SYSID as DFTS. Any changes that you make are saved
in the control file and become the new default values.
If you are
editing the DEFAULTS record, you must specify Y or N in
each field. You cannot specify a blank.
Figure 1. Collector CICS Resources Options panel, CIU240CIU240 CICS Interdependency Analyzer for z/OS - V5R1M0 2012/08/25
CICS Resources Options for 03:32:45PM
CICS Sysid :____ CICS Applid : ________
Modify the options and press Enter to update, or F12 to Cancel.
Detect command types Y=Yes, N=No 1
D=Yes+Detail, ( Only for API types marked with * ) 3
APIs 2
*Programs . . . _ *Files . . . . _ *Transactions . _ Task Control . _
Presentation . _ *TS Queues . . _ *TD Queues . . _ Journals . . . _
DTP . . . . . _ Counters . . . _ FEPI . . . . . _ *WEB Services . _
*Exits. . . . . _ Others . . . . _ *EVENTS . . . . _ ATOMServices . _
XMLtransform . _ WSAddressing . _
CICS Sysid: ____ CICS Applid: ________ TermID: ____
F1= F2= F3=Exit F4= F5= F6=
F7= F8= F9= F10= F11= F12=Cancel
- 1 Detect command types
- This option determines whether the Collector is
to monitor each of the types of dependency-related API command listed.
For each type of API command that you want the Collector to
monitor, type Y. For each type of API command that
you do not want the Collector to
monitor, type N or, to use the default value in the CICS IA control
file, specify a blank. When the control file is first created, the
system default value for each command is Y (Yes),
but you might have modified it since.
Note: If you are editing the
DEFAULTS record, you must specify Y or N in
each field. You cannot specify a blank.
- 2 APIs
The groups of CICS API
commands that can be monitored.
The commands are listed
by groups on the panel. The individual API commands that make up each
group are listed in
Dependency-related CICS API commands detected by the CICS Interdependency Analyzer.
The individual EXEC CICS FEPI
commands that make up the FEPI API group are listed in
CICS FEPI API commands.
Note: When collecting Command
Flow data for CICS TS V2.2
or earlier, set the TD Queues option to N so
that CICS IA collects
the Transient Data queue commands correctly. If the TD Queue flag
is not set to N, the results are unpredictable.
- 3 D=Yes+Detail option
- You can use option D only for the API
types marked with an asterisk.
Figure 2. Collector CICS Resources Options panel, CIU245CIU245 CICS Interdependency Analyzer for z/OS - V5R1M0 2012/08/25
CICS Resources Options for 03:32:45PM
CICS Sysid :____ CICS Applid : ________
Modify the options and press Enter to update, or PF12 to Cancel.
Detect command types Y=Yes, N=No 1
SPIs (Create/Inquire/Set/Discard/Perform) 2
Programs . . . _ Files . . . . _ Transactions . _ Temp Storage . _
Transient Data _ DB2 . . . . . _ DJAR . . . . . _ BRFacility . . _
Corbaserver . _ TCPIPService . _ FEPI . . . . . _ Journals . . . _
Library. . . . _ IPCONN . . . . _ BTS preoc . . _ Bundles. . . . _
ATOMServices . _ CSD. . . . . . _ XMLTransform . _ MQCONN . . . . _
JVMServer. . . _ Terminals. . . _ CICS System . _ Tasks . . . . _
DUMPs . . . . _ VTAM Conn. . . _ Statistics . . _ Tracing . . . _
SHUTDOWN . . . _
CICS Sysid: ____ CICS Applid: ________ TermID: ____
F1= F2= F3=Exit F4= F5= F6=
F7= F8= F9= F10= F11= F12=Cancel
- 1 Detect command types
- This option determines whether the Collector is
to monitor each of the types of dependency-related SPI command listed.
For each type of SPI command that you want the Collector to
monitor, type Y. For each type of SPI command that
you do not want the Collector to
monitor, type N or, to use the default value in the CICS IA control
file, specify a blank. When the control file is first created, the
system default value for each command is Y (Yes),
but you might have modified it since.
Note: If you are editing the
DEFAULTS record, you must specify Y or N in
each field. You cannot specify a blank.
- 2 SPIs
The groups of CICS SPI
commands that can be monitored.
The individual SPI commands
that make up each group are listed in CICS SPI commands.
The individual EXEC CICS FEPI
commands that make up the FEPI SPI group are listed in Dependency-related CICS FEPI SPI commands detected by the CICS Interdependency Analyzer.
For more information about restrictions affecting the monitoring
of commands that might cause dependencies or affinities,
see What is not monitored and Details of dependencies and affinities collected.