Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.4.0 HotFix 1
  • All Products

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. DTLREXE - Remote Execution Utility
  8. DTLUAPPL - Restart Token Utility
  9. DTLUCBRG - Batch Registration Utility
  10. DTLUCDEP - CDEP Maintenance Utility
  11. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  12. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  13. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  14. DTLURDMO - Data Map Utility
  15. DTLUTSK - Task Control Utility
  16. EDMLUCTR - Log Scan and Print Utility
  17. EDMXLUTL - Event Marker Utility
  18. HOSTENT - TCP/IP Address Reporter Utility
  19. PWXCATMY - MySQL Catalog Utility
  20. PWXUCCLPRT - Print Log Summary Utility
  21. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  22. PWXUCREG - Capture Registration Suspend Utility
  23. PWXUCRGP - Capture Registrations Print Utility
  24. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  25. PWXUGSK - SSL Reporting Utility for z/OS
  26. PWXUMAP - Map List Utility
  27. PWXUSSL - PowerExchange SSL Reporting Utility

Utilities Guide

Utilities Guide

Back Next

REG_COPY RENAME Statement

REG_COPY RENAME Statement

The RENAME statement renames elements of the copied capture registration on the target system or identifies an existing bulk data map on the target system that is named differently from the default.
  • For the DBD, IMSMAP, IMSSCHEMA, REG_NAME, SCHEMA, and TABLE parameters, the RENAME statement specifies the new name of the registration element on the target system.
  • For the BULKSCHEMA, BULKMAP, and BULKTABLE parameters, the RENAME statement identifies the bulk data map on the target system to be merged with the newly generated extraction map. Use these parameters if the bulk data map on the target system is named differently from the default.
    These parameters are available only on DB2 for z/OS or DB2 for Linux, UNIX, and Windows systems.
For most RENAME parameters, the first operand represents the item or items being renamed, and the second operand represents the new name. The first operand can be any of the following:
  • The full name of an item
  • A partial name with a wildcard (*)
  • A wildcard (*) only
The RENAME statement has the following parameters:
BULKMAP=(
old_map_name
,
new_map_name
)
Specifies a new map name to use in locating the bulk data map on the target system to merge with the copied extraction map. The BULKMAP parameter of the RENAME statement is valid only in conjunction with the RELATED BULK statement.
In the following example, all maps named
capture1
 are renamed to
capture2
: 
BULKMAP=(capture1,capture2)
In the following example, all maps are renamed to
newmap
: 
BULKMAP=(*,newmap)
In the following example, all map names ending in
01
 are renamed to fixed: 
BULKMAP=(*01,fixed)
BULKSCHEMA=(
old_schema_name
,
new_schema_name
)
Specifies a new schema name to use in locating the bulk data map on the target system to merge with the copied extraction map. The BULKSCHEMA parameter of the RENAME statement is valid only in conjunction with the RELATED BULK statement.
In the following example, all bulk schemas named
test
 are renamed to
prod
: 
BULKSCHEMA=(test,prod)
In the following example, all bulk schemas are renamed to
newprod:
BULKSCHEMA=(*,newprod)
In the following example, all schemas ending in
tmp
 are renamed to
fixed
: 
BULKSCHEMA=(*tmp,fixed)
BULKTABLE=(
old_table_name
,
new_table_name
)
Specifies a new table name to use in locating the bulk data map on the target system to merge with the copied extraction map. The BULKTABLE parameter of the RENAME statement is valid only in conjunction with the RELATED BULK statement.
In this example, all table names
testtab01
 are renamed to
prodtab01
: 
BULKTABLE=(testtab01t,prodtab01)
In this example, all tables are renamed to
newtable
: 
BULKTABLE=(*,newtable)
In this example, all tables ending in
01
 are renamed to
