Using Oracle TSAM Plus Console

This chapter contains the following topics:

•

Overview

•	Using Oracle TSAM Plus Console

Overview

The Oracle TSAM Plus monitoring console allows you to specify the Oracle Tuxedo components you want to monitor, as well as track events and alerts. The console has six major sections:

•	User Accessibility

•	Top Menu Bar

•	Component Tree

•	Search Panel

•	Domains Dashboard

•	Using Oracle TSAM Plus Console

Note:

To get the best experience and full functionality of Oracle TSAM Plus Console, Oracle recommends you use the following Web browsers:

•	Internet Explorer 7 and later versions.

•	Firefox 4, 5, 7, 8, and later versions.

User Accessibility

User accessibility settings can be adjusted from the log-in screen and the console page.

•	Log-in Screen

In the upper left-hand corner of the log-in screen, click the Settings drop-down menu. You can select the following three options; the settings take effect immediately:

•	I use a screen reader

Accessibility-specific constructs are added to improve screen reader behavior.

•	I use high contrast colors

Application display uses high-contrast instead of the default contrast.

•	I use large fonts

Application display uses large fonts instead of the default size fonts.

•	Console Page

In the upper right-hand corner of the Oracle TSAM Plus Console page, click Accessibility; the Accessibility Preferences page appears. It has the same three user accessibility options as the log-in screen.

When you have selected your options, click OK; the settings take effect immediately.

Top Menu Bar

The top menu bar contains the following Oracle TSAM Plus monitoring console functionality:

Policy: Define and manage system policies.

Tuxedo Metrics: Query Oracle Tuxedo monitoring metrics.

Tuxedo Application Runtime Metrics: Query Oracle Tuxedo Application Runtime monitoring metrics.

Load Generator: Create the replay definition from call paths.

Management: Define user management, data management, global parameter settings, and blackout.

Alert: Define and query alerts.

Help: On-line help page.

Component Tree

Tuxedo Domains Component Tree

Tuxedo Domains tree displays the Tuxedo Domain Group -> Domain -> Machine -> Group -> Server -> Service hierarchy information.

All service nodes are hidden in the Tuxedo Component Tree by default. You can click Show Service () to display them.

By default, the component tree displays the first domain. You can specify the domain to be displayed in the component tree from the Domain list. Your preference is remembered until the selected domain does not exist anymore.

The domain structure in the component tree and relevant pages will not automatically change after you logged in. Click Refresh () to display the current domain structure.

In the component tree, different icon colors indicate different nodes status:

•	Green: the domain and all its components are active

•	Yellow: at least one child node under current node is in inactive or unhealthy status

•	Red: the domain or component is inactive

Particularly, if an alert icon arises, it indicators the domain contains unread alerts.

You can filter the component tree to display only domains with unread alerts or inactive components, domains in particular group, or particular domain using the Domain list.

You can view the overall status for all domains, a Tuxedo domain group, or a Tuxedo domain by clicking corresponding node in the component tree. For more information, see Domains Dashboard.

CICS Regions Component Tree

CICS Regions tree displays the CICS Region -> CICS Transaction/CICS Terminals hierarchy information.

Besides hierarchy information, other information is displayed (such as Oracle Tuxedo version, Domain model, server status, etc.). Certain tasks (for example, Create Policy) can be performed directly on the tree nodes.

Batch Systems Component Tree

Batch Systems tree displays the JES application -> JES nodes -> Tuxedo JES servers hierarchy information.

Note:

Similar to the artjesadmin changeconcurrent command, the maximum concurrent job number can also be changed in TSAM Plus console. Right click ARTJESINITIATOR in the JES component tree, there is an menu item named Change Concurrent Jobs. If the server is active, the menu item is available. On this option is selected, a popup window appears with the current max concurrent job number displayed. Input a number between 1 and 32767, the concurrent job number is modified.

IMS Systems Component Tree

IMS Systems tree displays the IMS systems ->Tuxedo Domain ->Transactions/Programs hierarchy information.

IMS System Summary

In the IMS Systems tree, you can right-click the root node and select Summary to view the system summary page.

The ART IMS system summary page contains two panels.

IMS System Summary Table

The system summary table lists all the ART IMS systems (domains) currently monitored by TSAM Plus. Table 1‑1 describes each column:

 

Table 1‑1 IMS System Summary

Column Name	Description
Sysman Name	IMS system name. It is the first part string in the domain ID before the first ":" character. You can click the system name to go to the corresponding ART IMS Region Summary page.
Machine Names	The comma-separated list of all machine names in the domain.
Status	Domain status, Active or Inactive.
Last Start Time	The last startup time of the domain.
Number of Machines	Machine number in the domain.

IMS System Details Panel

When you select an IMS system line in the Summary table, the related system inforamtion is displayed in the Details panel below. The three tabs, MPP, BMP, and BMPT, represent three types of the ART IMS region monitored by TSAM Plus. The information shown for each region type are very similar. Table 1‑2 describes the MPP region type details.

 

Table 1‑2 MPP Region Details

Metrics		Description
Number of MPP Regions		The total number of MPP regions (ARTIMPP processes) in the domain.
Totals Since Startup	CPU Consumption	Total CPU consumption. The system and user CPU of all transactions since the system startup.
	System CPU	Total system CPU consumption of all transactions since the system startup.
	User CPU	Total user CPU consumption of all transactions since the system startup.
	Transaction Count	Total transaction count since the system startup.
Totals Since Last Hour	CPU Consumption	Total CPU consumption. The system and user CPU of all transactions in the last hour.
	System CPU	Total system CPU consumption of all transactions in the last hour.
	User CPU	Total user CPU consumption of all transactions in the last hour.
	Transaction Count	Total transaction count in the last hour.
Averages in the Last Hour	Transaction Time	The average transaction elapse time in the last hour (total transaction time / transaction count).
	Transaction CPU Consumption	The average transaction CPU time in the last hour (system and user CPU).
	Transaction System CPU	The average transaction system CPU time in the last hour.
	Transaction User CPU	The average transaction user CPU time in the last hour.
	Transaction Rate	The transaction count in each 15 minutes time window in the last hour.

IMS Region Summary

In the IMS Systems tree, you can right-click the domain node and select Summary to view the region summary page.

The ART IMS region summary page contains two panels.

IMS Region Summary Table

The IMS Region Summary table lists all the ART IMS regions (servers) currently monitored by TSAM Plus in this domain. Table 1‑3 describes each column:

 

Table 1‑3 IMS Region Summary

Column Name	Description
Region	The region name is in the format of "process name/group name/server id", for example, ARTIMPP/GROUP1/6 Note that each UBB server entry is considered as one region, no matter what MIN and MAX values are configured. One region can actually contains multiple server instances.
Region Type	The region type is one of the following values: • BMP (Batch-oriented): The process is ARTIBMP • BMP (Transaction-oriented): The process is ARTIBMPT • IFP: IMS Fast Path Region. The process is ARTIMPP, and "-p" is not configured in the CLOPT of the server. • MPR: Message Processing Region. The process is ARTIMPP, and "-p" is configured in the CLOPT of the server.
Status	Tuxedo server status, Active or Inactive.
Number of Servers	The started server instances number.
Last Start Time	The last server startup time.

IMS Region Details Panel

When you select an IMS region line in the Summary table, the related IMS region inforamtion is displayed in the Details panel below.

Table 1‑4 describes the metrics shown in the main area.

 

Table 1‑4 IMS Region Details

Metrics		Description
Totals Since Startup	CPU Consumption	Total CPU consumption. The system and user CPU of all transactions in this region since the server startup.
	System CPU	Total system CPU consumption of all transactions in this region since the server startup.
	User CPU	Total user CPU consumption of all transactions in this region since the server startup.
	Transaction Count	Total transaction count in this region since the server startup.
Totals Since Last Hour	CPU Consumption	Total CPU consumption, system + user CPU of all transactions in this region in the last hour.
	System CPU	Total system CPU consumption of all transactions in this region in the last hour.
	User CPU	Total user CPU consumption of all transactions in this region in the last hour.
	Transaction Count	Total transaction count in this region in the last hour.
Averages in the Last Hour	Transaction Time	The average transaction elapse time in the last hour (total transaction time / transaction count).
	Transaction CPU Consumption	The average transaction CPU time in the last hour (system and user CPU).
	Transaction System CPU	The average transaction system CPU time in the last hour.
	Transaction User CPU	The average transaction user CPU time in the last hour.
	Transaction Rate	The transaction count in each 15 minutes time window in the last hour.

Search Panel

Search component tree elements.

Domains Dashboard

When you log into Oracle TSAM Plus monitoring console, the Domains Dashboard is displayed with overall Tuxedo domains and domain groups metrics. It presents the following information:

•	Severity-level unread alert count. To read the alerts of a severity level, click the number after the level.

•	An aggregated view of all domains components availability. When clicking the inactive (red) part of a pie chart, a window is popped up showing all the inactive items in detail.

•	All domains and domain groups metrics charts

The metrics charts show the related metrics data captured in the selected time range. When you move the cursor over a data node, the data value is shown up. For the metrics data collection interval, you can set it from the Management-> Global Parameters page. For more information, see Global Parameters.

The domains dashboard always displays the first three metrics charts positioned in individual domain or domain group dashboard for a quick glimpse. By default, these charts are displayed with the data for all services in last 24 hours.

•	Throughput

The number of Tuxedo service calls per minute.

•	Response Time

The average response time (in microseconds) of Tuxedo service calls.

•	Failure Number

The number of Tuxedo service call failures per minute.

For the domain groups presented in the dashboard, you can manage them from the Management -> Domain Group Management page. For more information, refer to Domain Group Management.

From any domain or domain group dashboard, you can set the dashboard to refresh the data periodically by choosing the Auto Refresh box on the top and specifying the refresh interval from the list. The refresh interval you set affects all dashboard pages.

Note:

This feature is only available when Oracle database is used, and is not available if you are using Derby database.

Viewing Domain Group Dashboard

To view a domain group dashboard, click the domain group name in the dashboard or left component panel.

•	Unread Alerts

Displays severity-level unread alert count. To read the alerts of a severity level, click the number after the level.

•	Availability

Displays aggregated availability of all domains belonging to the group. When clicking the inactive (red) part of a pie chart, a window is popped up showing all the inactive items in detail.

•	Metrics Charts

The throughput, response time, and failure number charts are displayed with the data in last 24 hours by default. For any metrics chart, you can change the time range to show the chart from the drop-down list.

If you have set the chart to show metrics per service, you get multiple lines on the chart representing each selected service in different colors. You can hide or unhide certain services lines by checking or unchecking the short bar (-) icon before the desired services name under the chart.

You can also customize the charts in dashboard. For more information, refer to Customizing a Dashboard.

Click the group name on the top of the dashboard, you enter the domain group details page that presents the availability and the first three metrics charts of the domain group for each individual member domain. You can sort the domain list in ascending or descending order by the metrics selected in the Order By list.

To go further to view and edit individual domain dashboard, click the domain name. For more information, refer to Viewing Individual Domain Dashboard.

Viewing Individual Domain Dashboard

To view individual domain dashboard, click the domain name in any dashboard or left component panel.

•	Service Statistics

Click this link to enter the Service Statistics page, which shows you the last-time collected metrics data breakdown for each services.

You can filter the list to display desired services. Type the name keywords (case-insensitive) in the Filter textbox and click the button. You can input mulitiple keywords separated by commas, semicolons, or spaces.

You can also export the service statistics table as a CVS file by clicking Export to CVS.

To view detailed metrics data collected for a service, right-click the service row and select one of the time range:

•	24 Hours: displays the aggreated data of every collection interval in 24 hours.

•	7 Days: displays the aggreated data for every hour in the past six days.

•	31 Days: displays the aggreated data for every day in the past month.

•	Unread Alerts

Displays severity-level unread alert count. To read the alerts of a severity level, click the number after the level.

•	Availability

Displays availability of servers in the domain. When clicking the inactive (red) part of a pie chart, a window is popped up showing all the inactive items in detail.

•	Metrics Charts

The throughput, response time, and failure number charts are displayed with the data in last 24 hours by default. For any metrics chart, you can change the time range to show the chart from the drop-down list.

If you have set the chart to show metrics per service, you get multiple lines on the chart representing each selected service in different colors. You can hide or unhide certain services lines by checking or unchecking the short bar (-) icon before the desired services name under the chart.

You can also personalize the charts in dashboard. For more information, refer to Customizing a Dashboard.

Customizing a Dashboard

In a domain group or domain dashboard, you can chart metrics over any time period you choose, create your own charts to suit your need, and define the key services for regular monitoring. Click the Customize button in the upper right page to activate customization mode.

Note:

Any customization configuration made in the group dashboard does not affect the underlying domain dashboard definition and vice versa.

Defining Key Services

In many cases, you may want to monitor a fixed set of services regularly. You just need to define them as key services to avoid repeatedly specifying target services. The key services can then be used when you edit or create a chart.

To define the key services for a domain, click the Key Services in the upper right of the domain dashboard page and add the desired services to the left box.

To define the key services for a group, refer to Domain Group Management.

Editing a Metrics Chart

To customize the chart that appears, click Edit in any metrics chart field and define the parameters listed in Table 1‑5.

Table 1‑5 Metrics Chart Parameters

Options	Description
Chart Name	Specifies a name to identify the chart.
Service List	Specifies the services you want to monitor on the chart: • All Services • Key Services: The key services you defined before for regular monitoring purpose. For more information, refer to Defining Key Services. • Select Manually: Select particular services you want to monitor in the list.
Metrics	Specifies the metric chart type: • Throughput (per minute): Number of Tuxedo service calls per minute • Number of Successes (per minute): Number of success Tuxedo service calls per minute • Number of failures (per minute): Number of failed Tuxedo service calls per minute • Number of System Failures (per minute): Number of Tuxedo service calls with system failure per minute • Number of User Failures (per minute): Number of Tuxedo service calls with user failure per minute • Response Time (microsecond): Average Tuxedo service call response time • Wait Time (microsecond): Average Tuxedo service call wait time • Execution Time (microsecond): Average Tuxedo service execution time • CPU Time (microsecond): Average Tuxedo service CPU consumption time
Range	Specifies the time range to present the data on the chart. You can choose to display the data in: • Last Hour: the aggregation interval is every metrics collection interval • Last 24 Hour: the aggregation interval is every metrics collection interval • Last Week: the aggregation interval is one hour • Last 31 Day: the aggregation interval is one day By default, the chart presents data in last 24 hours.
Per Service	This option is available when Service List is not set to All Service. When selected, the chart shows lines of each service separately in different colors.
Chart Type	Specifies the chart type: Line, Bar, Area, Combination, or Line with Area.
Chart Size	Specifies the width of the chart.

Adding a Metrics Chart

You can create up to 12 new charts by clicking Add in the upper right page. For descriptions of parameters in the window that appears, refer to Table 1‑5.

 

Moving or Removing a Panel

You can move up, move down, or delete any chart by clicking related function buttons at the top of the chart field.

Only the top three charts positioned in an individual domain dashboard are presented in the group or all domains dashboard.

Using Oracle TSAM Plus Console

This section contains the following topics:

•	Monitoring Policy

•	Tuxedo Metrics Monitoring

•	CICS/IMS/Batch Management

•	User/Data Management

•	Alert Monitoring

Monitoring Policy

Oracle TSAM Plus provides comprehensive monitoring control of Oracle Tuxedo infrastructure behavior. Policy Management allows you to do the following:

•	Organize monitoring requirements into significant and useful monitoring policy solutions.

•	Manage monitoring policy (including import, export and usage tracking).

