Record Modification User (&USER)

The user ID that made the update on the source.

Data Type
Character
Restrictions and limitations:
Depending on the replication engine that you install, journal control fields may or may not be supported when mirroring or refreshing data. Unsupported journal control fields contain default values that vary between the replication engines.
  • CDC Replication Engine for Db2® for i—Support for this journal control field is available only when CDC Replication mirrors data, and is not available when refreshing data. If you decide to use this journal control field when refreshing data, CDC Replication sets this journal control field to UNKNOWN.
  • CDC Replication Engine for Db2 Database—Support for this journal control field is available only when CDC Replication mirrors data, and is not available when refreshing data. When mirroring data, this journal control field contains the Authorization ID that the job used to connect to DB2®.
  • CDC Replication Engine for Db2 for z/OS®—Support for this journal control field is available only when CDC Replication mirrors data, and is not available when refreshing data. When mirroring data, this journal control field contains the Authorization ID that the job used to connect to Db2. This is usually the User ID of the job.
  • CDC Replication Engine for PostgreSQL—The &USER journal control field is not supported.
  • CDC Replication Engine for Oracle XStream—Support for this journal control is available when mirroring data. The attribute USERNAME from an Oracle XStream LCR is supplied as part of the journal control field &USER. CDC Replication configures the Oracle XStream capture to include the attribute USERNAME as part of the LCRs that are supplied to CDC Replication. See the Oracle documentation for DBMS_CAPTURE_ADM.INCLUDE_EXTRA_ATTRIBUTE for more information on the USERNAME attribute.