Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 18 Monitoring and Controlling the TIBCO Object Service Broker Environment : Statistical Menu Items

Statistical Menu Items
A. General
This section describes three general screens: General Statistics, Enclave Statistics, and TCB Statistics.
General Statistics Screen
Function
Option A, GENERAL, displays the statistics accumulated since TIBCO Object Service Broker last started.
Example

 
S6BADMA1 S6DCDOBA GENERAL STATISTICS 2011JAN06 07:51:23
 
EXCEPTION STATISTICS
SENDERR 0 SYNAD 0 RPMLOCK 0
GTF ERR 0
 
POTENTIAL DELAYS (MAY INDICATE A CONFIGURATION OR PROCESSING ISSUE)
WAITS 410 CHPT-I 0 FLUSH 0
Q-RETRY 0 QR FAIL 0 WRAP 0
DEF PG 8775 PG WAIT 1049 INDBTQE 0
SNAPS 0 DEADLCK 0 EXCP-R 0
 
REQUEST HANDLING AND PROCESSING METRICS
SUPV 2 CHPT 0 COMM 201
FILE 7170 RTUQ 3 APPL 282177
OPER 12 CONS 0 TIMR 5
PH0 0 PH1 267678 PH2 1182
SERVER 0 INDOUBT 0
 
LAST CHPT 2011JAN05 09:42:24 CHPT# 926 COMPLETE 926
LAST SPIN 2011JAN06 07:49 JRNL# 2 JRNL% 0
 
PHYSICAL PROCESSING PERFORMED
READ 5474 RULE 47 CTAB 3688
WRITE 0 REPL 262 CTB S/R 0
DEL 2289 INS 674 CICS DISPLAY 0
JRNL 0 SMF 3 REDOLOG 2810
EXCP 0 WTO 60 GTF 0
SEND 269051 RECEIVE 269056 HITHASH 5475
LOGONS 11 LOGOFF 2 MISHASH 5610
MAXUSR 1000 MAXCON 9 TAMUSR 4
 
LOGICAL PROCESSING METRICS
GET 925994 RULE 12632 CTAB 353515
PUT 96904 REPL 4 INS 9786
DEL 76047 SYNC 1182
GET4K 3668 FRE4K 2486
GETF 135 PUTF 857
LOCK 145207 UNLOCK 352 DEF LCK 0
GETBUF 1207122 FREEBUF 1206777 DEF BUF 0
GETXTAB 0 FREEXTB 0
ENTER-REFRESH TOTALS PF4-TASK/TCB STATISTICS PF5-ENCLAVE STATISTICS
NO MORE DATA TO BE DISPLAYED

 
Fields
This section defines the fields on the General Statistics screen, as follows:
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.
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 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.
Enclave Statistics Screen
Function
The Enclave Statistics screen presents a summary of TIBCO Object Service Broker Enclave statistics.
Example

 
S6BADMA3 S6DCDOBA ENCLAVE STATISTICS 2011JAN06 07:52:05
 
 
TOTAL DELTA
HHH MM SS.MICRO HHH MM SS.MICRO
ZIIP ON CP TIME 000 00 00.769447 000 00 00.050681
ZIIP QUALIFIED TIME 000 02 28.038771 000 00 10.457387
ZIIP CPU TIME 000 02 27.269324 000 00 10.406706
CPU TIME 000 02 28.038843 000 00 10.457459
 
PHASE 1 REQUESTS 561452 31749
PHASE 1 SRB REQUESTS 561452 31749
 
 
 
