Previous | Contents | Index |
Inserts a startup definition.The inssta command inserts the designated startup definition using the filename.
inssta startup_name file_name [-options]
Alternateinsert -startup startup_name file_name
general options:
-[no]log
-[no]confirm
-hostname = target_node
#1 |
---|
Schedule> inssta options startup.txt |
-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.
Display a directory of startup files.The lssta command is used to display the directory of startup files.
lssta startup [-options]
Alternatedirectory -startup startup_file
general options:
-[no]log
-[no]confirm
-host =target_node
-noheading
-notrailing
-out=output_file
-template=/schedule_library/template_db.schedule
#1 |
---|
Schedule> lssta sch_test_startup |
-columns=number
The COLUMNS option specifies how many columns to use when listing just the item name. The default is four columns.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-noheading
The NOHEADING removes the heading information from the directory listing.-notrailing
The NOTRAILING removes the trailing information from the directory listing.-output=output_file
The OUTPUT option sends all output to a text file. Output can be printed or displayed as needed.-template=/schedule_library/template_db.schedule
The template option formats the directory output as it is defined in the template file /schedule_library/template_db.schedule . This output can be used for a variety of reasons and can be output to a file using the OUTPUT option . The supplied template file extracts all database information into a format suitable for insertion if desired.
Create a new startup file.The mksta command will add a new startup to the database.
mksta [-options] startup_name
Alternatecreate -startup [-options] startup_name
general options:
-[no]log
-[no]confirm
-hostname = target_node
#1 |
---|
Schedule> mksta /startup/new_start created /startup/new_start/ |
-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.
Rename a startup definition file.The mvsta command renames the startup from the old name to the designated new name.
mvsta old_name new_name [-options]
Alternaterename -startup old_name new_name
general options:
-[no]log
-[no]confirm
-hostname = target_node
#1 |
---|
Schedule> mvsta options options_2 |
-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.
Delete a startup file.The rmsta command deletes the designated startup file.
rmsta startup_name
Alternatedelete -startup startup_name
general options:
-[no]log
-[no]confirm
-hostname = target_node
#1 |
---|
Schedule> rmsta options |
-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.
12.5 General purpose commands
The general purpose commands includes all other commands used in
SCHEDULE that are not part of any other classification.
Displays all directory listings in the database.The directory -all displays the contents of the directories for the following database components:
Jobs
Calendars
Reports
Layouts
Startups
Variables
Schedule> directory -all
general options:
-columns=number
-host =target_node
-noheading
-notrailing
-out=output_file
-template=/schedule_library/template_db.schedule
#1 |
---|
Schedule> directory -all Job directory /boot calendar newfel newfelt new_a new_b new_c new_d run_job_a Total of 13 jobs Calendar directory /boot cal_1 cal_10 cal_11 cal_2 cal_5 cal_6 cal_7 cal_8 old Total of 13 calendars Layout Directory /boot default Total of 1 layout Startup Directory /boot user_default Total of 1 startup file Variable Directory /boot neato new turkey variable Total of 4 variables |
-columns=number
The COLUMNS option specifies how many columns to use when listing just the item name. The default is four columns.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-noheading
The NOHEADING removes the heading information from the directory listing.-notrailing
The NOTRAILING removes the trailing information from the directory listing.-output=output_file
The OUTPUT option sends all output to a text file. Output can be printed or displayed as needed.-template=/schedule_library/template_db.schedule
The template option formats the directory output as it is defined in the template file /schedule_library/template_db.schedule . This output can be used for a variety of reasons and can be output to a file using the OUTPUT option . The supplied template file extracts all database information into a format suitable for insertion if desired.
Exit from prompt mode.The exit command is used to exit from the SCHEDULE command prompt.
Schedule> exit
AlternateQUIT
[CTRL]+[Z]
#1 |
---|
Schedule> exit |
Display man page for a particular command or the overview.The man (or help) command displays a formatted man page for all commands used by SCHEDULE.
Schedule> man [command_name]
#1 |
---|
Schedule> man chjob chjob(1) chjob(1) chjob Modify a scheduled job definition. The chjob command will change any of the fields that make up a job definition. SYNOPSIS chjob [-options] job_name -section = field -section = field:value -section = (field,field,...) -section = (field:value,field:value,...) Alternate: . . . |
Manually replicate a directory throughout a workgroupThe PUSH command manually replicates a directory throughout a workgroup. This is usually performed when the data in a workgroup needs to be updated manually.
Schedule> push directory_name
general options:
-[no]log
-[no]confirm
-hostname = target_node
#1 |
---|
Schedule> push /workgroup_a/ |
-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.
Displays the command list or notices with substituted values of all preprocessor directives.The PREPROCESS displays the contents of the command list, substituting all values that are preprocessor directives. This can be used to test out the preprocessed values before the job is run or to output the processed list into a template or symbol table.
Schedule> preprocess job_name
-commands get
-confirm
-distribution
-[no]log
-hostname=target_node
-notices
-now=projected_time
-out=output_file
-env
-template=template_name
#1 |
---|
Schedule> preprocess job1 The date is 12-dec-2006 |
-commands
The COMMANDS option displays the commands list of the job with all preprocessor directives resolved.-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.-notices
The NOTICES option displays the notices list of the job with all preprocessor directives resolved.-now=projected_time
The NOW option displays the resulting value of the variable if the evaluation takes place in the time designated.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-output=output_file
The OUTPUT option sends all output to a text file. Output can be printed or displayed as needed.-env
Inserts the contents of the designated environmental variable into the command list of the job. The environmental variable is created using the more -env command.-template=/schedule_library/template_db.schedule
The template option formats the directory output as it is defined in the template file /schedule_library/template_db.schedule . This output can be used for a variety of reasons and can be output to a file using the OUTPUT option . The supplied template file extracts all database information into a format suitable for insertion if desired.
Put SCHEDULE into prompt mode. This is the default SCHEDULE command and is not necessary if the SCHEDULE command is entered without any paramaters or qualifiers.The prompt command allows SCHEDULE commands to be issued at a command prompt. This eliminates the necessity to enter the SCHEDULE command at the beginning of each SCHEDULE command. To exit the command prompt mode, enter EXIT or QUIT at the prompt.
general options:
-group_number=number
-primary_server=server
-hostname or /node=node
-default=default_directory
-reset_proxy
$ schedule prompt
#1 |
---|
$ schedule prompt Schedule> _ |
-group_number
The group_number qualifier will set the current group number of the session.-primary_server
The primary_server qualifier sets the current server of the session.-hostname or -node
Sets the current host or node of the current session.-default
Sets the default directory of the current session.-reset_proxy
When issued on a remote node, the reset qualifier brings up a prompt for user name and password which resets the proxy for the user.
Display current information on the SCHEDULE server.The server info command displays information about the server.
server info
#1 |
---|
Schedule> server info Version number = V5.0.28 Platform = Digital UNIX OSF1 V4.0, DEC 3000 - M300X Local node = dus Database node = dus Network nodes = Defined cluster = ,dus Active cluster = dus NRQ frame count = 91618 active count = 9 available count = 134 dispatch count = 203096 dispatch rate = 103/555/6039 Active threads = 5 Submit count = 0 Notify count = 0 Error count = 0 Channels SDE = 0/0/5/16/60/0/0 HST = 0/0/2/10/20/0/0 QD = 1/1/20/36/60/0/0 Networks = Tcp/Ip TCP/IP port id = 29347 QD Cache size = 139 Control flags = NoDECnetNetwork,NoCluster Controlled queues = B,H,I,K,L,P Peak working set = 36226 Current working set = 36226 Peak virtual size = 36226 Current priority = 0 Base priority = 0 Page faults = 381 Buffer I/O count = 1041 Direct I/O count = 1041 Cpu time = 000 00:06:04 Elapse time = 000 03:12:58 Cluster alias = Cluster lock group = A,1 File polling intrvl = 300 Disk polling intrvl = 300 Delay polling intrvl = 300 Stuck after intrvl = 300 History active = 1 Notify queue = user = root file = /schedule_library/schedule_notify.csh enabled = 1 priority = 14 P queue purge intrvl = 64800 Root dir owner = 65540 protection = 0 COM file extension = .SCHEDULE_SH Activity level = 0 |
Previous | Next | Contents | Index |