![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The hex address of the Execution Environment Block (HDRB) that is one of the main anchor blocks in the Execution Environment. The jobname for this Execution Environment, for example, the CICS jobname for a CICS region. The communication ID for the Data Object Broker. The Execution Environment specifies this in the TDS Execution Environment parameter. The Data Object Broker specifies this in the VTAMAPPLID parameter. The node name of the local node used for TIBCO Object Service Broker distributed processing.The monitor main menu appears after the HMON rule is executed. You select the individual options of the monitor by using the indicated PF key.
This menu reads the in-storage control blocks used for configuration settings. There are various places that these configuration parameters are set as shown in the following list:
• The EECONFIG install job that assembles the PARMXXXX members.
TIBCO Object Service Broker Parameters for a list of the available parameters.
Set by the TASKEXECNUM Execution Environment parameter and is the number of executor TCBs available. Set by the TASKFILENUM Execution Environment parameter and is the number of file TCBs available. Set by the TASKIMSNUM Execution Environment parameter and is the number of IMS/DB gateway TCBs available. Set by the TASKSORTNUM Execution Environment parameter and is the number of TCBs available for sorting using an external sort. Set by the TASKMISCNUM Execution Environment parameter and is the number of TCBs available for miscellaneous activities such as OAI initialization and termination. Set by the TASKINITNUM Execution Environment parameter and is the number of TCBs available for session initiation and termination. Set by the TASKOPERNUM Execution Environment parameter and is the number of TCBs available for servicing operator requests.
Set by the SMFTYPE Execution Environment parameter. This is the SMF record number that is used for TIBCO Object Service Broker SMF records. Set by the SMFDETAIL Execution Environment parameter and specifies whether subtype 72 detail statistics are to gathered. Set by the SMFPERFORMANCE Execution Environment parameter and specifies whether the performance section of the subtype 72 record is to be completed.
Set by the STAE or NOSTAE Execution Environment parameter and specifies whether the session should run with ESTAEs. Set by the TDS Execution Environment parameter and specifies the name of the Data Object Broker that this Execution Environment is connected to. Set by the MDL Execution Environment parameter and specifies the model to be used for the Execution Environment side of the Execution Environment to Data Object Broker communication.
Set by the REGIONTABLESIZE Execution Environment parameter and used to getmain storage for binding table data and definitions. (appears only if there are servers running in the Execution Environment) Set by the POOLSIZE server parameter and is used to getmain storage for servers.
Set by the SECACLSIZE Execution Environment parameter. This specifies the size of the discretionary permission list of TIBCO Object Service Broker objects. Set by the SECADMINSIZE Execution Environment parameter. This specifies the size of the area to contain a table of users and their security administrators. Set by the SECPACLSIZE Execution Environment parameter. This specifies the size of the discretionary permission access control list for parameterized tables. Set by the SECOBJSIZE Execution Environment parameter. This specifies the size of the TIBCO Object Service Broker object security information area. Set by the SECUSERSIZE Execution Environment parameter. This specifies the size of the area to contain the user basic security information. There is one entry for each user logged in. When an entry is built, the entry remains in the bound area for the life of the Execution Environment.The PF key choices provide direct entry into other configuration screens without going to the configuration menu.
Option set by the SORTPRINT Execution Environment parameter. This is used for external sort diagnostic messages. UNIT for SORTWK The z/OS unit specified in the SORTUNIT Execution Environment parameter that is the default unit used for sort work areas. Allocation CYLINDERS PRIM – Primary allocation for sort work data sets set by the TEMPRIMARYCYL Execution Environment parameter.SEC – Secondary allocation for sort work data sets set by the TEMPSECONDARY Execution Environment parameter. Maximum number of sort work files allowed. Set by the SORTWORKFILESMAX Execution Environment parameter. MAX Memory SORT PGM Limit for storage that the external sort program can use. Set by the SORTEXTMEMMAX Execution Environment parameter.
MAX PAGES for Rows Maximum number of 4 KB pages the internal sort processes before switching to external sort. This is set by the SORTINTPAGESMAX Execution Environment parameter. MAX Memory INCORE Maximum amount of in-core memory an internal sort is allowed to consume. Set by the SORTINTMEMMAX Execution Environment parameter. # Concurrent Sorts Maximum allowed number of concurrent sorts. This is set by the SORTINTNUMMAX Execution Environment parameter.
The estimated number of builtins used to build a hash table for quick lookup. Set by the BLTINNUM Execution Environment parameter. The estimated number of installation library rules. Used to build a hash table for quick lookup. Set by the INSTLIBNUM Execution Environment parameter. The estimated number of system library rules. Used to build a hash table for quick lookup. Set by the SYSLIBNUM Execution Environment parameter. Shows the default search path set by the SEARCH Execution Environment parameter. Obsolete. Used to show the level of syntax checking set by the EXECMODE parameter, which is no longer in use. Shows the default browse mode set by the BROWSE/NOBROWSE Execution Environment parameter. Shows the default test mode set by the TEST/NOTEST Execution Environment parameter. Shows the default for DB2 logging used to build Static SQL. This is set by the DB2LOG server parameter. Shows the setting of the debug option that is set by the DEBUG Execution Environment parameter. Shows the default login rule name and is set by the LOGONRULENAME Execution Environment parameter.
The setting for the SESSIONMEMMAX Execution Environment parameter, which limits the total session memory one user can use. The setting for the TRANSACTIONMEMMAX Execution Environment parameter, which limits the total transaction memory one transaction can use. The setting for the MSGLOGMAX Execution Environment parameter, which limits the total memory one user can use for MSGLOG memory. TAM ROW BUFFER The setting for the TAMBMIN Execution Environment parameter, which sets the minimum buffer size for a data row. The setting for the TAMBMAX Execution Environment parameter, which sets the maximum buffer size for a data row. SESS MAX TABLE SIZE The setting for the TAMBSTS Execution Environment parameter, which sets the buffer size for session tables. SESS FILE MAXIMUM The setting for the SESSIONFILEMAX Execution Environment parameter, which controls the maximum number of data sets a user can have open at one time. The setting for the PRINTDEST Execution Environment parameter, which sets the default print destination. The setting for the PRINTCLASS Execution Environment parameter, which sets the default print class. STATS COLLECTION Obsolete. Used to be the setting for the STATS parameter, which controlled the production of interpreter statistics. # STATS RECORDS The setting for the STATSBUF Execution Environment parameter, which controls how many statistics buffers each user has allocated. Each buffer is 160 bytes in length. Obsolete. Used to be the setting for the EXECMODE parameter, which controlled the level of default syntax checking. The setting for the BROWSE Execution Environment parameter, which controls the default browse mode of a transaction. The setting for the TEST Execution Environment parameter, which controls the default test mode of a transaction. The setting for the SEARCH Execution Environment parameter, which controls the default search path for the first rule to be executed. The setting for the EXECHASHSIZE Execution Environment parameter, which specifies the number of executor rule name hash table buckets. The setting for the EXECSCOPESIZE Execution Environment parameter, which specifies the number of 4 byte items in the executor scope stack. The setting for the EXECLOCALNAMESIZE Execution Environment parameter, which is the size of the local variable name storage area. The setting for the EXECSTACKSIZE Execution Environment parameter, which is the size of the executor runtime stack. The setting for the EXECLOCALSIZE Execution Environment parameter, which sets the size of the executor local variable storage. The setting for the TRANMAXNUM Execution Environment parameter, which limits the maximum number of transactions allowed in a stream of transactions.
The storage subsection shows the TIBCO Object Service Broker storage manager’s view of virtual storage, which it manages. The first option shows the allocated versus use statistics for storage segments getmained from z/OS. The second option shows what type of storage is suballocated from each of the storage segments. Most of the storage used is getmained from extended private storage subpool 52. Storage getmained from 24 bit storage is gotten in 8 KB pieces and use is minimal. Most below-the-line storage is obtained to service older file access methods (for example, QSAM).
The SSB display shows the TIBCO Object Service Broker storage utilization for TIBCO Object Service Broker managed virtual storage. Most storage is obtained from z/OS subpool 52 in extended storage. There is one set of storage allocated from below the 16 MB line and is noted by the Below flag being set to Y. This is allocated in 8 KB pieces. When a segment appears on the allocated display, it is not returned to z/OS via a freemain until the Execution Environment is recycled or, in the case of CICS, a HTRM transaction is run. The storage is available for TIBCO Object Service Broker use during this time.
The size of TIBCO Object Service Broker virtual storage segment size in KB. TSO and batch have a segment size of 256 KB. CICS and the Native Execution Environment have a segment size of 1 MB. All allocation for segments below the 16 MB line are 8 KB. The amount of virtual storage getmained from z/OS that is available to be given out by the TIBCO Object Service Broker storage manager in KB.
This display can be used to find the high-water virtual-storage mark for the TIBCO Object Service Broker storage manager. The allocated total is this high-water mark.
This display shows which type of TIBCO Object Service Broker storage is in use. The following documents, in alphabetic order, the various storage pools that could appear.
Session work areas (SMGBLWA); one per user in the Execution Environment.
The record size of the storage pool in bytes. A zero block size means that the entire block is allocated to the requester.
This display gives a picture of where what type of storage is being used on a region-wide basis. Transaction storage tends to consume most of the storage managed by TIBCO Object Service Broker. One transaction uses 256 KB of virtual storage.
This field is cursor-sensitive. By placing the cursor next to the name of the user you want to zoom in on and pressing one of the following PF keys causes different types of information to appear.
Displays the Execution Environment storage that is managed by TIBCO Object Service Broker and used by a user. The storage pools are documented in Storage Subsection. Displays the number of session tables in use by a user, and the reference counts and the amount of storage used by each session table.
The session number assigned for this user. This number is incremented throughout the life of the region as new user sessions are added. The transaction number of the last transaction run. Example: If trans # is 153, this is the 153rd transaction run within this session. The stream level of the session. For example, if the LVL is 2, there is one parent and one child transaction running in this session.Note If a peer server has never been used, the LVL indicator is equal to zero. This means that no transaction was ever executed. RULE OR RMTUSERID The last rule that was active. If the user ID is TAMAPIxx, this field is the user ID of the remote user of the peer server. The SMF field set by the $SETTRANSACTION tool. If this field is filled in by the application, this provides greater granularity in monitoring the flow of an application. If the user ID is TAMAPIxx, INACTIVE shows up in this field if there is no activity on the peer server.
This display shows the storage managed by TIBCO Object Service Broker and used by this user. The storage pools are described in Storage Subsection. This is the total used by this user minus the session table storage.
This display shows the SMF detail buffers for a user. The following statistics are included:
•
•
•
The high-water mark in 4 KB virtual storage pages for this TIBCO Object Service Broker user. This should be similar to the HSR62PGH field in the TIBCO Object Service Broker subtype-62 record. The number of used 4 KB virtual-storage pages accumulated currently for this TIBCO Object Service Broker user. A measure of storage residency. The calculation is derived by the following formula: number of 4 KB pages times the number of seconds. This should be similar to the HSR62PGS field in the TIBCO Object Service Broker subtype-62 record.
The amount of time that the TIBCO Object Service Broker session spent waiting for a response from the terminal. The amount of time the TIBCO Object Service Broker session spent waiting for Execution Environment locks. The amount of time the TIBCO Object Service Broker session spent waiting to schedule a system service in the Execution Environment. The amount of time the TIBCO Object Service Broker session spent waiting for resumption of the TIBCO Object Service Broker interpreter following a system service.
This display shows the SMF performance buffers for a user. This is a wide screen that can be scrolled right and left with the PF11 and PF10 keys. The following information is included:This shows the first 100 rules executed in the most current transaction. When this panel appears for the first time, the number in the lower left corner of the screen shows the number of rules that information was collected for in the display.These statistics are by default sorted in descending order by elapsed time. Each field can be sorted by placing the cursor on the field and pressing PF14.
PROGRAM NAME The wall clock time in seconds that this routine has run. This time is the accumulation of all iterations of the routine.
NNNN
(in the lower left corner of the screen)
The number of times this session table has been referenced. A count of zero says that the session table was used once and not referenced again.
The three displays below fit on a 3270 model 5 screen. In this manual, the screen is divided into three screens.
This is a circular buffer and its size is set by the STATSBUF Execution Environment parameter. The default is 200 buffers. Consider increasing this for a development or new production system to capture better information on how an application is doing. Each entry is 160 bytes in length.
The first rule in a transaction started by a TRANSFERCALL, an EXECUTE, or a DISPLAY & TRANSFERCALL. The date a ruleset started, in Julian date format (yyddd where yy is the year and ddd is the sequential day of the year). The time that the ruleset started in hhmmss format.Note The leading zero is truncated; for example, 92235 is 09:22:35. The number of table access method calls, which is the number of table accesses for all table types. The CPU consumed by this ruleset. This is only TCB time. SRB time is kept on an address-space basis. The number of external routine load requests. This is caused by calls to TIBCO Object Service Broker external routines. The number of times rules were obtained by going to the Data Object Broker MetaStor (non-buffered rules). The number of messages sent to the Data Object Broker that in turn cause access to the MetaStor.
This menu provides selections to find out what CPU, storage, and I/O resources this region is consuming.
This display shows the CPU usage for each task in the Execution Environment. The totals are given for total TCB usage, SRB usage, and I/O counts.
DFHxxxx HFILIxxx The task used to process file requests not defined by a PPT entry in CICS and all file requests for other Execution Environment types. HMISCxxx HSORTxxx HOPERxxx HSINxxx HINTRxxx The number of each of the tasks are controlled by the Execution Environment parameters prefixed by “TASK”.
By looking at the utilization amount of each TCB, you can decide whether various classes of TCB are under- or over-allocated.
This display shows the virtual storage limits, virtual storage used, and the virtual storage available for use in this region. All measures are in KB of storage. These numbers are valid at the time of display and could fluctuate based on z/OS storage requests. The limits remain static for the life of the region.This information is similar to the following Execution Environment initialization messages, but is dynamic in nature:
This menu lists the types of binding information that is available for your inquiry. The categories are divided into:This display represents the usage of the rules binding areas and shows total usage of the region-wide rules binding areas. The system (called COMMON by default) library and the installation (called SITE by default) libraries are shown in detail. If you have large site libraries, these functions are somewhat resource-intensive.This display shows which table definition and data are bound in the Execution Environment as well as the reference counts for these tables. Bound tables also include bound screens.This display shows the statistics for the security binding areas. If you use the SEC_REBIND tool, the statistics are reset.
You can use this menu to see if rules were in fact being accessed or bound in the installation library. The table binding statistics indicate whether you are getting good hit counts on the bound tables and definitions. You can use the security statistics to size the security areas set by the Execution Environment parameters.
This display shows the binding information for the system rules library. Rules are loaded only when accessed. You can expect these statistics to increase over time as more rules are accessed.
The library name specified in the SYSLIBNAME Execution Environment parameter (COMMON by default). This is set by the SYSLIBNUM Execution Environment parameter. Each slot is a four-byte hash bucket that speeds system rules library search. The number of system rules loaded into the region rules binding area during this execution of the Execution Environment.
The overflow number is the number of duplicate hashes created in the hashing algorithm. This number should be as low as possible for a more efficient hash. You can control this by finding the prime number closest to but not less than your total number of rules in the system library and specifying this value for the SYSLIBNUM Execution Environment parameter.
This display shows the binding information for the installation rules library. Rules are loaded only when accessed. You can expect these statistics to increase over time as more rules are accessed.
The library name specified in the INSTLIBNAME Execution Environment parameter (SITE by default). This is set by the INSTLIBNUM Execution Environment parameter. Each slot is a four-byte hash bucket that speeds installation rules library search. The number of installation rules loaded from the installation library into the rules binding area for the region during this execution of the Execution Environment.
The overflow number is the number of duplicate hashes created in the hashing algorithm. This number should be as low as possible for a more efficient hash. You can control this by finding the prime number closest to but not less than your total number of rules in the system library and specifying this value for the INSTLIBNUM Execution Environment parameter.
This shows information about the table definition and data binding area. The storage for the table binding area is getmained from subpool 9, which resides above the 16 MB line. The REGIONTABLESIZE Execution Environment parameter is the amount getmained and remaining allocated for the life of the Execution Environment.
The setting of the REGIONTABLESIZE Execution Environment parameter in bytes. The specification is in kilobytes for the parameter. The amount of the table binding area in use. Tables are bound when accessed if the binding flags are set. The number of directory entries used. This is the number of table definitions or/and table data bound. The number of times that this table has been accessed. This is the hit count for the bound table. NNNN
(in the lower left corner of the screen) Accumulation of the CTABLE size entries. The difference between USEDSPACE and this number is the space used for bound table data.
The storage for the bound security area is getmained from subpool 9 in extended private storage. The total storage gotten is the sum of the following Execution Environment parameters:
Size of the bound security Address of bound security Set by the SECOBJSIZE Execution Environment parameter. This specifies the size of the TIBCO Object Service Broker object security information area. Set by the SECACLSIZE Execution Environment parameter. This specifies the size of the discretionary permission list of TIBCO Object Service Broker objects. Set by the SECPACLSIZE Execution Environment parameter. This specifies the size of the discretionary permission access control list for parameterized tables. Set by the SECADMINSIZE Execution Environment parameter. This specifies the size of the area to contain a table of users and their security administrators. Set by the SECUSERSIZE Execution Environment parameter. This specifies the size of the area to contain the user basic security information. There is one entry for each user logged in. When an entry is built, the entry remains in the bound area for life of the Execution Environment.Note You must press PF8 to see the USERSEC statistics on a 3270 Mod 3. Max. Entries The maximum number of entries allowed in this bound security area. This can be changed by the Execution Environment parameters described above. The amount of storage allocated as a result of the Execution Environment parameter setting described above.
This set of screens displays the SMF information for various levels of detail. The summary SMF screen shows the region-level SMF statistics that reflect what is contained in the TIBCO Object Service Broker SMF subtype-52 record. The next three displays are user-related and show the information contained in the TIBCO Object Service Broker SMF subtype-62 record. The various displays contain basically the same information, although they are ordered differently based on your selection.The Transaction Monitor is an application that demonstrates how you can use rules to access the performance information around your application and rules.
This screen displays the SMF information that appears in the TIBCO Object Service Broker SMF subtype-52 record. The statistics in the subtype 52 buffers are accumulated at session end for each user. You could see the counters at zero at the beginning of the region’s operation because no users have logged out.This display shows the SMF detail buffers for the entire Execution Environment. The following information is included:
The high-water mark in 4 KB virtual-storage pages for this Execution Environment. This should be similar to the HSR52PGH field in the TIBCO Object Service Broker subtype‑52 record. A measure of storage residency. The calculation is derived by the following formula. Number of 4 KB pages times the number of seconds. This should be similar to the HSR52PGS field in the TIBCO Object Service Broker subtype‑52 record.
The amount of time the Execution Environment spent waiting for Execution Environment locks. The amount of time the Execution Environment spent waiting to schedule a system service in the Execution Environment. The amount of time the Execution Environment spent waiting for resumption of the TIBCO Object Service Broker interpreter following a system service.
The total TCB time in seconds used by this user while running on TIBCO Object Service Broker TCBs. This does not include CICS TCB time. This is similar to the TIBCO Object Service Broker SMF subtype‑62 HSR62CPU field. The PF keys provide a fast path to other SMF functions. PF4, PF5, and PF6 are cursor-sensitive. Place the cursor next to the user you want to zoom in on.
This screens displays the SMF information for each user in descending order by the number of messages sent to the Data Object Broker.
The total TCB time in seconds used by this user while running on TIBCO Object Service Broker TCBs. This does not include CICS TCB time. This is similar to the TIBCO Object Service Broker SMF subtype‑62 HSR62CPU field. The PF keys provide a fast path into other SMF screens. PF4, PF5, and PF6 are cursor-sensitive. Place the cursor next to the user you want to zoom in on.
This screens displays the SMF information for each user, sorted in descending order by the amount of memory used and by the number of transactions used since login (accumulated).
The total TCB time in seconds used by this user while running on TIBCO Object Service Broker TCBs. This does not include CICS TCB time. This is similar to the TIBCO Object Service Broker SMF subtype‑62 HSR62CPU field. The PF keys provide a fast path to other SMF screens. PF4, PF5, and PF6 are cursor-sensitive. Place the cursor next to the user that you want to zoom in on.The transaction monitor is a tool that allows customers to monitor the performance statistics of groups of users. To monitor a group of users of an application, the following actions are required:
• The userid(s) to be monitored needs to be added to the monitor using the PF5 option or by updating the table HMON_TRNUSERS directly.
•
• The statement "CALL HTRN_STATS;" needs to be added to the application at points where a statistics record needs to be cut.The recorded data can be reviewed using the PF2 and PF4 options or by reviewing the table HMON_TRANLOG, which is parameterized by date. It contains the following fields:
This display groups other existing tools together for your convenience. Each tool on this menu is documented in the screen-level help. For information on getting a list of users, refer to Menu Item: Users Logged On. For information on getting statistics, refer to Monitoring Via the Workbench.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |