While we're at it:
You should probably activate (by removing the comment marker, "!") the lines 3 and 4 and put them everywhere you want to check for errors. If you don't at least have them once, your job will always end ENDED_OK even if there is an error.
If you do this after your
copy
statement, most likely you won't even need to check if the file exists, because then your "copy" statement will fail (and likely it prints "File not found" by itself).
(edited, brainfart).
Best regards,
Original Message:
Sent: 10-14-2019 07:17 AM
From: Daniele Giannicola
Subject: ONE Automation Error management
Hi Alan,
tx about information.
When I script I receive this:
What do you think about?
Can you send me an example about code to use to exit command script with return code?
Regards
Daniele
------------------------------
Employee
Postevita
Original Message:
Sent: 10-14-2019 06:29 AM
From: Alain Moisy
Subject: ONE Automation Error management
Did you use :DATA :<label> in your script ?
This is indicating to the AE Engine that the : is not for an internal script command but for the shell command.
Regards.
Alain
Original Message:
Sent: 10-14-2019 02:51 AM
From: Daniele Giannicola
Subject: ONE Automation Error management
Hi gay,
i've got some problem about managing error scripting. I need to exit from script intercepting an error code. I used dos shell but function goto not respond because ":" interpreter is used about OneAutomation framework.
Can you help me ?
Tx
Daniele
------------------------------
Daniele
Postevita
------------------------------