Skip to main content

Important Scheduler Information

Prior to adding a new scheduling configuration, please review the following information:

Scheduler

  • Scheduler has an internal inter-locking mechanism that uses a bookmark file to help reduce memory leaks. Bookmark files have an extention of .LASTRUN, labeled in the following format: Pimsoft.Sigmafine.Scheduler.exe.\<DATABASE\>.LASTRUN, and are automatically managed by Scheduler. The bookmark files are used to lower the AF-actions against the AF Server, thereby reducing memory leaks and problems with other applications/users working over the same Sigmafine database/system.
  • DST transitions are managed automatically by the Sigmafine Scheduler. The Scheduler suspends all executions across the transition periods in order to avoid any wrong or overlapped execution that could cause infinite loops. As soon as Scheduler recognizes that the transition period has been completed, it automatically resumes the executions.
  • Starting with Sigmafine version 4.6.5, Scheduler skips unnecessary executions after a copy/paste or import/export action of the entire Sigmafine databases. Scheduler looks at the description of the SF_Scheduler AF table and checks if the GUID written in the description of the TABLE is the same as in the database ID. If they are the same, it Scheduler considers it a valid execution of a database. If they are not the same, Scheduler considers it as a "copied" or "temporary" database to be skipped. By default, system “CONFIGURATION” database is skipped.
  • Starting with Sigmafine version 4.6.5, log files are stored in a dedicated folder (\LOG\). A new internal command-line utility has been provided for running basic debugging commands, and for triggering Scheduler interfaces. This utility is not documented, as it should be used only with the assistance of a Sigmafine Technical Support representative when performing advanced system and Scheduler debugging.
  • In Windows Server 2008 R2 and greater operating systems, the Scheduler Configuration Tool requires that you run it as an administrator. If not run as an administrator, you receive an error message on both instance managements and analyses tables, indicating that the Scheduler service cannot open on the machine. The following figure displays the actual error message.Figure 1028: Error message when tool is not run as an administrator

SF_Scheduler Table

  • A default empty 'SF_Scheduler' table is automatically created when Sigmafine Scheduler runs for the first time for a target AF database.
  • Pimsoft strongly suggests that the Scheduler table be maintained only by system administrators.
  • (Only for experienced or advanced Sigmafine users.) Though the configuration is carried-out by the Sigmafine Scheduler Configuration Tool, you have the ability to change the configuration by directly modifying the 'SF_Scheduler' table inside the Sigmafine database. See Configure SF_Scheduler Table for further details.