DB Change Utility (ucybchng) fails to count the number of characters correctly if the term 'VALUE' is used.

Issue/Introduction:

Error Message :
N/A

DB Change Utility (ucybchng) fails to count the number of characters correctly if the term 'VALUE' is used.

This problem only affects transport files that were generated under Unix or Linux.

Investigation

When using a rule like below in the DB change script:
REPLACE_PART JOBS,*, VALUE:&TEST#, 'CA_AUTOMIC\01234', 'CA_AUTOMIC\56789'

Both values 'CA_AUTOMIC\01234' and 'CA_AUTOMIC\56789' are 16 characters long, but DB change invalidly sets a 15 character count for the new value ('F003M000000015' instead of 'F003M000000016') upon amending the transport file:

20171115/160914.845 - Old line:F003M000000016CA_AUTOMIC\01234
20171115/160914.845 - New line:F003M000000015CA_AUTOMIC\56789

This results in truncating the value by one character when the transport is loaded into the target environment.

Cause:

Cause type:
Defect
Root Cause: DB Change Utility (ucybchng) doesn't count the number of characters correctly when the term "VALUE" was used.
This problem happens only for transport case files which have been created on a LINUX or an UNIX OS.

Here is an exemple for the case which led to this problem:
REPLACE_PART 'JOBS', 'SOME_TEST_JOB', 'VALUE:&VAR#', 'old_content', 'new_content'

Environment:

OS: All Linux/Unix
OS Version: ALL

Resolution:

Update the DB Change Utility to a fix version listed below or a newer version if available.

Fix Status: In Progress

Fix Version(s):
Component(s) : Utility
Automation Engine 12.2.0 - Available
Automation Engine 12.1.1 - Available
Automation Engine 12.0.4 - Available
Automation Engine 11.2.7 - Available

Additional Information:

Workaround :
N/A