Administrator's Reference

DEFINE SCHEDULE (Define a Client or an Administrative Command Schedule)

Use the DEFINE SCHEDULE command to create a new schedule. The DEFINE SCHEDULE command takes two forms, depending on whether the schedule applies to client operations or administrative commands. The syntax and parameters for each form are defined separately.

Restrictions:

Not all clients can run all scheduled operations, even though ADSM allows you to define the schedule on the server and associate it with the client. For example, a Windows 3.1 client cannot run a schedule when the action is to restore or retrieve files, issue a command, or run an executable script (called a macro by ADSM). An executable script is also known as a command file, a batch file, or a script on different client operating systems. A Macintosh client cannot run a schedule when the action is to restore or retrieve files, or run an executable script.
You cannot schedule MACRO or QUERY ACTLOG commands.

Defining Client Schedules: Use the DEFINE SCHEDULE command to create a new schedule for client operations such as backing up or archiving clients in a specified policy domain.

A schedule determines:

The automatic function to be performed, for example, an incremental backup
A startup window that indicates a time range during which the operation can begin
The time period between startup windows

For each schedule, a startup window is specified. The startup window is the time period during which the schedule must be initiated. The schedule will not necessarily complete execution within this window. If the schedule needs to be retried for any reason, the retry attempt must begin before the startup window elapses, or the operation does not restart.

After you define a schedule, use the DEFINE ASSOCIATION command to associate specific clients with the schedule so that they will execute it.

Privilege Class

To define a client schedule, you must have system privilege, unrestricted policy privilege, or restricted policy privilege for the policy domain to which the schedule belongs. To define an administrative command schedule, you must have you must have system privilege.

Syntax for Defining Client Schedules

>>-DEFine SCHedule--domainname--schedulename-------------------->
 
    .-Type--=--Client--.
>---+------------------+--+------------------------------+------>
                          '-DESCription--=--description--'
 
    .-ACTion--=--Incremental------.
>---+-----------------------------+----------------------------->
    '-ACTion--=--+-Incremental-+--'
                 +-Selective---+
                 +-Archive-----+
                 +-REStore-----+
                 +-RETrieve----+
                 +-Command-----+
                 '-Macro-------'
 
>----+---------------------------+------------------------------>
     '-OPTions--=--optionstring--'
 
>---+--------------------------------+-------------------------->
    |         (1)                    |
    '-OBJects-------=--objectstring--'
 
    .-PRIority--=--5---------------.
>---+------------------------------+---------------------------->
    '-PRIority--=--priorityvalue---'
 
     .-STARTDate--=--currentdate--.
>----+----------------------------+----------------------------->
     '-STARTDate--=--startdate----'
 
     .-STARTTime--=--currenttime--.
>----+----------------------------+----------------------------->
     '-STARTTime--=--starttime----'
 
     .-DURation--=--1---------------.
>----+------------------------------+--------------------------->
     '-DURation--=--durationvalue---'
 
     .-DURUnits--=--Hours-----------.
>----+------------------------------+--------------------------->
     '-DURUnits--=--+-Minutes----+--'
                    +-Hours------+
                    +-Days-------+
                    '-INDefinite-'
 
     .-PERiod--=--1-------------.  .-PERUnits--=--Days---------.
>----+--------------------------+--+---------------------------+>
     '-PERiod--=--periodvalue---'  '-PERUnits--=--+-Hours---+--'
                                                  +-Days----+
                                                  +-Weeks---+
                                                  +-Months--+
                                                  +-Years---+
                                                  '-Onetime-'
 
     .-DAYofweek--=--ANY------------.
>----+------------------------------+--------------------------->
     '-DAYofweek--=--+-ANY-------+--'
                     +-WEEKDay---+
                     +-WEEKEnd---+
                     +-SUnday----+
                     +-Monday----+
                     +-TUesday---+
                     +-Wednesday-+
                     +-THursday--+
                     +-Friday----+
                     '-SAturday--'
 
     .-EXPiration--=--Never---------------.
>----+------------------------------------+--------------------><
     '-EXPiration--=--+-Never----------+--'
                      '-expirationdate-'

1	The OBJECTS parameter is optional when ACTION=INCREMENTAL, but is required for other actions.

Parameters for Defining Client Schedules

domainname

Specifies the name of the policy domain to which this schedule belongs. This parameter is required.

schedulename

