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


Chapter 4 Understanding Data Object Broker Parameters : Parameter Descriptions

Parameter Descriptions
BWO
Specifies whether Backup While Open is supported.
Operator Modifiable
CHKTRACE
Specifies whether to make a checkpoint trace.
If CHKTRACE is set to Y (a trace is requested), a message is printed to the Data Object Broker log at the beginning and end of each checkpoint.
CHPAGELIMIT
The threshold, in number of changed pages, that triggers a checkpoint.
Use the default as a starting point, and then monitor the frequency of checkpoints. You can adjust this value in conjunction with CHTRANLIMIT to cause a moderate frequency of checkpoint activity during peak load times.
NOTE  The value can be reduced by the Data Object Broker startup process if the redolog and cache are determined to be too small.
A high frequency of checkpoints can have a negative effect on the overall performance of the Data Object Broker. However, the frequency should support your backup and recovery requirements.
The journal must be large enough to hold 50 checkpoints, that is, 50*CHPAGELIMIT 4 KB pages.
If the journal is too small, adjust CHPAGELIMIT accordingly or increase the size of the journal data sets.
z/OS: If collection of SMF records is enabled, a subtype 12 record is produced on a checkpoint. The field HU12PAG contains the number of physical pages updated during each checkpoint.
CHPTINTERVAL
The maximum time interval in minutes between checkpoints, before the Data Object Broker triggers another checkpoint.
This feature should be used only when you want to set a maximum interval between checkpoints during periods of low activity.
A high frequency of checkpoints can have a negative effect on the overall performance of the Data Object Broker. However, the frequency should support your backup and recovery requirements.
z/OS: If collection of SMF records is enabled, a subtype 12 record is produced on a checkpoint. These records contain the date and time of each checkpoint taken.
CHTRANLIMIT
The number of commits, issued from Execution Environments connected to this Data Object Broker, that cause it to take a checkpoint.
You can adjust this value in conjunction with CHPAGELIMIT to cause a moderate amount of checkpoint activity during peak load times.
A high frequency of checkpoints can have a negative effect on the overall performance of the Data Object Broker. However, the frequency should support your backup and recovery requirements.
A value of 0 causes the actual value of CHTRANLIMIT to be set based on the calculated maximum capacity of the redolog ((size of redolog in bytes - 4096)/32768).
z/OS: If collection of SMF records is enabled, a subtype 12 record is produced on a checkpoint. The field HU12NTRX contains the number of commits processed during each checkpoint.
CLOGRETRYINT
The retry interval, in seconds, at which the Data Object Broker should attempt to resolve in-doubt distributed transactions.
COMMID
The Data Object Broker communications identifier. If a user wants to connect to this Data Object Broker, the identifier must be specified as the TDS Execution Environment parameter.
Specify a valid communications application identifier dedicated to this Data Object Broker.
NOTE  This identifier is required regardless of the communication method used, for example, VTAM, Cross Memory Services, or TCP/IP.
CTABAGE
The CTABLE LRU-2 aging threshold.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information on the LRU‑2 algorithm.
CTABLESIZE
The maximum size, in kilobytes, for CTABLEs, the internal representations of TIBCO Object Service Broker table definitions.
The size required depends on the complexity of the table definition.
The ESTIMATETBLDFN tool provides an approximation of CTABLE size required for table definitions.
If the CTABLESIZE is too small to accommodate a table definition, the transaction requesting the table definition fails.
The actual amount of storage allocated by the Data Object Broker for CTABLEs is CTABLESIZE * CTABRESIDENT. This CTABLE pool is above the 16 MB line on z/OS.
Refer to TIBCO Object Service Broker Shareable Tools for more information about the ESTIMATETBLDFN tool.
CTABRESIDENT
The maximum number of table definitions, in CTABLEs, that can simultaneously reside in Data Object Broker storage.
Application response times and Data Object Broker CPU consumption will be reduced if requested CTABLES are resident and do not have to be built.
The actual amount of storage allocated by the Data Object Broker for CTABLEs is CTABLESIZE * CTABRESIDENT. This CTABLE pool is above the 16 MB line on z/OS.
Field HU10BLDC is the number of physical CTABLE requests. This means that the CTABLE had to be built to satisfy the request.
Try to attain the highest possible ratio of logical CTABLE requests to physical CTABLE requests.
The TIBCO Object Service Broker Administration menu also displays the logical and physical CTAB values on the General Statistics screen.
DATAPAGELIMIT
The maximum number of data pages that can be updated within a transaction synchronization point process.
Requests attempting to update more data pages than the specified value are aborted.
The larger the value the more data pages can be physically held by a transaction, thus there is greater potential for interference between transactions.
DBPROFILE
The action to be performed when an external resource commit fails and the resource has Fail Safe level set to 0.
This parameter has no effect if the resource has Fail Safe level set to 1.
For serial commit with more than 1 external resource. If the first resource fails the commit terminates. If the second or subsequent commit terminates, fail continuance depends on the value for this parameter.
TIBCO Object Service Broker for z/OS Managing Backup and Recovery or TIBCO Object Service Broker for Open Systems Managing Backup and Recovery
TIBCO Object Service Broker for z/OS Installing and Operating or TIBCO Object Service Broker for Open Systems Installing and Operating
DBSNAP
Specifies whether a snap dump is to be generated when an in-doubt transaction is detected.
The resources required to schedule the snap dump are minimal and have little impact on the system.
DESCACTION
The descriptor code to use for A (alert) WTO messages. This is also a Message Switch parameter.
Descriptor codes determine how the system displays and deletes messages. If you do not specify a descriptor code, messages are issued as standard console messages.
See Also
The MVS Routing and Descriptor Codes IBM manual for code descriptions of WTO messages.
DESCERROR
The descriptor code to use for E (error) WTO messages. This is also a Message Switch parameter.
Descriptor codes determine how the system displays and deletes messages. If you do not specify a descriptor code, messages are issued as standard console messages.
DESCINFORM
The descriptor code to use for I (information) WTO messages. This is also a Message Switch parameter.
Descriptor codes determine how the system displays and deletes messages. If you do not specify a descriptor code, messages are issued as standard console messages.
DESCLOG
The descriptor code to use for L (log) WTO messages. This is also a Message Switch parameter.
Descriptor codes determine how the system displays and deletes messages. If you do not specify a descriptor code, messages are issued as standard console messages.
DESCWARN
The descriptor code to use for W (warning) WTO messages. This is also a Message Switch parameter.
Descriptor codes determine how the system displays and deletes messages. If you do not specify a descriptor code, messages are issued as standard console messages.
DUPLEXLOGFAIL
Specifies whether to continue processing in the event of an I/O error on the primary or duplex redolog.
If DUPLEXLOGFAIL is set to CONTINUE, processing is based on a single image of the log.
DUPUSERID
Specifies whether to allow duplicate online user IDs to create sessions concurrently.
If ISPF remote console servers are used, you should change the default ISPF command separator from a semicolon (;) to some other character. When DUPUSERID is Y, a semicolon separates the user ID from the user connection identifier.
Provides a unique identifier for user connections. The CANCELUSER, NOTRACE, and TRACEID operator commands refer to this identifier (COMMNUM). If DUPUSERID is set to Y, and one of these commands is issued for a user ID with multiple connections, the command returns messages that help you identify the connection you want to process. The messages prompt you to repeat the command with a unique identifier.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information on the CANCELUSER, NOTRACE, and TRACEID commands.
DYNAMICRESOURCE
Specifies whether to allow resource entries to be created dynamically.
If set to N, all external gateway and Peer resources must be pre-defined using the Object Service Broker Administration utility.
If set to Y, allows Object Sevice Broker gateways to dynamically create resource manager entries when they connect to the DOB. In this mode only Peer resources need to be pre-defined using the Object Service Broker Administration utility.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information on the Administration Utility, the pre-requisites paragraphs in the varous service gateway manuals for configuring the gateway resources, and Chapter 2 of the TIBCO Object Service Broker Managing Exterenal Data manual for configuring the service gateway for files resources.
ERRNOTRACE
Specifies whether to have system and internal error tracing. This traces the failure of system library calls showing the errno value at the point of failure.
ESTAE
Specifies whether to enable the Data Object Broker Extended Specific Task Abnormal Exit (ESTAE) routine for handling abnormal terminations.
EVENTLOG
Specifies whether to log Execution Environment and Data Object Broker events.
Registry entries for event logging can be created only if the user starting the Execution Environment or Data Object Broker has administrator rights.
FIXEDRPDPOOL
Specifies whether the Data Object Broker resident page directory is to be page fixed in storage.
A Y value causes the Data Object Broker to page fix additional real storage frames based on the RESIDENTPAGES value. It provides a performance benefit in a production environment by keeping the resident page directory in memory.
However, this can cause additional z/OS paging to occur when real storage is constrained.
If FIXEDRPDPOOL=N, the number of fixed frames required for the resident page directory is: Fixed Frames = (8*RESIDENTPAGES*1000/4096) rounded to next higher integer.
If FIXEDRPDPOOL=Y, the number of additional fixed frames allocated for the resident page directory is: Fixed Frames = (80*RESIDENTPAGES*1000/4096) rounded to next higher integer.
GTFID
The hexadecimal identifier for GTF trace records produced by the Data Object Broker when tracing is in effect.
Start the GTF trace with USR(xx), where xx is the value of GTFID.
Set the MSGTRACE and SSTRACE parameters to Y.
HAWKANAME
The TIBCO Hawk microagent application name. This name can be used by TIBCO Hawk Agents when applying a Hawk rulebase.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk.
HAWKDAEMON
The TIBCO Hawk Rendezvous daemon and TCP port parameters.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. Refer to product documentation for TIBCO Hawk and TIBCO Rendezvous for information about the Rendezvous daemon parameter.
HAWKDNAME
The TIBCO Hawk microagent display name. This name is displayed when using a TIBCO Hawk console application, such as TIBCO Hawk Display.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk.
HAWKNETWORK
The TIBCO Hawk Rendezvous network parameter.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. Refer to product documentation for TIBCO Hawk and TIBCO Rendezvous for information about the Rendezvous network parameter.
HAWKPOLL
The number of milliseconds to wait between TIBCO Hawk session creation attempts.
If the internal Hawk microagent is not able to establish a connection to TIBCO Hawk, then it will sleep for at most the specified number of milliseconds before trying again.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk.
HAWKSERVICE
The TIBCO Hawk Rendezvous UDP service port.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. Refer to product documentation for TIBCO Hawk and TIBCO Rendezvous for information about the Rendezvous network parameter.
HEAPSIZE
The number of kilobytes in the heap available to TDS for each table access message.
IOTRACE
Specifies whether to trace the page I/O.
If IOTRACE is set to Y (trace the I/O), a message is written to the Data Object Broker log for each I/O operation.
JOURNALS
Specifies whether to enable the Data Object Broker to write images of updated data store pages to journal files.
JOURNALS=Y causes the Data Object Broker to perform journaling for all segments whose database definition allows journaling to be done.
Regardless of the setting for this parameter, journaling is never done for a segment whose database definition explicitly specifies no journaling for the segment.
If journals are not available for your segments, you cannot create a continuous backup of your system. This means you can restore your system only to the last complete backup taken.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information on journal control commands.
LOCKBUFFERS
The number of additional 4 KB lock buffers to be acquired beyond the base amount.
z/OS: This base amount is defined as MAXTHREADS*8.
Use the default value unless you determine by measurement that you need additional lock buffers.
In heavy locking situations, a lock buffer pool that is too small can degrade service time, since transactions could be waiting on the lock buffer pool space.
z/OS: If the available lock buffer space is inadequate more table locks are generated to reduce the number of occurrence locks, thus making more space available.
On z/OS, the Buffer Pool screen of the TIBCO Object Service Broker Administration menu provides information about the LOCK pool usage. When the IN-USE MAX field shows the same value as the BUFFERS, the maximum has been reached. In that case use either this parameter or MAXTHREADS to increase the pool size.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
LOCKTIMEOUT
The wait interval in seconds before a lock request is retried if the initial request cannot be satisfied.
If lock interference results from transactions of short duration, a small value could be appropriate.
If an excessive number of transactions are failing due to lock interference the value is too small.
Also consider the application design, since it can have greater impact on response times than this parameter.
LOGMESSAGE
Determines whether logon or logoff messaging is to be issued by the Message Switch.
MAXCONCURRENT
The maximum number of concurrent Data Object Broker transactions that can execute at a time.
In a distributed data environment, the value of MAXCONCURRENT should be greater than the number of peers that you expect to be active simultaneously. For example, in a distributed data configuration with eight peers, you should set MAXCONCURRENT to at least nine.
MAXDBMS
The maximum number of external database servers that can be connected to the Data Object Broker at one time.
MAXDISPLAY
The maximum number of CICS display-type connections that are allowed to connect concurrently to the Data Object Broker.
Use the default of 0 to disable limit checking unless you have a reason to limit the number of CICS display type sessions.
Causes CICS sessions to be rejected with an S6BSM047E error message if the limit is exceeded.
Operator Modifiable
MAXNODES
The maximum number of peer nodes.
The default can be reduced to the number of peer TIBCO Object Service Broker nodes plus at least 10% for growth.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about TIBCO Object Service Broker resources.
MAXOPERATORS
The maximum number of concurrent operator/administrator sessions that can be connected to the Data Object Broker at one time.
MAXQUERY
The number of parallel query TCBs.
MAXQUERY supports the TIBCO Object Service Broker Accelerator Pack for z/OS, which is installed with TIBCO Object Service Broker.
MAXRESOURCES
The maximum number of TIBCO Object Service Broker resources.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about TIBCO Object Service Broker resource management and other administration controls.
MAXTDSEXTENTS
The maximum number of extents in a TDS page file.
Since an extent contains 31,744 pages and the default is 4 extents, you must adjust this parameter if any page file exceeds 126,976 pages (4 x 31,744 =126,976). Set this parameter to the number of pages in the largest TDS page file divided by 31,744 (rounded up to the next integer) or 4, whichever is larger.
MAXTHREADS
The number of requests that the Data Object Broker can service at the same time.
Specify a value that is at least equal to the number of queries and updates that can be pending in the Data Object Broker at any given time from all Execution Environment.
If too low a value is specified, requests are delayed. Approximately 70 KB of non-fixed virtual storage above 16 MB is used for each concurrent request.
Refer to IN-USE MAX field in the Buffer Pool Statistics screen (option D) of the TIBCO Object Service Broker Administration menu. One session buffer is assigned to each actively dispatched user.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
MAXUSERS
The maximum number of user sessions that the Data Object Broker allows to be active at one time. This is also a Message Switch parameter.
This number includes user online and batch sessions. User connections are refused after this limit is reached. This limit does not include operator, external server, and peer server sessions. External and peer server sessions are limited by:
Specify a value that is at least equal to the maximum number of user sessions logged in at one time.
If too low a value is specified, logins are rejected. On z/OS, approximately 2 KB of non-fixed virtual storage above the 16 MB is used for each login.
Additional operator sessions are started when an Execution Environment is started or terminated—one operator session per Execution Environment.
The impact of these sessions is minimal in most multiple-user Execution Environments (for example, Native Execution Environment or CICS). MAXUSERS should be increased only to accommodate the additional operator sessions if TSO or batch Execution Environments are heavily used.
The TIBCO Object Service Broker Administration menu’s General Statistics screen indicates how many users are currently logged in (USERS) and the maximum number of concurrent connections (users and servers) measured (MAXCON) during the life of this Data Object Broker.
On z/OS, this information is also available in TIBCO Object Service Broker SMF subtype-10 (total) and -26 (interval) records.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating or TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
MAXVSAMC
The maximum number of concurrent I/O requests to all page data sets.
You can reduce the maximum for a particular segment using the THREADS parameter in the segment’s database definition.
Too low a value causes processing overhead, as more VSAM scheduling is necessary. This results in additional VSAM requests and associated processing overhead. Increasing this value improves performance by allowing VSAM to allocate virtual storage for its control blocks.
The TIBCO Object Service Broker Administration menu shows the actual count of concurrent I/Os on its DASD Statistics screen. It shows the parameter setting on the Installation/Configuration screen as CONCURRENT VSAM.
This information is also available in the TIBCO Object Service Broker SMF subtype-11 records (at page data set level).
THREADS (Database definition parameter). The THREADS parameter is described in TIBCO Object Service Broker for z/OS Installing and Operating.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating or TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
MSGSIZE
The size of buffers, in kilobytes, for table access to TDS messages.
MSGTRACE
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.
GTF must be active to record the data produced. The use of GTF can affect overall system performance.
Solaris: Records are copied to $OS_ROOT/log/hrncr.99999.msg, where 99999 is the process ID of the hrncr supervisor process.
Windows: Records are copied to %OS_ROOT\LOG\hrncr.999.msg, where 999 is a sequence incremented for each instance of the log file.
NETVIEWBASE
The base code point indicator, during startup, for Netview support for alert-level messages.
NETVIEWBASE=0 turns off Netview support. The recommended NETVIEWBASE=1 setting translates to x'E000' as the base code point.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about Netview support.
NODENAME
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.
In Open Systems, the value for this parameter is also used as the communications identifier to identify the Data Object Broker to connect to for components such as client processes, Execution Environments, external database servers, and peer Data Object Brokers. (On z/OS, the COMMID parameter is used as the communications identifier to identify the Data Object Brokers to connect to for these components.)
When assigning a nodename, consider all other Data Object Broker nodes in your TIBCO Object Service Broker distributed network.
OPERATOR
One or more user IDs that should have operator authority for this Data Object Broker. User IDs with operator authority can cancel users.
Operating system user ID. Separate each entry with a comma. Up to fifteen values can be specified.
To specify an entry with non-alphanumeric characters, surround the entry with double quotes ("). The backslash (\) may be used to escape a double quote or itself.
NOTE  Case sensitive.
When assigning a node name, consider all other Data Object Broker nodes in your TIBCO Object Service Broker distributed data network.
PAGESWEEPACTION
The page sweep reporting option.
After triggering a page sweep report, the transaction continues normally.
When a message requests a logical page read that exceeds the threshold limit specified in the PAGESWEEPLIMIT parameter:
If the value is LOG, the S6BKF038W warning message appears in the log and on the console.
To get TIBCO Object Service Broker to perform more than one action, you must submit the PAGESWEEPACTION parameter more than once. For example, you could get an SVC dump and an SMF record.
The effect of PAGESWEEPACTION is global. To affect individual users, use the Sweepaction Data Object Broker command.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about Data Object Broker commands.
PAGESWEEPACTION takes effect only if PAGESWEEPLIMIT is greater than zero.
PAGESWEEPLIMIT
The threshold number of logical page reads for page sweep reporting.
On z/OS, when a Data Object Broker transaction processes this number of page reads, PAGESWEEPACTION is triggered.
Set the limit high enough that it is seldom reached. This reduces impact on your system, especially if you chose DUMP for action.
PAGESWEEPLIMIT is reset for each Data Object Broker transaction, of which there can be many during an Execution Environment transaction. In fact, each GET or FORALL in a rule starts a new Data Object Broker transaction. Also, if a FORALL retrieves more than 4 KB of data, each 4 KB request is a separate Data Object Broker transaction.
Each time the Data Object Broker reads a page, the counter is decremented. When it reaches zero on z/OS, the PAGESWEEPACTION is taken. When it reaches zero on Open Systems, a warning message is issued in the log. Because each Data Object Broker transaction can access more than one table, hitting the limit means the transaction has read the specified number of pages from all the tables it needed to access, not just a single table.
PAGESWEEPACTION on z/OS or the warning message on Open Systems reports the table being accessed at the time the transaction reads the last page; all the preceding pages could be from different tables if, for example:
A ctable had to be built, that is, the table is not bound or this is the first read for this table
PEERS
A connection that this Data Object Broker can establish with another Data Object Broker in the TIBCO Object Service Broker distributed data network. Define all the remote Data Object Brokers with which you want to establish communications. Session requests from undefined Data Object Brokers are rejected.
nodename—The node alias (in huron.dir) of the Data Object Broker being defined. The peer identified can be on any supported system, and must be valid and defined in the Data Object Broker directory file.
outbound—Maximum number of sessions to establish for this connection (minimum 0, maximum 128).
inbound—Maximum number of sessions that are accepted from the peer specified (minimum 0, maximum 128).
prefix—A one to three character prefix used to build user IDs to login to the target Data Object Broker. For example, for prefix TOR, user IDs TOR00001, TOR00002, and so on are generated.
fslevel—The Fail Safe level this connection is capable of supporting. For connections between Data Object Brokers, valid options are: 0, 1, or 2. This argument is optional; if it is omitted, the default 2 is assumed.
PRIVILEGED
One or more user IDs that should have privileges for this Data Object Broker. A privileged user can, for example, view the list of users, but cannot cancel users.
Operating system user ID. Separate each entry with a comma. Up to fifteen values can be specified.
To specify an entry with non-alphanumeric characters, surround the entry with double quotes ("). The backslash (\) may be used to escape a double quote or itself.
NOTE  Case sensitive.
REMOTEDUP
Specifies whether to allow connections with duplicate user IDs when either the existing or the connecting use is for an API process.
If there is likely to be a local user ID that matches the user ID of the request from an API process (for example, if batch jobs share names), specify REMOTEDUP=Y.
If REMOTEDUP is set to Y (allow connection), a user can connect under their user ID even though an API process is running under that same user ID.
Provides a unique identifier for user connections. The CANCELUSER, NOTRACE, and TRACEID operator commands refer to this identifier (COMMNUM). If REMOTEDUP is set to Y, and one of these commands is issued for a user ID with multiple connections, the command returns messages that help you identify the connection you want to process. The messages prompt you to repeat the command with a unique identifier.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information on the CANCELUSER, NOTRACE, and TRACEID commands.
RESAGE
The resident page LRU-2 aging threshold.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information on the LRU‑2 algorithm.
RESIDENTHASHSIZE
The number of entries in the resident page hash table.
Use the default. If the value is set, use a large prime number or a multiple of a large prime number to ensure that the hashing mechanism works effectively.
RESIDENTPAGES
The number of 4 KB pages for data and index buffers in thousands.
z/OS: 2 to 8192 (thousands of pages)
On z/OS, the actual number of pages allocated will be at the next higher 1 megabyte boundary. For example, a value of 2 (2000) will result in an allocation of 2048 pages.
Too low a value causes processing overhead and longer transaction times, as pages could have to be brought into memory to satisfy database access requests. A larger value increases the likelihood of needed pages being in storage, unless accesses are very random.
Non-fixed virtual storage requirements vary proportionally with this parameter. At a minimum, 4096 bytes of virtual storage is allocated for each buffer. This virtual storage is obtained above the 16 MB line.
Comparing Logical Gets to Physical Reads, as provided by the TIBCO Object Service Broker Administration menu’s General Statistics screen, gives an estimate of buffer hit rate.
Low ratios can indicate that performance could be enhanced by the allocation of more RESIDENTPAGES, while extremely high ratios can indicate an over-allocated resource (Virtual Storage).
On z/OS, the above information is also available in the TIBCO Object Service Broker SMF subtype-10 (total) and -26 (interval) records.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating or TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the Administration menu.
ROUTACTION
The route code for A (alert) WTO messages. This is also a Message Switch parameter.
0 to 9 and A to G (for 10-16). You can specify multiple values for the parameter. For example, ROUTACTION=B14 sets ROUTACTION to 1, 4, and 11.
You can view this parameter’s setting online through the TIBCO Object Service Broker Administration menu’s Installation/Configuration screen. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information on how this screen displays the settings.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
Associated Documentation
The MVS Routing and Descriptor Codes IBM manual for code descriptions of WTO messages.
ROUTERROR
The route code for E (error) WTO messages. This is also a Message Switch parameter.
0 to 9 and A to G (for 10-16). You can specify multiple values for the parameter. For example, ROUTERROR=B14 sets ROUTERROR to 1, 4, and 11.
You can view this parameter’s setting online through the TIBCO Object Service Broker Administration menu’s Installation/Configuration screen. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information on how this screen displays the settings.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
ROUTINFORM
The route code for I (information) WTO messages. This is also a Message Switch parameter.
0 to 9 and A to G (for 10-16). You can specify multiple values for the parameter. For example, ROUTINFORM=B14 sets ROUTINFORM to 1, 4, and 11.
You can view this parameter’s setting online through the TIBCO Object Service Broker Administration menu’s Installation/Configuration screen. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information on how this screen displays the settings.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
ROUTLOG
The route code for L (log) WTO messages This is also a Message Switch parameter.
0 to 9 and A to G (for 10-16). You can specify multiple values for the parameter. For example, ROUTLOG=B14 sets ROUTLOG to 1, 4, and 11.
You can view this parameter’s setting online through the TIBCO Object Service Broker Administration menu’s Installation/Configuration screen. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information on how this screen displays the settings.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
ROUTWARN
The route code for W (warning) WTO messages. This is also a Message Switch parameter.
0 to 9 and A to G (for 10-16). You can specify multiple values for the parameter. For example, ROUTWARN=B14 sets ROUTWARN to 1, 4, and 11.
You can view this parameter’s setting online through the TIBCO Object Service Broker Administration menu’s Installation/Configuration screen. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information on how this screen displays the settings.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about the Administration menu.
RSCSCHEDULES
The average number of schedule entries for each TIBCO Object Service Broker resource.
Each line in a schedule entry counts as an entry when estimating a value for RSCSCHEDULES.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about TIBCO Object Service Broker resource management and other administration controls.
SECCLASS
The security class of the request defined by TIBCO Object Service Broker for Data Object Broker access.
Refer to SECREQUESTOR, SECSUBSYSTEM, and TIBCO Object Service Broker Managing Security.
Operator Modifiable
SECREQUESTOR
The internal requestor name as defined by TIBCO Object Service Broker for Data Object Broker access.
Refer to SECCLASS, SECSUBSYSTEM, and TIBCO Object Service Broker Managing Security.
Operator Modifiable
SECSUBSYSTEM
The subsystem as defined by TIBCO Object Service Broker for Data Object Broker access.
Refer to SECCLASS, SECREQUESTOR, and TIBCO Object Service Broker Managing Security.
Operator Modifiable
SECUREADMIN
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).
The SAF interface is used to secure operator functions. While there is no effect on the operator MODIFY command, the functions supported by the S6BTLADM, S6BTLBRM, S6BTLCMD, and S6BSPJEX utilities are affected.
The SAF interface determines whether the user falls into one of four user types (general, privileged, DBA, or operator) based on user-written access rules in an external security package.
Refer to TIBCO Object Service Broker Managing Security for more information about using external security and to TIBCO Object Service Broker for z/OS Utilities for more information about the utilities.
SHAREDMALIGN
The virtual address boundaries where shared memory segments should be aligned.
The parameter can be used to position TIBCO Object Service Broker shared memory within available virtual space.
SHAREDMEMADDR
The virtual memory address where shared memory should begin.
When two or more peer Data Object Brokers coexist on the same system, the SHAREDMEMADDR must be different for each Data Object Broker:
If there are two nodes, adjust the SHAREDMEMADDR value of one of the nodes to a multiple of the value of its SHAREDMALIGN parameter.
If there are more than two nodes, each node must have a different value for SHAREDMEMADDR, and the values must align with the value of SHAREDMALIGN.
As a rule of thumb, you can approximate the value for the next SHAREDMEMADDR by converting the value 2500000 + 5000 * RESIDENTPAGES to hexadecimal and rounding up to the next multiple of SHAREDMALIGN.
A typical value for the next SHAREDMEMADDR that allows for the maximum size of RESIDENTPAGES is 0x5000000 plus the value of the SHAREDMEMADDR for the previous node.
SHAREDMEMPERM
The permission settings for Data Object Broker shared memory.
SIXDATAPAGLIM
The maximum number of data pages a table can have for a secondary index to be built on it online.
SMFRECORD
The numerical identifier that this Data Object Broker uses when generating SMF records.
This number is used to associate the SMF records with this Data Object Broker.
A value of zero (0) disables SMF recording.
If SMF recording is enabled, consider using the same identifier as the Execution Environments running off this Data Object Broker. This gives you a uniform identifier for the TIBCO Object Service Broker system that is based on this Data Object Broker.
If SMFRECORD is set to 0 when the Data Object Broker starts up, it can be set by operator command to a value in the 128 to 255 range. If it is set in the 128 to 255 range at Data Object Broker startup, the operator cannot set it to zero (0). This means SMF recording can be switched on only by an operator and cannot be switched off while the Data Object Broker is running.
TIBCO Object Service Broker for z/OS Monitoring Performance for more information about generating SMF records.
SMF13INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑13 records for Pagestore response time statistics. Records are produced only for segments that had I/O activity during the interval.
Each record contains an entry for every page data set contained in the segment. Segments with a large number of page data sets can have multiple records generated to describe all page data set activity.
A setting of zero (0) disables recording of this SMF record subtype.
Use the default value. During normal system operation a value of 15 should be adequate. When performing system tuning, a smaller value provides greater detail and enables the site to uncover any problem areas more easily.
The smaller the interval value the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
SMF22INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑22 records for lock manager statistics.
Use the default value. During normal system operation a value of 30 should be adequate. When performing system tuning a smaller value provides greater detail and enables the site to uncover any problem areas more easily.
The smaller the interval value the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
SMF23INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑23 records for query TCB statistics.
A setting of zero (0) disables recording of this SMF record subtype.
Use the default value. During normal system operation a value of 30 should be adequate. When performing system tuning a smaller value provides greater detail and enables the site to uncover any problem areas more easily.
The smaller the interval value the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
SMF24INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑24 records for query and commit response time statistics.
A setting of zero (0) disables recording of this SMF record subtype.
Use the default value. During normal system operation a value of 30 should be adequate. When performing system tuning a smaller value provides greater detail and enables the site to uncover any problem areas more easily.
WARNING  SMF24INTERVAL is mutually exclusive with SMF27INTERVAL. Specifying both parameters results in the following Data Object Broker initialization failure:
The smaller the interval value the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
SMF25INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑25 records. These records, used for message length histograms, contain the number of requests received and the message length associated with the requests.
A setting of zero (0) disables recording of this SMF record subtype.
Use the default value. During normal system operation a value of 30 should be adequate. When performing system tuning a smaller value provides greater detail and enables the site to uncover any problem areas more easily.
The smaller the interval value the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
SMF26INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑26 records, which contain general Data Object Broker statistics.
A setting of zero (0) disables recording of this SMF record subtype.
Use the default value. During normal system operation a value of 30 should be adequate. When performing system tuning, a smaller value provides greater detail and enables the site to uncover any problem areas more easily.
The smaller the interval value, the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
SMF27INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑27 records, which contain query and commit extended response time statistics.
A setting of zero (0) disables recording of this SMF record subtype.
If you want more detailed response time reporting than provided by SMF24 records, set SMF24INT to zero and set SMF27INT to 30.
WARNING  SMF27INTERVAL is mutually exclusive with SMF24INTERVAL. Specifying both parameters results in the following Data Object Broker initialization failure:
The smaller the interval value, the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
SMF28INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑28 records, which contain server usage response time statistics.
A setting of zero (0) disables recording of this SMF record subtype.
By default SMF28 records are not produced. To record and report server usage and response times, specify SMF28INT explicitly. Only resources whose Monitor/SMF flag is activated are recorded. Refer to the resource detail screen of the Resource Manager in the S6BTLADM (Administration Menu) utility.
The smaller the interval value, the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about the Administration menu.
SMF47INTERVAL
The interval in minutes for generating TIBCO Object Service Broker SMF subtype‑47 records for user Data Object Broker resource consumption statistics for an interval.
A setting of zero (0) disables recording of this SMF record subtype.
Use the default value. During normal system operation a value of 30 should be adequate. When performing system tuning a smaller value provides greater detail and enables the site to uncover any problem areas more easily.
The smaller the interval value the greater the number of SMF records created. There is a slight overhead in the preparation and recording of each record.
Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about this SMF record type.
SNAPCLASS
The JES output class for SYSOUT snap dumps generated by the Data Object Broker.
Specify a value that keeps a generated snap dump on JES spool long enough for it to be reviewed, if necessary.
Data Object Broker snap dumps are generally less than 500 lines and are taken only when a diagnostic dump is requested (from option Z on the Administration menu). This parameter takes effect only if SNAPOVERRIDE=N.
SNAPDSPREFIX
The high-level qualifiers for Data Object Broker snap dumps taken to a data set on DASD.
Data set qualifiers valid in z/OS. You can specify multiple levels and the total length including periods cannot exceed 17 characters. The first qualifier must be a valid catalog alias at your site.
Set by $HLQNONV$ in the OSEMOD ISPF edit CLIST used during Data Object Broker installation.
SNAPHOLD
Specifies whether a SYSOUT Data Object Broker snap dump should be held on the JES spool.
Determine how your site wants to handle Data Object Broker snap dumps. If snap dumps are held, they are available on JES spool for viewing. If they are not to be held, specify an output class and destination. Also consider if they should print automatically.
This determines the JES output queue (HELD or READY) where the snap dump data sets appear. Snap dump data sets must be manually deleted when they are no longer required.
SNAPOVERRIDE
Specifies whether the Data Object Broker snap dumps are to be written to individual data sets on DASD; if not, they go to JES SYSOUT.
Use whatever is appropriate for your site. You must ensure that there is sufficient DASD or JES spool space to hold all snap dumps taken during this Data Object Broker’s operation.
TIBCO Object Service Broker does not delete snap dump data sets. You must determine their disposition and manually delete them if you no longer need them.
Snap dumps are typically less than 500 lines. If the snap dumps are written to DASD, they go to the volume named by SNAPVOLSER, or in the DASD pool named by SNAPUNIT, with the name: SNAPDSPREFIX.#YYYYDDD.#HHMMSS.#TH.
SNAPQUERY
Specifies whether the Data Object Broker generates a transaction dump for failed query requests.
The Data Object Broker takes a transaction dump only when it fails a query request. This is an exceptional condition and should not occur frequently. The vast majority of Data Object Broker requests are queries.
SNAPREMOTE
The JES output destination for JES SYSOUT snap dumps generated by the Data Object Broker.
Refer to $JESPRT$ in OSEMOD ISPF edit CLIST for the default.
SYSOUT snap dumps generated by the Data Object Broker are sent to the destination specified. SNAPREMOTE is in effect only if SNAPOVERRIDE=N.
SNAPSUPPRESS
Specifies whether Data Object Broker transaction dumps are to be suppressed.
Use the default. A transaction dump often provides the necessary information to determine why a Data Object Broker request failed. It should be kept until technical support staff no longer need it.
A transaction dump is provided using the SVC dump facility, therefore it has the overhead and constraints of the SVC dump.
SNAPUNIT
The generic name of a DASD pool from which to allocate DASD snap dump data sets.
Refer to $INSTUNT$ OSEMOD ISPF edit CLIST used during Data Object Broker installation for the default.
Specify a value that is valid for your site and for the DASD volume where you want the Data Object Broker to allocate snap dump data sets.
SNAPUNIT is in effect only when SNAPOVERRIDE=Y. Refer to SNAPOVERRIDE for DASD space considerations.
SNAPVOLSER
The volume serial of the DASD where the Data Object Broker can allocate snap dump data sets.
Refer to $WORKVOL$ OSEMOD ISPF edit CLIST used during Data Object Broker installation.
Specify a volume serial with adequate space for the Data Object Broker to allocate snap dump data sets. Snap dumps are typically less than 500 lines. For current device types (3390, for example), several tracks are required.
The Data Object Broker security ID must have access to the specified volume to create and catalog data sets. If SNAPUNIT is specified, specify a volume serial that belongs to the DASD pool. SNAPVOLSER is in effect only if SNAPOVERRIDE=Y.
Refer to SNAPOVERRIDE for DASD space considerations.
SPINDSNAME
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.
Set by $HLQNONV$.$INSTVER$.JCL Refer to the OSEMOD ISPF edit CLIST used during Data Object Broker installation.
Applicable only if SPINOPTION=JOB. The Data Object Broker initialization fails if this data set does not exist or if member names set by SPINMEMBER do not exist in this data set.
SPININTERVAL
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.
Use this feature only if you need the extra journal spins during periods of low database activity. Keep in mind that you can schedule journal spins on demand via a TIBCO Object Service Broker operator command.
This feature causes extra journal spins, that is, in addition to those normally scheduled when journal data sets fill up.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about operator commands.
SPINMEMBER
The prefix for the member names that contain JCL for journal spins.
If SPINOPTION=JOB, this is used as a member name prefix for spin jobs. You need one member corresponding to each journal. A full member name consists of this prefix followed by a number representing the journal number.
For example, if SPINMEMBER=SPIN0, the Data Object Broker uses member SPIN01 to offload journal 1, SPIN037 to off load journal 37, and so on.
SPINOPTION=JOB: 1 to 7 characters; the prefix plus the journal number must be no more than 8 characters.
If SPINOPTION=STC, member names set by SPINMEMBER must be in the system PROCLIB; otherwise, the START command issued by the Data Object Broker fails.
SPINMEMBER is not operator modifiable. It is set at start up time only.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about operator commands.
SPINOPTION
Specifies whether the journal spin JCL is run as a started task or batch job.
If SPINOPTION=JOB the Data Object Broker, when it starts up, reads and stores in memory the spin JCL from the data set and members specified in the SPINDSNAME and SPINMEMBER parameters. It submits them as batch jobs for dumping the journal’s data and resetting it.
If SPINOPTION=STC the Data Object Broker issues a START command using the catalogued procedure name defined by SPINMEMBER. The system searches for the JCL procedure in the system PROCLIB concatenation that is in effect for the Data Object Broker. Your spin JCL modifications take effect the next time the Data Object Broker issues a START command.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information about operator commands.
SPINSHELL
The shell to use when executing a spin script.
The Data Object Broker will abend on startup if a valid path to a shell that is both readable and executable is not specified.
Refer to TIBCO Object Service Broker for Open Systems Managing Backup and Recovery for more information on journal processing.
SRBMODE
Controls the dispatching of Data Object Broker Query requests on z/OS.
Z — Use SRB mode dispatching and enable the dispatching of SRBs on any available zIPP processor.
N — Object Service Broker dispatches query requests to one of the query tasks that traditionally run in TCB mode. This task might involve queuing the request for a query task to become available.
Y or Z — Object Service Broker dispatches query requests in SRB mode. Since only one SRB applies to each valid thread, no queuing occurs for a task to become available in this mode.
Each valid thread consumes approximately 8 Kbytes of Extended System Queue Area (ESQA). The number of threads is the value of MAXTHREADS plus four. To take advantage of SRB scheduling, you might need to revise the z/OS system parameters.
SSTRACE
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.
Use Y only in consultation with the TIBCO Support to collect trace information for diagnosing problems.
Use of GTF trace can have some effect on overall system performance. GTF trace must be active to record the data produced.
STDERRTRACE
Specifies whether to include messages to stderr in the Data Object Broker log file.
STDOUTTRACE
Specifies whether to include messages to stdout in the Data Object Broker log file.
SVCTRACE
Specifies whether to write a message to the Data Object Broker for each supervisor call to the Data Object Broker from TDS.
SWAPPABLE
Specifies whether the Data Object Broker is marked as swappable after initialization.
SYNCTRACE
Specifies whether to write a message to the Data Object Broker for each commit.
SYSADMIN
The TIBCO Object Service Broker administrator user ID for this Data Object Broker.
An operating system user ID. Only one system user ID can be the TIBCO Object Service Broker system administrator.
To specify an entry with non-alphanumeric characters, surround the entry with double quotes ("). The backslash (\) may be used to escape a double quote or itself.
NOTE  Case sensitive.
TIMEOUTABEND
The time allowed for the Data Object Broker to abend.
If the abend is not completed in the specified time, all Data Object Broker processes are immediately killed.
TIMEOUTSTART
The time allowed for the Data Object Broker to complete startup processing.
If the Data Object Broker is not successful in the specified time, the Data Object Broker abends and all processes are killed.
TIMEOUTSTOP
The time allowed for the Data Object Broker to perform a graceful shutdown.
If the Data Object Broker is not successful in the specified time, the Data Object Broker abends and all processes are killed.
TIMESTAMP
The interval in minutes for producing a WTO message reporting current date and time.
TRXREADLIMIT
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.
Requests that cause more physical reads than the specified value are aborted. This prevents transactions from flooding the resident page pool with pages with a low reference frequency, allowing pages referenced more frequently to be read.
Some operations process many buffers, without requiring I/O services (for example, when an entire table is already in the resident page pool). This can cause the Data Object Broker to be slow in processing new requests since the required data is always available. These transactions are not aborted, but they are periodically interrupted so that other service requests can be processed.
USEREXIT
Specifies whether user exit processing is required for this Data Object Broker. If USEREXIT is set to N and a USRX0000 routine is detected at startup, an error message appears and the Data Object Broker terminates. If USEREXIT is set to Y and a USRX0000 routine is not detected at startup, an error message appears and the Data Object Broker terminates.
Operator Modifiable
UNICODEDIR
The path to the directory that contains the Unicode configuration files.
Must be the same as the UNICODEDIR Execution Environment parameter.
None, TIBCO Object Service Broker uses its default information for Unicode processing.
The TIBCO Object Service Broker initialization code uses the files in this directory to configure Unicode processing.
In the absence of any of the files in the directory, TIBCO Object Service Broker uses the default information for that portion of Unicode processing: translation, casing, or collation.
Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about Unicode configuration.
USERSHUTDOWN
Specifies whether a user is allowed to use the S6BTLADM (Administration menu) utility to shut down the Data Object Broker.
If USERSHUTDOWN is set to Y (allow shut down), a user can use the S6BTLADM (Administration menu) utility to display the Administration menu, and then use the operator functions to shut down the Data Object Broker.
Refer to TIBCO Object Service Broker for z/OS Installing and Operating for more information on monitoring and controlling the TIBCO Object Service Broker environment using the Administration menu.
WORKINGSET
The maximum number of Pagestore pages that can be updated or physically locked (held) in a single Data Object Broker commit.
z/OS: Specify 999 to set this limit to the value of the CHPAGELIMIT parameter or 4096, whichever is the smaller value.
Open Systems: If 999 is specified, the limit is set to 15% of the checkpoint size or 50% of the redolog size, whichever is larger.
WTOCLASS
The output class of a dynamically allocated JES SYSOUT file where the Data Object Broker copies WTO (write to operator) messages.
Use of this parameter enables the duplication of WTO messages. If it is not specified, WTO messages are not duplicated.
If WTO messages are suppressed by WTOSYSLOG, this parameter should be specified to collect all WTO messages for problem diagnosis.
Associated Documentation
The MVS Routing and Descriptor Codes IBM manual for code descriptions of WTO messages.
WTOCONSOLE
The minimum level of Data Object Broker WTO messages eligible for display on z/OS operator consoles. Message levels in descending order of importance are:
WTOCONSOLE=N requests that messages not appear on the console during Data Object Broker execution. Messages of lower importance are issued in SYSLOG, except during startup, shut down, or operator command responses.
WTODELETE
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:
The value N specifies that messages not be suppressed.
Specifying I deletes both I-level and L‑level messages, except during startup, shut down, or operator command responses.
WTOHOLD
Specifies whether the Data Object Broker’s WTO SYSOUT log data set is to be held in the JES output queue.
This parameter is in effect only if WTOCLASS is specified.
If Y is specified, the JES SYSOUT data sets must be deleted manually from the output queue.
If N is specified, these data sets are sent to their destination after the time interval set by WTOINTERVAL.
WTOINTERVAL
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.
Specifying 1440 produces a spun JES SYSOUT log data set daily at midnight. After the log is spun, you can print or delete it. The smaller the interval, the more frequently a JES SYSOUT log data set is spun, each containing a smaller number of WTO messages.
WTOPID
Specifies whether to include the process ID (PID) in WTO messages.
WTOREMOTE
The output destination for this Data Object Broker’s JES WTO SYSOUT log data set.
This parameter is in effect only if WTOCLASS is specified.
WTOSOURCE
Specifies whether to include source code origin in the ERRNOTRACE messages.
WTOSUFFIX
The suffix that identifies messages issued from a specific Data Object Broker and that is appended to all Data Object Broker messages, for example, S6BDB090I-XXXX. This is also a Message Switch parameter.
When several Data Object Brokers are active at the same time, this feature is useful for quickly determining which Data Object Broker issued a message.
WTOSYSLOG
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.
Message levels in descending order of importance are:
A parameter value of N specifies that all messages are to be written to the z/OS SYSLOG.
WTOTAG
Specifies whether to include the user ID/transaction tag in WTO messages.
WTOTIME
Specifies whether to include the timestamp in WTO messages.
XCFGROUP
The XCF group that the Data Object Broker is to join. This is a Message Switch parameter.
Any name that is unique to the set DOBs and message switches that comprise an OSB image.
See TIBCO Object Service Broker for z/OS Installing and Operating for details on how to use multiple Data Object Brokers.
XCFMEMBER
The member name of the Data Object Broker instance in the XCF group. This is a Message Switch parameter.
See TIBCO Object Service Broker for z/OS Installing and Operating for details on how to use multiple Data Object Brokers.
XCFMODE
Determines if a Data Object Broker is a primary or secondary Data Object Broker at startup. This is a Message Switch parameter.
AUTOMATIC — This DOB becomes the primary Data Object Broker if no primary Data Object Broker already exists in the XCF Group.
SECONDARY — This Data Object Broker initializes as a secondary Data Object Broker.
See TIBCO Object Service Broker for z/OS Installing and Operating for details on how to use multiple Data Object Brokers.
XCFSTRUCTURE
The name of Coupling Facility structure to be used by this Data Object Broker group. This is a Message Switch parameter.
See TIBCO Object Service Broker for z/OS Installing and Operating for details on how to use multiple Data Object Brokers.
XCFWAITTIME
The number of seconds an MSW address space waits for the primary Data Object Broker to become available. This is a Message Switch parameter.
See TIBCO Object Service Broker for z/OS Installing and Operating for details on how to use multiple Data Object Brokers.
XTABLESIZE
The size, in kilobytes, of the buffer pool for XTABLEs, the internal representations of TIBCO Object Service Broker report and screen definitions.
Use the default initially, and adjust if necessary. The default value supports approximately 150 fields.
The ESTIMATETBLDFN tool provides an approximation of XTABLE size required for screen and report definitions.
If the XTABLESIZE is too small to accommodate the definition, the transaction requesting the definition fails.
The Data Object Broker allocates the XTABLE pool in blocks, the size of which is determined by this parameter. This XTABLE pool is above the 16 MB line.
Refer to TIBCO Object Service Broker Shareable Tools for information about the ESTIMATETBLDFN tool.

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