•	Define monitoring policy entries for Oracle Tuxedo components and dynamic conditions.

•	Selectively enable and disable real-time communication with monitored Oracle Tuxedo back-end components.

This section contains the following topics:

•	Tuxedo Monitoring Policy

•	CICS Runtime Monitoring Policy

•	IMS Runtime Monitoring Policy

Tuxedo Monitoring Policy

On the menu bar, click Policy and select Tuxedo Monitoring Policy from the drop-down menu; the Monitoring Policy List page appears. It displays the existing defined policies and allows you to view, add, edit, or delete policies. This section contains the following topics:

•	Monitoring Policy List Page

•	Create/Edit Policy Page

Monitoring Policy List Page

The Monitoring Policy List page allows you to create and manage the Oracle Tuxedo component monitoring policies.

Button Bar

Table 1‑6 lists the Monitoring Policy List button bar functions.

 

Table 1‑6 Monitoring Policy List Button Bar

Button	Description
View	From the drop-down menu, select the following: • Columns: Select the columns displayed in the table. • Detach: Displays the table in a separate window. • Reorder Columns: Change how the column order is displayed.
Add	Creates a new monitor policy. The maximum policy name character length is 255. Note: You can also add a new policy by right-clicking a Domain listed in the Oracle Tuxedo Components panel.
Delete	Deletes selected monitoring policies.
Enable	Enables selected monitoring policies.
Disable	Disables selected monitoring policies.
Edit	Edits selected monitoring policies.
Clone	Clones a new policy from a selected policy.
Import	Imports previously exported policies from a user-specified location.
Export	Exports selected policies in an .xml file to a user-specified location.
Refresh	Updates the policies displayed in the Policy List table.
Detach	Displays the table in a separate window.

Policy List Table

The Policy List table displays the following columns:

•	Select: Allows you to select all or individual policies.

•	Name: Displays the current policy names.

•	Status: Displays the policy status.

•	enabled: The corresponding request is sent to Oracle Tuxedo.

•	disabled: The corresponding request is not sent to Oracle Tuxedo.

Note:

Policy monitoring does not take effect until the impacted Oracle Tuxedo processes have started.

•	Domain ID: Displays the domain identifier attached to the policy as follows: DOMAINID:Master:IPCKEY.

•	Tuxedo Components: String that represents policy impact scope of Tuxedo resources in selected domain. It is FML32 boolean expression compliant. For example: (TA_PMID%%'.*BOXBANK*') indicates using an FML32 boolean expression for machine selection.

Policy for PeopleSoft Domains

TSAM Plus provides out-to-box policies for monitoring Oracle PeopleSoft Applications. The PeopleSoft domain is displayed different from common Tuxedo domains in the list. Its Domain ID is separated by three colons, e.g. APPDOM_217989:LOCALHOST.COM:PS_DOMAI:PS. To monitor PeopleSoft domains, select the policy and click Enable.

Create/Edit Policy Page

The Create/Edit Policy page contains the following sections:

•	Tuxedo Component Panel

•	Monitoring Policy Panel

Tuxedo Component Panel

The Tuxedo Component panel contains the following selections:

•	Domain: Required.

•	Machine: Optional.

•	Group: Optional.

•	Server: Optional.

Machine, Group, and Server can also accept FML32 boolean expressions. Click the radio button to select an input method (from the drop-down list or manually enter an FML32 boolean expression). The value of each level is determined by its parent level (except for Domain).One monitoring policy must be specified for one domain.

Monitoring Policy Panel

The Monitoring Panel contains the following tabs:

Call Path Tab

Service Tab

XA Transaction Tab

Domain Gateway Tab

BRIDGE Tab

GWWS Tab

To use the listed tab options, click the Enable check box. If enable is not selected, all tab options are disabled. One monitoring policy can contain multiple monitoring categories.

Call Path Tab

Table 1‑7 lists the Call Path tab options.

 

Table 1‑7 Call Path Tab Options

Options	Description
Basic Policy Options
Enable	Enables/disables call path monitoring. Note: The fist policy deployed to the Tuxedo domain takes effect when there are more than one policies enabled on a Tuxedo target. The fist policy attributes, such as extended, bridge decode, affect the whole call path.
Ratio/Interval	Selects Ratio or Interval policy. If multiple policies cover one initiator process and the ratio or interval policy are different, the smaller value is used. Applies to other monitoring policy definitions as well. • Ratio: Accepts a value range of 1-65535. It indicates that monitoring starts for a certain number of requests. The default value is “1” (indicating each request is monitored). • Interval: Accepts a value range of 1-65535. It indicates a period of time (in seconds) that monitoring can be started. It is exclusive of ratio settings. The default value is “1”. The ratio/interval control only applies to the call path initiator.
Alert Only	Specifies alert evaluation only. No metrics are sent to manager.
Bridge Decode	Allows all BRIDGEs in the call path to decode messages. By default, BRIDGEs do not decode messages and the call path representation does not show BRIDGE points. Note: Use this option carefully. Decode/encode impacts application performance.
Enable Extended Monitoring	When this option is enabled, the extended monitoring data reported by the tsambegin() and tsamend() API are collected by call path. These API are invoked automatically in Oracle Tuxedo ART for CICS and Batch when a CICS command, EXEC SQL, or IMS DLI is invoked. Note: To monitor Pro*C sql by OCI , OCI library must be loaded in TSAM Plus Agent. Specify libclntsh.so location in the lib path when starting up the domain Following SQL are supported by OCI: • EXEC SQL ALTER • EXEC SQL AUDIT • EXEC SQL COMMENT • EXEC SQL CREATE • EXEC SQL DROP • EXEC SQL GRANT • EXEC SQL NOAUDIT • EXEC SQL RENAME • EXEC SQL REVOKE • EXEC SQL TRUNCATE • EXEC SQL DELETE • EXEC SQL EXPLAIN PLAN • EXEC SQL INSERT • EXEC SQL LOCK TABLE • EXEC SQL OPEN • EXEC SQL SELECT • EXEC SQL UPDATE • EXEC SQL SAVEPOINT • EXEC SQL EXECUTE • EXEC SQL PREPARE • EXEC SQL SET ROLE • EXEC SQL EXECUTE END-EXEC
Enable Extended Monitoring Limit	When this option is enabled, it specifies the maximum extended call path segments that can be generated in a call path when "Enable Extended Monitoring" is enabled. The acceptable value range is 1~ 2147483647. Default value is 1000.
Enable Service Contract Discovery	When this option is selected, the monitored services contract information is collected. For more information, see User Payload Collection.
Define Payload Collection	Click this button to specify the payload collection policies. For more information, see User Payload Collection.
Define Alert	Displays the alert definition page. For more information, see Tuxedo Alert Definition.
Define Conditional Filter	Click the button to define the conditional call path filters. When specified, only the call path metrics matched are collected and sent to TSAM Plus manager side. This feature saves network and database resources and allows administrators to focus on exceptional cases. To specify the filter, select Enable. • Report Previous/Next Callpath Number When it is enabled, the pervious and next call paths of the matched one are also collected. You can specify the amounts of the associated call paths. The available values range is 0~100. • Metrics Evaluation Expression(s) You can select the metric, operator and threshold value to compose an expression. The logic for the expression can be "and" or "or". Following conditional filters are available: – Elapse Time exceeds a numeric value – Execution Status is or is not a value – URcode (tpreturn) is or is not a numeric value – Call depth is greater than or equal to a numeric value – Message Number on Request Queue is greater than (or equal to) a numeric value • FML Boolean Expression(s) You can also input FML Boolean expressions directly.
Dynamic Filter Panel	Dynamic filter conditions are independent of each other. If multiple conditions are configured, the evaluation is true for all conditions and the monitoring can be initiated. For single condition items by default, if one of the item evaluations is true, then the condition is true. This applies to other monitoring policy definitions unless there is a special comment.
Initiator Type List	Allows you to choose the following Initiator types: • Native Client • Workstation Client • Jolt Client • Domain Gateway • Application Server • Web Service Client • TMQFORWARD Note: "Domain Gateway" acts as a call path initiator for local service requests. For imported services, the initiator type is set to the original caller process. The "Web Service Client" initiator point is established from the Web service gateway process (GWWS). To enable the call path monitoring for GWSNAX inbound request, you must select "Domain Gateway" when defining the policy. The WTC module is not supported for call path monitoring.
Service List	Specifies the initiator location monitored call path services. Select a service from the drop-down list. If Machine, Group, or Server is selected using an FML32 boolean expression, you must edit/input manually.
IP Address List	Applies to workstation client and Jolt client initiator types. Specifies the IP address that initiates call path monitoring. The value can be an IPV4 or IPV6 address, or an FML32 boolean expression.
Client Name List	Lists the native client, workstation client, and Jolt client initiator type client names.
User Name List	Lists the initiator type user names.

Service Tab

Table 1‑8 lists the Service tab options.

 

Table 1‑8 Service Tab Options

Options	Description
Basic Policy Options
Enable	Enables/disables service monitoring.
Ratio/Interval	Selects Ratio or Interval policy. If multiple policies cover a single process and the ratio or interval policy are different, the smaller value is used. Applies to other monitoring policy definitions as well. • Ratio: Accepts a value range of 1-65535. It indicates that monitoring is started among how many requests. The default value is “1” (indicating each request is monitored). • Interval: Accepts a value range of 1-65535. It indicates a period of time (in seconds) that monitoring can be started and is exclusive of ratio settings. The default value is “1”.
Alert Only	Specifies alert monitoring only. No metrics are sent to manager.
Enable Service Contract Discovery.	When this option is selected, the monitored services contract information is collected. For more information, see User Payload Collection.
Enable Payload Collection	When this option is selected, the user payload data of the monitored services is collected. For more information, see User Payload Collection.
Define Alert	Displays the alert definition page. For more information, see Tuxedo Alert Definition.
Dynamic Filter Options
Service List	Specifies the monitored services. Select a service from the drop-down list. If Machine, Group, or Server is selected using an FML32 boolean expression, you must edit/input manually. Note: Oracle TSAM Plus can also monitor CORBA interfaces. For CORBA, the interface name is the same as Oracle Tuxedo ATMI services; however, "Enable Service Contract Discovery" does not apply the CORBA interface.

XA Transaction Tab

Table 1‑9 lists the XA Transaction tab options.

 

Table 1‑9 XA Transaction Tab Options

Options	Description
Basic Policy Options
Enable	Enables/disables XA Transaction monitoring.
Ratio	Selects Ratio policy. If multiple policies covering a single initiator process and the ratio policy are different, the smaller value is used. Applies to other monitoring policy definitions as well. It accepts a value range of 1-65535. It indicates that monitoring is started among how many requests. The default value is “1” (indicating each request is monitored). If transaction policy is applied to the transaction initiator process, then (similar to call path monitoring), the ratio is enforced during the initiator process. If it applies to a non-initiator transaction participator, the ratio impacts the monitored XA routines. Note: Monitoring from the transaction initiator is recommended.
Define Alert	Displays the alert definition page. For more information, see Tuxedo Alert Definition.
Dynamic Filter Options
Initiator Type List	Allows you to choose the following Initiator types: • Native Client • Workstation Client • Jolt Client • Domain Gateway • Application Server Transaction path monitoring from an initiator is currently supported. If monitoring is implemented during the initiator process, all XA Transaction points are monitored during the transaction propagation.

Domain Gateway Tab

Table 1‑10 lists the Domain Gateway tab options.

 

Table 1‑10 Domain Gateway Tab Options

Options	Description
Enable	Enables/disables Domain Gateway (GWTDOMAIN) monitoring.
Interval	Selects Interval policy. If multiple policies cover a single GWTDOMAIN process and the interval policy are different, the smaller value is used. Applies to other monitoring policy definitions as well. It indicates a period of time (in seconds) that monitoring can be started. It accepts a value range of 1-65535. The default value is 300.
Define Alert	Displays the alert definition page. For more information, see Tuxedo Alert Definition.

BRIDGE Tab

Table 1‑11 lists the Bridge tab options.

 

Table 1‑11 Sub Controls of BRIDGE Panel

Options	Description
Enable	Enables/disables Bridge monitoring.
Interval	Selects Interval policy. If multiple policies cover a single BRIDGE process and the interval policy are different, the smaller value is used. Applies to other monitoring policy definitions as well. It indicates a period of time (in seconds) that monitoring can be started. It accepts a value range of 1-65535. The default value is “300”.
Define Alert	Displays the alert definition page. For more information, see Tuxedo Alert Definition.

GWWS Tab

Table 1‑12 lists the GWWS tab options.

 

Table 1‑12 GWWS Panel Tab Options

Options	Description
Enable	Enables/disables GWWS monitoring.
Interval	Selects Interval policy. If multiple policies cover a single GWWS process and the interval policy are different, the smaller value is used. Applies to other monitoring policy definitions as well. It indicates a period of time (in seconds) that monitoring can be started. It accepts a value range of 1-65535. The default value is “300”.
Define Alert	Displays the alert definition page. For more information, see Tuxedo Alert Definition.

Notes:

A policy must belong to a single domain. Oracle TSAM Plus does not support cross-domain policies. When an invalid Oracle Tuxedo domain is removed, the policies are also removed.

All polices are global configurations that are visible for all users and editable for users with policy management administrator privileges.

It possible for a policy to be to modified simultaneously by multiple users. The final changes may not be seen by other users depending on the console refresh interval.

CICS Runtime Monitoring Policy

Oracle TSAM Plus provides comprehensive monitoring control of Oracle Tuxedo Application Runtime infrastructure behavior.

This section contains the following topics:

•	Monitoring Policy List Page

•	Create/Edit Policy Page

Monitoring Policy List Page

On the menu bar, click Policy and select Tuxedo Application Runtime Monitoring Policy from the drop-down menu. The Monitoring Policy List page appears. It displays existing defined Tuxedo Application Runtime monitoring policies and allows you to view, add, edit, or delete policies.

Button Bar

Table 1‑13 list the button bar functions.

 

Table 1‑13 Button Bar

Button	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns to shown in the table. • Detach: Displays the table in a separate window. • Reorder Columns: Change how the column order is displayed.
Add	Create a new monitor policy. The maximum policy name character length is 255. You can also add a new policy by right-clicking a Domain listed in the Oracle Tuxedo Components panel.
Delete	Selected monitoring policies are deleted.
Enable	Selected monitoring policies are applied.
Disable	Selected monitoring policies are cancelled.
Edit	Edit selected monitoring policy.
Clone	Clone a new policy from a selected policy.
Import	Imports previously exported policies from a user-specified location.
Export	Exports selected policies in an .xml file to a user-specified location.
Refresh	Updates the policies shown in the Policy List Table.

Policy List Table

The Policy List table displays the following columns:

•	Select: Allows you to select all or individual policies.

•	Name: Displays the current policy names.

•	Status: Displays the policy status.

•	enabled: The corresponding request is sent to Oracle Tuxedo.

•	disabled: The corresponding request is not sent to Oracle Tuxedo.

Note:

Policy monitoring does not take effect until the impacted Oracle Tuxedo processes have started.

•	CICS Region ID: Displays the CICS region identifier (CICS region name) attached to the policy.

Create/Edit Policy Page

The Create/Edit Policy page contains the following sections:

•	Policy Property Panel

•	Tuxedo Application Runtime Monitoring Policy Panel

Policy Property Panel

The Tuxedo Application Runtime Policy panel contains the following:

•	Name: Policy name input text box. Required.

•	CICS Region: Selection of region that the current policy attaches to. Required.

Tuxedo Application Runtime Monitoring Policy Panel

