AWI: cannot open SQL job report after deleting report file from file system; error message "An I/O error occurred: 'java.io.FileNotFoundException"

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The customer is running SQL jobs, the job is configured to store the report in the database as well as on the file system.

If the job ends error-free (ENDED_OK)

 we can retrieve the job report in AWI
 we can delete the report file on the file system (file name typically O<alpha-runnr>.TXT) and are still able to open the report in AWI

In case that the job terminates abnormally (ENDED_NOT_OK):

we can retrieve the job report in AWI
but after deleting the report file on the file system AWI is no longer able to open the report

An I/O error occurred: 'java.io.FileNotFoundException:C:\#####\#####\Agents\sql\bin\..\temp\OAADNXBS.TXT (Das System kann die angegebene Datei nicht finden)'com.uc4.ecc.framework.core.exceptions.MLSInternationalizedException
com.uc4.ecc.ae.commons.dialogs.reports.ReportPresenter.loadAgentReport(ReportPresenter.java:529)
com.uc4.ecc.ae.commons.dialogs.reports.ReportPresenter.fetchSingleReportPageData(ReportPresenter.java:323)
com.uc4.ecc.ae.commons.dialogs.reports.ReportPresenter.lambda$loadData$6(ReportPresenter.java:173)
com.uc4.ecc.framework.core.async.NoArgsLoaderWrapper.load(NoArgsLoaderWrapper.java:16)
com.uc4.ecc.framework.core.async.NoArgsLoaderWrapper.load(NoArgsLoaderWrapper.java:7)
com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$1.call(BaseRequestCoordinator.java:231)
com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$CallableImplementation.call(ContextAwareExecutorService.java:72)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)


This behavior is

independent of the Automic AWA/AWI version, we can reproduce in version 12.3.1 as well as 12.3.3
independent of the file location, i.e. "UC_EX_PATH_JOBREPORT=" can point to a local folder or network share


If we configure the SQL job to store the report in the database ONLY, the report can be retrieved in both cases, ENDED_OK and ENDED_NOT_OK. No error.

It seems that this behavior depends on the status AND the attribute "store to file".

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

The reports are stored in the database only when they do contain information, but since there is no information, no report is written in the database, and the report must be fetched from the agent.

This is working as designed.