ENTER-REFRESH TOTALS PF5-GENERAL STATISTICS

 
Information Displayed
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.
See the following table for details.
TCB Statistics Screen
Function
The TCB Statistics screen presents a summary of TIBCO Object Service Broker TCB usage statistics. The screen is present for all active TCBs.
Example

 
S6BADMA2 S6H1DOBB TCB STATISTICS 2006NOV29 09:43:50
TASK STATUS TIME BUSY TCB TIME MSGS PROCESSED INFLIGHT MAX-CON
0 READY 0:06 0.214
1 READY 0:01 0.190
j READY 0:00 0.006
2 ACTIVE 0:09 2.120
3 READY 0:03 0.803 572 0 1
31 READY 0:00 0.406
4 20.628
1 READY 0:26 20.628 121601 0 2
6 READY 0:00 0.040
c READY 0:00 0.007
t READY 0:03 3.516
 
 
 
 
 
 
 
 
ENTER-REFRESH TOTALS PF4-GENERAL STATISTICS

 
Information Displayed
SnnUnn – abnormal termination code
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
Key Commands
B. Segment/DASD
Function
Option B, SEGMENT/DASD, displays segment and DASD statistics.
Displaying Information for All Segments or for a Specified Segment
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.
Screens for Segment/DASD Statistics
Four screens are used to display segment and DASD statistics:
Each of these screens is described below.
Segment Statistics Screen
Function
The SEGMENT STATISTICS screen displays all segments known to the Data Object Broker as defined in the DBGEN.
Example of Segment Statistics Screen

 
S6BADMB1 S6H1DOBB SEGMENT STATISTICS 2006NOV29 10:13:15
 
SEG NAME MOD PAGES FREE % JRN SYS DEL D/S WARN READ WRITE HOLD THR
0 VTH.S000 R/W 360K 224K 62 YES YES LOG 4 80/05 5514 142 0 7
2 VTH.S002 R/W 216K 157K 73 YES NO LOG 2 80/05 30 10 0 24
3 VTH.S003 R/W 54K 53K 98 YES NO LOG 1 80/05 0 0 0 24
9 VTH.S009 R/W 18K 1428 7 YES YES LOG 1 80/05 6 18 0 24
 
ENTER-REFRESH PF2-DASD STATISTICS PF7-BACK PF8-FORWARD PF11-MODIFY

 
Information Displayed
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).
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.
Key Commands
Note  The base segment (segment 0) cannot be modified online.
DASD Statistics Screen
Function
The DASD Statistics screen presents statistical data for each page data set within a given segment.
Displaying the DASD Statistics Screen
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.
Illustration of the DASD Statistics Screen

 
S6BADMB2 S6H1DOBB DASD STATISTICS FOR SEGMENT 000:VTH.S000 2006NOV29 10:16:39
 
FIRST DSN HLQ.VTH.S000.PAGE1
 
DATASET # 1 2 3 4
VOLUME OSBD62 OSBD20 OSBD53 OSBD48
PAGES 90000 90000 90000 90000
USED PAGES 34014 34430 34096 33189
FREE PAGES 55986 55570 55904 56811
READ 1450 1544 1391 1129
WRITTEN 37 39 30 36
MAX CONC 1 1 1 1
ERRORS 0 0 0 0
DELAY TIME 0 0 0 0
DELAY CNT 0 0 0 0
DELAY AVG. 12 14 12 13
REQUESTED
ACTIVE
PENDING
 
 
ENTER-REFRESH PF2-BY PAGE TYPE PF4-SEG STATUS PF7-BACK PF8-FORWARD
NO MORE DATA TO BE DISPLAYED

 
Information Displayed
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.
Key Commands
 
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.
DASD Statistics by Page Type Screen
Function
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.
Illustration of the DASD Statistics by Page Type Screen

 
S6BADMB3 S6H1DOBB DASD STATS BY PAGE TYPE SEG 000:VTH.S000 2006NOV29 10:16:39
 
D A T A I N D E X O T H E R
DS# READ WRITTEN READ WRITTEN READ WRITTEN
1 988 12 107 10 355 15
2 1088 16 103 13 353 10
3 939 12 106 5 346 13
4 845 22 70 4 214 10
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ENTER-REFRESH PF2-DASD STATS PF4-SEGMENT STATUS PF7-BACK PF8-FORWARD

 
Information Displayed
This screen contains the following information:
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.
Key Commands
t
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.
Change Segment Status Screen
Function
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.
Displaying the CHANGE SEGMENT STATUS Screen
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.
Illustration of the Change Segment Status Screen

 
S6BADMB4 S6H1DOBB CHANGE SEGMENT STATUS 2006NOV29 11:43:39
 
