*/
file_name

You can use the asterisk wildcard in the
Library/File Override
property only for real-time extractions.
DB2 for i5/OS files that are included in a mapping require PowerExchange capture registrations. By using the asterisk as a library override, you can map and register a single file for change data capture in the PowerExchange Navigator. CDC sessions can extract changes for all of the file instances that occur across all libraries.
To extract changes for multiple file instances, the files must use the same journal and be defined with IMAGES(*BOTH).
The specified file name must be a valid i5/OS file name. You cannot specify DB2 table names.
If you use i5/OS-generated file names, make sure that you understand the journal contents. An i5/OS-generated file name is composed of only the first 5 characters of the DB2 table name followed by 5 digits. These file names might result in data extraction from unexpected files.
Each time a real-time extraction session runs, PowerExchange checks the journal for files that match the file name. The files for which changes are extracted can vary from session to session if you add new libraries that contain the same file name and use the same journal.
Restart tokens are only for sources that are included in a mapping. PWXPC indicates the presence of a
Library/File Override
value for a session by prefacing the extraction map name with the specified override.
The following example shows the restart tokens for a source that is processed by a session for which the
Library/File Override
attribute specifies */
file_name
:
<*/
file_name>d3
instance.
regname_tablename=
restart1
<*/
file_name>d3
instance.
regname_tablename=
restart2
You do not need to include the
Library/File Override
information in the restart token file when overriding a restart token. PWXPC includes the override information if it is found in the session properties.