A Control-M File Transfer job ends successfully when using a wildcard even though no file was found or transferred. Should the job fail?

A Control-M File Transfer job ends successfully when using a wildcard even though no file was found or transferred. Should the job fail?

Knowledge Article

Article Number

000292488

Old Article Number

000065282

Article Type

Solutions to a Product Problem

Title

A Control-M File Transfer job ends successfully when using a wildcard even though no file was found or transferred. Should the job fail?

Summary

Product

Control-M Managed File Transfer

Component

Control-M Managed File Transfer

Applies to

Control-M Managed File Transfer all versions
Control-M for Advanced File Transfer all versions
Control-M SaaS Managed File Transfer all versions

Problem

If a wildcard is used in the file name defined in the Job, and no files match the specified pattern, the job ends successfully.

Sample job output:
+ Job started at '0520 14:38:53:960' orderno - 'ORDERID' runno - '00003'
Number of transfers - 1
+ Host1 'HOSTNAME'[Unix-SFTP] username 'USERNAME' - Host2 'HOSTNAME'[Unix-SFTP] \
username 'USERNAME'
Local host is: HOSTNAME- HP-UX B.11.23 U 9000/800
Connection to SSH server on host 'HOSTNAME' was established
Connection to SSH server on host 'HOSTNAME' was established
+ Starting transfer #1 out of 1
No matching files for pattern 'TEST_*.dat*'
Transfer #1 completed successfully

Job executed successfully. exiting.

Job ended at '0520 14:38:57:180'
Elapsed time [4sec] CPU usage [1.0sec]

Cause

If a pattern was used and no files were found, AFT does not analyze this as a Transfer Error as no file was found and no file was transferred.

Solution

To make the job fail if no file was found, use the File Watch + Transfer capability of AFT and use an On-Do Action in the job definition to find "No matching files for pattern" in the job output and perform a Do -> Set to Not Ok

For example:
User-added image

Attachment(s):