SEGMENT 002:VTH.S002 TYPE=PAGESTORE
 
CURRENT REQUESTED
JOURNALLING YES
 
MODE READWRITE
 
STATUS ONLINE
 
 
PF7 CHANGE JOURNALLING
PF8 CHANGE SEGMENT MODE
PF9 CHANGE SEGMENT STATUS
 
 
 
NOTES 1-SEGMENT MUST BE OFFLINE TO EFFECT JOURNAL OR MODE CHANGES
2-ONLY ONE ITEM CAN BE CHANGED WITHIN A SINGLE REQUEST
 
 
PF4-SEGMENT STATUS PF11-ISSUE CHANGE REQUEST

 
Key Commands
C. Lock Manager
Function
Option C, LOCK MANAGER, displays a summary of the cumulative lock history.
Lock Manager Statistics Screen

 
S6BADMC1 S6H1DOBB LOCK MANAGER STATISTICS 2006NOV29 11:52:20
 
 
TRANSACTIONS REQUESTS UPGRADE REQUESTS
 
TOTAL 1138 TOTAL 37447 REQUESTS 924
MAXIMUM 10 GRANTED 22118 THRESHOLD 0
CURRENT 4 UPGRADE 924 ANCESTOR 2383
BLOCKED 0 NO-OP 16022
FREE 1134
 
RESOURCES NO-OP REQUESTS
 
TOTAL 18553 BLOCKED 0
MAXIMUM 356 DEADLOCK 0
CURRENT 61 IGNORED 169
REDUNDANT 15853
 
 
 
 
 
PF2-LIST HELD LOCKS BY TABLE ENTER-REFRESH
 

 
Columns and Fields
The fields of the LOCK MANAGER screen are defined by column as follows:
Transactions
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.
Requests
Requests are from the Execution Environments.
Resources
Resources are logical locks.
Upgrade Requests
NO-OP Requests
List Locks on a Table
To 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.

 
S6BADMC2 S6H1DOBB LOCKS HELD FOR TABLE MESSAGES 2006NOV29 11:52:20
 
 
USER-ID USER-ID USER-ID USER-ID USER-ID
DBA USR00 ABC30
 
 
 
 
PF5-REFRESH ENTER-TABLE NAME ________________
PLEASE SPECIFY TABLE NAME FOR HELD LOCKS INQUIRY

 
D. Buffer Pools
Function
Option D, BUFFER POOLS, displays statistics about TIBCO Object Service Broker buffer pools.
Buffer Pools Statistics Screen

 
S6BADMD1 S6H1DOBB BUFFER POOL STATISTICS 2006NOV29 11:55:32
 
POOL IN-USE QUEUED
NAME # GETS # FREES CURR MAX CURR MAX WAITS ERRORS BUFFERS
BUFQ 120
CLOG 25
COMM 352 312 40 78 851
LOCK 1615 1610 5 16 368
 NAMW 7
PAGE 551699 551699 11 7680
SESS 128306 128306 2 34
VRPL 6753 6753 7 1038
WORK 15101 15101 5 1054
XTAB 259 259 1 34
 
 
 
 
 
 
 
ENTER-REFRESH PF7-BACK PF8-FORWARD

 
TIBCO Object Service Broker Buffer Pools
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:
Column Headings
The column headings on the screen are described below:
F. Profile Displays
Function
Option F, PROFILE DISPLAY SELECTION, displays a menu from which various profiles can be requested for display.
Profile Display Selection Screen

 
S6BADMF1 S6H1DOBB PROFILE DISPLAY SELECTION 2006NOV29 11:56:48
 
 
1 MESSAGE LENGTH PROFILE
 
2 MESSAGE TURNAROUND TIME PROFILE
 