Specifies the name of the schedule to be defined. This parameter is required. The maximum length of the name is 30 characters.

Type=Client

Specifies that this schedule defines a client schedule. This parameter is optional. The default value is CLIENT. Administrative command schedules are defined by specifying TYPE=ADMINISTRATIVE.

DESCription=description

Specifies a description of the schedule. This parameter is optional. The maximum length of the description is 255 characters. The description must be enclosed in quotation marks if it contains any blank characters. The default is no description.

ACTion=actionvalue

Specifies the action that occurs when this schedule is executed. This parameter is optional. The default value is INCREMENTAL. Possible values are:

Incremental: Specifies that this schedule initiates the backup of any files that have changed since the last backup and for which the specified time between backups has elapsed. In addition, this schedule initiates the backup of any files for which a backup does not exist. Incremental also backs up any file where all existing backups may have expired.
Selective: Specifies that this schedule backs up only the files specified with the OBJECTS parameter.
Archive: Specifies that this schedule archives the files specified with the OBJECTS parameter.
REStore: Specifies that this schedule restores the files specified with the OBJECTS parameter.
RETrieve: Specifies that this schedule retrieves the files specified with the OBJECTS parameter.
Command: Specifies that the action is to be a client operating system command string specified with the OBJECTS parameter.
Macro: Specifies that a macro whose file name is specified with the OBJECTS parameter is to be executed.

OPTions=optionstring

Specifies options that are supplied to the DSMC command at the time the schedule is executed. Only those options that are valid on the DSMC command line may be specified for this parameter. This parameter is optional.

You can specify most options from the client's option file. Each option is preceded by a hyphen and delimited with a space. The option string must be enclosed in quotation marks if it contains any blank characters.

When applicable, these options override the options specified by a client node after it has successfully contacted the server.

Do not include the following options because they have no effect on the client's execution of the scheduled command:

MAXCMDRETRIES

QUERYSCHEDPERIOD

RETRYPERIOD

SCHEDLOGNAME

SCHEDMODE

TCPCLIENTADDRESS

TCPCLIENTPORT

OBJects=objectstring

Specifies the objects for which the specified action is performed. This parameter is required except when ACTION=INCREMENTAL. The allowed objects depend on the action you specify with the ACTION parameter and the operating system used by the clients associated with the schedule. To select all filespaces or drives, explicitly list them in the objectstring. Entering an asterisk will cause the backup to only occur for the directory where the scheduler was started.

When you specify ACTION=INCREMENTAL and do not specify any objects with this parameter, the DSMC command is invoked without specified objects and attempts to process objects as defined in the client's option file.

You can specify more than one object by separating the objects with commas, with no intervening spaces. If the value for this parameter contains any blank characters or a string of file names, it must be enclosed in quotation marks. If multiple file names are specified, each must be surrounded by its own pair of double quotes, with one pair of single quotes surrounding the file list. For example, to specify the following file strings:

C:\FILE 2,D:\A B C,E:\MY TEST FILE, enter:

OBJECTS='"C:\FILE 2","D:\A B C",E:\MY TEST FILE"'
D:\TEST FILE, enter:

OBJECTS="D:\TEST FILE"

PRIority=priorityvalue

Specifies the priority value for a schedule. This parameter is optional. You can specify an integer in the range of 1-10, inclusive, with 1 being the highest priority and 10 being the lowest. The default value is 5.

If two or more schedules for a given client have the same window start time, this value determines the order of execution. The schedule with the highest priority starts first. For example, a schedule with PRIORITY=3 starts before a schedule with PRIORITY=5.

STARTDate=startdate

Specifies the date for the beginning of the window in which the schedule is first executed. This parameter is optional. The default value is the current date. This parameter is used in conjunction with the STARTTIME parameter to specify when the initial startup window begins.

Possible values are:

MM/DD/YYYY: Specifies the date for the beginning of the startup window in MM/DD/YYYY format (for example, 01/31/1997).
TODAY: Specifies that the beginning of the startup window is on the current date.
TODAY+numdays or +numdays: Specifies that the beginning of the startup window is a specific number of days after the current date. The maximum value for the number of days is 9999.
For example, to specify that the beginning of the initial startup window is 3 days from now, you can specify STARTDATE=TODAY+3 or STARTDATE=+3.

STARTTime=starttime

