When migrating from DB2 or DDCS Version 2 to the Version 5 SPM, first ensure that there are no indoubt transactions. You can verify this by entering the following command in the command line processor:
list drda indoubt transactions
Note that, before issuing LIST DRDA INDOUBT TRANSACTIONS, the application must be connected to the Syncpoint Manager (SPM) instance - use the SPM_NAME database manager configuration parameter as the dbalias on the CONNECT statement. If any transactions are listed, ensure that automatic resolution occurs, or - if automatic resolution is not possible - you can force the resolution by issuing the following command:
list drda indoubt transactions with prompting
If the Encina PPC Gateway was defined on a node different from the node on which the SPM will be defined, then the user must make sure that the required SNA definitions are available on the SPM node.
The following are special considerations when migrating from a DB2 for AIX V2.1.0 Encina Peer-to-Peer Communications (PPC) Gateway environment.
In this case, follow all the steps defined above in "Setting up Communications for the SPM", including those for the TP Name and CPI-C Side Information profiles, which must be redefined.
Otherwise, if you will use the same non-CP LU name for SPM as in your DB2 for AIX V2.1.0 configuration, the existing CPI-C Side Information profile can be re-used without change, but you will have to define the TPN profiles that you require.
For details, refer to the CICS for Open Systems Administration Guide.
The Encina PPC Gateway and the DB2 SPM cannot share the same LUs. If the Encina PPC Gateway is still required you must configure either the DB2 SPM or the PPC Gateway to use a different LU.