OPTIONS - connect_cdc_sqdata - Latest

When dealing with Change Data, one piece of relevant information is the "Change Op", that indicates the kind of operation being processed. For historical reason, Change Op has been ‘I’ for insert, ‘D’ for delete and ‘R’ for update (or replace in IMS parlance). When dealing with relational data it is more natural to refer to update as ‘U’. Still, for backward compatibility reasons, it is not possible to change the default. This option allows you to choose the 3 characters used to represent the 3 different operations. If you choose to use it is strongly recommended that you stick to CDCOP( 'I', 'U', 'D').

Only applies to AVRO formatted Kafka targets. The url of the Confluent Schema Registry to be used to retrieve/register AVRO schemas. The presence of that option also triggers the generation of a confluent header in front of each AVRO encoded Kafka topic written.

JSON Type Datastore targets only. The Apply Engine automatically transforms source datastore Description field/column names into what is referred to as "lower snake_case" where every alphabetic character is turned to lower case and all non-alphanumeric characters are transformed to '_' (underscore). While the AVRO Type Datastore specification only excludes the '-' (dash) character, Mainframe Datastore Descriptions, such as COBOL Segment Descriptions and DB2 Column Names tend to use All Caps, which is frowned upon in other environments and are therefore changed to lower case. Testing and validating results formatted as AVRO can be a challenge due to the separation of schema from data and the cryptic formatting that separates individual data points. Using this option together with the "temporary" specification of JSON rather than AVRO formatting produces typical JSON output but with the same literal names that will be present in the AVRO schemas making it much easier to validate output before moving to AVRO formatted target Datastores.

NAMESPACE '<name_space>'

Optional name_space assigned to the Objects created, that will appear in the JSON/AVRO (header/payload) as the "namespace":"<name_space>" pair.

(<metadata_name> [AS <metadata_alias> ] [,<metadata_name> [AS <metadata_alias> ]] [, ...])

Metadata header tags for JSON or AVRO target datastores ONLY. See METADATA Header Tags and examples.

APPLICATION ENCODING SCHEME = <ccsid>

Specifies the precision of the fractional seconds of the METADATA "timestamp" option where <n> must be less than or equal to the precision of the original source log timestamp, the zOS Storeclock. The range of values in ISO8601 PRECISION <n> is 0-6. Zero results in seconds with no precision and 6 is Microseconds. The zOS Storeclock is more precise at 64 bits and technically both hardware and application dependent. If more precision is desired then the METADATA "stck" value containing the actual Storeclock should be used.

IMS and VSAM Datastores only. For historical reasons, when processing binary source records, the Engine would treat some values as 'NULL" indicators, even though there is no such thing as NULL in either IMS or VSAM data. For backward compatibility reasons this can not be changed but this option changes the product behavior. It is strongly recommended to use PSEUDO NULL = NO, and to reserve NULL for handling of invalid data, for instance with an INVALID <source_field> SETNULL; statement. Pseudo null has no impact at all on non-binary record input.