Specifies the time for the beginning of the window in which the schedule is first executed, in HH:MM format. This parameter is optional. The default value is the current time. This parameter is used in conjunction with the STARTDATE parameter to specify when the initial startup window begins.

Possible values are:

HH:MM:SS

Specifies the time for the beginning of the startup window in HH:MM:SS format (for example, 12:33:28).

NOW

Specifies that the beginning of the startup window is at the current time on the specified start date.

NOW+numhours:numminutes or +numhours:numminutes

Specifies the time for the beginning of the startup window is at the current time plus a specific number of hours (and, optionally, minutes) on the specified start date.

For example, if you issue the DEFINE SCHEDULE command at 5:00 with STARTTIME=NOW+02:00 or STARTTIME=+02:00, the beginning of the initial startup window is at 7:00.

NOW-numhours:numminutes or -numhours:numminutes

Specifies the time for the beginning of the startup window is at the current time minus a specific number of hours (and, optionally, minutes) on the specified start date.

For example, if you issue the DEFINE SCHEDULE command at 5:00 with STARTTIME=NOW-02:00 or STARTTIME=-02:00, the beginning of the initial startup window is at 3:00.

DURation=durationvalue

Specifies the number of units that define the length of the startup window. This parameter is optional. This value must be in the range of 1-999, inclusive. The default value is 1.

This parameter is used in conjunction with the DURUNITS parameter to specify the length of the startup window. For example, if you specify DURATION=20 and DURUNITS=MINUTES, the schedule must be started within 20 minutes of the start date and start time. The default value for the length of the startup window is 1 hour. The duration of the window must be shorter than the period between windows.

This value is ignored if you specify DURUNITS=INDEFINITE.

DURUnits=durunitsvalue

Specifies the time units used to determine the duration of the window in which the schedule can start. This parameter is optional. The default value is HOURS.

This parameter is used in conjunction with the DURATION parameter to specify how long the startup window remains open to execute the schedule. For example, if DURATION=20 and DURUNITS=MINUTES, the schedule must be started within 20 minutes of the start date and start time. The default value for the length of the startup window is 1 hour. The duration of the window must be shorter than the period between windows. Possible values are:

Minutes: Specifies that the duration of the window is defined in minutes.
Hours: Specifies that the duration of the window is defined in hours.
Days: Specifies that the duration of the window is defined in days.
INDefinite: Specifies that the startup window has an indefinite duration. The schedule can run any time after the scheduled start time, until the schedule expires. You cannot specify DURUNITS=INDEFINITE unless you also specify PERUNITS=ONETIME.

PERiod=periodvalue

Specifies the length of time between startup windows for this schedule. This parameter is optional. You can specify an integer in the range of 1-999, inclusive. The default value is 1.

This parameter is used in conjunction with the PERUNITS parameter to specify the period between startup windows. For example, if you specify PERIOD=5 and PERUNITS=DAYS (assuming that DAYOFWEEK=ANY), the operation is scheduled every 5 days after the initial start date and start time. The period between startup windows must exceed the duration of each window. The default value for the length of time between startup windows is 1 day.

This value is ignored if you specify PERUNITS=ONETIME.

PERUnits=perunitsvalue

Specifies the time units used to determine the period between startup windows for this schedule. This parameter is optional. The default value is DAYS.

This parameter is used in conjunction with the PERIOD parameter to specify the period between startup windows. For example, if you specify PERIOD=5 and PERUNITS=DAYS (assuming that DAYOFWEEK=ANY), the operation is scheduled every 5 days after the initial start date and start time. The period between startup windows must exceed the duration of each window. The default value for the length of time between startup windows is 1 day. Possible values are:

Hours: Specifies that the time between startup windows for the schedule is in hours.
Days: Specifies that the time between startup windows for this schedule is in days.
Weeks: Specifies that the time between startup windows for the schedule is in weeks.
Months: Specifies that the time between startup windows for the schedule is in months.
Years: Specifies that the time between startup windows for the schedule is in years.
Onetime: Specifies that the schedule executes only once. This value overrides the value specified for the PERIOD parameter.

DAYofweek=dayofweekvalue

Specifies the day of the week on which the startup window begins. This parameter is optional. If the beginning of the calculated startup window falls on a day that does not correspond with your value for the DAYOFWEEK parameter, the startup window will be shifted forward in 24-hour increments until the DAYOFWEEK parameter is satisfied.

