Problem:
Automic File Transfer (FT) jobs configured to use wildcard variables (&1, &2, etc.) in destination paths exhibit inconsistent and incorrect parsing behavior from source filenames when comparing newer Java-based OS Agents (v24.x) with older C-based OS Agents (v21.x, v12.3.x). This leads to files being transferred to unexpected locations or with incorrectly named directories/files.
Symptoms:
FT jobs complete, but target directories and filenames are created with incorrect values derived from wildcard substitution.
The issue is consistently reproducible.
Example Scenario:
/opt/a/b/c/d/e/0021710/*-*-*_*_name2.log.gz2025-07-01_12-56-56.444_name1_name2.log.gz/opt/a/b/c/d/e/0021710/&1-&2-&3/&1-&2-&3_&4_name2.log.gzObserved Behavior (Automic Java OS Agent v24.x - INCORRECT):
&1 = 2025-07-01_12&2 = 56&3 = 56.444/opt/.../2025-07-01_12-56-56.444/...Expected Behavior (Automic C-based OS Agent v21.x/v12.3.x - CORRECT):
&1 = 2025&2 = 07&3 = 01&4 = 12-56-56.444/opt/.../2025-07-01/...CA Automic Workload Automation - Automation Engine
The internal wildcard matching mechanism implemented in the Java-based OS Agents (v24.x) differs in its "greediness" and parsing logic compared to the original C-based agents (v21.x, v12.3.x). This discrepancy leads to an altered interpretation of substrings when multiple delimiters are present in the source filename, resulting in incorrect variable substitution for the target path.
Solution:
Update to a fix version listed below or a newer version if available.
The fix addresses the incorrect parsing of wildcard variables, restoring the expected behavior as observed in v21.x and v12.3.x agents.
This is a product defect (Defect ID: DE176029).