Before you start:
Create the broker and the database.
- Obtain the following DB2® values for the DB2 subsystem that you want to connect
your broker to. Use these values to customize the BIPEDIT, BIPDSNAO,
and BIPBRKP files.
| JCL variable |
Description |
Example value |
|---|
| ++DB2CONVERSION++ |
The DB2 converter |
SINGLE |
| ++DB2SUBSYSTEM++ |
The DB2 subsystem
ID which the component connects |
DFK4 |
| ++DB2LOCATION++ |
The DB2 location
value of the DB2 subsystem to
which the component connects |
DSN910PK |
| ++DB2CURRENTSQLID++ |
The default DB2 user
ID for connecting |
MQP1BRK |
| ++DB2DSNACLIPLAN++ |
The DB2 plan
name. |
DSNACLI |
| ++DB2HLQ++ |
The DB2 high-level-qualifier |
SYS2.DB2.V910 |
| ++DB2RUNLIB++ |
The DB2 run
library value |
DSN910PK.RUNLIB.LOAD |
- Copy the supplied sample BIPDSNAO file
into the component data set, and customize its content based on the
values obtained in step 1. The stanza for your database
will look like the following content:
[COMMON]
APPLTRACE=0
APPLTRACEfilename="DD:APPLTRC"
TRACETIMESTAMP=3
CONNECTTYPE=2
DIAGTRACE=0
DIAGTRACE_NO_WRAP=0
MAXCONN=0
MULTICONTEXT=0
MVSDEFAULTSSID=DFK4
; SUBSYSTEM
[DFK4]
MVSATTACHTYPE=RRSAF
PLANNAME=DSNACLI
; DATASOURCES
[DSN910PK]
CURRENTSQLID=MQP1BRK
- Update the broker profile BIPBPROF in
the component data set.
- Check that the environment variable DSNAOINI points
to your copy of the BIPDSNAO file in the component
data set. By default, it is set to the correct value; update this
variable if you use a different name.
- Check that the environment variable MQSI_DB2_CONVERSION is
set correctly.
- Submit BIPGEN to re-create the
broker ENVFILE and any integration server specific profiles.
- Update the EGENV and EGNOENV steps
in the broker started task JCL to include the following DB2 data sets:
//STEPLIB DD DISP=SHR,DSN=&DB2HLQ..SDSNEXIT
// DD DISP=SHR,DSN=&DB2HLQ..SDSNLOAD
// DD DISP=SHR,DSN=&DB2HLQ..SDSNLOD2
// DD DISP=SHR,DSN=++DB2RUNLIB++
Check
that the PROC variable DB2HLQ='++DB2HLQ++' is
not commented out.
- Start the broker by using the start (/S) command.
Next: You can set up your databases
to participate in coordinated transactions by using the Resource Recovery
Service (RRS). For more information, see
Resource Recovery Service planning on z/OS.
Last updated Friday, 21 July 2017