Oracle Retail Job unable to match log file

Document ID : KB000116306
Last Modified Date : 03/10/2018
Show Technical Document Details
Issue:
SAIMPTLOGI - The err.saimptlogi_1.* exists, but the agent is unable to match it after running an Oracle Retail Job. 
Environment:
12.0.3 RA Core (Agent binaries)
2.0.0+build. 18 Oracle Retail Solution
Cause:
This behavior has been identified as incorrect, and will be fixed with a future release. 
Resolution:
This issue has been fixed and is planned for release with the following version:

RA.Oracle.Retail Solution 2.1.1
Planned Release: 2018-10-24
Additional Information:
As a workaround, use a post process script to register the output.

Documentation:

https://docs.automic.com/documentation/webhelp/english/AWA/12.2/DOCU/12.2/AWA%20Guides/help.htm#Script/Reference/REGISTER_OUTPUTFILE.htm?Highlight=registering output

Examples:

The following sample script of a Windows job writes the file list of the directory C:\temp to the file C:\temp\test.txt. The system then verifies whether the command could successfully be executed. If so, this file is registered as job output. Otherwise, the job aborts.

dir C:\temp /S >> C:\temp\test.txt 
@set retcode=%errorlevel% ! 
@if NOT %ERRORLEVEL% == 0 goto :retcode 
:REGISTER_OUTPUTFILE "C:\temp\test.txt", "N"

When defining an external interpreter, copy the register.outputfile element to its own client. The Automation Engine will use this version and will not overwrite it when delivering new initial data. A Perl example is shown below:

:if &$EXT_INTERPRETER# = 'PERL' or 'perl' or 'Perl'
system("&UC_JOBMD JNR=&UC_REALNR MNR=&UC_MANDANT PNR=&UC_IP_PORT IPA=&UC_IP_ADR TYP=O ULOGIN=&uc_register_ulogin OUTFILE=\"&uc_register_ofile\"");
:else
...
:endif