![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This section describes three general screens: General Statistics, Enclave Statistics, and TCB Statistics.Option A, GENERAL, displays the statistics accumulated since TIBCO Object Service Broker last started.
• Exception Statistics — Exception statistics show error conditions that can be caused by processing failures within the TIBCO Object Service Broker environment. The values could be accompanied by errors in the system log.
The number of failed send requests detected by the Query task when attempting to send a response back to the user. The number of VSAM I/O errors detected in both the Pagestore file handler and the checkpoint handler. The number of locked pages with no owner. This is an internal processing error and should be reported to TIBCO Support. The number of General Trace Facility write requests that terminated with a non-zero return code.
• Potential Delays — The values of potential delays could denote configuration or environmental issues that are adversely affecting performance and throughput.
The number of times a transaction was forced to wait for a logical lock or CTABLE resource. A logical lock wait occurs when another transaction holds the required lock, typically the result of transaction mix. A CTABLE is a table definition composite. A wait occurs when a CTABLE is being built by one transaction and a second transaction must wait for its completion. A high number of CTABLE waits could indicate that the Resident CTABLE Pool (CTABRESIDENT parameter) is set too small for the transaction mix. The number of page images copied because of checkpoint interference. Checkpoint interference is caused when a page within a checkpoint is required by a transaction outside the scope of the checkpoint. A copy of the page image is taken and used by the current transaction. Checkpoint interference is mainly the result of transaction mix. The number of checkpoints flushed. During checkpoint processing, page updates are written to the cache. When the cache I/O is complete, the next checkpoint build starts. Page images are recorded to the journal and Pagestore while the next checkpoint is being built. To reduce calls and smooth out I/O, page image updates are piggy-backed on to read to the same data set. As the next checkpoint build reaches a threshold, pages from the previous checkpoint not propagated back onto the Pagestore are written. This is referred to as flushing the checkpoint. If the majority of the checkpoints have to be flushed, the checkpoint size could be too low. The number of query transactions retried after a recoverable failure. The retrying of queries tends to result from environmental conditions that are transient, based on the current transaction mix. There is little that can be done to reduce the potential of these happening. The number of times the Resident Page Pool was interrogated and no slot was available that could be reassigned. A non-zero value in this field indicates that the Resident Page Pool is not large enough to accommodate the workload. The deferred page count; indicates the number of times a transaction waited because a required page was physically held by another user’s commit. A non-zero value indicates a delay in throughput that results from the transaction mix and it is not readily easy to retune. The number of in-doubt queries issued that could not be resolved (in-doubt query errors). When an external resource is interrupted during the processing of a Fail Safe level‑1 or level‑2 commit, the transaction is said to be in-doubt. When an appropriate resource becomes available, a query is sent to the resource to determine its status. If for some reason the resource cannot determine the status, the query fail error counter is incremented. The number of EXCP write retry errors; EXCP write errors to the contingency log and the cache that were retried.
The number of modify messages received from the operator console and passed onto the operator task.
The number of messages sent to Execution Environments, servers, and peer Data Object Brokers. The number of messages received from Execution Environments, servers, and peer Data Object Brokers. The maximum number of online and batch user sessions allowed at one time, as specified by the MAXUSERS Data Object Broker parameter. The high water mark for all connected sessions, including online and batch user sessions, operator, and external and peer server sessions.
The Enclave Statistics screen presents a summary of TIBCO Object Service Broker Enclave statistics.
For each value, a total for this instance of the Data Object Broker and a delta value between each refresh of this screen are displayed. CPU times are normalized, that is, the CPU times given for zIIP processors are those that would have been given for a regular processor to run the same work. ZIIP QUALIFIED work is work that is eligible to be executed on a zIIP processor regardless of where it was actually executed.
The TCB Statistics screen presents a summary of TIBCO Object Service Broker TCB usage statistics. The screen is present for all active TCBs.
For the Query (4) and Sync (3) tasks, three additional statistics appear. The Query Task TCB (4) has a summary line and then a line for each task running. This format is used to support the Multiple Query Task feature.
MSGS PROCESSED
You can display segment and DASD statistics for all segments, or for a specified segment. From the ENTER SELECTION prompt on the ADMINISTRATION MENU screen, type one of the following:
Bseg Where seg is the number of an active segment. This takes you directly to the DASD STATISTICS screen for the specified segment.If you attempt to go directly to the DASD STATISTICS screen with a segment that is offline or invalid, you receive a message indicating that the segment is offline or invalid.The SEGMENT STATISTICS screen displays all segments known to the Data Object Broker as defined in the DBGEN.
The total number of pages in all data sets within the segment. The page count appears in limited length output format, that is, if the number of pages exceed 5 digits, the value is factored by 1000 (KB), 1000000 (MB) or 1000000000 (GB). The number of pages that are currently free. This value is in limited output 5‑digit format. Whether (YES) the segment is a system-required segment, that is, it cannot be brought offline while the Data Object Broker is active. The delete processing used, either physical (PHS) meaning the free pages are actually written to the data store or Logical (LOG) indicating that only the bitmap reflects a free page. The first value is the threshold percentage at which warnings are produced to indicate a lack of free space within a segment. The second value is the rate at which the messages are produced. For example, if the display is 80/05 the first warning is produced when the segment is 80% full, addition messages are produced when the segment is 85%, 90% and 95% full.
This screen can appear for any active segment by placing the cursor beside the desired (online) segment on the SEGMENT STATISTICS screen and pressing PF2. If the segment number refers to a segment that is currently offline, the screen reappears with a message indicating the segment is offline.
The total page capacity of the data set. If the number of free pages is less than 15 percent of the total, the free value is highlighted.
DASD STATS BY PAGE TYPE screens use the same data collection area. Unless a redisplay is requested on either screen, the data in the screen display is not refreshed.In the Pagestore, there is a variety of page types, each with a specific purpose. The DASD STATS BY PAGE TYPE screen divides the page types into three categories: DATA, INDEX, and OTHER, and displays physical reads and writes for pages containing TDS data within these categories.
These pages contain index structures used to navigate indexes and data pages below them. There are a number of index types, including primary data index, secondary index, and parameterized table index. These pages are a catchall for pages not used for these purposes. They are primarily internal control pages.
DASD STATISTICS and DASD STATS BY PAGE TYPE screens use the same data. Unless a redisplay is requested on either screen, the data is not refreshed.The CHANGE SEGMENT STATUS screen provides a facility for authorized people to control the TIBCO Object Service Broker segments without using a batch job or the operator console.If you have authority to control segments, place the cursor on the desired segment number and press PF11 to display the CHANGE SEGMENT STATUS screen.
Request the status change to be sent to the Data Object Broker. You are prompted for confirmation.
The most important statistic on the inquiry is TRANSACTIONS BLOCKED. This number informs you how many Execution Environment transactions were blocked due to record locking since TIBCO Object Service Broker last started.
Accumulated total of lock requests refused because of locks held by other transactions.
The total number of requested locks upgraded from previously granted locks.
The number of lock request conflicts with granted lock of another transaction; request rejected. The total number of lock requests already granted at the requested level or strongerTo list the locks held on a specific table, press PF2. This displays a screen prompting for the name of the table. Provide a table name and press ENTER to display the locks for the table, as shown below for the MESSAGES table. A message appears if no locks are found for the specified table.
These statistics concern the eleven different TIBCO Object Service Broker buffer pools, and are cumulative from when TIBCO Object Service Broker last started. The pools are:
Option F, PROFILE DISPLAY SELECTION, displays a menu from which various profiles can be requested for display.
The MESSAGE LENGTH PROFILE screen displays the numbers of messages received and sent in different size ranges.
MESSAGE TURNAROUND TIME PROFILE displays the response time in microseconds to query and commit messages received, grouped according to response time. The commit count displayed could include messages that do not cause updates to the display.
CONTINGENCY LOG I/O TIME PROFILE displays time in milliseconds for I/O taken by the contingency log, grouped according to I/O response time.
REDOLOG RESPONSE TIME PROFILE displays time in milliseconds for I/O taken by the redolog.
Depending on the number of query tasks running in the Data Object Broker, as indicated by the value in the MAXQUERY Data Object Broker parameter, QUERY ECB WAIT PROFILE displays either of the following:
• If there is only one query task, a horizontal bar graph (on screen S6BADMF3) displays the depth of the queue (the number of messages waiting on the queue) versus the percentage of the total number of messages processed on the system.
• If there are multiple query tasks running, a vertical bar graph (on screen S6BADMF4) displays the depth of the queue versus the percentage of the total number of messages. On this screen, the information appears for each task and is identified as different sub-columns (1, 2, 3, and so on) under each depth column. You can press PF2 to toggle the values between percentages of the total and percentages of the delta change since the Enter key was last pressed.A depth of more than 1 means that more than 1 message is waiting in the queue for that task and indicates that queries are being delayed due to resource constraints.
To run multiple query tasks, you need the TIBCO Object Service Broker Accelerator Pack for z/OS. For more information, refer to the MAXQUERY Data Object Broker parameter in TIBCO Object Service Broker Parameters.
Option G, UPDATED PAGES PER TRANSACTION, displays the approximate number of pages updated by commit transactions. The bar graph shows the percentage of total transactions that fall within the specified range of updated pages, in 2% increments.
Option H, PHYSICAL CPU AND I/O STATISTICS, displays the CPU and I/O statistics for the current life of a Data Object Broker and the Operator Session.
The System Deltas section measures the usage between the times you press Enter. The other sections are updated each time you press Enter.
Option I, USER ACTIVITY, displays active user connections to the Data Object Broker on the ACTIVITY SUMMARY screen.
Place the cursor on the desired ID in the USER ACTIVITY screen and press PF2. To sort by column, place the cursor on the column heading and press PF9.
Identifies the type of region where the session connected, for example, TSO, CICS, Native Execution Environment. An estimate of CPU time accumulated since the connection was initiated. This value does not include some of the shared overhead costs and should not be used for accounting purposes. This is determined by the TIBCO Object Service Broker Communication System. Refer to Appendix B, Configurations for Communications for more information. Identifies the terminal used to connect to TIBCO Object Service Broker if the ID is supplied at connection time. Identifies the job name of a batch connection if the job name is supplied at connection time. Identifies the job step of a batch connection if the step name is provided at connection time.
CURRENT MESSAGE Identifies the type of request that is currently in progress, for example, query or commit. If the request is waiting on a TIBCO Object Service Broker resource, an exception is identified to indicate which resource. SEGMENT, PAGE, and TABLE If a request is in progress, these three values identify the current segment and page numbers and the table name last referenced by the request.
Place the cursor beside the desired type of Execution Environment and press PF2 to display a list of connections within that group. Place the cursor beside the desired type of Execution Environment and press PF2 to display the ACTIVE USER LIST screen for that Execution Environment.
The list of connections is sorted by user ID within user type. User type is indicated by the following letters:
Place the cursor in front of the desired user and press PF2 to display the activity detail for the user.
Toggle user-level Page Sweep Action reporting for the System Monitoring facility. Prepare to issue a CANCELUSER command to quiesce the current session connection. Prepare to issue a FORCEUSER command to forcibly remove the current connection from the Data Object Broker. Note the on-screen warning. Option J, INSTALLATION/CONFIGURATION, displays information about the operating environment and configuration of the Data Object Broker. It also includes the hardware configuration and TIBCO Object Service Broker software level under which the Data Object Broker is running. This information is extracted from system control blocks and Data Object Broker parameters.
This section presents information about the computer environment where the Data Object Broker is running. The data is extracted from the system Communications Vector Table.
Indicates the type of operating system. Extracted from the operating system. The identification number for the CPU where the Data Object Broker is executing. Extracted from the operating system. The model number of the CPU where TIBCO Object Service Broker is executing. Extracted from the operating system. The time difference between local time and GMT. Extracted from the operating system.This section presents values pertaining to the TIBCO Object Service Broker job extracted from the Task I/O Table and runtime parameters. When applicable, the parameter names appear in parentheses at the end of the field descriptions.
The name the Data Object Broker is executing under. This is extracted from the operating system. The Data Object Broker address space identifier. This is extracted from the operating system. A symbolic name to uniquely identify a Data Object Broker. When specifying a location in a rule, you use the “nodename” to identify the target location. (NODENAME) The version number of the TIBCO Object Service Broker software release. This value is constant and is set at the Data Object Broker source assembly time. The date and time the Data Object Broker started. This information is extracted from the operating system. (Y/N) Indicates whether relay communication is supported. This value is determined by the TIBCO Object Service Broker Communication System. For more information, see The Relay File. CROSS MEMORY (Y/N) Indicates whether Cross Memory communication is supported. This is determined by the TIBCO Object Service Broker Communication System. Refer to Configuring Cross Memory Services for more information. (Y/N) Indicates whether VTAM communication is supported. It is determined by the TIBCO Object Service Broker Communication System. Refer to Configuring VTAM Communications for more information. ESTAE SUPPORT Specifies whether to enable the Data Object Broker Extended Specific Task Abnormal Exit (ESTAE) routine for handling abnormal terminations. (ESTAE) OPERATOR SECURITY Specifies whether the System Authorization Facility (SAF) calls are made to the site’s security system. These calls are made for authorization of access to sensitive operational utilities requested from other than the z/OS operator console (for example, S6BTLADM, S6BTLCMD and S6BSPJEX). (SECUREADMIN) Specifies whether the Data Object Broker is marked as swappable after initialization. (SWAPPABLE) This section shows information about the parameters that affect the major storage blocks used by the Data Object Broker.Additional information about the Data Object Broker parameters associated with the following fields is available in TIBCO Object Service Broker Parameters. The parameter names appear in parentheses at the end of the field descriptions.This section presents the parameter values that affect the general processing of the Data Object Broker. The parameter names appear in parentheses at the end of the field descriptions.
The threshold, in number of changed pages, that triggers a checkpoint. (CHPAGELIMIT) The number of commits, issued from Execution Environments connected to this Data Object Broker, that cause it to take a checkpoint. (CHTRANLIMIT) The maximum time interval in minutes between checkpoints, before the Data Object Broker triggers another checkpoint. (CHPTINTERVAL) CONCURRENT VSAM The maximum number of concurrent I/O requests to all page data sets. (MAXVSAMC) The number of requests that the Data Object Broker can service at the same time. (MAXTHREADS) The maximum number of user sessions that the Data Object Broker allows to be active at one time. (MAXUSERS) LOCK TIMEOUT The wait interval in seconds before a lock request is retried if the initial request cannot be satisfied. (LOCKTIMEOUT) DUPLICATE USERID Specifies whether to allow duplicate online user IDs to create sessions concurrently. (DUPUSERID) DUP REMOTE USER Specifies whether to allow connections with duplicate user IDs when either the existing or the connecting use is for an API process. (REMOTEDUP) The maximum time interval between journal spins. If a spin is not scheduled during an interval due to a full journal or an operator request, the Data Object Broker schedules a spin at the end of this interval. Set this parameter’s value to the length of that interval, in minutes. (SPININTERVAL) The prefix for the member names that contain JCL for journal spins. (SPINMEMBER) Specifies whether the journal spin JCL is run as a started task or batch job. (SPINOPTION) The data set name from which SPIN jobs are submitted. It must be an existing partitioned data set containing member names set by the SPINMEMBER parameter. (SPINDSNAME)This section shows the values used in the control of transactions as they are processed through the Data Object Broker.
The maximum number of Pagestore pages that can be updated in a single Data Object Broker commit. (WORKINGSET) The maximum number of pages that can be read in by a single Data Object Broker request. Transaction message requests that exceed the specified number of pages are aborted. (TRXREADLIMIT) The maximum number of data pages that can be updated within a transaction synchronization point process. (DATAPAGELIMIT) The maximum number of data pages a table can have for a secondary index to be built on it online. (SIXDATAPAGLIM) The threshold number of logical page reads for page sweep reporting. (PAGESWEEPLIMIT) The page sweep reporting option.
(PAGESWEEPACTION — the Write to log option) The page sweep reporting option.
(PAGESWEEPACTION — the Write SMF record option) PG SWEEP DUMP The page sweep reporting option.
(PAGESWEEPACTION — the Abend the transaction option)This section presents the values that assist in the generation and collection of data to diagnose and monitor the usage and performance of the Data Object Broker. The parameter names appear in parentheses at the end of the field descriptions.
The hexadecimal identifier for GTF trace records produced by the Data Object Broker when tracing is in effect. (GTFID) The numerical identifier that this Data Object Broker uses when generating SMF records. (SMFRECORD) The interval time between SMF record generation for active user sessions. Refer to the SMF# interval parameters described in TIBCO Object Service Broker Parameters. Specifies whether to produce records for all query and commit requests received by the Data Object Broker. Use this parameter only in consultation with your TIBCO Support representative, as it can affect system performance. (MSGTRACE) SERVICE TRACING Specifies whether GTF records are to be created each time a TIBCO Object Service Broker system service event occurs. Use this parameter only in consultation with your TIBCO Support representative, as it can affect system performance. (SSTRACE) NETVIEW SUPPORT (Y/N) Indicates whether Netview is active in TIBCO Object Service Broker. Refer to TIBCO Object Service Broker Netview Support.The Data Object Broker is designed to generate a variety of console and SYSLOG messages to indicate processing steps. The parameter values presented in this section are used to control where and how these messages are generated and recorded. The parameter names appear in parentheses at the end of the field descriptions.
The time interval after which the WTO output is to copied to a new data set. This parameter is in effect only if WTOCLASS is specified. A value of zero (0) disables this feature. (WTOINTERVAL) The output destination for this Data Object Broker’s JES WTO SYSOUT log data set. (WTOREMOTE) The minimum level of messages to be written to the z/OS JES WTO SYSOUT file. All messages are written to the Data Object Broker JES SYSOUT file. (WTOSYSLOG) CONSOLE LEVEL The minimum level of Data Object Broker WTO messages to be suppressed rather than written to SYSLOG, or displayed on the z/OS operator console. The following message levels that can be suppressed: (WTOCONSOLE) The output class of a dynamically allocated JES SYSOUT file where the Data Object Broker copies WTO (write to operator) messages. (WTOCLASS) DELETE/ SUPPRESS The minimum level of Data Object Broker WTO messages to be suppressed rather than written to SYSLOG, or displayed on the z/OS operator console. The following message levels that can be suppressed: (WTODELETE)I — information
L — log The suffix to identify messages issued from a specific Data Object Broker. (WTOSUFFIX) The descriptor code to use for I (information) WTO messages. (DESCINFORM) ALERT/ ACTION The route code for L (log) WTO messages. (ROUTLOG)1 The route code for I (information) WTO messages. (ROUTINFORM)a The route code for E (error) WTO messages. (ROUTERROR)a ALERT/ ACTION The route code for A (alert) WTO messages. (ROUTACTION)a
This section presents the values that control the generation of SNAP and SVC dumps to aid in the diagnosis of transaction and process failures.
SNAP HIGH QUALIFIER The high-level qualifiers for Data Object Broker snap dumps taken to a data set on DASD. (SNAPDSPREFIX) The JES output class for SYSOUT snap dumps generated by the Data Object Broker. (SNAPCLASS) The volume serial of the DASD where the Data Object Broker can allocate snap dump data sets. (SNAPVOLSER) The generic name of a DASD pool to allocate DASD snap dump data sets. (SNAPUNIT) DUMP ON QUERY ABORT (Y/N) Specifies whether the Data Object Broker generates a transaction dump for failed query requests. (SNAPQUERY) DUMP ON TRANSACTION ABORT (Y/N) Specifies whether Data Object Broker transaction dumps are to be suppressed. (SNAPSUPPRESS) DUMP ON INDOUBT TRX (Y/N) Specifies whether a snap dump is to be generated when an in-doubt transaction is detected. (DBSNAP)TIBCO Object Service Broker for z/OS Monitoring Performance for more information about generating SMF records.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |