In the ADASEL-expanded PLOG files, the ETID userid can be expressed as either an actual user ID or a timestamp value. The ADASEL utility can produce ETID timestamp values in hexadecimal timestamp format, for example, x'400015321F404040', or replace timestamp values entirely with x'40' values, for example, x'4040404040404040'.

With Adabas versions earlier than 8.3, the PowerExchange ECCR always sets the ETID timestamp values to all x'40' values if the ETID values begin with x'40'. This behavior is the default behavior.

Beginning with Adabas version 8.3, the ADASEL utility writes internally generated values that begin with x'40' to the ETID field in the PLOG records, unless the user application provides a specific user ID in the call to Adabas. You can use this parameter to prevent the ECCR from writing the internally generated values as all x'40' values.

If the ADASEL-expanded PLOG files contain ETID values in hexadecimal timestamp format or in ADASEL-generated internal format and the ECCR replaces these values with all x'40' values, the ECCR will not be able match the change records from the PLOGs to the commit records. In this case, UOWs might remain open, causing the PowerExchange Logger for z/OS to generate many spill files. Also, spill file allocation errors and CDC session failures might occur. Use this parameter to allow the ECCR to read the ETID values "as is" from the PLOGs so that these errors can be avoided.

Valid values:

Default is N.