The Tuxedo Application Runtime Monitoring Panel contains the following tabs:

CICS Transaction Tab

CICS Terminals Tab

To use the options listed in each tab, click the Enable check box. If enable is not selected, all options in the tab are disabled.

CICS Transaction Tab

Table 1‑14 lists the CICS Transaction tab options.

 

Table 1‑14 CICS Transaction Tab Options

Options	Description
Enable	Enables/disables CICS Transaction monitoring.
Ratio/Interval	Selects Ratio or Interval policy. If multiple policies cover a single process and the ratio or interval policy are different, the smaller value is used. Applies to other monitoring policy definitions as well. • Ratio: Accepts a value range of 1-65535. It indicates that monitoring is started among how many requests. The default value is “1” (indicating each request is monitored). • It indicates a period of time (in seconds) that monitoring can be started and is exclusive of ratio settings. Interval: Accepts a value range of 1-65535. The default value is “1”.
Alert Only	Specifies alert monitoring only. No metrics are sent to manager.
Define Alert	Displays the alert definition page. For more information, see Tuxedo Alert Definition.
Transaction List	Select monitored CICS Transaction(s) from the drop-down list or input the FML boolean expression manually.

CICS Terminals Tab

Table 1‑15 lists the CICS Terminal tab options.

 

Table 1‑15 CICS Terminals Tab Options

Options	Description
Enable	Enables/disables CICS Terminal monitoring.
Interval	Indicates a period of time (in seconds) that monitoring can be started. It accepts a value range of 1-65535. The default value is 300.
Define Alert	Displays the alert definition page. For more information, see CICS Alert Definition.

Notes:

A policy must belong to a single CICS region. Oracle TSAM Plus does not support cross-region policies. When an invalid CICS region is removed, the policies are also removed.

All polices are global configurations that are visible for all users and editable for users with policy management administrator privileges.

It possible for a policy to be modified simultaneously by multiple users. The final changes may not be seen by other users depending on the console refresh interval.

If the UBBCONFIG group setting or the tuxgroups in the file Region-Group.mapping has been modified after the ART transaction policy is defined, the resource filter might be expired. In that case, policy should be redefined.

IMS Runtime Monitoring Policy

Oracle TSAM Plus provides comprehensive monitoring control of Oracle Tuxedo Application Runtime IMS infrastructure behavior.

This section contains the following topics:

•	Monitoring Policy List Page

•	Create/Edit Policy Page

Monitoring Policy List Page

On the menu bar, click Policy and select IMS Runtime Policy from the drop-down menu. The Monitoring Policy List page appears. It displays existing defined Tuxedo Application Runtime monitoring IMS policies and allows you to view, add, edit, or delete policies.

Button Bar

Table 1‑16 list the button bar functions.

 

Table 1‑16 Button Bar

Button	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns to shown in the table. • Detach: Displays the table in a separate window. • Reorder Columns: Change how the column order is displayed.
Add	Create a new monitor policy. The maximum policy name character length is 255. You can also add a new policy by right-clicking a Tree Node in IMS System component tree panel.
Delete	Selected monitoring policies are deleted.
Enable	Selected monitoring policies are applied.
Disable	Selected monitoring policies are cancelled.
Edit	Edit selected monitoring policy.
Clone	Clone a new policy from a selected policy.
Import	Imports previously exported policies from a user-specified location.
Export	Exports selected policies in an .xml file to a user-specified location.
Refresh	Updates the policies shown in the Policy List Table.

Policy List Table

The Policy List table displays the following columns:

•	Select: Allows you to select all or individual policies.

•	Name: Displays the current IMS policy names.

•	Status: Displays the IMS policy status.

•	Domian ID: Displays IMS policy Domain ID.

Create/Edit Policy Page

Click Add, Edit, or Clone, go to the Create/Edit Policy page. At the top of page, enter the name for IMS policy to be created and select a IMS Tuxedo domain.

The Create/Edit Policy page contains the following tabs:

IMS Transaction Tab

IMS Program Tab

To use the options listed in each tab, click the Enable check box. If enable is not selected, all options in the tab are disabled.

IMS Transaction Tab

This page is used to define policy to report IMS Transaction metric generated by MPP server. Table 1‑17 lists the IMS Transaction tab options.

 

Table 1‑17 IMS Transaction Tab Options

Options	Description
Enable	Enables/disables IMS Transaction monitoring.
Ratio/Interval	Selects Ratio or Interval to collect metrics.
Alert Only	Specifies alert monitoring only. No metrics are sent to manager.
Define Alert	Displays the alert definition page. For more information, see IMS Alert Definition.
Transaction List	Select monitored IMS Transaction(s) under the Tuxedo domain from the drop-down list or input IMS transactions separated by ";" manually. If no Filter is set, this policy is available for all IMS Transactions under this IMS domain.

IMS Program Tab

This page is used to define policy to report IMS Program metric generated by BMP server. Table 1‑9 lists the IMS Program tab options.

 

Table 1‑18 IMS Program Tab Options

Options	Description
Enable	Enables/disables IMS Program metric collection.
Ratio/Interval	Selects Ratio or Interval to collect metrics.
Alert Only	Specifies alert monitoring only. No metric is sent to manager.
Define Alert	Displays the alert definition page. For more information, see IMS Alert Definition.
Program List	Select monitored IMS program(s) under the Tuxedo domain from the drop-down list or input IMS programs separated by ";" manually. If no Filter is set, this policy is available for all IMS programs under this IMS domain.

Tuxedo Metrics Monitoring

Oracle Tuxedo Metrics collection is driven by policy monitoring. Once metrics are collected, you can view them on the related metric pages. Click Tuxedo Metrics on the menu bar; the Tuxedo Metrics page appears. From the drop-down menu you can select the following:

•

Call Path

•	Call Pattern

•

Service

•	XA Transaction

•	Domain Gateway

•

BRIDGE

•

GWWS

Call Path

Call Path metrics monitoring provides a quick way for you to view the latest call path information. For long-running call path situations, Oracle TSAM Plus allows you to view runtime executions dynamically in real time.

The Call Path Metric window contains the following panels:

•	Call Path Query by Filter Panel

•	Call Path Results Panel

Call Path Query by Filter Panel

Table 1‑19 lists the Call Path Query by Filter panel options. Results are displayed in the Call Path Results List panel.

 

Table 1‑19 Call Path Query By Filter Options

Options	Descriptions
Initiator	Specifies the call path initiator type to limit the scope. You can select the following values: • Type: – All – Workstation Client – Jolt Client – Native Client – Domain Gateway – Web Service Client – Application Server – TMQFORWARD The default value is "All". Note: The "Initiator Type" supports multiple selections for specific initiator types. • Domain: Lists all Domains. The default value is “Any”. • Machine: Lists all machines for the selected domain. The default value is “Any”. • Server: Lists all servers for the selected machine. The default value is “Any”. • Initial Called Service: The first service of the call path. Note: If the initiator type is set to "Application Server", the "Initial Called Service" value must be host service name. • Client Process Name: The initiator process name. • User Name: The Tuxedo user name is provided to call initial called service.
Message Tag	Specifies the Tuxedo Message Tag in the call path segments. Note: To use this function, the following product versions are required: • Oracle Tuxedo 12.1.3 RP013 • Oracle TSAM standalone 12.1.3 RP006 This filter only takes effect when the database type is Oracle.
Status	Checks the call path status. You can select the following values: • Any • Success • Running • Application Failure • System Failure • Any Failure The default value is "Any". Note: "Application Failure" indicates tperrno is TPESVCFAIL. Other errors situations belong to "System Failure"
Time	Specifies a specific time period. • Any. • Recent: Specifies the recent time period between 0~60 minutes/hours/days. Default value is 1 hour. • Time Period: Specifies a particular time span.
Min. Elapsed	Displays call paths with minimum microseconds spent (0 means all).
Max Record	Specifies the call path max number. If the query results are larger than this number, the latest max records are retrieved.
Correlation ID / ECID (Optional)	This option can be used to query call path by Correlation ID or ECID. If the Execution Context ID is inputted, Oracle TSAM Plus use it to filter related call path. ECID Query works only if related Tuxedo application enables ECID. If the call path Correlation ID is inputted, Oracle TSAM Plus uses it to filter. The default value is empty (which indicates a Correlation ID is not used in the query). Note: "Correlation ID" query is exclusive with "Filtering Parameters". The Correlation ID consists of the following field values separated by a space: • Tuxedo domain ID: <DOMAINID>:<master machine name>:<IPCKEY> in the UBBCONFIG *RESOURCE section. • Logical Machine ID: LMID in the UBBCONFIG *MACHINES section. • Process Name: • “client”: Used for native clients. • “JSH”: Used for Jolt clients. • “WSH”: Used for /WS clients. • <server name>: Used for the server name. • Process ID (pid) • Thread ID • A counter in range of 1..99999999 (starting from 1) • Timestamp Correlation ID Example: TUXEDO:lcsol18:200401 SITE1 client 18505 1 1 1259031468 ECID Example: 004u3D6nvTI5qYSLMEo2ye0003KL000000

Saving and Reusing Queries

You can save the frequently-used queries for reusing or as a base for creating similar queries. The Save/Reuse Queries area in the bottom provides the following functions:

•

Load: Loads a saved query. When you click this button, a Saved Queries list is displayed. Select the desired query, the related conditions are loaded in the Query by Filter panel and are editable. If a historical domain, group, machine, server, or service is already removed or renamed, it is displayed in a read-only text field beneath the corresponding list or shuttle selection. It can be cleared by changing the value of the corresponding list or shuttle selection.

•	New: Starts a new query. When you click this button, all query condition fields are reset to the default status.

•	Save: Saves a brand new query or changes in a loaded query. Before saving a query, you must execute the query first. For a new query, when you click this button, type a unique query name and click OK. The saved query name is displayed as Current Query Name.

•	Save As: Saves a loaded query to another name. Before saving a query, you must execute the query first.

•	Delete: When a query is loaded or saved, this button is activated to delete the loaded query.

Notes:

•	If a Tuxedo node (domain/machine/group/server/service) specified in a saved query does not exist anymore (e.g. removed or renamed), it can still be enquired and is displayed in the historical field in the Query by Filter panel when being enquired.

•	When a user account is deleted, all his/her queries saved in the system are removed.

Call Path Results Panel

This Call Path Results panel displays server-side call path queries.

There are two sub-panels:

•	Call Path Results List Panel

•	Call Path Details Panel

Call Path Results List Panel

Table 1‑20 lists the Call Path Results List panel options.

 

Table 1‑20 Call Path Results List Panel

Results	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns displayed in the table. • Detach: Displays the table in a separate window. • Reorder Columns: Change how the column order is displayed.
Refresh	Updates the user information list.
Detach	Displays the table in a separate window.
Call Path Data Grid	The data grid holds the entire call path information server-side query. One call path occupies one row. The columns are listed as follows: • Correlation ID. Click to display single call path details. • Root Service The first ATMI service made in the call path. • Start Time The time stamp for the start of the call path query in the following format: mmmdd,yyyy,hh:mm:ss:ms GMT • Status • Succeeded • Failed • Return Code • TPOK/0 • TPEXXX/tperrno TPEXXX is the error code string format and tperrno is the corresponding numeric value, for example, TPESVCFAIL/11. • Elapsed Time (microsecond) The amount of time passed during the call path query. The unit is seconds with granularity to millisecond. If a call path is completed, the value is the total elapsed time used. • CPU Time (microsecond) The total CPU time used on the call path. The CPU time is the service execution CPU time summary (CPU time for multi-threaded servers cannot be accurately calculated). • User CPU Time (microsecond) The total User CPU time used on the call path. The User CPU time is the service execution User CPU time summary (User CPU time for multi-threaded servers cannot be accurately calculated). • System CPU Time (microsecond) The total System CPU time used on the call path. The System CPU time is the service execution System CPU time summary (System CPU time for multi-threaded servers cannot be accurately calculated).
	• User return code • GTRID The XA Transaction identifier if the call path is involved in an XA Transaction. It provides the XA Transaction query results if XA Transaction monitoring is enabled. • ECID The minimum ECID if one call path has more than one ECID. • Message Tag The minimum Tuxedo Message Tag in the call path. • Client Address Client IP Address (if available). • User Name The Tuxedo user name is provided to call initial called service.
Status Bar Summary	The summary lists the following information: • Export to Excel button places the table contents into an MS Excel compatible file. • Total call path in this collection. • Running call path in this collection. • Successfully done call path number. • Application failed call path number. • System failed call path number.

Call Path Details Panel

Table 1‑21 lists the Call Path Details panel options.

 

Table 1‑21 Call Path Details Panel Options

Results	Description
Call Path Details Data Grid	The data grid holds the entire call path server-side queries. One call path occupies one row. The columns are as follows: • Message Flow: Message Flow format: ICON Server (tpcall/tpacall/tpforward/tpconnect Root Service) ICON Server (ARTIMS/DLI_OPERATION) Where: – ICON: • Send request • Get request • Send reply • Get reply • Server: Server name Note:   • If an Oracle Tuxedo server has invoked tpcall/tpacall/tpforward/tpconnect, the content is displayed in parentheses. For example, BROKER (tpcall DEPOSIT). • Following DLI operations are supported: GU, GHU, GN, GHN, GNP, GHNP, ISRT, DLET, CHNG, PURG, REPL, FLD, OPEN, CLSE, INQY, POS, and PING. • If OCI SQL is monitored, the ORACLE SQL/COMMAND is appended to Message flow, such as simpserv1(ORACLE SQL/SELECT). • If it is a tsambegin/tsamend node, "server process name(type/subtype)" is displayed. The type is Extended Monitoring Type specified by tsambegin(), and the subtype is Extended Subsidiary Monitoring Type specified by tsambegin(). For other columns, the detailed CICS command or SQL is displayed. • Domain: Domain call path step located. • Machine: Machine call path step located. • Group: Group call path step located. • Server: Server call path step located. • Timestamp: The logging point timestamp. • Duration (microsecond): Time span T(n) - T(n-1) (in seconds) • Elapsed time (microsecond): The total service elapsed time (in seconds). The default value is “hidden”. • Execution time (microsecond): The service execution time (in seconds).
	• Wait time (microsecond): The IPC queue wait time (in seconds). • Call Flag: The tpcall/tpacall call flags. • Message Size (bytes): The buffer size in bytes. • Message Queued: Number of messages in queue. • IPC queue ID: Identifies the service request queue. The default value is hidden. • Return Code • User Return Code • Extended Monitoring Type: specified by tsambegin(). • Extended Subsidiary Monitoring Type: specified by tsambegin(). • ECID: Execution Context ID. • Tuxedo Message Tag • Others: – LDOM – RDOM – Local GTRID – MSGCVTTIME: Message Web service conversion time. – SQL, AMOUNT, and RETURNCODE. • SQL: Original SQL content after EXEC SQL • AMOUNT: This number makes sense for insert/update/delete/select only. For insert/delete/update, it indicates the number of rows affected; for select, it indicates the number of rows putted into the user buffers. AMOUNT is 0 when sql open cursor is monitored. • RETURNCODE: The return code retrieved from the OCI call return code by TSAM Plus agent. Unlike SQLCODE, RETURNCODE can only be got from TSAM Plus agent code. • Web service conversion time
Status Bar	Displays the current selected call path Correlation ID. The Export to Excel button allows you to place the table contents into an MS Excel compatible file. Note: When exporting to Excel, if the callpath/callpattern tree is collapsed, only the nodes that are not collapsed are exported to excel file. If you want to export the full callpath/callpattern tree, you must fully expand it and then click Export to Excel.

