Processing - Schedule
This page contains the values for scheduling parameters for the data source in the Client Manager service's configuration file.
Configuration file parameters are included below with the
Scheduling options apply only to
process commands that are initiated by the service. The three buttons described below, allow you to schedule
process commands runs at specific times of the day or a fixed amount of time after a
process command run terminates. Selecting one of the last two scheduling options enables the further controls specific to the enabled option(s).
Indicates that the service will not use any scheduling. The Client runs are manually launched from the Administrative Console.
Fixed delay (in seconds)
Indicates that this data source will use fixed delay scheduling, The input field specifies the delay (in seconds) between the time one Client run stops and another one begins for the same data source.
Daily (12 maximum)
Using the time picker control provided, select or type the time at which the service should start a
processcommand run. Then select the Add button. The time entered will appear in the Scheduled Times group. You can specify up to 12 times per day for scheduled
processruns. The times provided do not to be in chronological order, as they will be sorted when added to the list.
processcommand is already running at these times, the service will ignore the scheduling request.
When enabled, two input fields will be available to specify times. Using the two input fields, specify the start and end times of a fixed block of time during which the Client cannot run. This option is useful for operations, such as database backups, that can only take place when the Client is inactive. For example, if you want to back up the database daily between 1:00 a.m. and 2:30 a.m. daily, define a blackout period from 0:55 to 2:30. The extra 5 minutes ensures that the Client finishes any long transactions before the database backup begins.
Automatic Run Options
Process data source on service startup
Enable this option so the service will start a
process command run when the service is started.
Redefine data source when DMSII reorganization detected
Enable this option to continue processing without any interruptions after a DMSII reorganization, provided the reorganization did not affect the table layouts. When the exit code for a
process command indicates that a DMSII reorganization has been encountered, the service starts DBClntCfgServer run that executes a
redefine command to update the Client control tables. If the
redefine command determines that the DMSII reorganization did not affect the table layouts, the
redefine command returns an exit status of 0, and the service immediately launches a
redefine command determines that new scripts need to be generated, manual intervention is required. To have the Client automatically generate scripts in these cases, select Generate scripts after an automatic redefine in addition to this option.
There is no option to automate the running of a
reorganize command, as it is not a good idea to run this command without first looking at what it will do, as altering big tables can take a very long time and possibly fill the database log, which can trigger a massive rollback.
Generate scripts after an automatic redefine
Enable this option to have DBClntCfgServer run a
generate command when the exit code for a
process command specifies that a
generate command is required.
This command creates a new set of scripts for the tables of data sets that require them. This usually indicates that the data set has been added or that the reorganization caused the data set to be re-cloned.
If the exit status for the
redefine command indicates that a
generate command is required, this means that one or more data sets will be re-cloned. If you do not want clone commands automatically started, refrain from setting this option.