Data Movement Utilities Guide and Reference

Migration and Back-level Compatibility

There are migration and back-level compatibility issues associated with the AutoLoader utility:

• An earlier version of the AutoLoader utility was invoked through the db2autold command. The current version is invoked through the db2atld command.
• db2atld uses sockets as internal communications channels (as opposed to named pipes), and it chooses a TCP port number from the default range of 6063 down to 6000. However, if your system requires this range for other applications, you have two options when you migrate:
  • The PORTS parameter in the AutoLoader configuration file can be used to specify a port range other than the default.
  • The DB2ATLD_PORTS DB2 registry variable can be defined by specifying the range as:

       <lower-port-number>:<higher-port-number>
    

  The priority sequence for determining the TCP port range is: the DB2ATLD_PORTS DB2 registry variable, the PORTS AutoLoader configuration parameter, and the default.

• If a password is needed for client-to-server database connections, you have two options when you migrate:
  • The AutoLoader configuration parameters AUTHENTICATION and PASSWORD can be used. If AUTHENTICATION is set to YES, and PASSWORD is defined, the password is used for authentication. If AUTHENTICATION is set to YES, and PASSWORD is not defined, you are prompted for a password.
  • The DB2 registry value DB2ATLD_PWFILE can be set to point to a file where the password is stored. If specified, the contents of the file are evaluated, and the first blank-delimited character string is used as the password. Since the registry value is evaluated last, if defined, it will be used to override other password values.