Try TT Now

All Gateways

TT Chron Parameters

Parameter Usage by Section

The following table lists the five different sections available in ttchron.ini and the various parameters that you can use in each of these sections.

TTChron Parameter Usage by Section

Section Type

Available Parameters

Global

cycle_freq

(Deprecated in TTChron Version 7.7 and higher.

fkill_delay

logging

svc_freq

(Deprecated in TTChron Version 7.7 and higher.

window

Holiday

Dates

Note

TT Chron does not support holidays for sections that have a weekly session. Configuring holidays for sections that have a weekly session can result in TT Chron bringing a scheduled process down at incorrect times.

Job

args

dir

disabled

end_date

holidays

path

run_days

run_flags

schedule

start_date

start_time

tags

window

Server

args

count

days_in_cycle

disabled

dir

end_date

end_time

holidays

max_at_once

path

run_days

run_flags

schedule

start_date

start_time

tags

throttle

window

Service

args

days_in_cycle

disabled

end_date

end_time

holidays

run_days

schedule

start_date

start_time

tags

Parameter Descriptions

While parameter names are not sensitive to case, parameters values can be case-sensitive.

The following table lists the different parameters available for use in ttchron.ini, the sections in which you can use, and a description of the parameter. If a default value exists for a parameter, the table includes it with the parameter name.

TTChron Parameter Descriptions
ParameterSection AvailabilityDescription

cycle_freq=1

(Deprecated in TTChron Version 7.7 and higher.

Global

Sets the frequency (in seconds) with which TTChron checks whether it is time to start or stop a server or program. Older versions of TTChron require this parameter.

TTChron Version 7.7 and higher rely on timers to trigger starts and stops and no longer requires the cycle_freq parameter.

svc_freq=5

(Deprecated in TTChron Version 7.7 and higher.

Global

Sets the frequency (in seconds) with which TTChron monitors the status of a server. Older versions of TTChron require this parameter.

TTChron Version 7.7 and higher continuously monitors the status of a server and no longer requires the svc_freq parameter.

logging=ALWAYS

Global

Sets how TTChron logs its activity. Available values include:

  • ALWAYS: Logs all TTChron scheduling activity and errors to a log file
  • NEVER: Produces no log file.

If this entry is not included, TTChron log errors only. This parameter’s available values are not sensitive to case.

TTChron generates a new log file daily. All log files older than ten days are purged from the system.

fkill_delay=120

Global

After TTChron shuts down a process, it waits the length of time (in seconds) set in fkill_delay, and then verifies that the process has ended. If the process is still running (i.e., hung), TTChron forces the hung process to stop using the fkill application.

window=MIN

Global

Job

Server

Sets how TTChron starts a process in a window. If included in a specific section, it overrides the global setting for that particular process. Values include:

  • NORM or NORMAL: Processes launch in normal-sized desktop windows
  • MAX or MAXIMIZE: Processes launch in maximized windows
  • MIN or MINIMIZE: Processes launch in minimized windows

This parameter’s available values are not sensitive to case.

Dates

Holiday

Sets a holiday date for a Holiday section (format M/D/YYYY), where M is the one or two-digit month, D is the one or two-digit day, and YYYY is the four-digit year.

holidays

Job

Server

Service

Name of the Holiday section that determines the program’s run days. Do not use brackets. If included in a section, the relevant program does not run on the days listed in the referenced Holiday section.

Example:

holidays=Holidays-UK

Note

TT Chron does not support holidays for sections that have a weekly session. Configuring holidays for sections that have a weekly session can result in TT Chron bringing a scheduled process down at incorrect times.

schedule

Job

Server

Service

Schedules days and times for starting and stopping the job, service, or server program. For details on using this parameter and an example of its use, refer to Using the schedule Parameter.

start_date

Job

Server

Service

Sets the effective start date (Format MM/DD/YYYY) for the section’s program. TTChron does not run a job or service before its start_date. This parameter overrides any schedule settings.

Example:

start_date=06/01/2008

end_date

Job

Server

Service

Sets the effective end date (Format MM/DD/YYYY) for the section’s program. TTChron does not run a job or service after its end_date. This parameter overrides any schedule settings

Example:

end_date=07/01/2010

disabled

Job

Server

Service

Disables the entire program section and prevents TTChron from starting the section’s program. This parameter has no assigned value. TTChron continues to monitor the program but considers the program turned off. While disabled, if the program is manually started, TTChron shuts it down. When you remove disabled from the section, TTChron manages the program as configured in the section.

TTChron Version 7.7 and higher contains an enhancement that will automatically close a disabled service or server that is� manually launched. Previous versions only affected disabled services.

Example:

disabled

tags

Job

Server

Service

Sets a section identifier. Separate multiple section identifiers with a comma (,). TTK uses the value(s) of tags to identify ttchron.ini sections. You can add any value to tags to identify a section. This parameter is not sensitive to case.

By default, each section is assigned the exchange-flavor selected during installation of the TT Gateway (e.g., Eurex-B, CME-C, etc.).

path

Job

Server

Required. Sets the absolute pathname of the program to run.

Example:

path=c:ttbinhouse.exe

args

Job

Server

Service

Sets arguments that you want TTChron to use when it starts the specified process. You can use any command line arguments that the specified process allows.

Example:

args=Parm1 p2

run_days

Job

Server

Service

Conditional. If you do not use the schedule parameter, you must use run_days, and start_time. In Server and Service sections, you must also use days_in_cycle and end_time.

Designates the days of the week on which TTChron starts the program.

A string of up to 7 digits: 0, 1, 2, 3, 4, 5, 6, where 0 indicates Sunday, 1 indicates Monday, etc.

Example:

run_days=135

run_flags

Job

Server

Configures how TTChron starts processes. Available values include:

  • DETACHED: TTChron starts the process invisibly. Detached processes run in the background of the system and do not have a console.
  • INHERIT: TTChron starts the process as a child of TTChron. If TTChron has a command prompt open, this process runs in the same window. If TTChron is stopped, so are its child processes.
  • CONSOLE: TTChron starts the process in its own command window.

If run_flags is not specified, the default setting is DETACHED. This parameter’s available values are not sensitive to case.

Example:

run_flags=CONSOLE

Note

By default, TTChron installs as a Windows service with the option Allow Interaction with Desktop selected. If you remove this option, TTChron cannot start processes on the desktop, and no matter how you configure run_flags, the process behaves as if run_flags is set to DETACHED.

start_time

Job

Server

Service

Conditional. If you do not use the schedule parameter, you must use run_days, and start_time. In Server and Service sections, you must also use days_in_cycle and end_time. Sets the time (in military format, HH:MM) at which TTChron begins the program.

Example:

start_time=07:00

dir

Job

Server

Specifies the working directory from which the program is run.

Example:

dir=c:ttdatafiles

count

Server

Indicates how many instances of the given process TTChron must start up and maintain (keep running) when ttchron.ini schedules the program to run.

For an example, refer to the parameter max_at_once.

Example:

count=20

max_at_once

Server

Sets the maximum number of process instances that TTChron can start at any one time (i.e., Order Routers). TTChron uses this parameter with count and throttle parameters, to spawn large numbers of processes over a staggered time frame.

Example:

count=20

max_at_once=5

throttle=5

Using these parameter settings, TTChron starts up five process instances, waits five seconds and continues this process (starting sets of instances followed by a delay) until 20 instances are running. TTChron then monitors the processes to ensure that all 20 are running according to the schedule parameter.

throttle

Server

Sets the delay (in seconds) between starting up sets of process instances. max_at_once sets the number of processes in each set.

For an example, refer to the parameter max_at_once.

end_time

Server

Service

Format HH:MM – In military time, the time of day to terminate the service.

Example:

end_time=07:00

days_in_cycle

Server

Service

Indicates how many days are in each service run cycle. This equals any value from 1 to 7.

days_in_cycle is used in conjunction with the run_days, start_time, and end_time parameters. On the days set in run_days, TTChron starts a service according to the time set in start_time. TTChron then runs the service for the number of days equal to the value set in days_in_cycle. Once the service has completed this cycle, TTChron terminates the service at the time set in end_time.

Example:

days_in_cycle=5

Using the schedule Parameter

By using the schedule parameter, you can configure a program to run on a weekly cycle at different times on different days. In Server and Service sections, you can also configure the program to run for different lengths of time. Thus:

  • In a Job section, using schedule, you can set a program to execute on Monday at 7:00 AM and again at 5:00 PM on Friday.
  • In a Server or Service section, using schedule, you can set a program to start on Monday at 7:00 AM, run for three days, and then stop at 5:00 PM on Thursday.

However, you cannot set a program to start or stop more than once on the same day. Thus, you cannot run a program at 10 AM and at 3 PM on the same day.

Because schedule overrides any other start and stop information in the section, using it helps simplify your ttchron.ini sections such that:

  • If you use schedule in a Job section, you do not need to include start_time or run_days.
  • If you use schedule in a Server or Service section, you do not need to include start_time, run_days, days_in_cycle, and end_time.

The schedule parameter uses the following syntax:

Example Schedule Parameter

DAY@HH:MM-HH:MM/N;DAY@HH:MM-HH:MM/N; ...

Where:

  • DAY is a string of one to seven characters: S, M, T, W, R, F, and B, each representing a day of the week. S signifies Sunday, M is Monday, through B for Saturday.
  • HH:MM is the start and end time (military time). The first time is the start and the second time is the end. Because Job Sections list parameters for programs not monitored by TTChron (these programs are only started by it), do not include an end time. However, you must include an end time when adding schedule to a Server or Service Section.
  • N indicates how many days the program runs before being shut off. By default, TTChron behaves as if set to 1. Because Job Sections list parameters for programs not monitored by TTChron (these programs are only started by it), do not include the N parameter in a Job Section. However, you must include the N parameter when adding schedule to a Server or Service Section.
  • ; separates multiple time schedule instances for the same program. If you have only one time schedule, do not include the semi-colon.