Notes:

If multiple async calls are made in one process (for example, in a service two tpacalls are made), the order is based on the service invocation sequence for the reply instead of the timestamp. This allows you to easily correlate requests and reply in an "ordered" manner.

For GWWTDOMAIN, both local domain and remote domain are displayed. LDOM/RDOM information is displayed in the domain gateway cell.

For BRIDGE, the message full stages are supported (same as GWTDOMAIN).

Call Pattern

Call Pattern monitoring provides a quick way for you to view the Call Pattern information. The Call Pattern Metric window contains the following panels:

•	Call Pattern Query by Filter

•	Call Pattern Results Panel

Call Pattern Query by Filter

Table 1‑22 lists the Call Pattern Query by Filter panel options.

 

Table 1‑22 Call Pattern Filter Panel

Options	Description
Initiator	• Domain: Lists all Domains. The default value is “Any”. • Machine: Lists all machines for the selected domain. The default value is “Any”. • Group: Lists all groups for the selected machine. The default value is "Any". • Server: Lists all servers for the selected machine. The default value is “Any”. • Initial Called Service: The first service of the call path. • Client Process Name: The initiator process name. • User Name: The Tuxedo user name is provided to call initial called service.
From/To	Time Span. This option is available only when “Recent“ is not specified.
Recent	Specifies the recent time period between 0~60 minutes/hours/days. The default value is 1 hour. This option is available only when “From/To“ is not specified.
Minimum Request Number	The minimum number of requests that form a pattern. Usually a call pattern contains a large number of calls. This threshold prevents listing a pattern with a small number of calls.
Service Pattern	Checked: Displays only service call path pattern Unchecked: Displays service call path pattern including detailed location and GWTDOMAIN information

Click the Query button; the Call Pattern Result List panel appears.

Note:

For Oracle Database, there is a lag time of minutes specified in Call Pattern Calculation Delay before you can query call patterns in one hour or day. That is, you can only query the call patterns occurred in one hour or day after the Call Pattern Calculation Delay minutes of this hour or day. For example, suppose the Call Pattern Calculation Delay is 30 minutes, if you select to query the call patterns occurred from 9 to 10 o'clock, you can actually query the desired information after 10:30, similarly, if you select to query the call patterns occurred yesterday, you can actually query the desired information after today 00:30.

Saving and Reusing Queries

You can save the frequently-used queries for reusing or as a base for creating similar queries. For more information, refer to Saving and Reusing Queries.

Call Pattern Results Panel

The Call Pattern Results panel displays server-side Call Pattern queries. There are two sub-panels:

•	Call Pattern Results List Panel

•	Call Pattern Details Panel

Call Pattern Results List Panel

Table 1‑23 lists the Call Pattern Results List panel options.

 

Table 1‑23 Call Pattern Results List Panel Options

Options	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns displayed in the table. • Detach: Displays the table in a separate window. • Reorder Columns: Change how the column order is displayed.
Refresh	Updates the user information list.
Detach	Displays the table in a separate window.
Call Pattern Data Grid	The data grid holds the entire call path server-side queries. One call path occupies one row. The columns are as follows: • Description: Brief information for this call pattern. Clicking it displays call pattern details as follows. • Total Number: Total number of call paths in a call pattern. • Success Number: Successful number of call paths in a call pattern. • Application Failure Number: Application failure number of call paths in a call pattern. • System Failure Number: System failure number of call paths in a call pattern. • Average Elapsed Time (microsecond): Average call pathelapsed time in a call pattern.
Status Bar Summary	• Total call pattern in this collection. The Export to Excel button allows you to place the table contents into an MS Excel compatible file. Note: When exporting to Excel, if the callpath/callpattern tree is collapsed, only the nodes that are not collapsed are exported to excel file. If you want to export the full callpath/callpattern tree, you must fully expand it and then click Export to Excel.

Call Pattern Details Panel

Click any row in the Call Pattern list, the selected Call Pattern details are displayed. Table 1‑24 lists the Call Pattern Details panel options.

 

Table 1‑24 Call Pattern Details Panel

Options	Description
Call Pattern Details Data Grid	The tree table data grid holds the entire call path details queried from server side. The columns are as follows: • Message Flow: Message Flow format: – ICON Service Where: – ICON: • Send request Root Service: Initial service at Call Pattern For example, BR_ACNT_SUM • Domain: Domain call pattern step located. Displayed when Service Pattern is unchecked. • Machine: Machine call pattern step located. Displayed when Service Pattern is unchecked. • Group: Group call pattern step located. Displayed when Service Pattern is unchecked. • Server: Server call pattern step located. Displayed when Service Pattern is unchecked.
Status Bar	Status Bar displays the current selected call pattern index in the Call Pattern List panel. The Export to Excel button allows you to place the table contents into an MS Excel compatible file.

Service

Service Monitoring allows you to monitor Oracle Tuxedo services. Click Tuxedo Metrics and select Service from the drop-down menu; the Service page appears.

The filtering options panel allows you to specify supply information to the services you want monitored. On the left, there are drop-down lists of Domain, Machine, Group and Server. There are two modes for the service selection, select the most active services or particular services on the right. Table 1‑25 lists the Service Selection options.

 

Table 1‑25 Service Selection Options

Options	Description
Services Selection	• Domain: Lists all Domains. The default value is “Any”. • Machine: Lists all machines for the selected domain. The default value is “Any”. • Group: Lists all server groups for the selected machine. The default value is “Any”. • Server: Lists all servers for the selected machine. The default value is “Any”. • User Name: The Tuxedo user name is provided to call initial called service.
Monitoring Mode	Four monitoring modes are supported: • Most Active (Live): Allows you to query the most active services in the latest refresh-time window • Most Active (Historical): Allows you to query the most active service over a long time interval and displays the service metrics distribution during that time span. • Selected Services (Live): Allows you to monitor service dynamic execution status in the latest refresh-time window. When selected, the Available Services/Selected Services panel appears. – Available Services/Selected Services: Selects the services to be monitored. – Show services with same name as one service: If checked, specifies the query only uses the service name as the query key. If unchecked, the services are queried using the service location for same name service. – Aggregation Time: Applies to alive related queries. The algorithm is time span. – Refresh Interval: Specifies the refresh aggregation interval for service metrics computing. It only applies to live monitoring related query. • Selected Services (Historical): Allows you to query services execution status during a long time span. A time window is needed for aggregation purpose. When selected, the Available Services/Selected Services panel appears. – Available Services/Selected Services: Selects the services to be monitored. – Show services with same name as one service: If checked, specifies the query only uses the service name as the query key. If unchecked, the services are queried using the service location for same name service. – From, To: Time period. For historical query. This option is available only when “Recent“ is not specified. – Recent: Specifies the recent time period between 0~60 minutes/hours/days. The default value is 1 hour. This option is available only when “From/To“ is not specified. – Time Window: Specifies the time increment (in seconds). The default value is 3600.

Click Query; the query results are displayed in the Service Monitoring Results panel. Table 1‑26 lists the Service Monitoring Results panel options.

 

Table 1‑26 Service Monitoring Results Panel Options

Options	Description
Metrics	From the drop-down list you can select the following service monitoring metrics: • Average Execution time (microsecond) • Success Number • Failure Number • Max Message Size (bytes) • Min message size (bytes) • Average CPU time (microsecond) • Average System CPU time (microsecond) • Average User CPU time (microsecond) • Average Message Queue Length • Average Message Wait Time in Queue (millisecond) For "CPU time", only single threaded servers are calculated (CPU time for multi-threaded servers cannot be accurately calculated). The Pause/Resume button allows you to stop the data refresh temporarily. The default is Pause (which indicates that a current refresh is in progress). Clicking it will Resume and refresh stops. Clicking it again restores the status.
Chart/Table	Displays results in either a chart or table. The default view is Chart (either line or bar chart). One service is one series. The horizontal axis represents the time series; the vertical axis represents the selected metrics. In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.

Saving and Reusing Queries

You can save the frequently-used queries for reusing or as a base for creating similar queries. For more information, refer to Saving and Reusing Queries.

XA Transaction

There are two ways to initiate XA Transaction queries: you can specify an XA Transaction identifier, or you can query using filtering parameters. These two ways are exclusive. Table 1‑27 lists the XA Transaction Query by Scope filtering options.

 

 

Table 1‑27 “XA Transaction Query by Scope Panel Options

Options	Description
Initiator Type	There XA Transaction monitoring scenarios: 1. If the monitoring policy is applied to an XA Transaction initiator, monitoring initiated with the XA Transaction path propagation (similar to Call Path). 2. If monitoring is initiated for particular processes only (such as TMS without initiator involved), propagation does not take place and only the monitored XA Transaction calls are reported. The "Initiator Type" applies to the first situation, so that a specific XA Transaction can be retrieved. It has the following values: – All – Native Client – Workstation Client – Jolt Client – Domain Gateway – Application Server The default value is "All" and the second monitoring scenario must use the default setting.
Status	Allows you to select the following values: • Any • Succeeded • Failed
Query for latest	Query under latest time (in seconds).
Query during	Query XA transactions during a specific time period.
Query by GTRID	Query an XA transaction by using an XA transaction identifier. For example x0 x46524a28 x1. For more information, see How the System Tracks Distributed Transaction Processing in the Oracle Tuxedo User Documentation. The Exact Match checkbox is under the text field. If checked, the whole identifier string must be matched, otherwise all the XA transaction IDs that contain the specified string are listed.

Click Submit; the XA Transaction results appears in the XA Transaction Result List panel.

Table 1‑28 lists the XA Transaction Results List panel options.

 

Table 1‑28 XA Transaction Results List Panel Options

Options	Description
GTRID	Global Transaction ID.
Initiator	The initiated process where the transaction starts.
Status	Successful transactions indicated by Failed transactions indicated by
Start Time	Time when the XA Transaction started.
Duration (microsecond)	Total transaction time span.
Execution Time (microsecond)	Total transaction time per Oracle Tuxedo service.
Parent GTRID	Displays the GTRID of the previous domain if the transaction was propagated from another Oracle Tuxedo domain.

When you click on a transaction item in the list, the transaction path, related call path ID and transaction details are displayed in the XA Transaction Path, Corresponding Call Path Correlation ID and XA Transaction Detail panels respectively.

The XA Transaction Path shows the XA Transaction network in a tree structure similar to the Component Tree. In the XA Transaction Path tree, each node represents one domain XA Transaction. If multiple /T domains are involved in the XA Transaction, the XA transaction spread path can be easily observed.

In the Corresponding Call Path Correlation ID panel, the call path(s) related to the XA transaction are listed. You can include multiple call path correlation IDs in an XA Transaction. To do so, you must define an XA Transaction policy element and a call boundary call path policy element. If the two elements are applied to one process, one XA Transaction monitoring process includes multiple call paths. Clicking on the call path ID displays the call path detail in the Call Path Metric.

Table 1‑29 lists the XA Transaction Detail panel options.

 

Table 1‑29 XA Transaction Detail Panel Options

Options	Description
XA Routine	The transaction routine names are as follows: • tpbegin • tpcommit • tprollback • tpabort • xa_commit • xa_start • xa_prepare • xa_rollback • xa_end • tms_msg_xxx (for GWTDOMAIN XA Transaction activities) • xa_msg_xxx (for GWTDOMAIN XA Transaction activities)
Return Code	The XA Routine return code.
Machine/Group/Process	The XA Routine process information. The process can be an Oracle Tuxedo server or a client.
Start Time	The time when the XA Routine started.
Execution Time (microsecond)	The elapse time used for the XA Routine.

Domain Gateway

A monitoring project may contain multiple domain gateways; however, one monitoring chart can only monitor one local domain gateway (due to data source consistency). Click Tuxedo Metrics and select Domain Gateway from the drop-down menu; the Domain Gateway Metrics page appears. The Domain Gateway page contains two panels:

•	Domain Gateway Selection

•	Domain Gateway Monitoring

Domain Gateway Selection

Table 1‑30 lists the Domain Gateway Selection panel options.

Note:

Domain Gateway only supports GWTDOMAIN.

 

 

Table 1‑30 Domain Gateway Selection Panel Options

Options	Description
Domain	Lists all Domains. Required.
Local Access Point	This drop-down list contains the local domain gateway configured in "Gateway" monitoring. The format is as follows: domain id/group/server id. Note: One group can only have one gateway instance.
Available Remote Access Point/Selected Remote Access Point	The remote domain gateway link connected with the selected local domain gateway. They are the RDOM in DMCONFIG.Multiple remote domains can be selected.
Monitoring Mode	• Live – Aggregation Time: Applies to alive related query. The algorithm is time span (in seconds). – Refresh Interval. Specifies the refresh interval for live monitoring (in seconds). • Historical – From/To: time period for historical query. – Time Window. Specifies the aggregation window for historical query (in seconds).

Domain Gateway Monitoring

Table 1‑31 lists the Domain Gateway Monitoring panel options.

 

Table 1‑31 Domain Gateway Monitoring Panel Options

Options	Description
Metrics	From the drop-down list you can select the following metrics: • Network Message Number • Network Message Bytes • Network Pending Number • Network Pending Bytes • Network Outstanding Requests
Chart/Table	Displays results in either a chart or table. The default view is Chart (either line or bar chart). One service is one series. The horizontal axis represents the time series; the vertical axis represents the selected metrics. In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.

BRIDGE

Similar to Domain Gateway.

Note:

There is no "Network Outstanding Requests" metric.

GWWS

Click Tuxedo Metrics and select GWWS from the drop-down menu; the GWWS Metric page appears. The GWWS Metric page contains two panels:

•	GWWS Query by Filter

•	GWWS Live/History Monitoring

GWWS Query by Filter

Table 1‑31 lists the GWWS Query by Filter options.

 

Table 1‑32 GWWS Query by Filter Panel Options

Options	Description
Domain	Lists all Domains. Required.
GWWS	GWWS server list. The default is “All”.
Monitoring Mode	• Live – Aggregation Time: Applies to alive related query. The algorithm is time span (in seconds). – Refresh Interval. Specifies the refresh interval for live monitoring (in seconds). • Historical – From/To: time period for historical query. – Time Window. Specifies the aggregation window for historical query (in seconds).

GWWS Live/History Monitoring

Table 1‑33 lists the GWWS Live/History Monitoring options:

 

Table 1‑33 GWWS Live/History Monitoring Panel Options

Options

Descriptions

Metrics

From the drop-down list you can select the following metrics: • Active Thread Numbers (average active thread numbers) • Average Inbound Process Time (microsecond) • Average Outbound Process Time (microsecond) • Inbound One-Way Failure Number • Inbound One-Way Success Number • Inbound RPC Failure Number • Inbound RPC Success Number • Outbound One-Way Failure Number • Outbound One-Way Success Number • Outbound RPC Failure Number • Outbound RPC Success Number • Inbound Pending Request • Outbound Pending Request

CICS/IMS/Batch Runtime Metrics Monitoring

Metrics collection is driven by policy monitoring. Once metrics are collected, you can view them on the related metric pages. The Tuxedo Application Runtime Metrics page includes four panels:

To access the Tuxedo Application Runtime Metrics page, click Tuxedo Application Runtime Metrics on the menu bar. From the drop-down menu you can select the following:

•	CICS Transactions

•	CICS Terminals

•	Batch Jobs

•	IMS Transactions

•	IMS Programs

•	IMS System Traces

CICS Transactions

CICS Transactions monitoring provides a quick way for viewing the latest CICS Transaction information.

The CICS Transactions page contains the following panels:

•	CICS Transactions Query by Filter Panel