3 CONTINGENCY LOG I/O TIME PROFILE
 
4 REDOLOG RESPONSE TIME PROFILE
 
5 QUERY ECB WAIT PROFILE
 
 
 
 
 
 
 
ENTER ITEM NUMBER _
 
 
 

 
Available Profiles
The following profiles are available and discussed below:
1. Message Length Profile
2. Message Turnaround Time Profile
3. Contingency Log I/O Time Profile
4. Redolog Response Time Profile
5. Query ECB Wait Profile
You can select any of the profiles by entering the associated number.
Key Commands
1. Message Length Profile
Function
The MESSAGE LENGTH PROFILE screen displays the numbers of messages received and sent in different size ranges.
Illustration of Message Length Profile Screen

 
S6BADMF3 S6H1DOBB MESSAGE LENGTH PROFILE 2006NOV29 11:56:48
DELTA TIME
LEN PERCENTAGE OF TOTAL COUNT DELTA
RECEIVES ----1----2----3----4----5----6----7----8----9----+
64 |***** | 13350
128 |**************************** | 72853
256 |**************** | 41296
512 |* | 2269
1024 |* | 14
2048 |* | 8
4096 |* | 13
>>> | | 0
SENDS ----1----2----3----4----5----6----7----8----9----+
64 |******************************* | 80666
128 |**** | 11553
256 |* | 4348
512 |*** | 7614
1024 |**** | 10389
2048 |* | 4298
4096 |**** | 10873
>>> |* | 49
RECEIVES 129803
ENTER-REFRESH PF4-PROFILE SEL SENDS 129790

 
2. Message Turnaround Time Profile
Function
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.
Illustration of Message Turnaround Time Profile

 
S6BADMF3 S6DCDOBA MESSAGE TURNAROUND TIME PROFILE 2007MAR30 08:08:45
DELTA TIME
TIME PERCENTAGE OF TOTAL COUNT DELTA
QUERIES ----1----2----3----4----5----6----7----8----9----+
250 |******************************************* | 116540
500 |***** | 14269
1000 |* | 1975
2000 |* | 904
4000 |* | 414
8000 |* | 203
16000 |* | 205
>>> |* | 93
COMMITS ----1----2----3----4----5----6----7----8----9----+
250 |* | 50
500 |* | 4
1000 |* | 2
2000 |*********** | 1739
4000 |************************************ | 5441
8000 |* | 243
16000 |* | 46
>>> |* | 31
QUERIES 134603
ENTER-REFRESH PF4-PROFILE SEL COMMITS 7556
 
--------------------------------------------------------------------------------
€‚ 1 Sess-1 10.101.5.104 1/1

 
3. Contingency Log I/O Time Profile
Function
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.
Illustration of the Contingency Log I/O Time Profile Screen

 
S6BADMF3 S6H1DOBB CONTINGENCY LOG I/O TIME PROFILE 2006NOV29 11:58:58
DELTA TIME
TIME PERCENTAGE OF TOTAL COUNT DELTA
WRITES ----1----2----3----4----5----6----7----8----9----+
2 | | 0
4 | | 0
8 | | 0
16 | | 0
32 | | 0
64 | | 0
128 | | 0
>>> | | 0
----1----2----3----4----5----6----7----8----9----+
 
WRITES 0
ENTER-REFRESH PF4-PROFILE SEL

 
4. Redolog Response Time Profile
Function
REDOLOG RESPONSE TIME PROFILE displays time in milliseconds for I/O taken by the redolog.
Illustration of the Redolog Response Time Profile Screen

 
S6BADMF3 S6H1DOBB REDOLOG RESPONSE TIME PROFILE 2006NOV29 11:59:57
DELTA TIME
TIME PERCENTAGE OF TOTAL COUNT DELTA
WRITES ----1----2----3----4----5----6----7----8----9----+
1 |************************************************ | 612
2 |* | 12
4 |* | 2
8 |* | 4
16 |* | 7
32 |* | 1
64 |* | 2
>>> | | 0
----1----2----3----4----5----6----7----8----9----+
 
