Configuring multisite update without a transaction processor (TP) monitor, with TCP/IP protocol, and using non-universal databases (except OS/390 V5)

Use the Configure Multisite Update SmartGuide to configure multisite update when you are not using a transaction processor (TP) monitor and when you are using a TCP/IP protocol and non-universal databases (except OS/390 version 5).

Fields and controls

Authorities and privileges

To configure a multisite update without a transaction processor (TP) monitor, with a TCP/IP protocol, and using non-universal databases (except OS/390 version 5):

1. Open the Configure Multisite Update SmartGuide.

2. On the TP Monitor page:
   • Select the Do not use a TP monitor radio button.
   • Click Next to open the Protocol page.

3. On the Protocol page:
   • Select the TCP/IP check box.
   • Click Next to continue to the TM Database page.

4. On the TM Database page:
   • Select one of two options. The first option makes a TM database the initial database to which your application connects. The second option uses a specific cataloged database:
     • Use the first database your application connects to (1ST_CONN)
     • Use a cataloged database
   • Click Next to continue to the Server Environment page.

5. On the Server Environment page:
   • Select the Other check box for Specify the types of database servers involved in the multisite update, if the multisite update refers to other types of database servers. A sync-point manager is required if the Other check box is selected.
   • Select the No radio button for Is TCP/IP the only protocol used between servers involved in the multisite update? If you are not sure, select No, if TCP/IP is not the exclusive protocol used between servers involved in the multisite update. Select the No radio button if you are uncertain of the protocols shared between database servers. A sync-point manager is required, if the No radio button is selected.
   • Click Next to continue to the Sync-Point Manager page.

6. On the Sync-Point Manager page:
   • The following three fields are pre-filled with your database manager values. These fields are pre-filled by default, but you may adjust them:
     • Sync-point manager name (SPM_NAME)
     • Log file size (SPM_LOG_FILE_SZ)
     • Maximum number of resync agents(SPM_MAX_RESYNC)
   • Optional: Type a path for the Log path (SPM_LOG_PATH) field.

7. Click Done to configure the instance.

Related information

• Configure Multisite Update SmartGuide -- Overview
• Testing multisite update