The following information is not documented in “Managing jobs and scheduled tasks” in Chapter 4, “Advanced Concepts and Tools.”
[CR #584973] The Last Result column in the Runtime Manager displays a value of either Failed or Succeeded for any scheduled task that has already run. The same information appears in the Execution Result column of the Schedule Task List when viewed in the Web Monitor.
Succeeded – means either the task completed as expected or was prematurely terminated in one of these ways:
By clicking the Terminate a Running Schedule icon on the toolbar of the Runtime Manager, or by selecting Actions | Terminate.
By clicking Cancel Execution on the Execution Monitor.
By clicking Cancel in the Web Monitor.
The value of Succeeded in the Last Result column does not always mean that the task ran to completion without errors.
Failed – means that the task was unexpectedly terminated, for example, by killing the grid engine process using the Windows Task Manager or through operating system command line.
Sybase recommends that you do not use the Windows Task
Manager or operating system command line to terminate scheduled
tasks.
[CR #589842] If you are using ETL Scheduler to set up a repeated task using a server that is running on UNIX, you must configure the .odbc.ini file on the UNIX machine to include a pointer to the repository data server.
Use a text editor to open the etc/.odbc.ini file.
Add an entry similar to:
[repository_data_server] uid=dba pwd=sql EngineName=demo CommLinks=tcpip(host=<hostname>;port=<portnumber>) AutoStop=no DatabaseName=demo
where repository_data_server is the name of the SQL Anywhere data server.
Make sure that the entry does not include the “AutoPreCommit” connection
parameter.
Save the file.
In the ETL Scheduler, set up the repeated task, then run the job.
Configuring .odbc.ini file 