•	CICS Transactions Live/History Monitoring Panel

CICS Transactions Query by Filter Panel

Table 1‑34 lists the CICS Transactions Query by Filter options.

 

Table 1‑34 CICS Transactions Query By Filter Options

Options	Description
CICS Region	Lists all CICS regions. The default value is “All”.
Transaction Class	Lists all Transaction classes. The default value is “All”.
Transaction	Lists all Transactions. The default value is “All”.
Monitoring Mode	• Live – Aggregation Time: Applies to alive related query. The algorithm is time span (in seconds). – Refresh Interval. Specifies the refresh interval for live monitoring (in seconds). • Historical – From/To: time period for historical query. – Time Window. Specifies the aggregation window for historical query (in seconds).

CICS Transactions Live/History Monitoring Panel

Table 1‑35 lists the CICS Transactions Live/History Monitoring Graph tab metrics.

 

Table 1‑35 CICS Transactions Live/History Monitoring Options

Options	Description
Chart Control	From the drop-down list you can select the following metrics: • Number of Transaction Calls • Average Execution Time (microsecond) • Average CPU Time (microsecond) • Average System CPU Time (microsecond) • Average user CPU Time (microsecond)
Chart/Table	Displays results in either a chart or table. The default view is Chart (either line or bar chart). One service is one series. The horizontal axis represents the time series; the vertical axis represents the selected metrics. In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.

 

CICS Terminals

CICS Terminals metrics provides a quick way for you to view the latest CICS Terminals information.

The CICS Terminals window contains the following panels:

•	CICS Terminals Query by Filter Panel

•	CICS Terminals Live/History Monitoring Panel

CICS Terminals Query by Filter Panel

Table 1‑36 lists the CICS Terminals Query by Filter options.

 

 

Table 1‑36 CICS Terminals Query By Filter Options

Options	Description
CICS Region	Lists all CICS regions. The default value is “All”.
Monitoring Mode	• Live – Minimum Policy Interval: Applies to alive related query. It is the minimum value among all Tuxedo Application Runtime monitoring policies defined (in seconds). – Refresh Interval. Specifies the refresh interval for live monitoring (in seconds). • Historical – From/To: time period for historical query. – Time Window: Specifies the aggregation window for historical query (in seconds). – Since CICS Region Start Checkbox: If checked, From/To is replaced by Start Time/Shutdown Time. – Start Time/Shutdown Time: CICS region start/shutdown time.

CICS Terminals Live/History Monitoring Panel

Table 1‑37 lists the CICS Terminals Live/History Monitoring panel options.

 

Table 1‑37 CICS Terminals Live/History Monitoring Graph Options

Options	Description
Chart Control	From the drop-down list you can select the following metrics: • Successful Transaction Number • Failed Transaction Number • Session Number
Chart/Table	Displays results in either a chart or table. The default view is Chart (either line or bar chart). One service is one series. The horizontal axis represents the time series; the vertical axis represents the selected metrics. In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.

Batch Jobs

Batch Jobs allows you to monitor the running status of the Batch Jobs. It contains two panels: Query by filter and Monitor view.

JES Metrics Query by Filter Panel

The filtering condition panel let user supply information to specify the jobs to be observed in the JES system. On the left, there are dropdown lists for JES application name, Job classes, Job priorities and Job owners, and one edit box for Job name.

There are two modes for the JES metrics monitoring, live monitoring and history monitoring.

Table 1‑38 lists the UI components and their relationships.

 

Table 1‑38 JES Metrics Query by Filter Panel

Elements	Description
JES application name	Specifies which JES system the Job is executed. The single choice dropdown list contains only live/active ones, mandatory. Same as the JES tree node name.
Job classes	Specifies one or more classes
Job name	Specifies a search a string contained in the job name.
Job priorities	Specifies one or more priorities
Job owners	Specifies one or more owners
Monitoring Mode	Two monitoring modes are supported: Live and Historical • Live Monitoring. It allows user to monitor the JES system execution status in a latest refresh window. • History Monitoring. It allows user to query JES system execution status during a long time span. A time window is needed for aggregation purpose.
Aggregation Time	Applies to history monitoring mode. The algorithm is time span
Refresh Interval	Specifies the refresh aggregation interval for JES system metrics computing. It only applies to live monitoring.

When the conditions filing is complete, click Submit; the monitoring results page appears on the right.

JES Monitor View

 

Table 1‑39 JES Monitor View

Elements	Description
Chart Control	The "Metrics" drop down list let user select the metric aspect interested in the chart, • Successful job number in the Aggregation Time Window Failed job number in the Aggregation Time Window • Waiting job number in different queues and the sum of all queues • Average CPU Time: – Average user CPU time for successful jobs in milliseconds int the Aggregation Time Window – Average system CPU time for successful jobs in milliseconds int the Aggregation Time Window Note: Failed jobs do not have "Average CPU Time" Button "Pause/Resume" allows you to temporarily stop the data refresh . The default is "Pause" which means the current refresh is in progress. Clicking it again will "Resume" and the refresh stops. Clicking it again restores the status.
Chart/Table	Chart/Table will show results in style either chart or table. The chart is can be line style or bar chart. One kind of job class is one series. The horizontal axis is time series and the vertical axis is for the metrics selected.

The Export button allows you to save the table contents to an EXCEL compatible file.

IMS Transactions

IMS Transactions monitoring provides a quick way for viewing the latest IMS Transactions information and shows IMS transactions metrics generated by MPP server.

The IMS Transactions page contains the following panels:

•	IMS Transaction Query by Filter Panel

•	IMS Transaction Live/History Monitoring Panel

IMS Transaction Query by Filter Panel

Table 1‑40 lists the IMS Transaction Query by Filter options.

 

Table 1‑40 IMS Transaction Query By Filter Options

Options	Description
Domain	Lists all IMS domains. The default value is empty.
Transaction Class	Lists all Transaction classes. The default value is empty.
Transaction	Lists all Transactions. The default value is empty.
Monitoring Mode	• Live – Aggregation Time: Applies to alive related query. The algorithm is time span (in seconds). – Refresh Interval. Specifies the refresh interval for live monitoring (in seconds). • Historical – From/To: time period for historical query. – Time Window. Specifies the aggregation window for historical query (in seconds).

IMS Transaction Live/History Monitoring Panel

Table 1‑41 lists the IMS Transaction Live/History Monitoring Graph tab metrics.

 

Table 1‑41 IMS Transaction Live/History Monitoring Options

Options	Description
Chart Control	From the drop-down list you can select the following metrics: • Number of Transaction Calls • Average Execution Time (microsecond) • Average CPU Time (microsecond) • Average System CPU Time (microsecond) • Average user CPU Time (microsecond) • Average user DLI Time (microsecond)
Chart/Table	Displays results in either a chart or table. The default view is Chart (either line or bar chart). One transaction is one series. The horizontal axis represents the time series; the vertical axis represents the selected metrics. In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.

IMS Programs

IMS Programs monitoring provides a quick way for viewing the latest IMS Programs information and shows IMS programs metrics generated by BMP server.

The IMS Programs page contains the following panels:

•	IMS Program Query by Filter Panel

•	IMS Program Live/History Monitoring Panel

IMS Program Query by Filter Panel

Table 1‑42 lists the IMS Program Query by Filter options.

 

Table 1‑42 IMS Program Query By Filter Options

Options	Description
Domain	Lists all IMS domains. The default value is empty.
Program	Lists all programs. The default value is empty.
Monitoring Mode	• Live – Aggregation Time: Applies to alive related query. The algorithm is time span (in seconds). – Refresh Interval. Specifies the refresh interval for live monitoring (in seconds). • Historical – From/To: time period for historical query. – Time Window. Specifies the aggregation window for historical query (in seconds).

IMS Program Live/History Monitoring Panel

Table 1‑43 lists the IMS Program Live/History Monitoring tab metrics.

 

Table 1‑43 IMS Transaction Live/History Monitoring Options

Options	Description
Chart Control	From the drop-down list you can select the following metrics: • Number of Program Calls • Average Execution Time (microsecond) • Average CPU Time (microsecond) • Average System CPU Time (microsecond) • Average user CPU Time (microsecond) • Average user DLI Time (microsecond)
Chart/Table	Displays results in either a chart or table. The default view is Chart (either line or bar chart). One program is one series. The horizontal axis represents the time series; the vertical axis represents the selected metrics. In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.

IMS System Traces

The IMS System Traces page contains the following panels:

•	Search Panel

•	Query Result List Table

•	Detailed Information Panel

Search Panel

Table 1‑44 lists the query filters on the Search panel.

 

Table 1‑44 Query Filters

Options	Description
Domain	Lists all IMS domains. The default value is empty.
Machine	Lists all the machines belong to the selected domains. The default value is empty.
Group	Lists all the machines belong to the selected machines. The default value is empty.
Server	Lists all the machines belong to the selected groups. The default value is empty.
Transaction Class	1 ~ 999. The default value is empty.
Transaction	Lists all the transactions belong to the selected domains. The default value is empty.
Program Name	Lists all the programs belong to the selected domains. The default value is empty.
Region Type	MPP and BMP. The default value is empty.
From / To	The transaction/program ending time span. The default value is latest 24 hours.
Max Queried Out Record	Limits the returned record number. Default is 500. Too large value in this field may cause browser out of response

Clicking on the Reset button resets all the query filters (except Max Queried Out Record) to the initial status.

Query Result List Table

When clicking the Query button, all the Transaction/Program collect instances met the search criteria are listed in the Query Result List table. Click any of the entries listed in the Query Result List table to display the detailed information in the Detailed Information panel.

Clicking on the Refresh button executes the last query once more and loads the latest DB data in the list table.

Detailed Information Panel

This panel displays the detailed information of the entry selected in the Query Result List Table. Table 1‑45 lists the detailed information.

 

Table 1‑45 Detailed Information

Name	Description
Domain	Tuxedo domain ID
Machine	Machine name
Group	Group name
Server	Server name
Server ID	Tuxedo server ID
PID	Server PID
Transaction Class	IMS transaction class
Transaction Name	IMS transaction name
Program Name	IMS program name
Logic Terminal	Logic terminal name
Region Type	The IMS region type, MPP or BMP
User ID	OS user ID
Start Time	IMS transaction/program start time point
End Time	IMS transaction/program stop time point
Elapsed Time	IMS transaction/program elapsed time from start to end (microseconds)
System CPU Time	System CPU time (microseconds)
User CPU Time	User CPU time (microseconds)
PSB Name	IMS PSB name
Program Elapsed Time	IMS program elapsed time (microseconds)
Current SPA Size	SPA size
Abend Code	Program abend code
Elapsed Time in DL/I	Total time elapsed in DL/I (microseconds)
Enqueue Number	Message number pushed in /Q
Dequeue Number	Message number popped from /Q
DLI Summary Information	The DLI summary information is presented by a table. One transaction/program may contain one or multiple DLI entries. There are four columns of the table, DL/I Event Name, DL/I Type, DL/I Invoked Count, and DL/I Total Duration (microsecond).

CICS/IMS/Batch Management

•	Batch Jobs Submit

•	Batch Jobs Search/Display

•	Batch Syslog Search/Display

•	CICS Resources View/Edit

•	IMS Resources View/Edit

Batch Jobs Submit

JES Job submit provides a quick way for you to submit a job through the TSAM Plus console. For more information, see Oracle ART Runtime documentation.

Notes:

To enable JES job submit and monitoring, you must set the JESMONITOR environment variable to yes before you start the LMS server and set the "JOBREPOSITORY" value in the JES configuration file to specify the path of the job repository.

If the "JOBREPOSITORY" value is not in the JES configuration file, the list panel lists the JOB in the APPDIR.

The JES job submit window contains the following panels:

•	JES Application Selection Panel

•	Job File Information List Panel

JES Application Selection Panel

Click List Available Jobs, all available job script files are listed in the Job File Information List Panel" if the selected JES application is alive.

Job File Information List Panel

Table 1‑46 lists the JES Job File Information List Panel options.

 

Table 1‑46 Job File Information List Panel Options

Options	Description
Script Name	Job script file name.
Name	Job name.
Priority	Job priority.
Class	Job class. Value may be [A-Z], [0-9]
Restart Option	The name of the step to use to restart the job
Type run	Indicates what should be done with the job. Choose one of the following: COPY - Copy the job directly in an output stream to sysout. HOLD - The system should hold the job. JCLHOLD - JES should hold the job. SCAN - Scan JCL for syntax errors only.
Version	The EJR runtime engine version.
Start label	The label of the first phase to be started
EJR Option	Enter the EJR Option you want to start the job with.
Shell Option	Enter the Shell Option you want to start the job with.

Select an item, and click Submit. If the job is submitted successfully, the display message appears as follows:

"Submit of Job xxxx was successful", where "xxxx" is the job id. Click View Job to see a detailed message. If it fails, an error message is displayed.

Batch Jobs Search/Display

JES Jobs metrics provides a quick way for you to view the latest JES jobs information.

The JES jobs window contains the following panels:

•	JES Jobs Query by Filter Panel

•	Jobs Query Results List Panel

•	Job Detail Information Panel

JES Jobs Query by Filter Panel

Table 1‑47 lists the JES Jobs Query by Filter options.

 

Table 1‑47 JES Jobs Query By Filter Options

Elements	Description
JES application	Specifies which JES system the Job is executed,. The single choice dropdown list contains only live/active ones, mandatory. Same as the JES tree node name.
Job classes	Specifies one or more classes
Job name	Specifies a search a string contained in the job name.
Job priority	Specifies one or more priorities
Job owners	Specifies one or more owners separated by a semi-colon (;) or a coma (,).
Job status	Specifies one or more of the following status categories: • EXECUTING • CONVING • WAITING • DONE • FAIL • HOLD_WAITING • HOLD_CONVING • INDOUBT • DISCARD
Submitted in latest _ seconds	Query the most recent Jobs submitted in latest a few seconds
Submit during	Query JES Jobs submitted during a specific time period.

You can also query the exact job ID by using 'Query by Job ID' subform. Fill in 'Job ID' and click Query; if found, the corresponding job is listed in the result.

Jobs Query Results List Panel

Table 1‑48 lists the JES Jobs Query Results List table columns.

 

Table 1‑48 'Jobs Query Results List Table Columns

Sort Options	Description
Name	Job name.
ID	Job ID
Node	Machine name
Owner	The person that submitted the job
Priority	Job priority.
Current Queue	The current queue where the job is placed.
Class	Job class. Value may be [A-Z], [0-9]
Submit Time	Time when the job was submitted.
End Time	Time when job completes.
Status	Job status.

Certain actions can be made to the queried out job list entries. Besides the Refresh button, Cancel, Purge, Hold, and Release actions can be used on selected jobs. The job cancel and purge behavior is the same same as the artjesadmin command. The command return status is displayed in a popup window.

Notes:

A job can be held only when the status is CONVING or WAITING.

A job can be released only when the job status is HOLD_WAITING.

A job can be purged only when the job is not in the PURGE queue.

Two additional actions/buttons (Job Logs and Job Sysouts) are located on the button bar that provide job log and job sysout information.

Notes:

If job logs or job sysouts exceed 10, 000 bytes, the file is truncated (that is, only the last 10,000 bytes are retained).

Purged jobs do not have Job Logs and Sysouts to view

All records in the job list table can be exported to a .xls file by clicking the Export to Excel button below the list table.

Note:

If you are using Internet Explorer, and IE security is set above medium, a warning message pops up when you click the Export to Excel button. Click the export button again to ignore the warning.

Choosing Monitoring Mode

