Hi!
Problems, problems problems :-(
I´m trying to update a table in DB2 (z/OS) version 8 using a 3:rd
party SQL tool(AQT). About 300 rows are affected by the update.
There is an updatetrigger on the table that uses
DB2MQ.MQSEND(fu nction) to put a message (for each updated row) on a
remote queue that exists on a z/OS MQ queue manager.
Syncpoint is enabled for the MQ functions in DB2.
The remote queue points to a local queue on a Windows MQ queue manger.
begin transaction
update table
trigger(DB2.MQS END(queue, service))
remote queue -local queue on windows
commit transaction.
The update seems to go well but when it comes to commit it takes a
awfaul long time. With just 70 rows the commit statement takes about 5
minutes to finish. The more rows affected the longer it takes to
commit.
I can see that messages are building up in the transmission queue
waiting for the commit (as I understand it). When it eventually does
the messages are immediately sent over to the Windows Queue manager.
Anyone with similar experiences and a reasonably explanation or
suggestion?
Cheers
Thomas B
Problems, problems problems :-(
I´m trying to update a table in DB2 (z/OS) version 8 using a 3:rd
party SQL tool(AQT). About 300 rows are affected by the update.
There is an updatetrigger on the table that uses
DB2MQ.MQSEND(fu nction) to put a message (for each updated row) on a
remote queue that exists on a z/OS MQ queue manager.
Syncpoint is enabled for the MQ functions in DB2.
The remote queue points to a local queue on a Windows MQ queue manger.
begin transaction
update table
trigger(DB2.MQS END(queue, service))
remote queue -local queue on windows
commit transaction.
The update seems to go well but when it comes to commit it takes a
awfaul long time. With just 70 rows the commit statement takes about 5
minutes to finish. The more rows affected the longer it takes to
commit.
I can see that messages are building up in the transmission queue
waiting for the commit (as I understand it). When it eventually does
the messages are immediately sent over to the Windows Queue manager.
Anyone with similar experiences and a reasonably explanation or
suggestion?
Cheers
Thomas B