| Previous | TContents | YIndex |
> The only qualifiers allowed are the general SCHEDULE qualifiers, /CONFIRM and /LOG. N 4.4 Creating a calendar
F A calendar indicates what days to run or not to run a particular job. H Any number of calendars can be setup. Three calendars are automatically D set up when you install the system. They are STANDARD, WORKDAYS and 7 HOLIDAY all are in the system wide [DEFAULT] directory.
C The simplest way to create a calendar is to issue a command of the following format:
|
" / $ SCHEDULE CREATE/CALENDAR my_special_calendar |
/ Some of the commonly used qualifiers are listed
| Qualifier | &Description |
|---|---|
| " /COMMENT=``any text string'' | 9 Any descriptive text string. Up to 100 characters. |
| /WORKDAYS | Only workdays count. |
| /NOWORKDAYS | 1 All days count (i.e. a standard calendar.) |
> Information in the SCHEDULE database is grouped into C directories. Directories can be up to two levels deep (i.e. only a E top-level and a sub-level can be specified). The default top + level directory is your user name.
E If you are just starting to use SCHEDULE then you will most ; likely have to create your top level directory1.
B The format of the create command to make a top level directory is:
|
" - $ SCHEDULE CREATE/DIRECTORY [top_level_name] $ $ SCHEDULE CREATE/DIRECTORY [SMITH] |
F To tell the system the current default SCHEDULE directory to & use just define the following logical.
|
" , $ DEFINE SCHEDULE_DEFAULT_DIRECTORY [SMITH] |
= If this is your user name then the above DEFINE statement is unnecessary.
| N N 1 If protection settings prevent you K from doing this then ask your system manager to do it for you. |
B The two most common commands to alter a job definition or add new B information to it, each with advantages for a given situation are listed below.
| Command | &Description |
|---|---|
| MODIFY/JOB | changes field parameters |
| EDIT/JOB | $ modifies any one of the lists |
| Previous | VNext | TContents | YIndex |