You can change monitoring to auto refresh mode by specifying the Refresh Interval in the query result list panel toolbar; auto refresh is disabled by default. The refresh rate can be set as follows:

•

1 minute

•

5 minutes

•	10 minutes

•	30 minutes

•	60 minutes

•	120 minutes

Job Detail Information Panel

When you select a Job in the Job Query Results List table, detailed information for the selected job is displayed in the Job Detail Information panel. The job detailed information is self-explanatory and includes the following:

•	Running step

•	Running time

•	Current queue

•

Status

•

Type Run

•

Initiator

•

End Time

•	User CPU usage

•	System CPU usage

Note:

Job detail information is retrieved along with the Job Query List; the content may not reflect the latest information. To view the latest job details, click the refresh button.

Batch Syslog Search/Display

Oracle TSAM Plus allows you to query the Batch JES system log.

The Batch Syslog window contains the following panels:

•	JES Syslogs Query by Filter Panel

•	JES Syslogs Query Results Panel

JES Syslogs Query by Filter Panel

Table 1‑49 lists the JES Syslogs Query by Filter options.

 

Table 1‑49 JES Syslogs Query by Filter Options

Options	Description
JES Application	Specifies the JES system by which the JES syslog is showns
Job Name	Specifies a search string contained in the job name
Generated in Latest	Query syslog generated in the latest few seconds
Generated During	Query syslog generated during a specific time period

You can also query the exact syslog using the related job ID. In the field Query by Job ID , fill in the job ID and click Query. The corresponding syslog is listed in the results if searched.

JES Syslogs Query Results Panel

By default, only the latest 5000 lines of Batch JES syslog are shown. If there are more logs in your system, you can click the Prev chunk or Next chunk button to view the previous or next 5000 lines (the size of chunk) of the system logs.

In the current chunk, you can click the First/Prev/Next/Last page button to browse the system logs.

CICS Resources View/Edit

Oracle TSAM Plus allows you to query and edit CICS resource configuration files on the Oracle Tuxedo master node

Note:

To enable this function, you must make sure the ARTADM server runs on each node and the KIXCONFIG environment variable is set to the CICS resource files directory.

Querying CICS Resources

You can query CICS resources by region. All of the CICS Resource configuration files are listed after you select a CICS region and click the Query button.You can also click Refresh button to refresh the CICS Resource list for the selected CICS region.

Editing/Viewing CICS Resources

You can edit or view the CICS resource depending on the authority configured in User Management.

To edit the CICS Resource configuration file, you must do the following steps:

1.	Select one CICS region from region dropbox, then click the Query button. All of the CICS configuration files belonging to the selected region are listed.

2.	Select a configuration file then click the Edit button.

Note:

The Edit button is enabled when the number of selected configuration file is 1.

3.	Click the Update button to save the modification. You can also click the Back button to return to the list of CICS Resources without modifying the file.

Note:

If there are any format errors in the listed files, an error message is displayed.

For more information, see Oracle Tuxedo Application Runtime for CICS and Batch documentation.

IMS Resources View/Edit

Oracle TSAM Plus allows you to query and edit IMS resource configuration files on the Oracle Tuxedo master node.

Querying IMS Resources

You can query IMS resources by IMS domain. All of the IMS Resource configuration files are listed after you select an IMS domain and click the Query button.You can also click Refresh to refresh the IMS Resource list for the selected Tuxedo domain.

Editing/Viewing IMS Resources

You can edit or view the IMS resource depending on the authority configured in User Management.

To edit the IMS Resource configuration file, you must do the following steps:

1.	Select one IMS domain from IMS Domain drop down list, and then click the Query button. All of the IMS configuration files belonging to the selected domain are listed.

2.	Select a configuration file then click the Edit button.

Note:

The Edit button is enabled when the number of selected configuration file is 1.

3.	Click the Update button to save the modification. You can also click the Back button to return to the list of IMS Resources without modifying the file.

Note:

If there are any format errors in the listed files, an error message is displayed.

For more information, see Oracle Tuxedo Application Runtime for IMS documentation.

User/Data Management

Click Management and select the following from the drop-down list:

•	User Management

•	Data Management

•	Global Parameters

•

Blackout

•	Domain Group Management

User Management

The User List page allows you to add, edit and delete users and groups. An Oracle TSAM Plus group is a set of privileges. The default groups are "administrator" and "viewer". They cannot be deleted.

An Oracle TSAM Plus user may belong to one or more groups. When Oracle TSAM Plus is installed, the default user is “admin” (configured during installation), and cannot be deleted.

You can enter the Group List menu bar by clicking the Group List button, and return to the User List menu bar by clicking the User List button. Table 1‑50 lists the User List Menu Bar options.

 

Table 1‑50 User List Menu Bar

Elements	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns displayed in the table. • Detach: Displays the table in a separate window. • Reorder Columns: Change how the column order is displayed.
Change Properties	Allows you to change user properties (if proper permission is set) after login to the system. You can change all user properties from the User Management window if you have User Management administrator privileges. Select the user you want to edit and click the Change Properties button. If you are the selected user, you can change your own properties. The current property settings are shown in the corresponding text fields. Type new values for the following properties: • Full Name • Description • Group
Change Password	Allows you to change user password (if proper permission is set) after login to the system.Enter your old password, then enter the your new password. The password should be limited to 6~16 characters, and can contain the following characters: alphanumeric characters, underscores. You can change all user passwords from the User Management window if you have User Management administrator privileges. Select the user whose password you want to change and click the Change Password button. If you are the selected user, you can change your own password. Click Change Password to change the password. Click Back to cancel the operation and return to the User Management window. Note: The TSAM Plus user password is valid for 180 days. You need to change your user password before it is expired. If the password has expired, you can find related information recorded in the tsam.log file.
Create User	Allows you to add a new user. You must enter the following: Note: The Create User button is enabled only when the current logged-in user has User Management administrator privileges. • Name(*) The user login name. User name should be limited to 5~16 characters, and can contain the following characters: "[a-z], [A-Z], [0-9], _". The initial character must be [a-z] or [A-Z]. • Full Name The user full name. User full name should be limited to 128 characters, and can contain the following characters: alphanumeric characters, underscore, space, or period. • Password(*) User password. You need to provide password and confirm password. The password should be limited to 6~16 characters, and can contain the following characters: alphanumeric characters, underscores. • Description The users description. The description is limited to 255 characters, and can contain the following characters: alphanumeric characters, underscore, space, or period. • Group(*) A drop-down list. A created user can belong to on or more groups.
Delete User	Deletes the selected user.
Online User	The information of all online users is displayed in Online Users window. The available information of users includes Name, IP Address, Login Time and Session ID.
Refresh	Updates the user information list.
Detach	Displays the table in a separate window.

Table 1‑51 lists the Group List button bar options.

 

Table 1‑51 Group List Button Bar

Elements	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns displayed in the table. • Detach: Displays the table in a separate window. • Reorder Columns: Change how the column order is displayed.
Modify	Allows you to change group properties The "Modify" button is enabled when the current login user has the administrator privilege of group management. Select the group you want to edit and click the Modify button. The current property settings are shown in the corresponding text fields of the window. Type new values for the following properties: • Description • Privileges
Create Group	Allows you to add a new group. You must enter the following: Note: The Create Group button is enabled when the current logged-in user has User Management administrator privileges. The privileges you need to set are displayed below the input bar and listed in • Name(*) The group name. Group name should be limited to 5~16 characters, and can contain the following characters: "[a-z], [A-Z], [0-9], _". The initial character must be [a-z] or [A-Z]. • Id The group Id. It should be an integer and not less than 0. Note: If you use LDAP authentication, the Group ID must be the same as the one of the corresponding user in the LDAP server. • Description The group description. The description is limited to 255 characters. It can contain the following characters: alphanumeric characters, underscore, space, or period. • Privileges(*) A table. Allows you to set group privileges.
Delete Group	Deletes the selected group. A group cannot be deleted if there are any users who belongs to it.
Refresh	Updates the group information list.
Detach	Displays the table in a separate window.

Oracle TSAM Plus Group/User Privileges

Table 1‑52 lists the Oracle TSAM Plus Group/User privilege options.

 

Table 1‑52 Oracle TSAM Plus Group/User Privileges

Category	Privilege(s)
User Management	view, administrate
Group Management	view, administrate.
Data Management	administrate
Tuxedo Component Tree	view, administrate
ART region Tree	view, administrate
JES Component Tree	view, administrate
Global Parameter Setting	view, administrate
Tuxedo Policy Definition	view, administrate
ART Policy Definition	view, administrate
Tuxedo Alert Definition	view, administrate
ART alert Definition	view, administrate
Tuxedo Alert	view, administrate
ART Alert	view, administrate
Tuxedo Metrics	View Service Metrics, view call path Metrics, view transaction Metrics, view gateway Metrics, view bridge Metrics, view GWWS Metrics
ART Metrics	view Terminal Metrics, view CICS transaction Metrics
JES Metrics Management	View JES Metrics, administrate

Notes:

Note the following:

•	For lower left Unread Alert notification panel:

•	If you have Tuxedo Alert view privilege, but do not have ART alert view privilege, only the numbers of the Tuxedo alerts are shown.

•	If you do not have Tuxedo alert view privilege, but have ART alert view privilege, only the numbers of the ART alerts are shown.

•	If you do not have both Tuxedo and ART alert view privileges, the entire panel is hidden.

•	On the alert query page, if you have both Tuxedo alert view and ART alert view privileges, both types of alerts can shown in the query result table. However, without corresponding administrate privilege, administrator tasks (such as Clear and Delete) are not available.

For example, you have Tuxedo alert, ART alert and Tuxedo alert administrate privileges. When you select all the queried out alerts (including both Tuxedo alert and ART alert type), the Clear and Delete button above the query result table is disabled.

•	Group privilege is based on the User View privilege. The user cannot enter the group management console without User Management view privileges.

Data Management

Data Management allows you to purge the Oracle TSAM Plus database data (including the monitoring data in the database and the invalid Oracle Tuxedo components in the database).

Purging Monitoring Metrics Data

You can purge all monitoring data including Server/Service data and Call Path/ XA Transaction data. To purge Monitoring data, do the following steps:

1.	Select the Types you want purged.

•

All

•

Call Path

•

Bridge

•

GWTDOMAIN

•

Service

•	XA Transaction

•	User payload metrics

•

GWWS

•

Alert

•	Tuxedo CICS Terminals

•

JES

•

IMS

Note:

•	If you want to purge Tuxedo CICS Transaction data, "Service" type can be selected.

•	Only user payload metrics stored in TSAM plus database can be purged here. User payload metrics stored in Hadoop or local file can only be purged by the user manually.

•	Purging call path or service metrics does not delete the corresponding user payload metrics.

2.	Set the Old Than date, before which the monitoring data will be purged.

3.	Click the Purge button to delete monitoring data from the database.

The statistics service metrics data are purged automatically:

•	Raw data are purged after 7 days.

•	Hourly aggregated data are purged after 32 days.

•	Daily aggregated data are purged after 12 months.

Purging Invalid Tuxedo Components Nodes

Tuxedo components can be changed to "INValid" status due to management operations at Tuxedo application side. By default, the "INValid" Tuxedo components are not deleted from the database.Customers can purge all "INValid" Tuxedo components in the Data management window.

Note:

Currently, only the purging all "INValid" Tuxedo components on the data management page is supported. Invalid components can be purged in the component tree.

Global Parameters

The Global Parameters page contains following tabs:

•	TSAM Plus Global Properties

•	TSAM Plus Manager Properties

Table 1‑53 lists the TSAM Plus Global properties.

 

Table 1‑53 TSAM Plus Global Properties

Properties	Description
TSAM Plus User password Life Time(days)	The period of time, in days, that a user password is in effect. Its value can be 0~2147483647. The default value is 180 days. If specified to 0, the password will never expire.
Maximum Selected Services in Service Metrics	The maximum selected services in Service Metrics.
Call pattern calculation schedule	The period of statistics job run for Call Pattern. The valid value is DAILY or HOURLY. DAILY is the default value. The modifications of this parameter take effect immediately. This parameter is applicable for Oracle Database only. If TSAM database is Derby, it is invisible.
Call pattern calculation delay (minutes)	The delay minutes after one hour or day for statistics job run for Call Pattern. If schedule is HOURLY, the valid value is 10~59. and 30 is the default value. If schedule is DAILY, the valid value is 10~1439, and 120 is the default value. The modifications of this parameter take effect immediately. This Parameter is applicable for Oracle Database only. If TSAM database is Derby, it is invisible.
Automatic data purge	Automatically purge data or not. FALSE is the default value. The modifications of this parameter is stored in Oracle database immediately. If Automatic data purge is TRUE, the expired monitoring data is purged at time by the value of Daily Maintenance Every Day. This Parameter is applicable for Oracle Database only. If TSAM database is Derby, it is invisible.
Reserve monitoring data for days	Days for data to be reserved before purging. If purge is FALSE, it is set to -1 and is not editable. If purge is TRUE, its valid value is 0~2880. The modifications of this parameter is stored in Oracle database immediately. If Automatica data purge is TRUE, the expired monitoring data is purged at time by the value of Daily Maintenance Every Day. This Parameter is applicable for Oracle Database only. If TSAM database is Derby, it is invisible.
Daily Maintenance Every Day	Change the schedule when Oracle Database daily maintenance job (TSAM_JOB_DAILY) executes. TSAM_JOB_DAILY purges expired monitoring data if Automatic data purge is TRUE.
Statistics Collection Interval (minutes)	Specify the interval to collect the statistics metrics data presented in dashboards. For more information, refer to Domains Dashboard.
Payload Storage	Select one of the user payload data storage: Database, Hadoop, or local file.
Hadoop URL	Specify the Hadoop URL where you want to storage the user payload data. The Hadoop URL must include the hostname, port, and payload file directory. For example: hdfs://localhost:8080/tmp/tuxPayload/ If the URL is invalid or unreachable, a warning message is displayed.

Table 1‑54 lists the TSAM Plus Manager properties for each panel.

 

Table 1‑54 Manager Parameter Properties

Properties	Description
Default Top N of Services	The number of most active services on Service Monitoring page. The default value is 2.
Tuxedo Application Runtime Feature Enabled Check Box	Indicates if oracle Tuxedo Application Runtime related components/pages are displayed on TSAM Plus console. Note: If you check or unchecked Tuxedo Application Runtime Feature Enabled, you must restart the Oracle TSAM Plus application for the change to take effect.
Synchronous Query Timeout (seconds)	Allows you to set the JES Job query timeout value (in seconds). The default value is 30 seconds.
Authentication Type	This value specifies the authentication method used by TSAM Plus manager.The optional values are: LDAPOnly and LocalFirst. LDAPOnly specifies that authentication is performed through LDAP. LocalFirst specifies that TSAM Plus manager tries to do authentication with TSAM Plus database first. The default value is LocalFirst.
Configuration Files Backup Directory	The directory for configuration files backup. The default path is $USER_INSTALL_DIR$. Note: To back up configuration files successfully, properly set the file permission of the backup directory, or start up TSAM Plus Manager web server using the same account as the backup directory file owner
Max Persistence Threads	Denotes how many persistence threads in a persistence thread pool. This number should not be bigger than the CPU number of the host running the Data server of TSAM Plus manager. The default value is 2.
Data Persistence Queue Size	The maximum of the metric entity list in queue. The default value is 5000.
Data Persistence Queue Size	The maximum of the metric entity list in the persistence queue before traffic control. The default value is 5000.
Queue Full Sleep Interval (milliseconds)	Denotes the sleep interval (in milliseconds) in case the MAX_INQUEUE_RUNNER_NUM value is crossed. The default value is 500.
Queue Full Sleep Interval (milliseconds)	Denotes the LMS sleep interval (in milliseconds) in case the value of Data Persistence Queue Size is exceeded. The default value is 500. If the value of Data Persistence Queue Size is exceeded, TSAM Plus Manager persistence threads process the data metric as normal, and at same sends LMS a response with sleep interval (in milliseconds). LMS sleeps for the interval before sending another data metric.
Timeout Shutdown (seconds)	Denotes the timeout (in seconds) to give metric entity persistence threads a chance to finish their job after you shutdown the Oracle TSAM Plus manager. The default value is 30.
Enable DYNAMIC_RAP	Denote if DYNAMIC_RAP(configure in BDMCONFIG) feature Oracle Tuxedo JCA Adapter should be supported or not. If this parameter is enabled, the remote JCA adapter domain connected by DYNAMIC_RAP can be selected from domain gateway monitored page.
TSAM Plus Manager Log Level	Log level control for TSAM Plus Manager. The default value is Info. (Trace, Debug, Info, Warn, Error). Log level modifications take effect immediately; you do not need to reboot the application server.
JPA SQL Log Level	Log level control for JPA SQL. The default value is Warn. (Trace, Debug, Info, Warn, Error). Log level modifications take effect immediately; you do not need to reboot the application server.

