Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLINFOX - Enhanced Release Information Utility
  8. DTLREXE - Remote Execution Utility
  9. DTLUAPPL - Restart Token Utility
  10. DTLUCBRG - Batch Registration Utility
  11. DTLUCDEP - CDEP Maintenance Utility
  12. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  13. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  14. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  15. DTLURDMO - Data Map Utility
  16. DTLUTSK - Task Control Utility
  17. EDMLUCTR - Log Scan and Print Utility
  18. EDMUOPTS - Service Aid Utility
  19. EDMXLUTL - Event Marker Utility
  20. HOSTENT - TCP/IP Address Reporter Utility
  21. PWXCATMY - MySQL Catalog Utility
  22. PWXUCCLPRT - Print Log Summary Utility
  23. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  24. PWXUCREG - Capture Registration Utility
  25. PWXUMAP - Map List Utility
  26. PWXUCRGP - Capture Registrations Print Utility
  27. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  28. PWXUGSK - SSL Reporting Utility
  29. PWXUSSL - PowerExchange SSL Reporting Utility
  30. WRKJRNLCKE- Journal Lock Table Utility for IBM i

REG_COPY MODIFY Statement

REG_COPY MODIFY Statement

The MODIFY statement modifies certain attributes of the copied registrations.
This statement can include the following optional parameters:
CONDENSE={FULL|PART|NONE}
Specifies condense options for the captured data on the target system.
DBID=
database_ID
For Adabas and Datacom databases, specifies a new database identifier.
DBNAME=
database_name
For IDMS databases, specifies a new database name for the registration.
FN=
file_name
Specifies the file name associated with the registration. For example:
FN=NEW.KSDS.FILE001
MSSOPTS=(DBSERVER=
database_server
,DBNAME=
database_name
)
Specifies the following Microsoft SQL Server options for selecting the registration to modify:
  • DBSERVER specifies the database server ID for the registration. You can optionally include a port number in the following format:
    DBSERVER="
    database_server
    ,
    port_number
    "
    In this case, the double-quotation marks are required.
  • DBNAME specifies the database name for the registration.
MUFNAME=
muf_name
For Datacom databases, specifies a new MUF name for the registration. Use this parameter to specify a new database instance for the registration in the same way you can use the NEW_DBID parameter for other database types.
NEW_DBID=
database_ID
Specifies a new database instance for the registration. This value depends on the source type. Usually, it is the instance value from the registration group.
For Microsoft SQL Server sources, this value is a unique user-defined instance identifier for the database server and database name combination defined in the MSSOPTS parameter. Maximum length is seven characters. This instance identifier identifies a set of registrations for the publication database on the target system. If you also define the CREATEXMAPS statement in the registration copy syntax, the instance identifier is incorporated into the names of the extraction maps that are generated for the copied registrations on the target. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file on the target. If you do not enter a NEW_DBID value, PowerExchange generates a unique instance identifier that is composed of all or part of the publication database name followed by a 3-digit number if a number is required to make the identifier unique.
If you are migrating from one SQL Server environment to another, you can enter an instance identifier that matches the instance identifier in the source system. In this manner, you can avoid using a generated instance identifier and having to update the extraction map names in PowerCenter workflows and edit the PowerExchange Logger DBID parameter value on the target. In this case, ensure that the DBMOVER configuration files in the source and target environments define unique paths in the CAP_PATH and CAPT_XTRA statements.
SUBSCHEMA=
subschema_name
For IDMS databases, specifies a new subschema for the registration.

0 COMMENTS

We’d like to hear from you!