Working with two DB2 subsystems on the Mainframe
DESCRIPTION
Working with two different DB2 subsystems on the mainframe
SOLUTION
You must have two datasources, one for e.g DB2T should be used when working with the DB2T subsystem and the DB2P should be used when working with the DB2S subsystem:
Add two workspaces as follows:
- <DATASOURCE type="DB2mfcli" transactionType="1PC" owner="NAV" name="DB2T">
- <DATASOURCE type="DB2mfcli" transactionType="1PC" owner="NAV" name="DB2P">
On the PC side you will have two DataSources DB2T and DB2P that point to the ones defined on the mainframe:
- A workpspace called TEST that is using the ATTSRVR server which points to the odbcinit member (pointing to DB2T subsystem) :
<WORKSPACE name="TEST" startupScript="ATTSRVR.XY" description="Attunity Connect Server" etc... serverMode="reusable">- a workspace called PROD that is using the ATPSRVR server which points to the odbcinip member ( pointing to DB2S subsystem):
<WORKSPACE name="PROD" startupScript="ATPSRVR.XY" description="Attunity Connect Server" serverMode="reusable" etc..>
And two remote machines where each one points to the relevant workspace:
- <DATASOURCE type="REMOTE" name="DB2T" connect="MVSTEST">
- <DATASOURCE type="REMOTE" name="DB2P" connect="MVSPROD">
odbcinip and odbcinit - both members need to be copied to HLQ.userlib (HLQ: high level qualifier where Attunity Connect is being installed)
- <REMOTEMACHINE name="MVSTEST" workspace="TEST" port="2551" address="IP_address">
- <REMOTEMACHINE name="MVSPROD" workspace="PROD" port="2551" address="IP_address">
ATTSRVR modifed to point to odbcinit 000021 //DSNAOINI DD DSN=HLQ.USERLIB(ODBCINIT),DISP=SHR
- odbcinit ----includes the definition of the DB2T subsystem MVSDEFAULTSSID=DB2T ; Example SUBSYSTEM odbcini for DSN1 subsystem DB2T ;MVSATTACHTYPE=CAF
- odbcinip---- includes the definition of the DB2S subsystem MVSDEFAULTSSID=DB2S ; Example SUBSYSTEM odbcini for DSN1 subsystem DB2S¨ ;MVSATTACHTYPE=CAF
ATPSRVR - modified to point to odbcinip 000021 //DSNAOINI DD DSN=HLQ.USERLIB(ODBCINIP),DISP=SHR
BOTH should be copied to the user PROCLIB and should be given the right permission in your security manager (e.g RACF) as described in the doc (post-installation requirements)


LinkBack URL
About LinkBacks