Clicking on the Modify Command button saves the modifications into DB or properties file. If you need to reboot the TSAM Plus Manager, you can get the information in popup box.

Clicking on the Refresh command loads current value of each property from DB or properties file.

Blackout

With the Blackout management feature, users can easily control the metric data collection schedule. Once a Blackout starts, there is no metric data communication between TSAM manager and agent. Blackouts can be started or ended immediately, or according to a specific schedule.

List Blackout Definitions

Blackout List panel lists all the defined blackout definitions. Blackout policy is enabled on domain level. The blackout list contains the following information for each blackout definition:

 

Table 1‑55 Blackout List Table Content

Column	Description
Select	The selection checkbox.
Blackout Name	Globally unique Blackout name.
Domain ID	On which domain the Blackout defines.
Status	Enabled/Disabled This status indicates whether this blackout is enabled.
Schedule Summary	Show the Blackout schedule summary. Policy content is organized in xml, each policy have following child nodes. • starttime: start time in seconds. • duration: duration time in seconds. -1 for infinite • endtime: end time in seconds.-1 for no end time • repeattype: repeat type. • repeatvalue: repeat value. Default value is 0. • heartbeat: heart beat interval. -1 for stopping heartbeat

Note:

Blackout Name and Policy Name must be different as they share the same naming space.

Table 1‑56 lists the actions you can take:

 

Table 1‑56 Blackout List Table Controls

Control	Description
Add	Adds Blackout schedule on specific domain(s). The Blackout creation is done in the Edit Blackout page.
Delete	Removes defined Blackout on the selected domain(s). Blackout on this domain is removed if the connection between agent and manager is OK.
Enable	Enables the selected Blackout(s) immediately.
Disable	Disables the selected Blackout(s) immediately.
Edit	Edits the Blackout definition. The control is disabled when multiple Blackouts are selected.
Clone	Adds a new Blackout with the same schedule of the selected one. The control is disabled when multiple Blackouts are selected.
Refresh	Refreshes the table.

Add/Edit a Blackout Definition

On clicking of the Create or Edit button in the Blackout List table, the Create/Edit Blackout page is shown. Table 1‑57 lists the fields that should be filled to define a Blackout schedule.

 

Table 1‑57 Create/Edit Blackout Fields

Field	Options	Description	Validation
Name		Globally unique Blackout name.	It cannot exceed 255 characters.
Domain		The corresponding Domain.
Heartbeat Frequency		Agent send heart beat frequency. Agent do not send heart beat if this check box is not choosen.
Start	Immediately	Blackout start time. It's converted to TSAM manager current time when user save this blackout.
	Later	Specify the Blackout start date/time.	A valid date string
Duration	Infinite	No end Blackout.
	Length	How many hours and minutes the Blackout last.	Hour should be a number and in range (0,1000000). Minutes should be a number and in range (0,59) Hours and Minutest should not be zero at the same time.
	Until	Until the designated time.	A valid date string
Repeating	Type	At what frequency the Blackout repeats. "By minutes","By Hours","By Days". "Weekly","Monthly".
	Frequency	Repeat period..	It should be a number and in range (0,1000000)
End Date	No End Date	Infinite repeating.
	Specified End Date	Specify the repeating end date/time.	A valid date string

Note:

TSAM Plus Manager should be synchronized with agent. All time inputted in TSAM Plus console is taken as the time zone of TSAM Plus Manager.

Add and Add & Enable buttons are shown when you create a new blackout.

Save and Save & Enable buttons are shown when you edit an existing blackout.

•

Add

Save the Blackout schedule configuration, start the Blackout immediately if "Immediately" is configured, or schedule it for later run.

•	Add & Enable

Save and enable blackout, then back to the Blackout List Page.

•

Save

Save the modified Blackout schedule configuration, start the Blackout immediately if "Immediately" is configured, or schedule it for later run.

•	Save & Enable

Save and enable the modified Blackout schedule configuration.

•

Cancel

Cancel the Blackout creation/edition and back to the Blackout List page.

Domain Group Management

The Domain Group Management page allows you to create and manage domain groups. A domain group can be monitored in the domains dashboad.

Viewing Domain Group List

The Domain Group List shows all the domain groups created. Table 1‑58 lists the information you can view for each group.

 

Table 1‑58 Domain Group List

Items	Description
Name	Domain group name
Domain Count	The number of domains included in the group
Domains	The name of domains belonging to the group
Key Services	Key services defined in the group. The key services is a set of services you want to monitor regularly from the domains dashboard.

Creating a New Domain Group

To create a new domain group, do the following:

1.	From the Domain Group List, click Add.

2.	In the window that appears, specify the following and click OK.

•	Domain Group Name: Define a group name

•	Domain Selection: Select the domains you want to include in the group

•	Key Services: Optional. Select up to seven services that you want to monitor regularly from the group dashboard. Only the services that are available across all domains can be selected.

Editing a Domain Group

To edit a domain group, do the following:

1.	From the Domain Group List, highilght the group you want to edit.

2.	Click Edit.

3.	Specify the domains and key services, and then click OK.

Load Generator

You can create the replay definition from call paths by Clicking Load Generator ->Replay Definition. Based on the replay definition, you can execute the replay for standard and stress test modes. For more information, see Using Test Load Generator.

Alert Monitoring

Click Alert and select one of the following:

•	Tuxedo Alert Definition

•	CICS Alert Definition

•	IMS Alert Definition

•	Batch Alert Definition

•	Alert Query

•	Alert Metrics Tables

Tuxedo Alert Definition

Click Alert and select Tuxedo Alert Definition from the drop-down list; the Tuxedo Alert Definition List Panel appears. This panel lists available alert definitions and allows you to create, edit, and manage alert definitions.

Table 1‑59 and Table 1‑60 list the Tuxedo Alert Definition Menu Bar and Tuxedo Alert Column options respectively.

 

Table 1‑59 Tuxedo Alert Definition Menu Bar Options

Options	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns displayed in the table. • Detach: Displays the table in a separate window. • Reorder Columns: Change how the column order is displayed.
Add	Creates a new alert definition.
Delete	Deletes the alert definition.
Enable	Enables the alert definition.
Disable	Disables the alert definition.
Edit	Modifies the alert definition.
Clone	Creates a new alert with same definition as current alert but the name is left empty.
Alerts	See all alerts generated by this alert definition.
Refresh	Refresh the alert definition list.
Detach	Displays the table in a separate window.

 

Table 1‑60 Tuxedo Alert Columns

Column	Description
Selection checkbooks	Select a set of alert definitions in current page for processing.
Name	The alert name specified in the alert definition.
Status	Displays alert status. The status could be enabled or disabled. Enable: The alert definition enabling request has been sent to Oracle Tuxedo. Disable: The alert definition disabling request has been sent to Oracle Tuxedo.
Type	The monitoring category and system are consistent with policy definition. The category types are as follows: • Call Path • Service • XA Transaction • BRIDGE • GWTDOMAIN • GWWS • Service Statistics: a “default_adaptive_alert” is enabled by default.
Evaluation Condition	The FML Boolean expression of the alert triggering conditions
Tuxedo Components	The resource FML Boolean expression (similar to Policy definition).

Define New Alert Page

Click the Add, Edit or Clone button on the Alert Definition List Menu bar; the Define New Alert page appears. It allows you to define a concrete Oracle Tuxedo alert definition.

The Define New Alert page is divided into four sections:

•	Alert Properties

•	Tuxedo Components

•	Metrics Evaluation Expression(s)

•	FML Boolean Expression(s)

Alert Properties

Table 1‑61 lists the Alert Properties options.

 

Table 1‑61 Alert Properties Options

Options	Descriptions
Name	The name of the alert. It must be unique among the alerts globally. The name value is limited to 255 characters and must be unique within the project. The initial character must not be a “.”.
Type	The type of the alert; it is based on monitoring policy. The drop-down list includes the following items: • Call Path • Service When you select a service alert, the Metrics Independent Checking check box appears. It allows Oracle TSAM Plus to check service timeouts independent of metrics collection. The alert can be generated while the service is running. If checked, “Drop Message” is removed from the “Action” option drop-down menu. • Service Statistics You can define one or more service statistics alerts for a Tuxedo domain or a domain group. When you select a service statistics alert, the configuration panel becomes different than other alert types. You can configure TSAM Plus to compare the instant metric data with a static threshold or historical data to evaluate and trigger the service statistics alerts. For more information, see Adaptive Settings (For Service Statistics Alerts Only). • XA Transaction • GWTDOMAIN • BRIDGE • GWWS
Severity	The severity drop-down list contains the following severity levels: • Fatal • Critical • Warn • Information
Interval	Accepts an integer value in seconds. The current alert is evaluated only once during this interval. The purpose is to throttle alert volume in similar scenario. If the interval value is 0, any alert is reported.
Action	Specifies what kind of action is executed when an alert definition is set to "true". The following actions are supported: • Publish to Tuxedo Event Broker An event is posted to the Oracle Tuxedo event broker. The event name is the alert name by default; you can also specify it manually. The buffer is an FML32 buffer containing the metric snapshot. • Drop Message If this alert evaluation is true, the request message is dropped and the call fails (TPESYSTEM). This only applies to Call Path and Service type alerts. The evaluation points come before the request sent to the IPC queue (call path) and after it is retrieved from the IPC queue (call path, service). This alert can be used to avoid unneeded service processing for stagnant requests. For example, if the request message "Wait Time" in the IPC queue exceeds a particular threshold, the client may have already timed out. In this case, the action can drop the stagnant request and the application server will not process it. Caution: If the drop message action is executed in a embedded Tuxedo call, the whole call fails.

Tuxedo Components

The Component Scope panel contains the following selections:

•	Domain Group: For service statistics alerts only.

•	Domain: Optional

•	Machine: Optional

•	Group: Optional

•	Server: Optional

Note:

Machine, Group, and Server can also accept FML32 boolean expressions.

Click the radio button to select input method (use the drop-down list or manually enter an FML32 boolean expression). The values of each level is determined by its parent level, except for Domain.

•	Services: For service statistics alerts only.

Metrics Evaluation Expression(s)

You can select the metric, operator and threshold to compose one expression. The logic for the expression can be "and" or "or".

FML Boolean Expression(s)

You can also input FML Boolean expressions directly. For more information, see Alert Metrics Tables. For call path alerts, if the elapsed time only is evaluated in the evaluation expression, the alert is triggered once along the entire call path. Other metrics combined with elapse time do not have this effect.

Note:

The TSAM Plus Console cannot guarantee FML Boolean expression syntax correctness.

Adaptive Settings (For Service Statistics Alerts Only)

For service statistics alerts, when you select Adaptive Threshold in the Logic for Expression panel, you need to continue to configure the Adaptive Settings. It specifies a past time of which the metrics data are used for comparison with current time collected data. If the comparison result meets the criteria you set in the metrics evaluation expression, an alert is reported.

•	Daily: the average or aggregated metrics data of one day is compared for evaluation. You can select one day of the past 30 days.

•	Hourly: the average or aggregated metrics data in one hour of a day is compared for evaluation. You can specify how many hours ahead (-) of or after (+) current hour in one day of the past 30 days.

For example, if you define an adaptive alert evaluation expression for the response time metrics and specify Adaptive Settngs as “Hourly, 1 day ago, -5 hours”, the average response time between 1:00 pm to 2:00 pm yesterday will be used for comparison with each response time data collected during 6:00-7:00 pm today.

The Per Service Instance is only avaiable for the time-related metrics, of which average data is calculated. When this option is checked, the metrics data collected from each service instance is evaluated against the historical average data.

CICS Alert Definition

Click Alert and select CICS Alert Definition from the drop-down list; the CICS Alert Definition List panel appears. This panel lists available CICS alert definitions and allows you to create, edit, and manage alert definitions.

CICS Alert Definition List Panel

Table 1‑62 and Table 1‑63 list the CICS Alert Definition List menu bar options and columns respectively.

 

Table 1‑62 CICS Alert Definition List Menu Bar

Elements	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns to shown in the table • Detach: Displays the table in a separate window • Reorder Columns: Change the order how the columns are displayed
Add	Creates a new alert definition.
Delete	Deletes the alert definition.
Enable	Enables the alert definition.
Disable	Disables the alert definition.
Edit	Modifies the alert definition.
Clone	Creates a new alert with same definition as current alert but the name is left empty.
Alerts	Identifies all alerts generated by this alert definition.
Refresh	Updates the alert definition list.
Detach	Displays the table in a separate window.

 

Table 1‑63 Alert Definition List Columns

Column	Description
Selection checkbooks	Select a set of alert definitions in current page for processing.
Name	The alert name which is specified in alert definition
Status	Displays alert status. The status could be enabled or disabled. Enable: The alert definition enabling request has been sent to Tuxedo. Disable: The alert definition disabling request has been sent to Tuxedo.
Type	The monitoring category and system, consistent with policy definition. The category types are as follows: • CICS Transaction • CICS Terminal
Evaluation Condition	The FML Boolean expression of the alert triggering conditions.

Define New Alert Panel

Click Add or Clone on the menu bar; the Define New Alert panel appears. This panel allows you to define concrete Tuxedo Application Runtime alert definitions.

The Define New Alert panel is divided into three sections:

•	Alert Properties

•	Metrics Evaluation Expression(s)

•	FML Boolean Expression(s)

Alert Properties

Table 1‑64 lists the Alert Properties options.

 

Table 1‑64 Alert Properties Options

Column	Description
Name	The name of the alert. It must be unique among the alerts globally. The name value is limited to 255 characters and must be unique within the project. The initial character must not be a “.”.
CICS Region	Defines the function scope of the defined alert.
Type	The type of the alert; it is based on monitoring policy. The drop-down list includes the following items: • CICS Transaction • CICS Terminals
Severity	The severity drop-down list contains the following: • Fatal • Critical • Warn • Information
Interval	It accepts an integer value (in seconds). The current alert is evaluated only once during this interval. The purpose is to throttle alert volume in a similar scenario.
Action	Specifies what kind of action is executed when an alert definitionset to "true". It supports the following action: • Publish to Tuxedo Event Broker An event is posted to the Oracle Tuxedo event broker. The event name is the alert name by default; you can also specify it manually. The buffer is an FML32 buffer containing the metric snapshot.

