CREATE PROCEDURE CopyMessageToDatabase() BEGIN
		DECLARE msg REFERENCE TO InputRoot.XMLNSC.message;
		DECLARE size INTEGER;
		DECLARE x INTEGER;

		DECLARE SQLState1 CHARACTER;
		DECLARE SQLErrorText1 CHARACTER;
		DECLARE SQLCode1 INTEGER;
		DECLARE SQLNativeError1 INTEGER;

		SET OutputRoot = InputRoot;
		SET size = CARDINALITY(InputRoot.XMLNSC.message."person"[]);

		SET x =  1 ;
		WHILE x <= size
			DO
			INSERT INTO Database.PEOPLE.PEOPLE(ID, NAME, MIDDLE_NAME, FAMILY_NAME, PHONE_NUMBER, ADDRESS)
			VALUES(
			msg.person[x].id,
			msg.person[x].name,
			msg.person[x].middle_name,
			msg.person[x].family_name,
			msg.person[x].phone_number,
			msg.person[x].address
			);

			SET SQLCode1 = SQLCODE;
			SET SQLState1 = SQLSTATE;
			SET SQLNativeError1 = SQLNATIVEERROR;
			SET SQLErrorText1 = SQLERRORTEXT;

			IF - 803  = SQLNativeError1 THEN -- I like DB2 error codes
				-- Update existing row in the table
				UPDATE Database.PEOPLE.PEOPLE AS T
				SET
				NAME = msg.person[x].name,
				MIDDLE_NAME = msg.person[x].middle_name,
				FAMILY_NAME = msg.person[x].family_name,
				PHONE_NUMBER = msg.person[x].phone_number,
				ADDRESS = msg.person[x].address
				WHERE
				T.ID = msg.person[x].id
				;
			END IF;

			SET SQLCode1 = SQLCODE;
			SET SQLState1 = SQLSTATE;
			SET SQLNativeError1 = SQLNATIVEERROR;
			SET SQLErrorText1 = SQLERRORTEXT;

			IF  0  <> SQLNativeError1 THEN
				SET SQLState1 = SQLSTATE;
				SET SQLErrorText1 = SQLERRORTEXT;
				SET SQLNativeError1 = SQLNATIVEERROR;
				LOG EVENT MESSAGE  2950  VALUES('The SQL State' , SQLState1 , SQLCode1 , SQLNativeError1 , SQLErrorText1);
				THROW USER EXCEPTION MESSAGE  2950  VALUES('The SQL State' , SQLState1 , SQLCode1 , SQLNativeError1 , SQLErrorText1);
			END IF;

			SET x = x +  1 ;
		END WHILE;
	END;

If the broker is running on a distributed system, you can configure the databases and the connections to be coordinated with other resource activity.  Global coordination on distributed systems is provided by WebSphere® MQ,  and can include interactions with local or remote databases, including remote databases that are defined on z/OS systems. If you establish a JDBC type 4 connection to a database from a broker that is running on z/OS, coordination is not provided. For information about setting up connections and coordination, see Enabling JDBC connections to the databases.