| Previous | Contents | Index |
The FIXED_SET_ID flag forces a job to always use a constant set id.
The operating system flags determine the operating system the job was created to run on: OPEN_VMS for an Open VMS job, UNIX for a UNIX job or NT for a Windows NT job.
The BLOCKED flag is used to block a job from running. The job will not run until this flag is set to the default noblocked.
The DELETE_UPON_COMPLETION flag is used to delete a job once it has completed and is removed from the P queue. The interval that it will remain in the P queue is normally 15 hours. When that time elapses, the job will be deleted from the database.
who specifies whether permissions are being defined for user(u), group(g) or all others(o).
permission specifies the permissions being defined. Read permission(r) allows reading. Write permission (w) allows the ability to write out a new version. Execute permission(x) allows execution of jobs and calendars, search of directories.
| Field | description |
|---|---|
| cpu_time | average number of seconds |
| elapse_time | average number of seconds |
| io_count | average number of buffered and direct I/O |
| num_count | number of times average is based on |
| Flag | Default | Description |
|---|---|---|
| [NO]HOLD | NOHOLD | Hold job in queue until released |
| [NO]KEEP | KEEP | Keep log file |
| [NO]DELETE | DELETE | Delete COM file |
| [NO]RESTART | NORESTART | Flag as restartable |
| [NO]RETAIN | NORETAIN | Flag as retained if delete_upon_completion is ON |
The format defines the way that environmental variables are output. The default output specification is: "$export %s=\" %s\" "" (ksh), "$setenv %s=\" %s\" "" (csh) which produces the following format style.
sc_account = "developm" |
Alternate output styles may be created by changing the format field.
Create a new job definition.The mkjob command will add a new job definition to the database.
mk [-options] job_name
Alternatecreate -job [-options] job_name
-resources=
[no]disk_space : (disk,number_of_blocks)
[no]file : file_spec
measured : (cpu_time,elapse_time,io_count, num_count)
estimated : (cpu_time,elapse_time,io_count)
-notify=
after_delay : delta_time
[no]submitted : ([username(s)][,mail (default)] [,broadcast])
[no]started
[no]delayed
[no]completed
[no]failed
[no]all : (modify all of the above together)
-process=
shell : text
node : node_name
cputime : delta_time
[no]hold
[no]keep
[no]restart
[no]delete
[no]log_file : file_spec
versions_of_log : number
name : text
parameter : (p1,p2,...p8)
user : username
variable : (var1=value, var2=value etc.)
-general=
comment : text
next_submit : date
last_start : date
last_submit : date
last_completed : date
restart_count : number
up_count : number
down_count : number
flags : [no]history,[no]fixed_set_id,[no]blocked, open_vms|unix|windowsnt
owner : uic
protection : (ugo+/-rwx)
status : number
[no]job_tag : text
startup_window : delta_time
execute_window : delta_time
[no]pre_com_file : file_spec|"I myfile.com"|$ command
[no]post_com_file : file_spec|"I myfile.com"|$ command
-rescheduling=
interval : delta_time
marked : letter_mark
monthly : (january...december,ordinal_number,day_of_week)
named : (monday...sunday,445...544,month_start...year_end)
none
calendar : calendar_name
time_of_day : [+/-]delta_time
general options:
-[no]log
-[no]confirm
-hostname = target_node
general options:
-from = prototype_name
-ignore_errors
| #1 |
|---|
Schedule> mk monthly_accounting
-resch=(interval=0:10,calendar=standard)
|
-general=comment:"any text string"
The COMMENT field is any useful description that you may want to add. This is an 80 character option.-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-node=node_name
The NODE option specifies what node (either local or remote) you want the operation performed on.endactions
The ENDACTIONS listing is a list of resource adjustments that are to be run upon completion of the job.-from=prototype_name
The FROM qualifier specifies the name of a job prototype that the new job will be based on. The properties of the prototype job will be adopted by the new job in the Windows client. The prototype job must be in the search path that traverses the local folder, the user's DEFAULT folder and the DEFAULT folder of the system.-general=down_count:number
The DOWN_COUNT field indicates the remaining number of times a job is to be executed. This is automatically updated. When zero is reached no further jobs will be submitted automatically.-general=execute_window:delta_time
The EXECUTE_WINDOW specifies the interval in which a job is allowed to have all requirements met and execute. This is the time it takes a job to move from scheduling queue C or D to M. Any job that exceeds this interval will have none of its initiates activated. This interval is designed to prevent a run away catch up mode from happening if the system is down for a long period. The interval time check is suppressed if this field is set to zero (i.e. the window is infinite).-general=flags:history|fixed_set_id
-general=flags:nohistory|fixed_set_id
-general=flags:open_vms|unix|nt
-general=flags:[no]blocked
-general=flags:[no]delete_upon_completion
The HISTORY flag indicates whether or not history data is to be recorded for this job. A job that runs very frequently generates a lot of history data. To reduce the growth of this history file specify the NOHISTORY flag.The FIXED_SET_ID flag forces a job to always use a constant set id.
The operating system flags determine the operating system the job was created to run on: OPEN_VMS for an Open VMS job, UNIX for a UNIX job or NT for a Windows NT job.
The BLOCKED flag is used to block a job from running. The job will not run until this flag is set to the default noblocked.
The DELETE_UPON_COMPLETION flag is used to delete a job once it has completed and is removed from the P queue. The interval that it will remain in the P queue is normally 15 hours. When that time elapses, the job will be deleted from the database. The job will not be deleted if the retain_on_error submit flag is on.
-general=job_tag:text
The JOB_TAG field specifies the initial value for the SET_TAG value when the job is first entered into the scheduling queues.-general=last_completed:date
The LAST_COMPLETED field indicates when a job was last completed. This is automatically updated.-general=last_start:date
The LAST_START field indicates the last time a job was started. This is automatically updated.-general=last_submit:date
The LAST_SUBMIT field indicates when a job was last submitted. This is automatically updated.-general=next_submit:date
The NEXT_SUBMIT field allows the user to specify the next job start date. A job will start on its own only if this date and time are set.-general=owner:uic
The OWNER field indicates the owner user id and group id code for the job.-general=post_com_file:file_spec | "I myfile.com"| $ unix command
-general=nopost_com_file
The POST_COM_FILE field indicates that a COM file is to be executed after the scheduled job has run to completion. The COM file and the job are run in the same batch job.The "I" indicates that the contents of "myfile.com" will be included into the temporary COM file that is submitted.
The $ indicates that the following unix command will be executed.
-general=pre_com_file:file_spec | "I myfile.com" | $ unix command
-general=nopre_com_file
The PRE_COM_FILE field indicates that a COM file is to be executed prior to running the scheduled job. The COM file and the job are run in the same batch job.The "I" indicates that the contents of "myfile.com" will be included into the temporary COM file that is submitted.
The $ indicates that the following unix command will be executed.
-general=protection:[who]+permission
-general=protection:[who]-permission
The PROTECTION field modifies the read, write and execute permissions of specified jobs.who specifies whether permissions are being defined for user(u), group(g) or all others(o).
permission specifies the permissions being defined. Read permission(r) allows reading. Write permission (w) allows the ability to write out a new version. Execute permission(x) allows execution of jobs and calendars, search of directories.-general=restart_count:number
A nonzero RESTART_COUNT allows the job to be restarted (up to the specified number of times) if it is terminated with a failure status code.-general=startup_window:delta_time
The STARTUP_WINDOW specifies the interval after which a job in schedule queue B will not be initiated. This only occurs if the system is down when a job would have had a time based start. If the system comes up within this interval then the job will start immediately. After this interval this immediate initial run is not done.The interval time check is suppressed if this field is set to zero (i.e. the window is infinite).
-general=status:number
The STATUS field is a full 32 bit integer status code that indicates the success (odd) or failure (even) of a job execution. This field is automatically updated each time a job completes.-general=up_count:number
The UP_COUNT field indicates how many times a job has been submitted for execution. This is automatically updated.-log
-nolog
The LOG option causes each completed operation to issue a note to the user.-notify=after_delayed:delta_time
The AFTER_DELAYED datum specifies a time limit so that any job that has waited longer than this interval for prerequisites, disk space, or a file is considered delayed. At this time a notification is sent.-notify=all:([user(s)] [,mail(def)] [,broadcast])
-notify=noall
The ALL sets and the NOALL clears all other NOTIFY commands. Thus ALL will cause the creator of the job to be notified when the job is submitted, started, delayed, completed, or if and when a job failed. If BROADCAST is set then a logged in user will get a broadcast message. Use NOBROADCAST to disable this. If MAIL is set a mail message is sent. Use NOMAIL to disable this. If more then one user name is specified surround the names with parentheses and separate with commas.-notify=completed:([user(s)] [,mail(def)] [,broadcast])
-notify=nocompleted
The COMPLETED field will notify the creator of a job when the job is completed. If BROADCAST is set then a logged in user will get a broadcast message. Use NOBROADCAST to disable this. If MAIL is set a mail message is sent. Use NOMAIL to disable this. If more then one user name is specified surround the names with parentheses and separate with commas.-notify=delayed:([user(s)] [,mail(def)] [,broadcast])
-notify=nodelayed
The DELAYED field will notify the creator of a job if and when the job is delayed. If BROADCAST is set then a logged in user will get a broadcast message. Use NOBROADCAST to disable this function. If MAIL is set a mail message is sent. Use NOMAIL to disable this function. If more then one user name is specified surround the names with parentheses and separate with commas.-notify=failed:([user(s)] [,mail(def)] [,broadcast])
-notify=nofailed
The FAILED field will notify the creator of a job if and when the job failed. If BROADCAST is set then a logged in user will get a broadcast message. Use NOBROADCAST to disable this. If MAIL is set a mail message is sent. Use NOMAIL to disable this. If more then one user name is specified surround the names with parentheses and separate with commas.-notify=started:([user(s)] [,mail(def)] [,broadcast])
-notify=nostarted
The STARTED field will notify the creator of a job when the job is started. If BROADCAST is set then a logged in user will get a broadcast message. If MAIL is set a mail message is sent. If more then one user name is specified surround the names with parentheses and separate with commas.-notify=submitted:([user(s)][,mail(def)] [,broadcast])
-notify=nosubmitted
The SUBMITTED field will notify the creator of a job when the job is submitted. If BROADCAST is set then a logged in user will get a broadcast message. Use NOBROADCAST to disable this function. If MAIL is set a mail message is sent. Use NOMAIL to disable this function. If more then one user name is specified surround the names with parentheses and separate with commas.-resources=disk_space:(disk,number_of_blocks)
-resources=nodisk_space
The DISK_SPACE resource specifies how many blocks must be available before the job is submitted for execution.-resources=estimated:(cpu,elapse,io)
The ESTIMATED datum allows for establishing an initial estimate of cpu_time, elapse_time, and io_count. These estimated values are not used1 for any computation. Their purpose is to assist in planning and initially setting up the job.
Field Description cpu estimated number of seconds elapse estimated number of seconds io estimated number of buffered and direct I/O -resources=file:file_spec
-resources=nofile
The FILE datum indicates which file, if any, must be present prior to a job being submitted for execution.-resources=measured:(cpu,elapse,io,count)
The MEASURED datum displays information about cpu_time, elapse_time, io_count, and num_count. It is usually modified automatically as a job completes.
Field Description cpu average number of seconds elapse average number of seconds io average number of buffered and direct I/O count number of times average is based on -rescheduling=calendar:calendar_name
The CALENDAR datum specifies which calendar to use when evaluating a rescheduling method. An example of a calendar is one that specifies which days are holidays.-rescheduling=interval:delta_time
The INTERVAL datum allows the user to specify how often or at what interval the job is run. The INTERVAL datum is mutually exclusive of the MARKED, NAMED, or NONE datum.-rescheduling=marked:letter_mark
The MARKED datum allows the user to run a job on days that are "marked" with the indicated letter. The MARKED datum is mutually exclusive of the NAMED, INTERVAL, or NONE datum. The TIME_OF_DAY datum is used to specify the time the job is to run on the specified day(s).-rescheduling=monthlyjanuary...december,ordinal_number,day_of_week
The MONTHLY datum allows the user to specify a month, several months or ALL for all months that the job will run in. The months are separated by commas followed by a comma then by an ordinal number (FIRST, SECOND, THIRD, FOURTH), followed by a comma then the day of the week.
JANUARY FEBRUARY MARCH APRIL MAY JUNE JULY AUGUST SEPTEMBER OCTOBER NOVEMBER DECEMBER ALL FIRST SECOND THIRD FOURTH DAY_OF_WEEK -rescheduling=named:date
The NAMED datum allows the user to specify a particular date or sequence of dates on which a job is to run by its name. The NAMED datum is mutually exclusive of the MARKED, INTERVAL, or NONE datum. The TIME_OF_DAY datum is used to specify the time the job is to run on the specified day(s).
SUNDAY TUESDAY THURSDAY SATURDAY MONDAY WEDNESDAY FRIDAY MONTH_START YEAR_START 445 544 MONTH_END YEAR_END 454 -rescheduling=none
The NONE datum indicates that the job is not to start based on time. Such jobs will only start if initiated by another job or manually submitted.-rescheduling=time_of_day:[+/-]delta_time
The TIME_OF_DAY field allows the user to specify what time of day to run a job. This command is used with the MARKED and NAMED option s. The interval specified here is added to the selected day. The interval specified can be of any length, from seconds to days. The job must be on either named day or marked calendar rescheduling.-resources
Create a generalized resource and add to RESOURCE list. The list is where the bulk of advanced job programming occurs. Here IF-THEN and SET statements are processed that can check or alter the value of a variable, supress a job run or cause a wait to occur.
Note
1 In a future release these values and the measured values will be used in a chart displaying the progress of the job.
Previous Next Contents Index