Post V24 migration SQL JOB is NOT supporting :PUT_ATT SQL_COLUMN_SEPERATOR = '§' & SQL_COLUMN_SEPERATOR = '¥'

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Post V24 migration SQL JOB is NOT supporting PUT_ATT SQL_COLUMN_SEPERATOR = '§' and PUT_ATT SQL_COLUMN_SEPERATOR = '¥' in the pre process tab of the SQL job. This is noticed for these two characters currently.

In V21, it is working fine.

Steps to Reproduce:

• Create a SQL Job
• Set ; as Separator for “Column Separator” field under “Result Table Settings” in the SQL tab
• In the Pre Process page, write  :PUT_ATT SQL_COLUMN_SEPERATOR = '§'
• Execute the job

The 21.0.9 version shows the column separator as '§'
1§TEST1§101
2§TEST2§102
3§TEST3§103
4§TEST4§104
5§TEST5§105

The 24.4.4 version shows the column separator as ';'
1;TEST1;101
2;TEST2;102
3;TEST3;103
4;TEST4;104
5;TEST5;105

Environment

Version(s) of affected/involved component:
Automic Engine 24.4.4  

Cause

Defect DE208817

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automation Engine

Automation.Engine 24.4.6 - TBA
Automation.Engine 26.1.0 - TBA

Additional Information

Public Title: :PUT_ATT exceeds length limit for multi-byte characters

Public Description: A problem has been fixed where the script command :PUT_ATT SQL_COLUMN_SEPERATOR was exceeding the length limit for multi-byte characters because bytes was counted instead of characters. As a workaround for SQL_COLUMN_SEPERATOR the value can be saved directly in the attributes of an SQL job.