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
  • 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

NOTIFY Keyword Set

NOTIFY Keyword Set

This set of keywords tells the utility to insert a special marker into the PowerExchange active log. The special marker notifies the component using the data of an event change, such as a change in the edition value.
This is used to generate a restart point in the PowerExchange Change Capture log.
Syntax:
For ACCESS=STRUCTURE:
EVENT TYPE=BASEEDM NOTIFY=
type
 OBJECT=
database_type

      ACCESS=STRUCTURE {DBD=
database_name
 DSN=
data_set_name
 |
      SYSID=
ssid
}
For ACCESS=OBJECT:
EVENT TYPE=BASEEDM NOTIFY=
type
 OBJECT=
db_type

      ACCESS=
level_of_data_objects
 
      {EDMNAME=
edmname
 | 
        DBD=
database_name
 DSN=
data_set_name
 SEGMENT=
segment_name

        [SEGMENT=
segment_name
 ...] | DBD=
database_name
 DSN=
data_set_name
 |
        SYSID=
ssid
 CREATOR=
tbcreator
 TABNAME=
table_name

        [TABNAME=
table_name
 ...]}
The following table lists and describes the variables that you can use with the BASEEDM category:
Variables
Description
type
Tells the utility what type of notification the event marker signals.
The following value is valid:
  • EDITION provides notification that a resource registration is changing.
db_type
Indicates the database type of the associated resource. The following values are valid:
  • IMS
  • VSAM
  • DB2
level_of_data_objects
Indicates the level of data objects to be associated with the notification. The following values are valid:
  • STRUCTURE indicates that all data objects within the database, data set, or subsystem are to be associated with the notification. When you specify ACCESS=STRUCTURE, you must specify either the DBD and data set name or the subsystem ID. For example, for OBJECT=IMS, you would specify DBD and DSN.
  • OBJECT indicates that only the specified object is to be associated with the notification. When you specify ACCESS=OBJECT, you can specify either the EDMNAME or the fully qualified data object name. For example, for OBJECT=IMS, you would specify DBD, DSN, and SEGMENT.
edmname
You can specify a particular registered source segment, record, or table by using its EDMNAME. This variable supports delimited strings, but you must enclose them in quotation marks.
dbdname
When used alone, allows you to specify the database description (DBD) name of a set of IMS segments or VSAM records. When you use the DBD name as part of a fully qualified name, this name allows you to specify a particular IMS segment or VSAM record.
data_set_name
Specifies the data set name of a particular IMS segment or VSAM record as part of a fully qualified name.
segment_name
Specifies a particular IMS segment as part of a fully qualified name. You can use this variable multiple times (up to 255) in a single statement to associate multiple segments with the notification.
ssid
You can specify the subsystem ID of a particular set of DB2 tables when used alone, or a particular DB2 table when used as part of a fully qualified name
tbcreator
Specifies the creator of a particular DB2 table as part of a fully qualified name. This variable supports delimited strings, but you must enclose them in quotation marks.
tbcreator cannot handle DB2 long names and is limited to 8 bytes.
table_name
Specifies a particular DB2 table as part of a fully qualified name. You can use this variable multiple times (up to 255) in a single statement to associate multiple tables with the notification. These tables must be in the same subsystem and have the same creator ID.This variable supports delimited strings, but you must enclose them in quotation marks.
table_name cannot handle DB2 long names and is limited to 18 bytes.
If the DB2 ECCR is active when you run the create-event-marker utility to update the edition level, you must refresh the ECCR. To do so, run the
MODIFY
 job_name,
REFRESH
 command (where job_name is the name of the MVS batch job or started task that runs the DB2 ECCR). This ensures that the DB2 ECCR reads the new edition level in the PowerExchange repository.
Alternatively, you can stop and restart the DB2 ECCR with the
WARM START
 keyword.
0 COMMENTS
We’d like to hear from you!