If the error trapping is in the prolog then the approach I take is to set the datasource to null rather than use ProcessBreak, this way you skip to the epilog without an error in the server log. Effectively we are removing the datasource from the TI if errors are found at run time.
Something like this
#Prolog
If (Some error check fails);
errorCode=1; #Reference this in the epilog to decide on action.
DatasourceNameForServer='NULL';
EndIf;
Note this isn't documented anywhere and I've not done it for a while so testing required...
------------------------------
Steven Rowe
------------------------------
Original Message:
Sent: Tue May 07, 2024 06:21 AM
From: Hallbjorn Bjornsson
Subject: Quit TI process without "ERROR" post to tm1server.log
Hi, I use the server log to follow up on the helth of my PA servers and what I usually do is to scan for the "ERROR" lines in the tm1server.log
What is bothering me is that I have processes that I run on schedule and if certain conditions are met then the run full, else I just stop the process. To do that I have used "ProcessBreak" and based on what I have read it should just send me to Epilog where I can decide on further actions. But what happens in the tm1server.log is that I get an "ERROR" line...se following for process that only runs ProcessBreak:
17792 [4] ERROR 2024-05-07 10:10:18.480 TM1.Process Process "TEMP": finished with ProcessBreak
Is there a way to terminate process without at least getting an "ERROR" id code in the tm1server.log file?
------------------------------
Hallbjorn Bjornsson
------------------------------