If you select a value for DAYOFWEEK other than ANY, and depending on the values for PERIOD and PERUNITS, schedules may not be executed when you would expect. Use the QUERY EVENT command to project when schedules will be executed and thereby ensure that the desired result is achieved. The default value is ANY. Possible values are:

ANY: Specifies that the startup window can begin on any day of the week.
WEEKDay: Specifies that the startup window can begin on Monday, Tuesday, Wednesday, Thursday, or Friday.
WEEKEnd: Specifies that the startup window can begin on Saturday or Sunday.
SUnday: Specifies that the startup window begins on Sunday.
Monday: Specifies that the startup window begins on Monday.
TUesday: Specifies that the startup window begins on Tuesday.
Wednesday: Specifies that the startup window begins on Wednesday.
THursday: Specifies that the startup window begins on Thursday.
Friday: Specifies that the startup window begins on Friday.
SAturday: Specifies that the startup window begins on Saturday.

EXPiration=expirationdate

Specifies the date on which this schedule is no longer used, in MM/DD/YYYY format. This parameter is optional. The default value is NEVER. Possible values are:

Never: Specifies that the schedule never expires.
expirationdate: Specifies the date on which this schedule is no longer used, in MM/DD/YYYY format. If you specify an expiration date, the schedule expires at 23:59:59 on the specified date.

Defining Administrative Command Schedules: Use the DEFINE SCHEDULE command to create a new schedule for the execution of an administrative command.

A schedule determines:

The administrative command to run
A startup window that indicates a time range during which the operation can begin
The time period between startup windows

For each schedule, a startup window (or duration) is specified. The startup window is the time period during which the schedule must be initiated. The schedule will not necessarily complete execution within this window. If the server is not running when this window starts, but is started before the end of the defined window is reached, the schedule will run when the server is restarted.

Syntax for Defining Administrative Command Schedules

>>-DEFine SCHedule--schedulename---+--------------------------+->
                                   '-Type--=--Administrative--'
 
                            .-ACTIVE--=--No----.
>---CMD--=--commandstring---+------------------+---------------->
                            '-ACTIVE--=--Yes---'
 
>----+------------------------------+--------------------------->
     '-DESCription--=--description--'
 
    .-PRIority--=--5---------------.
>---+------------------------------+---------------------------->
    '-PRIority--=--priorityvalue---'
 
     .-STARTDate--=--currentdate--.
>----+----------------------------+----------------------------->
     '-STARTDate--=--startdate----'
 
     .-STARTTime--=--currenttime--.
>----+----------------------------+----------------------------->
     '-STARTTime--=--starttime----'
 
     .-DURation--=--1---------------.
>----+------------------------------+--------------------------->
     '-DURation--=--durationvalue---'
 
     .-DURUnits--=--Hours-----------.
>----+------------------------------+--------------------------->
     '-DURUnits--=--+-Minutes----+--'
                    +-Hours------+
                    +-Days-------+
                    '-INDefinite-'
 
     .-PERiod--=--1-------------.  .-PERUnits--=--Days---------.
>----+--------------------------+--+---------------------------+>
     '-PERiod--=--periodvalue---'  '-PERUnits--=--+-Hours---+--'
                                                  +-Days----+
                                                  +-Weeks---+
                                                  +-Months--+
                                                  +-Years---+
                                                  '-Onetime-'
 
     .-DAYofweek--=--ANY------------.
>----+------------------------------+--------------------------->
     '-DAYofweek--=--+-ANY-------+--'
                     +-WEEKDay---+
                     +-WEEKEnd---+
                     +-SUnday----+
                     +-Monday----+
                     +-TUesday---+
                     +-Wednesday-+
                     +-THursday--+
                     +-Friday----+
                     '-SAturday--'
 
     .-EXPiration--=--Never---------------.
>----+------------------------------------+--------------------><
     '-EXPiration--=--+-Never----------+--'
                      '-expirationdate-'

Parameters for Defining Administrative Command Schedules

schedulename

Specifies the name of the command schedule to be defined. This parameter is required. The maximum length of the name is 30 characters.

Type=Administrative

Specifies that this schedule defines an administrative command (as opposed to a client command). This parameter is optional. An administrative command is assumed if the CMD parameter is specified.

CMD=commandstring

Specifies the actual administrative command that is to be scheduled. The maximum length of the command is 512 characters. The administrative command must be enclosed in quotation marks if it contains any blank characters. This parameter is required for administrative command schedules.

