JOBF completes successfully even though the destination path lacks a leading slash.

Products

• CA Automic Workload Automation - Automation Engine
• Automic SaaS

Issue/Introduction

A JOBF file transfer completes successfully with an ENDED_OK (ended normally) status, even though the destination path lacks a leading slash.

 

Note: opt/automic/files2 does not exist on the OS itself.

ls opt/automic/files2
ls: cannot access 'opt/automic/files2': No such file or directory

 

The system copies the files to the user's home directory and expands the path.

U00063088 FT '2664010':   '/opt/automic/files/ra_log_09.TXT'
U00063088 FT '2664010':   '/opt/automic/files/ra_log_08.TXT'
U00063088 FT '2664010':   '/opt/automic/files/ra_log_07.TXT'
U00063089 FT '2664010': Files selected: '3'.
U00011133 OK    '20326' Bytes, '250' Records for file '/opt/automic/files/ra_log_09.TXT'->'/home/support/opt/automic/files2/ra_log_09.TXT' transferred. Duration '00:00:00'.
U00011133 OK    '20326' Bytes, '250' Records for file '/opt/automic/files/ra_log_08.TXT'->'/home/support/opt/automic/files2/ra_log_08.TXT' transferred. Duration '00:00:00'.
U00011133 OK    '20326' Bytes, '250' Records for file '/opt/automic/files/ra_log_07.TXT'->'/home/support/opt/automic/files2/ra_log_07.TXT' transferred. Duration '00:00:00'.

Environment

 

• Product: CA Automic Workload Automation - Automation Engine

• Component: Unix File Transfer (JOBF)

• Version: 24.X

 

 

Cause

When a destination file path is defined without a leading slash, the Agent interprets this as a relative path instead of an absolute one.

Resolution

To ensure the file transfer works as expected, always use the correct absolute path with a leading slash in the destination settings (e.g., /opt/automic/files2/ra*).