After entering the event duration and type filters on the Transaction Trace screen, continue by entering the CICS or IMS filter criteria. You can skip this step if you do not want to restrict the trace generation to the mainframe system. If you want to generate traces from the front end distributed tiers, it is best to skip this step.
Note: The CICS and IMS filters are mutually exclusive.
Select the check box and enter the value for each filter as needed.
Filtered Property: Job Name or Server Name
Supported Trace Sources: CICS back-end traces that were invoked using CTG.
Value: The name of the server that was used to invoke the CTG call.
Filtered Property: Communication Method
Supported Trace Sources: CICS or IMS back-end
Value: Cross-process tracing into CICS or IMS is available for the front-end application that invoke the transaction through the following communication CICS or IMS methods.
Enter one of these methods:
The web services CA SYSVIEW tracer is installed on top of the Service-Oriented Architecture (SOA) tracer. A correlation ID with the front-end transaction trace is included so it can be matched up with the corresponding back-end trace from the mainframe.
Recommend filter criteria:
Select the minimum transaction duration, enter a numeric value, and then select a duration unit from the drop-down list.
Example: 5000 milliseconds
(Optional) Select URL of the application from the drop-down list and enter the URL.
Note: Remove the leading protocol specifier, computer name, and port number.
Example URL: /ExampleAppClientV6Web
The CTG CA SYSVIEW tracer includes a correlation ID with the front-end transaction trace that can be associated with the corresponding mainframe back-end trace.
Recommend filter criteria:
Select the minimum transaction duration, enter a numeric value, and then select a duration unit from the drop-down list.
(Optional) For CTG front-end traces with Program Name and Transaction Name properties, select CICS Program Name CTG equals and enter the program name or transaction name.
Note: CTG front-end traces never have server name, web service name, or microsecond lifetime properties. If these properties are entered in the filter criteria, no front-end traces appear in the Trace Viewer.
The traces into the MQ Series do not use correlation IDs, so the front-end and back-end correlation cannot be made using this correlation ID. Instead, the correlation is done using a preexisting MQ message ID and MQ correlation ID.
Recommend filter criteria:
Select the minimum transaction duration, enter a numeric value, and then select a duration unit from the drop-down list.
This filter restricts the display to those transactions that run longer than the specified time.
Example: 5000 milliseconds
Note: The IBM Websphere MQ Connectors and Messaging System Extension tracer is used as the MQ series front-end tracer.
The HTTP CA SYSVIEW tracer includes a correlation ID with the front-end transaction trace that can be associated with the corresponding mainframe back-end trace.
Recommend filter criteria:
Select the minimum transaction duration, enter a numeric value, and then select a duration unit from the drop-down list.
Example: 5000 milliseconds
(Optional) Select CICS/IMS Communication Method equals HTTP.
(Optional) Select URL of the application from the drop-down list and enter the URL. Be careful when using the URL because it is specific to the tier being traced. If used, set the URL of the servlet of first tier of the application that has an installed HTTP tracer.
Note: Remove the leading protocol specifier, computer name, and port number from any URL.
Example Servlet URL: /HTTPTest/servlet/FrontEndClient
Example CICS URL: /CICS/CWBA/DFJ$JWB1
The front-end application used the IMS Bridge Queue to invoke the IMS transaction.
The MQ IMS Adapter was used to get the MQ message that was sent from the front-end application.
Filtered Property: Program Name
Supported Trace Sources: CTG front-end; CICS back-end
Value: The name of the program that was executed on the CICS region.
Filtered Property: Transaction ID
Supported Trace Sources: IMS back-end
Value: The transaction name.
Filtered Property: Job Name (Dependent Region)
Supported Trace Sources: IMS back-end
Value: IMS-dependent region job name that processed the transaction.
Filtered Property: Web Service Name
Supported Trace Sources: Web Services front-end; CICS back-end
Value: Name of the web service that is used to execute this transaction. This property is applicable only to web service transaction tracers.
Filtered Property: Microsecond Lifetime
Supported Trace Sources: CICS or IMS back-end
Value: The transaction lifetime in microseconds
Minimum value: One microsecond
Filtered Property: Transaction Processor
Supported Trace Sources: CICS or IMS back-end
Value: The transaction processor that ran the transaction.
Filtered Property: PSB Name
Supported Trace Sources: IMS back-end
Value: The PSB name that is associated with the transaction.
Filtered Property: Transaction Name
Supported Trace Sources: CTG front-end; CICS back-end
Value: Name of the transaction on the CICS region.
The CICS/IMS filters are set. Proceed to setting the trace duration and agents filters.
|
Copyright © 2013 CA.
All rights reserved.
|
|