Note:

Redirection characters cannot be specified with this parameter.

ACTIVE=activevalue

Specifies if the defined administrative command is immediately eligible for scheduled execution. This parameter is optional. The default value is NO. The administrative command schedule must be set to the active state with the UPDATE SCHEDULE command to be made eligible for scheduled execution. A defined administrative command schedule will not be executed unless it is set to the active state. Possible values are:

YES: Specifies that the defined administrative command is eligible for scheduled execution.
NO: Specifies that the defined administrative command is not eligible for scheduled execution.

DESCription=description

PRIority=priorityvalue

If two or more administrative schedules have the same window start time, this value determines the order of execution. The schedule with the highest priority starts first. For example, a schedule with PRIORITY=3 starts before a schedule with PRIORITY=5.

STARTDate=startdate

Possible values are:

MM/DD/YYYY: Specifies the date for the beginning of the startup window in MM/DD/YYYY format (for example, 01/31/1997).
TODAY: Specifies that the beginning of the startup window is on the current date.
TODAY+numdays or +numdays: Specifies that the beginning of the startup window is a specific number of days after the current date. The maximum value for the number of days is 9999.
For example, to specify that the beginning of the initial startup window is 3 days from now, you can specify STARTDATE=TODAY+3 or STARTDATE=+3.

STARTTime=starttime

Possible values are:

HH:MM:SS

Specifies the time for the beginning of the startup window in HH:MM:SS format (for example, 12:33:28).

NOW

Specifies that the beginning of the startup window is at the current time on the specified start date.

NOW+numhours:numminutes or +numhours:numminutes

Specifies the time for the beginning of the startup window is at the current time plus a specific number of hours (and, optionally, minutes) on the specified start date.

For example, if you issue the DEFINE SCHEDULE command at 5:00 with STARTTIME=NOW+02:00 or STARTTIME=+02:00, the beginning of the initial startup window is at 7:00.

NOW-numhours:numminutes or -numhours:numminutes

Specifies the time for the beginning of the startup window is at the current time minus a specific number of hours (and, optionally, minutes) on the specified start date.

For example, if you issue the DEFINE SCHEDULE command at 5:00 with STARTTIME=NOW-02:00 or STARTTIME=-02:00, the beginning of the initial startup window is at 3:00.

DURation=durationvalue

Specifies the number of units that define the length of the startup window. This parameter is optional. This value must be in the range of 1-999, inclusive. The default value is 1.

This value is ignored if you specify DURUNITS=INDEFINITE.

DURUnits=durunitsvalue

Specifies the time units used to determine the duration of the window in which the schedule can start. This parameter is optional. The default value is HOURS.

Minutes: Specifies that the duration of the window is defined in minutes.
Hours: Specifies that the duration of the window is defined in hours.
Days: Specifies that the duration of the window is defined in days.
INDefinite: Specifies that the startup window has an indefinite duration. The schedule can run any time after the scheduled start time, until the schedule expires. You cannot specify DURUNITS=INDEFINITE unless you also specify PERUNITS=ONETIME.

PERiod=periodvalue

Specifies the length of time between startup windows for this schedule. This parameter is optional. You can specify an integer in the range of 1-999, inclusive. The default value is 1.

This value is ignored if you specify PERUNITS=ONETIME.

PERUnits=perunitsvalue

Specifies the time units used to determine the period between startup windows for this schedule. This parameter is optional. The default value is DAYS.

Hours: Specifies that the time between startup windows for the schedule is in hours.
Days: Specifies that the time between startup windows for this schedule is in days.
Weeks: Specifies that the time between startup windows for the schedule is in weeks.
Months: Specifies that the time between startup windows for the schedule is in months.
Years: Specifies that the time between startup windows for the schedule is in years.
Onetime: Specifies that the schedule executes only once. This value overrides the value specified for the PERIOD parameter.

DAYofweek=dayofweekvalue

Specifies the day of the week on which the startup window begins. If the beginning of the calculated startup window falls on a day that does not correspond with your value for the DAYOFWEEK parameter, the startup window will be shifted forward in 24-hour increments until the DAYOFWEEK parameter is satisfied.