WRITES 640
ENTER-REFRESH PF4-PROFILE SEL

 
5. Query ECB Wait Profile
Function
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.
Illustration of the Query ECB Wait Profile Screen – Single Query Task

 
S6BADMF3 S6H1DOBB QUERY ECB WAIT PROFILE 2006NOV29 12:00:39
DELTA TIME
CNT PERCENTAGE OF TOTAL COUNT DELTA
DEPTH ----1----2----3----4----5----6----7----8----9----+
1 |************************* | 139344
2 |************************ | 135493
4 | | 0
8 | | 0
16 | | 0
32 | | 0
64 | | 0
>>> | | 0
----1----2----3----4----5----6----7----8----9----+
 
DEPTH 274837
ENTER-REFRESH PF4-PROFILE SEL

 
The system where this illustration was produced is a six-way system with 100 concurrent users.
Illustration of the Query ECB Wait Profile Screen – Multiple Query Tasks

 
S6BADMF4 S6PMDOBI QUERY ECB WAIT PROFILE (TOTAL) 2006NOV29 12:17:22
DEPTH 1 2 4 8 16 32 64 64+
100 12
90 12
80 12
70 12
60 12
50 12
40 12
30 12
20 12
10 12
0 123 123 123 123 123 123 123 123
 
QUERY TASK 1 COUNT 471 DELTA 471 DELTA TIME
2 1 1
3 0 0
ENTER-REFRESH PF2-DELTA TOGGLE PF4-PROFILE SELECT

 
G. Updated Pages Per Transaction
Function
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.
Updated Pages Per Transaction Screen

 
S6BADMG1 S6H1DOBB UPDATED PAGES PER TRANSACTION 2006NOV29 12:25:51
 
PAGES PERCENTAGE OF TOTAL TRANSACTIONS
UPDATED ----1----2----3----4----5----6----7----8----9----+ TRANSACTIONS
1 |* | 19
2 |************************************* | 680
3 |******** | 155
4 |* | 23
5 |** | 33
6 |* | 3
7 |* | 7
8 | | 0
9 |* | 2
10 | | 0
11 | | 0
12 | | 0
13 | | 0
14 | | 0
15 | | 0
>15 | | 0
 
TOTAL 922
ENTER-REFRESH

 
Key Commands
H. Physical CPU and I/O Statistics
Function
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.
Physical CPU and I/O Statistics Screen

 
S6BADMH1 S6H1DOBB PHYSICAL CPU AND I/O STATISTICS 2006NOV29 09:27:51
 
 
------- SYSTEM TOTALS ------ -- ADMIN SESSION TOTALS ---
HHH MM SS.MICRO HHH MM SS.MICRO
TCB TIME 000 00 27.927455 TCB TIME 000 00 00.064672
SRB TIME 000 00 03.406916 SRB TIME 000 00 00.001406
--------------------------- ---------------------------
CPU TOTAL 000 00 31.334371 CPU TOTAL 000 00 00.066078
I/O COUNT 12 813 I/O COUNT 101
 
 
------- SYSTEM DELTAS ------- - ADMIN TRANSMIT/RECEIVE --
HHH MM SS.MICRO HHH MM SS.MICRO
TCB TIME TCB TIME 000 00 00.000208
SRB TIME SRB TIME 000 00 00.000063
--------------------------- ---------------------------
CPU TOTAL CPU TOTAL 000 00 00.000271
I/O COUNT REAL TIME 000 00 00.000381
ELAPSE TIME
 
 
ENTER-REFRESH

 
The System Deltas section measures the usage between the times you press Enter. The other sections are updated each time you press Enter.
Key Commands
I. User Activity
Function
Option I, USER ACTIVITY, displays active user connections to the Data Object Broker on the ACTIVITY SUMMARY screen.
Activity Summary Screen

 
S6BADMI6 S6H1DOBB ACTIVITY SUMMARY 2006NOV29 12:28:00
 
