| Contents | Index | JAMS Home | Support |
|
||||
|
| Previous | Contents | Index |
1.3 Job Definitions
Job Definitions define a single command file's attributes. The Job
definition serves to document the command file's existence as well as
providing the capability of submitting the command file using the
JAMS Submit sub-system.
1.3.1 Job Name
The Job Name is a unique identifier for a Job. It is analogous to the filename of a command file.
A Job Name must be a valid OpenVMS identifier. This means that it must
begin with an alphabetic character and contain only the characters A-Z,
0-9, $ (dollar sign), and _ (underscore). Also the last character may
not be an underscore.
1.3.2 Description
The Description option is used to view or update the Job's
description. The description is used in menus, lists and reports to
provide a more complete description of the Job than provided by the Job
Name. Two lines of 50 characters are provided. If you use only one
line, use the first one.
1.3.3 System
The System option is used to view or update the Job's System I.D. The System I.D. specifies to which System this Job definition belongs. This is a required field and must be a System which has already been defined using the System Definitions option.
Some of the information from the selected System Definition is also
displayed on this form.
1.3.4 Security
If you select the Security option and you have CONTROL access to the Job (or the OpenVMS BYPASS privilege), the Job's Access Control List will be displayed. You can then make modifications to the ACL. The following access rights can be specified:
| Right | Meaning |
|---|---|
| CONTROL | Allows modification of this Job's Access Control List. |
| CHANGE | Allows modification of this Job definition provided that the user also has CHANGE access to Job Definitions. |
| INQUIRE | Allows inquiry into this Job definition provided that the user also has INQUIRE access to Job Definitions. |
| DELETE | Allows deletion of this Job definition provided that the user also has DELETE access to Job Definitions. |
| SUBMIT | Allows submission of this Job. |
| DEBUG | Allows submission of this Job but only if the /DEBUG qualifier is used on the JAMS SUBMIT command. This qualifier will submit the Job under the users OpenVMS username rather than the OpenVMS username specified in the System Definition. |
| OPERATOR | Allows the user to use the JAMS Job Monitor to hold, reschedule, release or delete an occurrence of this Job. |
| ABORT_JOBS | Allows the user to use the JAMS Job Monitor to abort or restart an occurrence of this Job. |
Note that in order to change a Job definition's System I.D., you must
have JOB_DELETE access to the old System I.D. and JOB_ADD access to the
new System I.D.
1.3.5 Submit Options
The Submit Options option is used to view or update fields associated with submitting this Job. The fields on this screen include:
This field is used to specify the name of the batch queue where this Job should be submitted. This entry will only be used if the execution method for the Job utilizes batch queues. If not specified, the Default Batch Queue from the System Definition is used.
This number is used to calculate the scheduling priority for this Job. This number may range from -127 to 127, the default being 0. When a Job is submitted by the JAMS submit sub-system, the scheduling priority is calculated by adding together the OpenVMS default scheduling priority, the System's priority modifier and the Job's priority modifier.
Specifies the retention policy for this Job. The options are:
| Always | Job is always retained until specifically deleted. |
| Never | Job is never retained in the queue. |
| Error | Job is retained if they complete with a severity of Warning or worse. |
| Timed | Job is retained for the specified time after completion. |
| Not Specified | Use the default specified in the System Definition. |
This field specifies whether or not this Job should be placed in a "holding" state when it is submitted.
This is useful for Jobs which are requested, or submitted, by end-users but require operator approval before execution.
This field specifies whether or not the Job can be restarted after a failure.
This field specifies whether or not this Job should be excluded from JAMS Submit menus. If set to "Yes", the job will never be displayed on a Submit menu. The only way to submit the Job is via the JAMS SUBMIT command or with a Setup definition.
This field specifies whether or not the /NOTIFY qualifier is used when submitting this Job. Note that when /NOTIFY is specified, the username who submitted the job is notified, not the username under which the job ran.
You can specify the username under which this Job should run. This will override the Username specified in the Job's System Definition. You must have either the CMKRNL privilege or SUBMIT access to the Username which you specify. See the JAMS SET USERNAME command for information on setting access to Usernames.
For Jobs which execute on remote nodes, this is the name of the system
where they will execute. This system must be running either the
JAMS Agent or an rexec server (depending on the Execution
Method used by the Job).
1.3.6 Submit Times
This field is used to specify the name of a JAMS Named Time which defines this Job's Submit Window. You can specify a Named Time or a specific time range but not both.
These fields are used to specify a specific Submit Window for this Job. You can specify a Named Time or a specific time range but not both.
This field specifies the action that JAMS should take if this Job misses it's time window. Possible actions are:
| No Action | The window is only used to limit the time which can be entered when the Job is manually submitted. |
| Continue | The Job will not start until the time window opens but will not be rescheduled or aborted if the window closes before the Job completes. |
| Abort or Delete | The Job will not start until the time window opens and will be deleted or aborted if the window closes before the Job completes. |
| Reschedule or Continue | The Job will not start until the time window opens. If the Job has not started when the window closes, it will be rescheduled for the next time that the window opens. If it has started, it will be allowed to continue. |
| Restart or Reschedule | The Job will not start until the time window opens. If the Job has not complete when the window closes, it will be rescheduled for the next time the window opens. If the Job is executing when the window closes it will be aborted and rescheduled. |
Defines whether or not JAMS should perform notification if the Job misses it's time window.
This field is used to specify a default submit date which is used when this Job is manually submitted.
This field is used to specify a default submit time which is used when
this Job is manually submitted.
1.3.7 Schedule Options
The Schedule Options option is used to define a scheduled time for this Job. You can also use a Setup Definition to schedule a Job.
This is an English language representation of the date, or dates, on which this Job is scheduled to run.
You can specify multiple scheduled days by separating the text with commas. For example, "MONDAY,WED,FRIDAY" means that this Job should be run every Monday, Wednesday and Friday.
Note that the quotations shown in the examples should not be entered in the scheduled date field. For a complete description of English language date representations, refer to Chapter 7 of the JAMS User Guide.
This is an English language representation of a date, or dates, on which this Job should not be run. If you want to schedule a Job to run every Monday, except for the last Monday of the month, you would enter "MONDAY" into the Scheduled Date field and "LAST MONDAY OF MONTH" into this field.
This is the time of day when this Job should be run.
If you want this Job to run many times during a day, you can specify the delta time between runs and the time of day to stop repeating. Then, any time this Job completes it will be resubmitted to run hh:mm later. The Job will be resubmitted no matter what its completion status was or how it was submitted. The only way to stop this repetition is to abort/delete the scheduled entry.
You can specify what time to use as the base for calculating the next run time, the base may be the Scheduled, Start or End time.
Automatic Submit at Scheduled Date and Time
This field indicates whether or not this Job should be automatically submitted at the scheduled date and time.
A no entry indicates that the scheduled date and time are to be used only for management and capacity planning.
This field indicates how this Job should be scheduled if the day it is scheduled to run falls on a non-workday. There are three options:
S - Schedule the Job, even on non-workdays.
I - Ignore the Job, do NOT schedule on non-workdays.
D - Defer the Job until the next workday.
A Job may have zero or more parameters. When the JAMS Submit sub-system is used to submit a job which has parameters, the person submitting the job is presented with a "fill in the blanks" form which they use to provide values for the Job's parameters.
Normal OpenVMS batch Jobs are limited to eight parameters but a JAMS parsed Job may have up to 255 parameters. If a job is not parsed, parameters other than P1 through P8 are of very little value. If a job is parsed, you can embed parameter names into the job's DCL command file and JAMS will replace the embedded parameter name with the value of the parameter. Please refer to Chapter 5, Templates and Job Parsing for a complete description of Job parsing, template expansion and parameters.
Note that the order of parameters is important. When JAMS builds a parameter form, the parameters are placed on the form in the order in which they are defined.
This is the name for the parameter. It must be unique within the Job.
For OpenVMS jobs, the names P1, P2, P3, P4, P5, P6, P7 and P8 have special significance. They are treated exactly the same as any other parameter, but they are also specified as parameters to the Job as though you had used the /PARAMETER qualifier of the OpenVMS SUBMIT command.
Parameter Names must be valid symbol names. They must begin with a alphabetic character and contain only the characters A through Z, 0 through 9, $ (dollar sign) and _ (underscore). In addition, a symbol name may not begin with the character string "JAMS_". Symbols which begin with this string are reserved for JAMS.
When a job is submitted by JAMS, a form is created which is used to prompt the user for the values of the job's parameters. This text will be right justified and used as a prompt on this parameter form.
This field specifies the data type of the parameter. Valid entries are:
If the field has a data type of TEXT or INTEGER, you must specify the maximum length of the field.
This field is the default edit string to be used when formatting this parameter during Job parsing. This field does not affect what the end-user sees or enters. It only affects how the parameter is passed to the Job. This field can be overridden in a parsed job.
This field applies only to fields with a data type of DATE, TIME or INTEGER.
This is a Y (yes) or N (no) field which specifies whether or not an entry into this field is required.
This is a Y (yes) or N (no) field which specifies whether or not the user must completely fill this field.
This is a Y (yes) or N (no) field which specifies whether or not the data entered is converted to uppercase upon entry.
This is a Y (yes) or N (no) field which specifies whether or not the the end-user will be allowed to make an entry into this parameter when they are submitting the Job.
This is a Y (yes) or N (no) field which specifies whether or not the this parameter will be displayed when the end-user is submitting this Job.
This field specifies the name of a JAMS Variable whose value will be used as the default value for this parameter when the Job is submitted. If you enter a Variable Name here, you will not be able to enter a value in the Default field.
This field specifies the default value for this field.
The default value for date fields may be entered as a specific date or using JAMS English language date text such as "LAST MONDAY", "FIRST MONDAY OF MONTH" etc. For more information on this syntax, refer to Chapter 7 of the JAMS User Guide.
The text entered here is displayed when the user presses the
[Help] key while the cursor is located in this parameters
field.
1.3.9 Reports
Report definitions are used to document and control the reports produced by a Job. For Jobs which are not parsed by JAMS, Report definitions serve as documentation only. Jobs which are parsed, make full use of Report definitions. During the parsing, a logical name is defined which translates into a full file specification for the Report's print file. OpenVMS PRINT commands are also generated which send these print files to a printer queue. Refer to Chapter 5, Templates and Job Parsing for a complete description of Job parsing and template expansion.
A Job may have one or more Report definitions. There is no practical limit to the number of report definitions which a Job may have.
The Report I.D. is an identifier used to name a report. It must be unique within a Job.
This field provides a description of the Report which is used in the Report list, and can be used in the heading of the actual printed report.
When JAMS parses a Job, it can create the DCL command needed to define logical names which point to the actual report listing file. This field specifies this Report's logical name. If you leave this field blank, the Report I.D. is used as the value for the logical name.
This is also used when a Job needs to print the same report more than one time, such as to two different print queues. To accomplish this, define two Reports for the Job (which must have different Report I.D.s) but enter the same value in the logical name field for both Reports. When JAMS parses the .JOB file, it will define the logical name only once but it will generate two print commands, one for each Report.
This field specifies the OpenVMS print queue where the Report should be printed at the conclusion of the Job. If you leave this field blank, the Default Print Queue in the Job's System definition is used.
This field specifies the OpenVMS print form which will be used when the Report is submitted to a print queue. If you leave this field blank, the default form of the Report's print queue will be used.
This field specifies a valid OpenVMS file name. The use of this field is determined by the template definitions. The default JAMS templates use this field as the base for a reports file name and any missing fields are replaced as follows:
This field specifies the number of copies of the report which should be printed. If you specify 0, the report is not sent to a print queue. If the value you specify is greater than 1, a /COPIES= qualifier is added to the print command which JAMS generates.
This field specifies the number of days the report file should be retained. JAMS will create a SET FILE/RETENTION= command in the parsed .JOB file which will set the file's expiration date. JAMS does not delete these files when the expiration date has passed.
If you specify a value of 0 for retention days, the /DELETE qualifier will be added to the print command which JAMS generates.
If a report is to be printed more than once, then you must specify a value greater than 0 here. Otherwise, the /DELETE qualifier will be added to all of the print commands, and the file could be deleted before it has printed at all locations. |
The text entered here is appended to the Reports OpenVMS print command
when JAMS parses the Job file. The text entered here must
consist of valid qualifiers for the OpenVMS print command and must
begin with a slash.
1.3.10 Dependencies
Job dependencies are used to insure that all prerequisite processing has been performed before a Job can begin executing. A Job dependency can be based on:
1.3.10.1 Job Completion Fields
The job completion fields are:
This is the name of the Job which the current Job depends upon. This Job must have completed since the last time that the Since Job completed or within the range of time specified in the days and hours fields. This is a required field.
The "Depends on Job" must complete with a OpenVMS severity level which is equal to or better than this severity. The possible values, in order from good to bad, are S (Success), I (Informational), W (Warning), E (Error) and F (Fatal or Severe). This is a required field.
This is the name of a Job which is used as a reference point when determining if the "Depends on Job" has completed. Many times this will be the same as the current Job (i.e. JOBA must have completed since the last time I ran).
This is an optional field, if you leave this field blank, the Time Range fields are used to determine if the dependency has been satisfied.
When evaluating the last time that the Since Job completed, JAMS requires that the Job completed with a severity which is equal to or better than the severity entered here. The possible values, in order of severity, are S (Success), I (Informational), W (Warning), E (Error) and F (Fatal or Severe).
The time range fields (number of days and hours) let you define a dependency which is time based and usually less restrictive than a normal dependency.
These are optional fields. If you leave the Time Range fields zero, and leave the Since Job field blank, then whenever the current job is submitted, it will wait in the queue until the dependent job completes with a satisfactory status.
An example of when a time based dependency could be useful would be a situation where you have one update job and a number of reporting jobs. If you ran the update job at the end of every month, followed by the reporting jobs, you could define a dependency for each of the reporting jobs which requires that the update job completed within the past 28 days.
If you enter a "Y" in this field, when the Job is ready to
run, JAMS will look to see if the "depends on" Job
is scheduled or executing. If one or more of the "depends on"
Jobs are found, the current Job will remain in a pending state until
all occurrences of the "depends on" Job have completed.
1.3.10.2 Remote Job Completion Fields
The remote job completion fields are:
This is the DECnet node name of the remote node, or node group, where the "Depends on Job" runs. This field is present only for Remote Job Completion dependencies.
JAMS treats a VMScluster as a single unit. You can specify any node in the remote VMScluster which is running JAMS with networking enabled. The dependent job can run on any node in the remote VMScluster and the dependency will be satisfied.
An entry into this field must be either a valid JAMS Node Definition or a valid JAMS Node Group Definition. You can use the [Find] key to list the valid Nodes and Node Groups.
Creating a dependency which refers to a Node Group is functionally equivalent to creating a dependency for every node in the Node Group. The primary advantage of Node Groups is that when the list of nodes in the group changes, you do not have to change all of your dependent jobs.
This is the name of the Job which the current Job depends upon. This Job must have completed since the last time that the Since Job completed or within the range of time specified in the days and hours fields. This is a required field.
Since this Job resides on the remote node, it is not validated during data entry.
The "Depends on Job" must complete with a OpenVMS severity level which is equal to or better than this severity. The possible values, in order from good to bad, are S (Success), I (Informational), W (Warning), E (Error) and F (Fatal or Severe). This is a required field.
This is the name of a Job which is used as a reference point when determining if the "Depends on Job" has completed. Many times this will be the same as the current Job (i.e. JOBA must have completed since the last time I ran).
This is an optional field, if you leave this field blank, the Time Range fields are used to determine if the dependency has been satisfied.
When evaluating the last time that the Since Job completed, JAMS requires that the Job completed with a severity which is equal to or better than the severity entered here. The possible values, in order of severity, are S (Success), I (Informational), W (Warning), E (Error) and F (Fatal or Severe).
The time range fields (number of days and hours) let you define a dependency which is time based and usually less restrictive than a normal dependency.
These are optional fields. If you leave the Time Range fields zero, and leave the Since Job field blank, then whenever the current job is submitted, it will wait in the queue until the dependent job completes with a satisfactory status.
An example of when a time based dependency could be useful would be a situation where you have one update job and a number of reporting jobs. If you ran the update job at the end of every month, followed by the reporting jobs, you could define a dependency for each of the reporting jobs which requires that the update job completed within the past 28 days.
If you enter a "Y" in this field, when the Job is ready to
run, JAMS will look to see if the "depends on" Job
is scheduled or executing. If one or more of the "depends on"
Jobs are found, the current Job will remain in a pending state until
all occurrences of the "depends on" Job have completed.
1.3.10.3 Variable Value Fields
The variable value fields are:
This is the name of the JAMS Variable which this Job will depend upon.
This is the boolean operator or code used to define how the comparison will be performed. Press the [Find] key to display a list of the valid conditions.
This is the value which the Variable will be compared to. This field
has no meaning if the condition code is "Changes".
1.3.11 Source Options
The Source Options option is used to specify the Job's source command file and how it will be processed. The fields on this form include:
The Execution Method specifies which of the defined Methods should be used to execute this Job. The following Methods are defined when JAMS is installed. You can also create your own Methods with the CREATE METHOD command.
| SUBMIT | OpenVMS batch job with direct command procedure. |
| PARSED | OpenVMS batch job with parsed command procedure. |
| JACKET | OpenVMS batch job with jacketed command procedure. |
| DETACHED | OpenVMS detached process with direct command procedure. |
| DETPARSED | OpenVMS detached process with parsed command procedure. |
| NT | Windows NT Agent with direct command procedure. |
| NTPARSE | Windows NT Agent with parsed command procedure. |
| NTCMD | Windows NT Agent with single line command. |
| REXEC | Rexec server with single line command. |
The Job Source is either the filename and extension of the command file associated with this Job or the command for execution methods which require a single line command.
The Directory specification for the command file is provided by the System Definition. If the location specified in the System Definition is a default location, then you can include a full file specification in the Job Source Field.
If left blank, the default filename is the Job Name. The default
extension is obtained from the Execution Method.
1.3.12 View Source
The View Source option displays this Job's source command file
in a scrollable window.
1.3.13 Edit Source
The Edit Source option activates a OpenVMS text editor and lets you edit or view this Job's source command file. The default editor is TPU but you can select from TPU, LSE and EDT by defining the logical name JAMS_EDITOR to be TPU, LSEDIT or EDT. With TPU and LSE you can also include qualifiers in the logical name which change the editor. For example:
$ DEFINE JAMS_EDITOR "LSEDIT/SECTION=MYSECTION/NOCOMMAND"
|
The Precheck Job option is used to define this Job's Precheck Job. A Precheck Job is used to check for user defined prerequisites for this Job. When a Job which has a Precheck Job is submitted, it will remain in a pending state until the Precheck Job completes successfully. JAMS will automatically submit the Precheck Job when the main Job is ready to run. By ready to run we mean that the Job is not held or waiting for a specific time, all of the Job's Dependencies have been satisfied, and there are sufficient Resources available.
A Precheck Job has four options.
If the Precheck Job is parsed then the following predefined parameters are available:
| JAMS_TRYAGAIN | The integer value of the status JAMS_TRYAGAIN. |
| JAMS_SCANCELJOB | The integer value of the status JAMS_SCANCELJOB. |
| JAMS_ICANCELJOB | The integer value of the status JAMS_ICANCELJOB. |
| JAMS_WCANCELJOB | The integer value of the status JAMS_WCANCELJOB. |
| JAMS_ECANCELJOB | The integer value of the status JAMS_ECANCELJOB. |
| JAMS_FCANCELJOB | The integer value of the status JAMS_FCANCELJOB. |
| JAMS_CANCELJOB | The integer value of the status JAMS_CANCELJOB. This status is also an E level status and is included for backwards compatibility. |
| JAMS_PRECHECK_ENTRY | The entry number of the Job which this Job is doing the checking for. |
| JAMS_PRECHECK_COUNT | The number of times that the Precheck Job has run for this entry. |
The Recovery Job option is used to define this Job's Recovery actions. The fields on this form include:
If this Job completes with a severity which is equal to or worse than the severity specified on this screen, the Recovery Job will be automatically submitted.
The Recovery Job is not submitted if this Job is intentionally aborted.
This is the name of a valid JAMS Job which is to be submitted if this Job completes with a severity which is equal to or worse than the specified severity.
If the Recovery Job is parsed then the following predefined parameters are available:
| JAMS_RECOVERY_ENTRY | The OpenVMS queue entry number of the Job that failed. |
| JAMS_RECOVERY_JAMS_ENTRY | The JAMS entry number of the Job that failed. |
| JAMS_RECOVERY_JOB_NAME | The JAMS Job name of the Job that failed. |
| JAMS_RECOVERY_JOB_STATUS | The most recent status text set by the failed Job using the JAMS SET STATUS command. |
| JAMS_RECOVERY_LOG_FILENAME | The full file specification of the log file for the job which failed. |
| JAMS_RECOVERY_MAIL_ADR | The list of names which will be notified via OpenVMS Mail. |
| JAMS_RECOVERY_OPER_CLASSES | The list of OPCOM classes which will be notified. |
| JAMS_RECOVERY_PID | The OpenVMS PID of the failed Job. |
| JAMS_RECOVERY_REPLY_USERS | The list of names which will receive a broadcast message. |
| JAMS_RECOVERY_RESTART_COUNT | The number of times the failed job has been restarted. |
| JAMS_RECOVERY_RON | The JAMS run occurrence number of the failed Job. |
| JAMS_RECOVERY_STATUS | The final OpenVMS status of the failed Job. |
| JAMS_RECOVERY_SYSTEM_ID | The JAMS System I.D. of the failed Job. |
The Recovery Instructions option is used to edit or view this Job's restart/recovery instructions. These instructions are included in the OpenVMS mail message notification messages.
You can also create restart/recovery instructions at the System level.
1.3.17 Notify Names
The Notify Names screen is used to define who should be notified when this Job requires notification.
These names can augment or replace the names specified on the Job's System definition. To remove a name which is specified in the System definition prefix the name with a minus sign. To remove all named specified in the System definition, enter "-*".
Notification is performed when:
The fields on this category include:
This is a list of OpenVMS Mail addresses, separated by commas. You can also specify logical names which equate to one or more OpenVMS Mail addresses.
This is a list of OpenVMS usernames, separated by commas. You can also specify logical names which equate to one or more OpenVMS usernames.
This is a list of OpenVMS operator classes, separated by commas. You can also specify logical names which equate to one or more OpenVMS operator classes.
Valid OpenVMS operator classes are:
CARDS
CENTRAL
CLUSTER
DEVICES
DISKS
NETWORK
OPER1 through OPER12
PRINTER
SECURITY
TAPES
This is the name of a JAMS Job which should be submitted when notification is required. A Job specified here will override a Notification Job specified in the System definition.
If the Notification Job is parsed then the following predefined parameters are available:
| JAMS_NOTIFY_ENTRY | The OpenVMS queue entry number of the job which caused the notification. |
| JAMS_NOTIFY_JAMS_ENTRY | The JAMS entry number of the job which caused the notification. |
| JAMS_NOTIFY_JOB_NAME | The Job Name of the job which caused the notification. |
| JAMS_NOTIFY_JOB_STATUS | The current Job Status value of the job which caused the notification. |
| JAMS_NOTIFY_LOG_FILENAME | The full file specification of the log file for the job which caused the notification. |
| JAMS_NOTIFY_MAIL_ADR | The list of names which will be notified via OpenVMS Mail. |
| JAMS_NOTIFY_OPER_CLASSES | The list of OPCOM classes will receive an operator message. |
| JAMS_NOTIFY_PID | The process ID of the job which caused the notification. |
| JAMS_NOTIFY_REASON | The reason for the notifications. This parameter could be: COMPLETED, FAILED, SHORT, RUNAWAY, STALLED or MISSED_WINDOW. |
| JAMS_NOTIFY_REPLY_USERS | The list of names which will receive a broadcast message. |
| JAMS_NOTIFY_RON | The JAMS run occurrence number of the job which caused the notification. |
| JAMS_NOTIFY_STATUS | The final status of the job which caused the notification. |
| JAMS_NOTIFY_SUBMITTED_BY | The username which submitted the job which caused the notification. |
| JAMS_NOTIFY_SYSTEM_ID | The JAMS System I.D. of the job which caused the notification. |
Notify options specified in a Job Definition override those specified in a System Definition.
This field is used to define the minimum completion severity which will cause notification messages to be sent. If the Job's completion severity is equal to or worse than the specified severity, notification messages will be sent. You can also enter "N" to disable notification.
The Stalled Time specifies how much time may elapse after the Job's scheduled time before the job is considered to be stalled. When the job is considered stalled, JAMS will perform notification for the job.
The Runaway Job Elapsed Time specifies how long the job may run before it is considered a runaway job. This is specified as a delta time. When the job is considered runaway, JAMS will perform notification for the job.
The Runaway Job Elapsed Time Percent specifies how long the job may run before it is considered a runaway job. This is specified as a percentage of the Job's average elapsed time. When the job is considered runaway, JAMS will perform notification for the job.
The Runaway Job CPU Time specifies how much CPU time the job may consume before it is considered a runaway job. This is specified as a delta time. When the job is considered runaway, JAMS will perform notification for the job.
The Runaway Job CPU Time Percent specifies how much CPU time the job may consume before it is considered a runaway job. This is specified as a percentage of the Job's average CPU time. When the job is considered runaway, JAMS will perform notification for the job.
The Short Job Elapsed Time specifies a minimum elapsed time for a job. If the job completes successfully in less than this amount of time it is considered a Short Job. When a job is determined to be a short job, JAMS will perform notification for the job and may change the completion severity of the job.
The Short Job Elapsed Time Percent specifies a minimum elapsed time for a job. If the job completes successfully in less than this amount of time it is considered a Short Job. This is specified as a percentage of the Job's average elapsed time. When a job is determined to be a short job, JAMS will perform notification for the job and may change the completion severity of the job.
The Short Job CPU Time specifies a minimum CPU time for a job. If the job completes successfully but used less than this amount of CPU time it is considered a Short Job. When a job is determined to be a short job, JAMS will perform notification for the job and may change the completion severity of the job.
The Short Job CPU Time Percent specifies a minimum CPU time for a job. If the job completes successfully but used less than this amount of CPU time it is considered a Short Job. This is specified as a percentage of the Job's average CPU time. When a job is determined to be a short job, JAMS will perform notification for the job and may change the completion severity of the job.
If specified, when a job is determined to be a Short
Job, the completion severity will be changed to the severity
specified here.
1.3.19 Log Options
Log File options specified in a Job Definition override those specified in a System Definition.
When the field is true, or "Y", batch log files will not be deleted at the completion of the Job.
When the field is true, or "Y", batch log files will be printed when the Job completes.
When the field is true, or "Y", batch log files be time stamped with an extension of .LOG_yyyymmdd_hhmmsscc.
You can override the default filename for the log file created when
this job runs.
1.3.20 Resources
The Resources option will display a list of the Resource Requirements which are currently defined for this Job.
Resource requirements specified in a Job Definition augment the
Resource Requirements specified in the Job's System Definition. If the
Job and System both specify the same Resource, the requirements are
summed.
1.3.21 Execution Statistics
The Execution Statistics option displays performance statistics for this Job. These statistics are updated only if the Job completes with a severity level of Success or Informational. The screen shows the average, minimum and maximum values for the following statistics:
| Count | The number of times that one or more fields in this column has been updated. |
| Elapsed Time | The total wall clock time from the start of execution to completion. |
| CPU Time | The amount of CPU time used. This is weighted according to the CPU rating established by the logical name JAMS_CPU_RATING. |
| Direct I/O | The number of direct I/O operations performed. |
| Buffered I/O | The number of buffered I/O operations performed. |
| Peak Working Set | The largest number of pages of memory used by this Job at any one time. |
| Page Faults | The total number of hard and soft page faults incurred by this Job. |
| Peak Virtual Pages | The largest number of pages of virtual memory used by this Job at any one time. |
The Completion Dates option shows the date and time of the last time this Job completed with each of the five possible completion severity levels.
If a date and time are all spaces, then the Job has never completed
with that severity level.
1.3.23 References
The References screen lists all of the references to this Job. A Job may be referenced by:
| Previous | Next | Contents | Index |
 | Copyright © 2000, MVP Systems, Inc. All rights reserved. |