Configuring a multisite update without a transaction processor (TP) monitor with an SNA protocol, and or TCP/IP protocol

Use the Configure Multisite Update SmartGuide to configure a multisite update when you are not using a transaction processor (TP) monitor and when you are using an SNA protocol and or TCP/IP protocol.

Fields and controls

Authorities and privileges

To configure multisite update without a transaction processor (TP) monitor with an SNA protocol, and or TCP/IP protocol:

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 SNA check box and or TCP/IP check box. This is the protocol that will be used to connect to host or AS/400 systems that will be involved in the multisite update.
   • 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 Sync-Point Manager page.

5. 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.

6. Click Done to configure the instance.

Related information

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