Migrating to Replication Agent for DB2 UDB 15.0 software

Follow the procedures in this section only when upgrading to Replication Agent for DB2 UDB for z/OS version 15.0. Sybase recommends that you perform this procedure during a period of low activity.

If you have not installed and used earlier versions of Replication Agent software before, do not use this procedure.

To upgrade Replication Agent software to version 15.0 from 12.6

1. To prevent updates to the DB2 primary tables, use the following syntax:

   START DATABASE (database_name) SPACENAM (space_name) ACCESS (RO)
   

2. Stop the currently installed Replication Agent using the instructions in the Replication Agent for DB2 UDB User’s and Troubleshooting Guide for z/OS.

3. Shut down Replication Server.

4. On the Adaptive Server containing the RSSD for the primary Replication Server, issue the rs_zeroltm stored procedure using the following syntax:

   rs_zeroltm RS_source_ds,RS_source_db
   

   where the values for RS_source_ds and RS_source_db match the values you recorded in sections 8e and 8f of the Installation Worksheet.

5. Use ISPF to edit the hlq.TRUNCPT data set. Edit columns 1 through 36 to contain only binary zeros.

6. Review the configuration parameter values from the version of Replication Agent that you used most recently.

   1. Change the values of the parameters in the Replication Agent for DB2 UDB for OS/390 version 15.0 configuration file, located in the LTMCNFG member of the hlq.JCL library, to match the values you used in the most recent version of Replication Agent.

   2. Increase the value of the GenID parameter by 1 in the LTM configuration file to prevent QID sequence errors.

7. Start Replication Server.

8. Start the 15.0 version of Replication Agent using the instructions in the Replication Agent for DB2 UDB User’s and Troubleshooting Guide for z/OS.

9. Resume updates to the primary tables on DB2.

   You can use the following example syntax:

   START DATABASE (database_name) SPACENAM (space_name) ACCESS (RW)
   

   This command restores read and write access to the DB2 database.

   Replication Agent begins processing the log at the point where it stopped processing.

To upgrade Replication Agent software to version 15.0 from 12.0 or 12.5

1. To prevent updates to the DB2 primary tables, use the following syntax:

   START DATABASE (database_name) SPACENAM (space_name) ACCESS (RO)
   

2. Allow the currently installed Replication Agent to process to the end of the log.

   To determine whether processing has reached the end of the log, issue the XSTATUS command from the MVS operator console. This command displays the hlq.PDR.PARMLIB parameter values for Replication Extract version 12.0 or 12.5.

   Use the following information to evaluate the values of the following parameters:

   • HI extracted RBA. The relative byte address (RBA) of the last DB2 log record processed by Replication Extract. It uniquely identifies the position at which Replication Extract is processing the DB2 log.

   • DB2 HI written RBA. The RBA of the last record that DB2 wrote to the log. Compare this value with the high-extracted RBA to determine where Replication Extract is in relationship to the end of the DB2 log.

3. Stop the currently installed Replication Agent using the instructions in the Replication Agent for DB2 UDB User’s and Troubleshooting Guide for z/OS.

4. Shut down Replication Server.

5. On the Adaptive Server containing the RSSD for the primary Replication Server, issue the rs_zeroltm stored procedure using the following syntax:

   rs_zeroltm RS_source_ds,RS_source_db
   

   where the values for RS_source_ds and RS_source_db match the values you recorded in sections 8e and 8f of the Replication Agent Installation Worksheet.

6. Use ISPF to edit the hlq.TRUNCPT data set. Edit columns 1 through 36 to contain only binary zeros.

7. Review the configuration parameter values from the version of Replication Agent that you used most recently.

   1. Change the values of the parameters in the Replication Agent for DB2 UDB for z/OS version 15.0 configuration file, located in the LTMCNFG member of the hlq.JCL library, to match the values you used in the most recent version of Replication Agent.

      Replication Agent 15.0 uses an IBM-supplied API to access the DB2 log. The values that previously were in hlq.PDR.PARMLIB are now parameters in the LTM configuration file.

   2. Use the following chart to correlate the parameters from the most recent release of Replication Agent that you have used with the new parameter names. The new parameters use the same values as those prior to version 15.0, except where noted.

      Parameters in hlq.PDR.PARMLIB, prior to version 15.0	Parameters in LTM configuration file, version 15.0
      SETUP00
      SSID	Log_identifier
      LOADLIBS	No equivalent parameter
      PLANS00
      PDRPLANS	LTMPlan
      PDR
      REPL_ERROR: TERM or MSG	LogExtractError: valid values are either terminate or message
      POLL_INTVL	PollInterval
      CI_COUNT	CIMax
      ARCHIVE	Not used
      BUFFERS	Buffers
      LOGCOPY2	No equivalent parameter
      TRACE	LogTrace
      GENID	GenID
      SET_TRUNC	SetTruncPoint
      READER_TYPE (only applies if RA used in SMO)	SharingType (only applies to RA used in DB2 Data Sharing environments)
      READER_NAME (only applies if READER_TYPE = SMO)	SharingName (only applies to RA used in DB2 Data Sharing environments)

      The Adaptive Server Enterprise server IP address and port number can be specified in the LTM configuration file with parameters RSIPAddress and RSPort. If these values, along with the parameter TCPName are specified, they will override the entry in the SYGWXCPH for the server name set as RS= in the LTM configuration file.

      The Replication Server IP address and port number can be specified in the LTM configuration file with parameters RSSDIPAddress and RSSDPort. If these values, along with the parameter TCPName are specified, they will override the entry in the SYGWXCPH for the servername set as RSSD_server= in the LTM configuration file. This is only valid if Use_repdef=Y.

      If the specification for the IP address and port number are to be obtained from the SYGWXCPH file, RSIPAddress, RSPort, RSSDIPAddress, RSSDPort, and TCPName should not be included in the LTM configuration file.

      Replication Agent for DB2 UDB for z/OS version 15.0 does not verify that the name specified in the RS= parameter and the RSSD_server= parameter match what the Replication Agent is actually connecting to.

   3. Increase the value of the GenID parameter by 1 in the LTM configuration file to prevent QID sequence errors.

8. Start Replication Server.

9. Start the 15.0 version of Replication Agent using the instructions in the Replication Agent for DB2 UDB User’s and Troubleshooting Guide for z/OS.

10. Resume updates to the primary tables on DB2.

    You can use the following example syntax:

    START DATABASE (database_name) SPACENAM (space_name) ACCESS (RW)
    

    This command restores read and write access to the DB2 database.

    Replication Agent begins processing the log at the point where it stopped processing.

See also

• Chapter 3, “Replication Agent Installation Worksheet”

• Appendix A, “LTM for MVS Configuration Parameters,” for information about editing the LTM configuration file

• Replication Server Reference Manual for information about the rs_zeroltm stored procedure

---

Copyright © 2007. Sybase Inc. All rights reserved.

View this book as PDF