Redpaper - IBM Redbooks

solution for setting up SupportPac IP13 for running in a sysplex is to follow the
steps below:
1. Create a new RACF group that will be the schema name for the unique
SupportPac IP13 DB2 table.
2. Connect the user IDs under which the broker started tasks run to the
previously created RACF group.
3. Create the SupportPac IP13 SHAREPRICES table using job JBDB2DEFS,
inserting the new RACF group name as the schema.
4. SET CURRENTSQLID in the ESQL of the mesageflow. See DB2U message
flow configuration below for details.
OEMPUTX batch job configuration
There are several parameters that can be passed to OEMPUTX in order to
cause different behavior of the application. The parameters we chose for our
testing included:
-n25000 Total number of messages to put, in this case 25000.
-m4 Causes the program to run for four minutes. In the test
environment, no single broker was capable of processing 25000
messages within four minutes, so these first two parameters
provided a steady-state message flow rate.
-gm Causes OEMPUTX to use same MQMD.MsgId for all MQPUTs in
the loop, and MQGET replies by this MsgId. With this option,
there is no Message Broker affinity.
-w45 Sets the MQGET MQMD.WaitInterval to wait_time seconds.
-c Commit every msgs_in_loop messages. msgs-in-loop was not
set and the default is one message per batch.
We also used non-persistent messages.
DB2U message flow configuration
Recall that in each broker’s dsnaoini file, the CURRENTSQLID is set to the user
ID of that broker. This configuration would normally prevent brokers from
accessing DB2 tables outside of their schema. To circumvent this behavior:
► Add the following line of ESQL to the DB2U message flow to set the
CURRENTSQLID to the RACF group name created for the SupportPac IP13
SHAREPRICES table (see Chapter 3, “Topology and system setup” on
page 21). This value has to have single quotes surrounding it for z/OS DB2 to
process it correctly, as shown in the example below:
PASSTHRU('SET CURRENT SQLID= ''SYSDSP''');
Chapter 4. Failover scenarios 35