Antoine_Sauteron_1266

3 reasons why job reports remain locally on the agent

Discussion created by Antoine_Sauteron_1266 on Sep 16, 2016
Latest reply on Mar 20, 2017 by Wolfgang_Brueckler_1288
Did you ever face a problem where job reports stay in the agent's folder? These .txt files bear 8 character names that start with an 'O'.

Here are 3 possible reasons why this can happen:

1 - Jobs are configured to save reports locally on the agent.
To check this, go to the Unix / Windows tab of the object and verify if the "file" box is checked in the "job report" section.

bjz8pmsz93j7.png

2 - Reports' size exceed the limit set in UC_HOSTCHAR_DEFAULT > MAX_REPORT_SIZE :
3u44jod2320p.png.
Default value is 120 blocks = 937 KB.
If a job report exceed this size it may not be sent back to the DB and locally removed from the agent's directory.

Please note this setting may be in a different VARA than UC_HOSTCHAR_DEFAULT if UC_EX_HOSTCHAR points to a different variable.

In this example the setting will need to be adjusted in UC_HOSTCHAR_SAA:
enntfni1ei0c.png

3 - There was an issue during the job's execution or the agent crashed.
You may verify this by converting the file name into a RunID search for this RunId in the agent's log / in the server logs.

Outcomes