For an overview of broker properties, see Broker properties.
The following table shows the broker, flow, and node properties that are accessible from ESQL. The table's fourth column indicates whether the properties are also accessible from Java nodes.
If a property is listed as being accessible from Java nodes (fourth column), it is accessible from Java nodes only, not from Java routines called as ESQL functions or procedures.
Property type | Property name | Return type | From Java nodes? | What is it? |
---|---|---|---|---|
General broker properties 4 | BrokerDataSourceUserId | Character | Yes. 1 | The data source user ID used by the broker. |
BrokerDataSource | Character | No. | The ODBC Data Source Name (DSN) of the database that contains the broker's tables. | |
BrokerName | Character | Yes.2 | The name of the broker. | |
BrokerUserId | Character | No | The user ID that the broker uses to access its database tables. | |
BrokerVersion | Character | No | The 4-character version number of the broker (see BrokerVersion below). | |
ExecutionGroupLabel | Character | Yes.3 | The label of the Execution Group (a human-readable name). | |
ExecutionGroupName | Character | No | The name of the Execution Group (often a UUID identifier). | |
Family | Character | No | The generic name of the software platform that the broker is running on ('WINDOWS', 'UNIX', or 'ZOS'). | |
ProcessId | Integer | No | The process identifier (PID) of the DataFlowEngine. | |
QueueManagerName | Character | Yes.5 | The name of the MQ queue manager to which the broker is connected. | |
WorkPath | Character | No. | The (optional) directory in which working files for this broker are stored. | |
Flow properties | AdditionalInstances | Integer | No | The number of additional threads that the broker can use to service the message flow. |
CommitCount | Integer | No | How many input messages are processed by the message flow before a syncpoint is taken. | |
CommitInterval | Integer | No | The time interval at which a commit is taken when the CommitCount property is greater than 1 (that is, where the message flow is batching messages), but the number of messages processed has not reached the value of the CommitCount property. | |
CoordinatedTransaction | Boolean | Yes.6 | Whether or not the message flow is processed as a global transaction, coordinated by WebSphere MQ. | |
MessageFlowLabel | Character | Yes.7 | The name of the flow. | |
Node properties | DataSource | Character | No | The ODBC Data Source Name (DSN) of the database in which the user tables are created. |
DataSourceUserId | Character | No | The user ID that the broker uses to access the database user tables. | |
MessageOptions | Integer (64-bit) | No | The bitstream and validation options in force. | |
NodeLabel | Character | Yes.8 | The name of the node. | |
NodeType | Character | No | The type of node (Compute, Filter, or Database). | |
ThrowExceptionOnDatabaseError | Boolean | No | Whether the broker generates an exception when a database error is detected. | |
Transaction | Character | No | The type of transaction (Automatic or commit) used to access a database from this node. | |
TreatWarningsAsErrors | Boolean | No | Whether database warning messages are treated as errors and cause the output message to be propagated to the failure terminal. |
#### Start Trace Input Message Time: ${CURRENT_TIMESTAMP} Broker: ${BrokerName} Version: ${BrokerVersion} Platform: ${Family} ProcessID: ${ProcessId} BrokerUserId: ${BrokerUserId} ExecutionGroupLabel: ${ExecutionGroupLabel} Transaction: ${Transaction} Root Tree: ${Root} #### End Trace Input Message
A fix pack is cumulative: that is, it contains all the fixes shipped in previous maintenance to the release, including previous fix packs. It can be applied on top of any previously-shipped maintenance to bring the system up to the current fix pack level.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ak04897_ |