fixed
: 
BULKTABLE=(*01,fixed)
DBD=(
old_dbd_name,new_dbd_name
)
For IMS data sources, specifies a new DBD name for the capture registration. DTLURDMO loads the corresponding DBD on the target system and updates the registration with the database organization.
The DBD specified in a RENAME statement takes precedence over the DBD name derived from a map specified by IMSSCHEMA or IMSMAP.
IDMS_PAGEGROUP_RADIX=(
old_page_group
,
new_page_group
,
old_radix
,
new_radix
)
For IDMS data sources, changes the page group or radix value. This parameter enables you to migrate registrations and extraction maps to environments with different values for the page group and radix database settings.
For
old_page_group
 and
new_page_group
, specify a value from 0 to 32767.
For
old_radix
 and
new_radix
, specify a value from 2 to 12.
You can create an extraction map on the target system with renamed page group and radix values by using the REG_COPY, CREATEXMAPS LOC=TARGET, and RENAME IDMS_PAGEGROUP_RADIX statements. Before you issue these statements, you must copy the data map to the target platform by using the DM_COPY statement. If the data map is not correct on the target platform, the results of the REG_COPY and accompanying optional statements are unpredictable.
IMSMAP=(
old_map_name,new_map_name
)
Renames IMS data maps that match the name or the pattern in the old data map name to the new data map name. The utility loads the specified data map from the target system and updates the registration with database organization using the DBD named in the data map.
In the following example, all schemas named
test
 are renamed to
prod
: 
IMSMAP=(test,prod)
IMSSCHEMA=(
old_schema_name,new_schema_name
)
Renames IMS schemas that match the name or pattern in the old schema name to the new schema name. The utility loads the specified data map from the target system and uses the DBD named in the data map to update the database organization information in the registration.
The new schema name must match the name of the schema for an existing bulk data map on the target system.
In the following example, all schemas named
test
 are renamed to
prod
: 
IMSSCHEMA=(test,prod)
NRDB_DM_TABLE=(
old_map_name
,
new_map_name
,
old_table_name
,
new_table_name
)
For IDMS data sources, identifies the old and new data map and table names. This parameter enables the registration to link to a data map that has a new identity in the new environment.
NRDB_DM_TABLE is required only if the data map contains information that is necessary for CDC extractions. Specifically, it is required to propagate changes to the page group or radix value to the extraction map.
The following rules apply:
  • Use the following format for
    old_map_name
     and
    new_map_name
    : 
    schema_name
    .
    data_map_name
    schema_name
    ,
    data_map_name
    , or both can consist in part or full of wildcards, as in the following examples: 
    *.test_map
    test_schema.*
    test*.*
  • If you omit
    old_map_name
     and
    new_map_name
    , include commas as placeholders, as follows: 
    NRDB_DM_TABLE=(,,
    old_table_name
    ,
    new_table_name
    )
  • You can omit
    old_table_name
     and
    new_table_name
    . If you include them, specify the complete table name, without wildcards.
REG_NAME=(
old_registration_name
,
new_registration_name
)
Renames the registration. Because the registration name is used to create the registration tag, this option overrides the KEEPREGTAG option.
SCHEMA=
old_schema_name,new_schema_name
Renames schemas that match the name or the pattern in the old schema name to the new schema name.
In the following example, all schemas named
test
 are renamed to
prod
: 
SCHEMA=(test,prod)
In the following example, all schemas are renamed to
newprod
: 
SCHEMA=(*,newprod)
In the following example, all schemas ending in
tmp
 are renamed to
fixed
: 
SCHEMA=(*tmp,fixed)
TABLE=
old_table_name,old_table_name
Renames tables that match the name or the pattern in the old table name to the new table name.
In the following example, all tables named
testtab01
 are renamed to
prodtab01
: 
TABLE=(testtab01,prodtab01)
In the following example, all tables are renamed to
newtable
: 
TABLE=(*,newtable)
In the following example, all tables ending in
01
 are renamed to
fixed
: 
TABLE=(*01,fixed)
0 COMMENTS
We’d like to hear from you!