USERID VIA QUERY COMMIT GET PUT READ Q-CPU IDLE
ABC30 TSO 17118 82 78862 255 280 3559 11480
USR00 TSO 15971 26 70543 63 9 2640 67
DBA TSO 13533 197 36406 244 211 2300 68
DZY00 TSO 6241 19 39217 45 1168 3849 5934
U00E6000 NDR 5 0 16 0 29 2 420583
U00E6001 NDR 5 0 4 0 0 0 420583
U00E6002 NDR 0 0 0 0 0 0 420583
U00E6003 NDR 0 0 0 0 0 0 420583
U00E6004 NDR 0 0 0 0 0 0 420582
U00E6005 NDR 0 0 0 0 0 0 420582
U00E6006 NDR 0 0 0 0 0 0 420582
U00E6007 NDR 0 0 0 0 0 0 420581
U00E6008 NDR 0 0 0 0 0 0 420581
U00E6009 NDR 0 0 0 0 0 0 420581
$00E6000 NDR 0 0 0 0 0 0 420575
$00E6001 NDR 0 0 0 0 0 0 420575
$00E6002 NDR 0 0 0 0 0 0 420574
$00E6003 NDR 0 0 0 0 0 0 420574
 
ENTER-REFRESH PF2-ACTIVITY DETAIL PF4-USER LIST PF5-REGION LIST PF9-RESORT

 
Headings
Key Commands
Available Screens
The following nested screens are available through the USER ACTIVITY screen:
These screens are described below.
Activity Detail Screen
Function
Displays a detailed listing for a specified user.
To Display
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.
Illustration of the Activity Detail Screen

 
S6BADMI2 S6H1DOBB ACTIVITY DETAIL FOR ABC30 2006NOV29 12:40:44
 
TYPE TSO USER IDLE TIME 94:35 EST. CPU 00:00:03.6 ACCESS XMS
TERMINAL TCP04015 REGION TSO JOB NAME ABC30 REF# 316
START TIME 8:21:06 DATE 2006NOV29 TRACE N
 
CURRENT MESSAGE IDLE-NO MESSAGE EXCEPTION
SEGMENT PAGE TABLE
 
QUERIES 17118 GETS 78862
COMMITS 82 PUTS 255
SERVERS 0 READS 280
RULES 2593
 
STR TRX ID SERVERS
1 00016550
2 0001BC06
 
ENTER-REFRESH PF2-LOCKS PF4-USER PF5-REGION PF9-SUMMARY PF11-OPER SERVICES

 
Sections on the Activity Detail Screen
The screen is divided into four sections:
The sections of the screen are described below:
Session Identification
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.
Identifies the terminal used to connect to TIBCO Object Service Broker if the ID is supplied at connection time.
Current Message
CURRENT MESSAGE
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.
Accumulated Statistics
External Resource Allocations
Key Commands
Logical Locks Screen
Function
Displays the logical locks held by a selected user.
To Display
From the ACTIVITY DETAIL screen, place cursor on the desired stream and press PF2.
Illustration of the Logical Locks Screen

 
S6BADMI3 S6H1DOBB LOGICAL LOCKS HELD BY ABC30 2006NOV29 12:54:16
 
STR TRX ID SERVERS
1 00016550
 
TABLE NAME TABLE NAME TABLE NAME TABLE NAME
$GRAMMARS MENU_ITEMS
@CHARACTERMAP MENU_TEMP
@COLOURS MESSAGES
@LIBRARIES PFKEY_SPECS
@MONTH_CODES REMIND
@MONTHLIST SEMANTIC
@OBJECTMSG SESSION_MENUS
@SCREENCOLOURS SESSMGR_MSG
@USERSOPTIONS STANDARD_BODY
@WEEKDAYS STANDARD_HEAD
ALTERNATIVES STANDARD_HIST
APPOINTMENTS
CALNDR
CMD_HIST_TEMP
GRAMMARS
 
