You can create and configure ESQL in message flows to access user databases.
Before you start:
To complete this task, you must have completed the following tasks:
You can use a number of ESQL statements and functions to access databases:
You can access user databases from Compute, Database, and Filter nodes. There is no difference between the database access capabilities of these nodes, but the following restrictions apply.
To access databases, you must ensure that suitable ODBC data sources have been created on the system on which the broker is running. If you have used the mqsisetdbparms command to set a user ID and password for a particular database, the broker uses these values to connect to the database. If you have not set values for a particular database, the broker uses the default database user ID and password that you supplied on the mqsicreatebroker command, or the user ID and password details that you specified if you have modfied them using the mqsichangebroker command.
On z/OS systems, the broker uses the broker started-task ID to connect to the database. You must also ensure that the database user IDs have sufficient privileges to perform the operations your flow requires. If they do not have the required privileges then errors will occur at runtime.
For a description of database transactional issues, see The Transactional model.
You are recommended to set the "throw exception on database error" and "treat warnings as errors" attributes to 'yes' and the "transaction" attribute to "automatic" as this gives the maximum flexibility. You then use the COMMIT and ROLLBACK statements for transaction control and handlers for dealing with errors.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac07000_ |