IBM Books

Replication Guide and Reference


Planning mobile replication

This section explains how to get your laptop up and running for mobile replication. This section discusses:

Software and hardware requirements

In addition to the nonmobile IBM Replication hardware and software, mobile replication also requires communication hardware and software to transfer data. This section lists probable hardware and software needs. This list is not exhaustive, because it would be impossible to list all the hardware and software requirements for the unlimited number of possible configurations.

Communication program requirements

Your database administrator can develop a program to dial and disconnect your communications lines for you. Although mobile replication does not provide any connecting or disconnecting communication programs, it does provide a means to automate your user-defined connection/disconnection communication programs via two environment variables: ASNDIAL and ASNHANGUP.

ASNDIAL
Specifies the dial-up exit routine. When specified, the mobile replication component calls the dial-up program every time a physical connection is needed. Mobile replication does not pass any parameters and does not expect any return code from this exit routine.

ASNHANGUP
Specifies the disconnect exit routine. When specified, the mobile replication component calls the disconnect program as soon as the line is no longer needed. The only exception is when the disconnect program is disabled by the hold-line (-H) ASNCOPY invocation option. You can disable the automatic disconnect function for a variety of reasons. For example, you might want to issue DB2 commands against the source server after ASNCOPY is finished, or you might need a repeated copy to successfully copy a large answer set. Mobile replication does not pass any parameters and does not expect any return code from this exit routine.

Specifying ASNDIAL and ASNHANGUP environment variables in OS/2

The following section describes how to specify ASNDIAL and ASNHANGUP environment variables in OS/2.

To set the ASNDIAL and ASNHANGUP environment variables:

  1. Declare the environment variables in your config.sys file. For example:

    Where:

    mydial.exe
    The program that you use to connect your mobile client to the source server.

    myhangup.exe
    The program that you use to disconnect your mobile client from the source server.

  2. Reboot your system to have these settings take effect.

Specifying ASNDIAL and ASNHANGUP environment variables in Windows NT

The following section describes how to specify ASNDIAL and ASNHANGUP environment variables in Windows NT.

To set the ASNDIAL and ASNHANGUP environment variables:

  1. From the Control Panel window, double-click the System icon. The System Properties notebook opens.

  2. Select the Environment tab.

  3. Set the ASNDIAL variable:

    1. In the Value field, type the path for your user-defined connect program. For example:
      C:\sqllib\bin\mydial.exe
      

    2. Click Set.

  4. Set the ASNHANGUP variable:

    1. In the Value field, type the path for your user-defined disconnect program. For example:
      C:\sqllib\bin\myhangup.exe
      

    2. Click Set.

  5. Click OK. The environment variables are set.

Specifying ASNDIAL and ASNHANGUP environment variables in Windows 95

The following section describes how to specify ASNDIAL and ASNHANGUP environment variables in Windows 95.

To set the ASNDIAL and ASNHANGUP environment variables:

  1. Declare the environment variables in your autoexec.bat file. For example:

    Where:

    mydial.exe
    The program that you use to connect your mobile client to the source server.

    myhangup.exe
    The program that you use to disconnect your mobile client from the source server.

  2. Reboot your system to have these settings take effect.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]