If you select a value for DAYOFWEEK other than ANY, depending on the values for PERIOD and PERUNITS, schedules may not be executed when you would expect. Use the QUERY EVENT TYPE=ADMINISTRATIVE command to project when schedules will be executed and thereby ensure that the desired result is achieved.

The default value is ANY. Possible values are:

ANY: Specifies that the startup window can begin on any day of the week.
WEEKDay: Specifies that the startup window can begin on Monday, Tuesday, Wednesday, Thursday, or Friday.
WEEKEnd: Specifies that the startup window can begin on Saturday or Sunday.
SUnday: Specifies that the startup window begins on Sunday.
Monday: Specifies that the startup window begins on Monday.
TUesday: Specifies that the startup window begins on Tuesday.
Wednesday: Specifies that the startup window begins on Wednesday.
THursday: Specifies that the startup window begins on Thursday.
Friday: Specifies that the startup window begins on Friday.
SAturday: Specifies that the startup window begins on Saturday.

EXPiration=expirationdate

Specifies the date on which this schedule is no longer used, in MM/DD/YYYY format. This parameter is optional. The default value is NEVER. Possible values are:

Never: Specifies that the schedule never expires.
expirationdate: Specifies the date on which this schedule is no longer used, in MM/DD/YYYY format. If you specify an expiration date, the schedule expires at 23:59:59 on the specified date.

Examples

Task 1

Define a schedule named MONTHLY_BACKUP that initiates an incremental backup of all associated nodes. Because the specified start date, May 1, 1997 (05/01/1997), is a Thursday and does not match the specified day of the week (Sunday), the initial startup window begins on the first Sunday after May 1, 1997 (05/01/1997). The startup windows for this schedule extend from 01:00 through 03:00. This monthly schedule initiates backup of c: and d: file spaces for all associated nodes.

Command:: define schedule standard monthly_backup description="Monthly Backup of c: and d: drives" objects="c:\* d:\*" startdate=05/01/1997 starttime=01:00 duration=2 durunits=hours period=1 perunits=months dayofweek=sunday

Task 2

Define a schedule named WEEKLY_BACKUP that initiates an incremental backup of all associated nodes. The initial startup window for this schedule extends from 23:00 on Saturday, June 7, 1997 (06/07/1997), to 03:00 on Sunday, June 8, 1997 (06/08/1997). Subsequent windows begin at 23:00, every Saturday. No messages are returned to the client node when this schedule is executed.

Command:: define schedule employee_records weekly_backup startdate=06/07/1997 starttime=23:00 duration=4 durunits=hours perunits=weeks dayofweek=saturday options=-quiet

Task 3

Define a schedule named BACKUP_ARCHIVEPOOL that backs up the primary storage pool ARCHIVEPOOL to the copy storage pool RECOVERYPOOL. The backup runs at 8 p.m. every two days.

Command:: define schedule backup_archivepool type=administrative cmd="backup stgpool archivepool recoverypool" active=yes starttime=20:00 period=2

Related Commands

Table 61. Commands Related to DEFINE SCHEDULE

Command Description
COPY SCHEDULE Creates a copy of an existing schedule.
DEFINE ASSOCIATION Associates one or more clients with a schedule.
DELETE SCHEDULE Deletes a schedule from the database.
QUERY EVENT Displays information about scheduled and completed events for selected clients.
QUERY SCHEDULE Displays information about one or more schedules.
SET MAXCMDRETRIES Specifies the maximum number of retries after a failed attempt to execute a scheduled command.
SET MAXSCHEDSESSIONS Specifies the maximum number of client/server sessions available for processing scheduled work.
SET RETRYPERIOD Specifies the time between retry attempts by the client scheduler.
UPDATE SCHEDULE Changes the attributes of a schedule.

Command	Description
COPY SCHEDULE	Creates a copy of an existing schedule.
DEFINE ASSOCIATION	Associates one or more clients with a schedule.
DELETE SCHEDULE	Deletes a schedule from the database.
QUERY EVENT	Displays information about scheduled and completed events for selected clients.
QUERY SCHEDULE	Displays information about one or more schedules.
SET MAXCMDRETRIES	Specifies the maximum number of retries after a failed attempt to execute a scheduled command.
SET MAXSCHEDSESSIONS	Specifies the maximum number of client/server sessions available for processing scheduled work.
SET RETRYPERIOD	Specifies the time between retry attempts by the client scheduler.
UPDATE SCHEDULE	Changes the attributes of a schedule.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]