PF4-ACTIVITY DETAIL PF7-BACK PF8-FORWARD

 
Key Commands
Press PF4 to redisplay the ACTIVITY DETAIL screen.
Region Selection List Screen
Function
The REGION SELECTION LIST screen displays the Execution Environment types.
To Display
Illustration of Region Selection Screen

 
S6BADMI5 S6H1DOBB REGION SELECTION LIST 2006NOV29 12:55:26
COMBINED NATIVE BATCH TSO
OPERATOR
 
ENTER-REFRESH PF2-SELECT REGION PF4-USER LIST PF5-ACTIVITY SUMMARY

 
Key Commands
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.
Connections in Region Peer Screen
Function
Lists all connections with the requested region code.
To Display
Position your cursor beside NATIVE in the REGION SELECTION LIST screen and press PF2.
Illustration of Connections in Region Native Screen

 
S6BADMI1 S6H1DOBB CONNECTIONS IN REGION NATIVE 2006NOV29 13:03:22
N-$00E6000 N-$00E6001 N-$00E6002 N-$00E6003 N-$00E6004
N-$00E6005 N-$00E6006 N-$00E6007 N-$00E6008 N-$00E6009
O-@OP00E60
 
ENTER-REFRESH PF2-ACTIVITY DETAIL PF4-REGION LIST PF5-ACTIVITY SUMMARY

 
User Types
The list of connections is sorted by user ID within user type. User type is indicated by the following letters:
Key Commands
Operator Services Screen
Function
The OPERATOR SERVICES screen provides the ability to make changes for the specified user.
To Display
To display from the ACTIVITY DETAIL screen, press PF11.
Illustration of Operator Services Screen

 
S6BADMI7 S6H1DOBB OPERATOR SERVICES FOR $00E6000 2006NOV29 13:04:54
 
SERVICE GLOBAL CURRENT DESIRED TOGGLE
TRACE NO NO ___ PF4
 
PAGE SWEEP
- LOG NO NO ___ PF5
- SMF NO NO ___ PF7
- DUMP NO NO ___ PF8
- LIMIT 0 0 _____
 
CANCEL NO ___ PF9
 
FORCE ___ PF10
WARNING:
FORCE IS INTENDED TO ABNORMALLY TERMINATE A USER IF FOR SOME REASON AN
OUTSTANDING CANCEL WAS UNABLE TO COMPLETE. EVERY EFFORT IS TAKEN TO ENSURE
THE USER IS REMOVED FROM THE SYSTEM AS CLEANLY AS POSSIBLE HOWEVER, THE
  NATURE OF THE FORCE CANNOT GUARANTEE TRANSACTION INTEGRITY.
 
FORCE MUST BE USED WITH EXTREME CAUTION AND ONLY AFTER ALL OTHER MEANS
HAVE BEEN EXAUSTED
PF2-ACTIVITY DETAIL PF11-ISSUE COMMAND

 
Key Commands
Prepare to issue a FORCEUSER command to forcibly remove the current connection from the Data Object Broker. Note the on-screen warning.
J. Installation/Configuration
Function
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.
Installation and Configuration Screen

 
S6BADMJ1 S6DCDOBA INSTALLATION AND CONFIGURATION 2011JAN07 03:05:48
 
ENVIRONMENT
O/S zOS 1.11 CPU ID F1A3 MODEL 2098 GMT ADJ FFFF94BB
 
JOB INFORMATION
TASKNAME DC52ADBA ASID 0218 NODENAME S6DCDOBA VERSION 600E006
START 2011JAN07 03:03:40 COMMUNICATIONS:RELAY Y CROSS MEMORY Y VTAM Y
ESTAE SUPPORT Y OPERATOR SECURITY N SWAPPABLE N SRBMODE Z
 
STORAGE LIMITS
CTAB RES 1024 CTAB SIZE 31744 XTAB SIZE 16384 RES PAGES 512
LOCK BUF 8192 RSC MAX 128 NODE MAX 128 SCH AVG. 1
TRACE EVENT 64 TRACE CTABLE 256 TRACE COMMIT 1024 TRACE QUERY 1024
TRACE COMM. 768
 