Metrics Evaluation Expression(s)

You can select the metric, operator and threshold to compose one expression. The logic for the expression can be "and" or "or".

FML Boolean Expression(s)

You can also input FML Boolean expressions directly. For more information, see Alert Metrics Tables.

Note:

The TSAM Plus Console cannot guarantee FML Boolean expression syntax correctness.

IMS Alert Definition

Click Alert and select IMS Alert Definition from the drop-down list; the Alert Definition List panel appears. This panel lists available Tuxedo Application Runtime IMS alert definitions and allows you to create, edit, and manage alert definitions.

IMS Alert Definition List Panel

Table 1‑65 and Table 1‑66 list the IMS Alert Definition List menu bar options and columns respectively.

 

Table 1‑65 IMS Alert Definition List Menu Bar

Elements	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns to shown in the table • Detach: Displays the table in a separate window • Reorder Columns: Change the order how the columns are displayed
Add	Creates a new alert definition.
Delete	Deletes the alert definition.
Enable	Enables the alert definition.
Disable	Disables the alert definition.
Edit	Modifies the alert definition.
Clone	Creates a new alert with same definition as current alert but the name is left empty.
Alerts	Identifies all alerts generated by this alert definition.
Refresh	Updates the alert definition list.
Detach	Displays the table in a separate window.

 

Table 1‑66 Alert Definition List Columns

Column	Description
Selection checkbooks	Select a set of alert definitions in current page for processing.
Name	The alert name which is specified in alert definition
Status	Displays alert status. The status could be enabled or disabled. Enable: The alert definition enabling request has been sent to Tuxedo. Disable: The alert definition disabling request has been sent to Tuxedo.
Type	The monitoring category and system, consistent with policy definition. The category types are as follows: • IMS Transaction • IMS Program
Evaluation Condition	The FML Boolean expression of the alert triggering conditions.

Define New Alert Panel

Click Add or Clone on the menu bar; the Define New Alert panel appears. This panel allows you to define concrete Tuxedo Application Runtime IMS alert definitions.

The Define New Alert panel is divided into three sections:

•	Alert Properties

•	Metrics Evaluation Expression(s)

•	FML Boolean Expression(s)

Alert Properties

Table 1‑67 lists the Alert Properties options.

 

Table 1‑67 Alert Properties Options

Option	Description
Name	The name of the alert. It must be unique among the alerts globally. The name value is limited to 255 characters and must be unique within the project. The initial character must not be a “.”.
Domain	Defines the function scope of the defined alert.
Type	The type of the alert; it is based on monitoring policy. The drop-down list includes the following items: • IMS Transaction • IMS Program
Severity	The severity drop-down list contains the following: • Fatal • Critical • Warn • Information
Interval	It accepts an integer value (in seconds). The current alert is evaluated only once during this interval. The purpose is to throttle alert volume in a similar scenario.
Action	Specifies what kind of action is executed when an alert definitionset to "true". It supports the following action: • Publish to Tuxedo Event Broker An event is posted to the Oracle Tuxedo event broker. The event name is the alert name by default; you can also specify it manually. The buffer is an FML32 buffer containing the metric snapshot.

Metrics Evaluation Expression(s)

You can select the metric, operator and threshold to compose one expression. The logic for the expression can be "And" or "Or".

FML Boolean Expression(s)

You can also input FML Boolean expressions directly. For more information, see Alert Metrics Tables.

Batch Alert Definition

You can view, add, edit and delete JES Alert Definitions through Alert Definition

Click Alert and select Batch Alert Definition from the drop-down list; the Batch Alert Definition List panel appears. This panel lists available Batch alert definitions and allows you to create, edit, and manage alert definitions.

Batch Alert Definition List Panel

Table 1‑68 and Table 1‑69 list the Batch Alert Definition List menu bar options and columns respectively.

 

Table 1‑68 Batch Alert Definition List Menu Bar

Elements	Description
View	From the drop-down menu, you can select the following: • Columns: Select the columns to shown in the table • Detach: Displays the table in a separate window • Reorder Columns: Change the order how the columns are displayed
Add	Creates a new alert definition.
Delete	Deletes the alert definition.
Enable	Enables the alert definition.
Disable	Disables the alert definition.
Edit	Modifies the alert definition.
Clone	Creates a new alert with same definition as current alert but the name is left empty.
Alerts	Identifies all alerts generated by this alert definition.
Refresh	Updates the alert definition list.
Detach	Displays the table in a separate window.

Click Add or Edit; the JES Alert Definition panel appears.

 

Table 1‑69 Alert Properties Options

Elements	Description
Name	The name of the alert. It must be unique among the alerts globally. The name value is limited to 255 characters and must be unique within the project. The initial character must not be a “.”.
Type	The type of the alert; it is based on monitoring policy. The drop-down list includes the following items: • JES Jobs • JES Metrics
Severity	The severity drop-down list contains the following: • Fatal • Critical • Warn • Information
Interval	It accepts an integer value (in seconds). The current alert is evaluated only once during this interval. The purpose is to throttle alert volume in a similar scenario.

Batch Alert Definition Filter Conditions

Table 1‑70 lists the Batch Alert Definition Filter Conditions options.

 

Table 1‑70 Batch Alert By Filter Options

Options	Description
JES Application	Identifies which JES application the Job is executed, single choice dropdown list, required. Note: Job information can be only be obtained when the selected JES application is alive. If an inactive JES application is selected when clicking the 'Query' button, a warning message window is displayed.
Job Name	The string contained in the job name, input text box.
Job Owner	One or more owners of the job, input text box.
Job Priority	One or more priorites.
Job Class	The job class, multiple choice dropdown list.

Batch Alert Definition Details

If the Type is Batch Job, the Batch metric detail panel provides the information shown in Table 1‑71. Three levels of metric details can be selected and displayed: Job Status, Job Execution Time, and Job.

 

Table 1‑71 JES Job Type Detailed Information

Elements	Description
Job Status	Job status is changed to the specified status. You can specify one of the following: • EXECUTING • CONVING • WAITING • DONE • FAIL • HOLD_WAITING • HOLD_CONVING • INDOUBT • DISCARD
Job	Job is purged
Job Execution Time	Job execution time >= ? millisecond during the last Interval seconds

If the Job Type is JES Metrics, the JES metric detail panel provides the information shown in Table 1‑72

 

Table 1‑72 JES Metrics Type Detailed Metrics Information

Elements	Description
Jobs average execution time	Job average execution time >= ? millisecond during the last Interval seconds
Jobs fails number	Jobs fails number >= during the last Interval seconds
Jobs waiting number	Jobs waiting number >= during the last Interval seconds

Alert Query

Alert Query view displays the alerts that have transpired. It includes metric alerts and system alerts. Metrics alert are the events generated against the defined metrics alert. System alerts represent system events.

Click Alerts and select Alert Query from the drop-down menu; the Alert Query page appears.The Alert Query page contains two tabs:

•	Unread Alerts Tab: Displays all unread alerts.

•	Historical Alerts Tab Provides historical alert query information.

Unread Alerts Tab

"Unread" alerts are most important for administrators because they represent events that they may not be aware of. The Unread Alerts tab contains two sections:

•	Filtering Condition

•	Unread Alert Columns

Table 1‑73 lists the Alert Query filtering condition options.

 

Table 1‑73 Alert Query Filtering Conditions

Options	Description
Contains	Select a set of alerts in current page for processing.
Type	The monitoring category and system are consistent with policy definition. The following category types are as follows: • Any • Call Path • Service • Service Statistics • XA Transaction • BRIDGE • GWTDOMAIN • GWWS • CICS Transaction • CICS Terminals • JES Job • JES Metrics • IMS Transaction • IMS Program • System Note: System represents this is a system-level event generated by Oracle TSAM Plus.
Severity	Four severity levels are supported: • Any • Fatal • Critical • Warn • Information

Table 1‑74 lists the Alert Query columns.

 

Table 1‑74 Alert Query Columns

Column	Description
Selection checkbox	Select a set of alerts in current page for processing.
Name	The alert name which is specified in alert definition.
Type	The monitoring category and system are consistent with policy definition. The following category types are as follows: • Any • Call Path • Service • Service Statistics • XA Transaction • BRIDGE • GWTDOMAIN • GWWS • CICS Transaction (Tuxedo Application Runtime only) • CICS Terminals (Tuxedo Application Runtime only) • IMS Transaction • IMS Program • JES Job (Tuxedo Application Runtime only) • JES Metrics (Tuxedo Application Runtime only) • System Note: System represents this is a system-level event generated by Oracle TSAM Plus.
Severity	Four severity levels are supported: • Any • Fatal • Critical • Warn • Information
Cleared	Indicates whether the alert has been marked as read.
Clear Time	Identifies the time an alert is “cleared.”
Log Time	The time an Alert occurs.
Description	The reason/cause for the alert. It uses the following format: "Process [%s:%d] evaluates alert [%s] with true, metrics[key=value,key=value...]"

Click Clear to clear all the selected alerts on current page.

Click Delete to delete all the selected events on current page.

Click Detail, a popup window with the following detailed Alert information appears:

•	All information in the alerts summary data grid.

•	The metrics detail and reason string for this alerts.

Once an alert is cleared as "Unread" status and not deleted, it still can be queried in the historical alert page, but not in the active alert page. The following filter conditions can be set:

•	Alert Type

•	Alert Severity

•	A custom "search" text string

The search operation finds matched records from all current filtered "unread" alert results, no limited to the "unread" alerts shown on the current page. Matched record means any alert that is matching the specified alert category condition, alert severity condition and having the given "search" text string within any of the following value fields: "Alert Name", "Alert Reason String (Description)".

Click the Reset button to reset filter conditions and list all "unread" alerts.

Historical Alerts Tab

The Historical Alerts Tab allows you to query historical alerts with supplied filtering conditions. It contains two panels:

•	Historical Alert Query Conditions

•	Alerts Query Results

Table 1‑75 lists the Historical Alert Query Conditions panel options.

 

Table 1‑75 Historical Alerts Query Conditions Options

Options	Description
Alert Name	The Alerts names configured in this project. "Any" is a reserved key word meaning all alerts.
Type	"Any" and the supported monitoring categories. System is in same level with other monitoring categories.
Severity	"Any" and supported severity levels. If Include Lower Level is checked, all alerts at this level or below are queried. The sequence is Fatal, Critical, Warn and Info.
Query During	The exact time of the previous day to the exact same time of the current day. For example: 7:45 Wednesday-to-7:45 Thursday.

Click Submit; the results are displayed in the Alert Query Result panel.

System Alerts Supported

Users cannot define System Alerts; they are generated automatically (for example, an invalid alert definition is encountered, or the database purging process is completed).

Table 1‑76 lists the supported system alerts.

 

 

Table 1‑76 System Alerts Supported

Alert name	Alert Severity	Alert Reason String
.INVALIDEXP	warning	Alert definition [%ALERT_NAME] has invalid evaluation expression
DB.PURGE	information	Data purging(sequence:?) filed at [%DATE_TIME] by admin is done.

Alert Metrics Tables

The Alert Metrics tables contain the alert metrics for all alert types. Each metric has the corresponding FML32 field name and applicable operators. Referencing these tables will help you write the alert metric FML boolean expression directly when defining a new alert.

•	Call Path Alert Metrics Table

•	Service Alert Metrics Table

•	GWTDOMAIN/BRIDGE Alert Metrics Table

•	GWWS Alert Metrics Table

•	XA Transaction Alert Metrics Table

•	CICS Transaction Alert Metrics Table

•	CICS Terminals Alert Metrics Table

•	IMS Transaction Alert Metrics Table

•	IMS Program Alert Metrics Table

Call Path Alert Metrics Table

 

Table 1‑77 Call Path Alert Metrics Table

Metric	FML32 Field	Operators
Elapse Time	TA_MONELAPSETIME	>, >=
Execution Status	TA_MONERRNO	==, !=
URcode	TA_MONURCODE	==, !=
Depth	TA_MONDEPTH	>, ==, <
Message Number on Request Queue	TA_MONMSGQUEUED	>, >=

Service Alert Metrics Table

 

Table 1‑78 Service Alert Metrics Table

Metric	FML32 Field	Operators
Execution Time	TA_MONEXECTIME	>, >=
Execution Status	TA_MONERRNO	==, !=
Request Message Size	TA_MONMSGSIZE	>, >=
Message Number on Request Queue	TA_MONMSGQUEUED	>, >=
URcode	TA_MONURCODE	==, !=
Waiting Time	TA_MONMSGWAITTIME	>, >=
CPU Time	TA_MONCPUTIME	>, >=

GWTDOMAIN/BRIDGE Alert Metrics Table

 

Table 1‑79 GWTDOMAIN/BRIDGE Alert Metrics Table

Metric	FML32 Field	Operators
Link Status (GWTDOMAIN/BRIDGE)	TA_MONLINKSTATUS	Lost, Reconnect
Outstanding Request (GWTDOMAIN)	TA_MONNUMWAITRPLY	>, >=

GWWS Alert Metrics Table

 

Table 1‑80 GWWS Alert Metrics Table

Metric	FML32 Field	Operators
Inbound one way failed number	TA_MONINOWFAIL	>, >=
Outbound one way failed number	TA_MONOUTOWFAIL	>, >=
Inbound RPC failed number	TA_MONINRPCFAIL	>, >=
Outbound RPC failed number	TA_MONOUTRPCFAIL	>, >=
Inbound average processing time	TA_MONINTIME	>, >=
Outbound average processing time	TA_MONOUTTIME	>, >=
Inbound Pending Request	TA_MONINBOUNDPEND	>=
Outbound Pending Request	TA_MONOUTBOUNDPEND	>=

XA Transaction Alert Metrics Table

 

Table 1‑81 XA Transaction Alert Metrics Table

Metric	FML32 Boolean Expression
Transaction Failed	TA_MONXANAME=='tpabort' || TA_MONXANAME=='xa_rollback'
Heuristically Completed	TA_MONXANAME=='xa_commit' && TA_MONXACODE==8
Heuristically Commit	TA_MONXANAME=='xa_commit' && TA_MONXACODE==7
Resource Manager Failure	TA_MONXANAME%%'xa_.* ' && TA_MONXACODE==-3

CICS Transaction Alert Metrics Table

 

Table 1‑82 CICS Transaction Alert Metrics Table

Metric	FML32 Field	Operators
Execution Time	TA_MONEXECTIME	>, >=
Message Number on Request Queue	TA_MONMSGQUEUED	>, >=
Waiting Time	TA_MONMSGWAITTIME	>, >=
CPU Time	TA_MONCPUTIME	>, >=

 

CICS Terminals Alert Metrics Table

 

Table 1‑83 CICS Terminals Alert Metrics Table

Metric	FML32 Field	Operators
Average Session Number	TA_MONSESSIONNUM	>, >=
Number of CICS Transactions Failed	TA_MONTRANFAIL	>, >=

IMS Transaction Alert Metrics Table

 

Table 1‑84 IMS Transaction Alert Metrics Table

Metric	FML32 Field	Operators
Execution Time	TA_IMS_EXECUSEC	>, >=
CPU Time	TA_IMS_CPUTIMEUSEC	>, >=
DLI Time	TA_IMS_DLIUSEC	>, >=

IMS Program Alert Metrics Table

 

Table 1‑85 IMS Program Alert Metrics Table

Metric	FML32 Field	Operators
Execution Time	TA_IMS_EXECUSEC	>, >=
CPU Time	TA_IMS_CPUTIMEUSEC	>, >=
DLI Time	TA_IMS_DLIUSEC	>, >=