PROCESS MANAGEMENT
PAGES/CHPT 32767 TRX/CHPT 13499 CHPT INTVL 120 CONCURR. VSAM 24
MAX THREADS 100 MAX USERS 1000 LOCK TIMEOUT 60 TIOT DELAY 25
MAX QUERY TCB 1 DUPLICATE USERID Y DUP REMOTE USER N CICS DSPL MAX 0
SPIN INTVL 0 SPIN MBR @CRASP SPIN RUN JOB
SPIN DSN S6B.DC.OSB60.CNTL
 
TRANSACTION MANAGEMENT
WORKING SET 999 READ LIMIT 0 DATA PG LIMIT 156 SIX PG LIMIT 00000
PAGE SWEEP 0 PG SWEEP LOG N PG SWEEP SMF N PG SWEEP DUMP N
 
MONITORING
GTFID AA SMF RECORD FA SMF-13 INT. 15 SMF-22 INT. 30
SMF-23 INT. 0 SMF-24 INT. 0 SMF-25 INT. 0 SMF-26 INT. 5
SMF-27 INT. 0 SMF-28 INT. 0 SMF-47 INT. 5 SMF-48 INT. 30
MSG TRACING N SERVICE TRACING N NETVIEW SUPPORT N
 
WTO REPORTING
INTERVAL 1440 REMOTE ID LOCAL SYSLOG LEVEL # CONSOLE LEVEL F
PRINT CLASS K DELETE/SUPPRESS N MSG SUFFIX DCA
DESC:LOG 0000 INFORMATION 0000 WARNING 0000 ERROR 0000 ALERT/ACTION 0000
ROUTE: 0020 0020 0020 0020 0020
 
SNAP/SVC DUMP REPORTING
SNAP HIGH QUALIFIER S6B.DC CLASS A VOLUME HRN070 UNIT HRNPOOL
DUMP ON QUERY ABORT Y DUMP ON TRANSACTION ABORT N DUMP ON INDOUBT TRX Y
NO MORE DATA TO BE DISPLAYED

 
Sections and Fields
The sections and the fields on this screen contain the following information:
ENVIRONMENT
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.
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.
JOB INFORMATION
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.
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)
STORAGE LIMITS
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.
The maximum number of table definitions, in CTABLEs, that can simultaneously reside in Data Object Broker storage. (CTABRESIDENT)
The maximum size, in kilobytes, for CTABLEs, the internal representations of TIBCO Object Service Broker table definitions. (CTABLESIZE)
The size, in kilobytes, of the buffer pool for XTABLEs, the internal representations of TIBCO Object Service Broker report and screen definitions. (XTABLESIZE)
TRACE EVENT
TRACE CTABLE
TRACE COMMIT
TRACE QUERY
TRACE COMM
PROCESS MANAGEMENT
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 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)
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)
Specifies whether to allow duplicate online user IDs to create sessions concurrently. (DUPUSERID)
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 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)
TRANSACTION MANAGEMENT
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 page sweep reporting option.
(PAGESWEEPACTION — the Write to log option)
The page sweep reporting option.
(PAGESWEEPACTION — the Write SMF record option)
The page sweep reporting option.
(PAGESWEEPACTION — the Abend the transaction option)
MONITORING
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
WTO REPORTING
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 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)
A — action
E — error
W — warning
I — information
L — log only
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)
A — action
E — error
W — warning
I — information
L — log
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)
ALERT/ ACTION
The route code for L (log) WTO messages. (ROUTLOG)1
ALERT/ ACTION

1

SNAP/SVC DUMP REPORTING
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 volume serial of the DASD where the Data Object Broker can allocate snap dump data sets. (SNAPVOLSER)
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)
See Also
TIBCO Object Service Broker for z/OS Monitoring Performance for more information about generating SMF records.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved