This document covers the following topics:

• Defining Scheduling Parameters for a Job

• Maintaining Schedule Dependencies for a Job

• Defining Schedule Dependencies for an Input Condition

• Sending a Late Message to One or More Users

• Viewing Job Accounting Data

---

Defining Scheduling Parameters for a Job

This feature allows you to define a schedule for the job master. You can define the time frame for the schedule, insert a message, assign account information and edit the schedule dependency information.

Related Topic:

• Rules for Time Frame Definitions

To define scheduling parameters at the job level

1. Type S in the line command input field of the selected job on the Job Maintenance screen.

2. Press ENTER.

   A Scheduling Parameters window similar to the example below opens:

   16-06-29 ***** Entire Operations ***** 17:19:30 Job Maintenance Owner SAGTEST Network B60-FLOW Version +-------------------------------------------------------------------------+ - ! ! ! Scheduling Parameters ! ! Job JOB-1-TEST ! E ! ! ! Estimated Elapsed Time ==> _________ Min. Average ==> 0.00 ! ! History Elapsed Time ==> 0.00 0.00 0.00 0.00 ! ! 0.00 0.00 0.00 0.00 ! ! Cyclic Interval ==> ____ min ! ! ! ! Earliest Start Time ==> 13:14:00 ___ days later ! ! Latest Start Time ==> 23:00:00 ___ days later ! ! Deadline Time ==> 23:30:00 ___ days later ! ! ! ! Schedule Dependency ==> N ! 1 ! ! * ! ---PF1---PF3------------PF5----------------PF9---PF10---PF11---PF12-- ! ! Help End Save LMsg Acct ScDep Menu ! +-------------------------------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down Menu

   If scheduling parameters have already been defined, they appear in this window and you can modify them for the job.

   When defining a new schedule, some default values are already displayed. You can replace them as required.

   The input fields are explained in Fields: Scheduling Parameters.

3. Press PF5 (Save) to save the job scheduling parameters.

4. Press PF3 (End) to return to the Job Maintenance screen.

This section covers the following topics:

• Fields: Scheduling Parameters

• Special PF Keys: Scheduling Parameters

Fields: Scheduling Parameters

The fields of the Scheduling Parameters window are described in the following table.

Field	Description
Estimated Elapsed Time	The expected total running time (in minutes) for the job. If not specified explicitly, this value is derived from the average running time of previous runs of the same job, displayed in the field directly below. If, for a real dummy job (job type DUM), this value is not equal to zero (0), then the dummy job is executed for exactly this amount of time. This enables you to perform time simulations, etc. Active scheduling parameters for a running dummy job: Modification of the estimated elapsed time causes the end time of the dummy job to be recalculated as sum of the start time and the new estimated elapsed time. If the new calculated end time is lower than the current time, the current time will be used instead. For temporary dummy jobs (e.g. dummy due to a condition), the defined estimated elapsed time is ignored. Temporary dummy jobs always have the execution time zero. Special value: For jobs of the type NET, 999999 can be specified. In this case, all start times after that are set to the ending times in the subnetwork.
Average	Average running time computed from five previous runs (see the field History Elapsed Time).
History Elapsed Time	Shows real running times of previous runs of the job. The average running time of all previous runs is used to compute the probable time the job will finish.
Earliest Start Time	The job will not be started before this time. Use days later if the Earliest Start Time is more than one day later than the network start time. See also Date and Time Formats (section Using Entire Operations) and Behavior for Schedule Times.
Latest Start Time	The job will not be started after this time. If this time precedes the Earliest Start Time and days later is null, days later is set to 1 so this time follows the Earliest Start Time. See also Date and Time Formats (section Using Entire Operations) and Behavior for Schedule Times.
Deadline Time	Time by which the job must be finished If the job cannot be finished before this time, it is not submitted. Dummy jobs with Estimated Elapsed Time not equal to zero (0) are finished at this time at the latest. See also Date and Time Formats (section Using Entire Operations) and Behavior for Schedule Times.
days later	You can use this field for Earliest Start Time, Latest Start Time and Deadline Time to define a time span lasting longer than 24 hours. See also Date and Time Formats (section Using Entire Operations) and Behavior for Schedule Times.
Schedule Dependency	A Y (Yes) here indicates that this job has a schedule dependency. An N (No) indicates that no schedule dependency is defined for the job. See also Maintaining Schedule Dependencies for a Job.
Cyclic Interval	This field is only available for cyclic jobs. Wait time (in minutes) between two executions of a cyclic job (special type C). Default: Monitor wait time

Special PF Keys: Scheduling Parameters

The following special PF keys are provided in the Scheduling Parameters window:

PF Key	Name	Description
PF9	LMsg	Late Message Define users to be informed if the job was not executed in the defined time range. See also Sending a Late Message to One or More Users.
PF10	Acct	Accounting Display accounting information for the job. See also Viewing Job Accounting Data.
PF11	ScDep	Schedule dependency Define days on which the job is to be replaced by a dummy job. See also Maintaining Schedule Dependencies for a Job.

Maintaining Schedule Dependencies for a Job

You can define whether job activation or input condition usage is valid (and checked) only on particular days of the week, month or year.

The date and time defined for job execution in the Scheduling Parameters window is then checked against the current schedule of the current network. For jobs in a subnetwork, we recommend you to specify that the topmost calling network is checked instead of the current network by using Schedule Usage option.

To define schedule dependencies at the job level

• Press PF11 (ScDep) in the Scheduling Parameters window.

  A Schedule Dependency Definition for Job window similar to the example below opens:

  17-10-06 ***** Entire Operations ***** 15:29:43 Job Maintenance Owner SAGTEST Network SAGNET Version +-------------------------------------------------------------------------+ - ! +---------------------------------------------------------------+ ! ! ! ! Job DE ! Schedule Dependency Definition for Job ! B ! ! ! B ! Estima ! Owner SAGTEST Job DEMO-JOB ! ! Histor ! Network SAGNET Condition ! ! ! ! ! ! The Job will be activated only (+) / not activated (-), ! ! ! if the execution date has the following position in the ! ! Earlie ! schedule or calendar: Schedule Usage ==> _ ! ! Latest ! ! ! Deadli ! Usage ==> _ + only - except ! ! ! A after Holiday too B before Holiday too ! 3 ! Schedu ! Type ==> _ H is Holiday X is Workday ! ! ! C Calendar Day W Workday S Schedule Day ! * ! ---PF1- ! in Period ==> _ W Week M Month Y Year ! s ! Help ! at Position ==> ____ ! +-------- ! ----PF1------PF3---------PF5------------------PF9----------- ! ! Help End Save Delete ! +---------------------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down Menu

  The input fields contained in the window are described in Fields: Schedule Dependency Definition.

This section covers the following topics:

• Fields: Schedule Dependency Definition

• Examples of Schedule Dependency Definitions

• Deleting Schedule Dependency Entries

Fields: Schedule Dependency Definition

The input fields of the Schedule Dependency Definition window provided for a job and/or input condition and the schedule dependency of a network are described in the following table:

Field	Description
Schedule Usage	Possible input values:
	blank	Checks the schedule of the current network (default). This setting is recommended for jobs in main networks.
	T	Checks the schedule of the topmost network that calls the job. This setting is recommended for jobs in subnetworks.
Usage (only or except)	Possible input values:
	+	For a job or condition: The job or condition is activated only if the execution date satisfies the criteria entered in the Type, in Period and at Position fields.
		For a network: The object is valid only for schedule days matching the following definitions.
	A	Like +, but the first workday after an otherwise matching holiday is valid, too.
	B	Like +, but the last workday before an otherwise matching holiday is valid, too.
	-	For a job or condition: The job or condition is activated except when the execution date satisfies the criteria entered in the Type, in Period and at Position fields.
		For a network: The object is valid for all schedule days except if they match the following definitions.
Type	Possible input values:
	H	Any holiday (no period and/or position required) The relative position to the holiday can be specified.
	X	Any workday (no period and/or position required) The relative position to the workday can be specified.
	C	Calendar day within the defined period A relative position refers to the real calendar period.
	W	Workday within the defined period A relative position refers to the workdays in the period.
	S	Schedule day within the defined period A relative position refers to the schedule days in the period.
in Period	Possible input values:
	W	Current week
	M	Current month
	Y	Current year
at Position	Schedule dependency position The position within the defined period depending on the specified type. Positive values (+) are relative to the period begin, negative values (-) are relative to the period end. For type H and X, this is the day difference. Valid value ranges are: For a week: -7 to -1 and +1 to +7 For a month: -31 to -1 and +1 to +31 For a year: -366 to -1 and +1 to +366 A value of zero (0) is not allowed. Note: You can specify up to three days for the period Week. Example: 24 is Tuesday and Thursday. See also Examples of Schedule Dependency Definitions.

Examples of Schedule Dependency Definitions

The following are example combinations for day calculation:

Type	Period	Position	Calculated Day
C	W	+2	Tuesday
		-1	Sunday
	M	+1	01
		-1	28 ... 31
	Y	+1	January 01
		-3	December 29
W	M	-1	Last workday of the month
H	n/a	+1	Day after a holiday

Special PF Keys: Schedule Dependency Definition for Job

The following special PF key is provided in the Schedule Dependency Definition for Job window:

PF Key	Name	Function
PF9	Delete	Delete entries in the fields Usage, Type, in Period and at Position. See also Deleting Dependency Entries.

Deleting Schedule Dependency Entries

To delete a schedule dependency entry for a job

1. In the Schedule Dependency Definition for Job window, press PF9 (Delete).

   The following window opens:

   16-07-07 ***** Entire Operations ***** 13:51:11 Job Maintenance Owner SAGTEST Network B60-FLOW Version +-------------------------------------------------------------------------+ - ! +---------------------------------------------------------------+ ! ! ! ! Job JO ! Schedule Dependency Definition for Job ! ! ! ! ! Estima ! Owner SAGTEST Job JOB-1-TEST ! ! Histor ! Network B60-FLOW Condition ! ! +-------------------------------------------------------------+ ! ! ! ! ! ! ! Please confirm ! ! ! Earl ! the Deletion of DEPENDENCY ! ! ! Late ! by entering 'Y' ===> _ ! ! ! Dead ! ! ! ! ! PF3 End ! ! ! Sche +-------------------------------------------------------------+ ! 1 ! ! C Calendar Day W Workday S Schedule Day ! * ! ---PF1- ! in Period ==> _ W Week M Month Y Year ! ! Help ! at Position ==> ______ ! +-------- ! ----PF1------PF3---------PF5------------------PF9----------- ! ! Help End Save Delete ! +---------------------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down Menu

2. Enter Y (Yes) and press ENTER to delete all field entries.

3. Press PF3 (End) to close the window.

Defining Schedule Dependencies for an Input Condition

You can define an input condition that is not used on all activation dates of a job network. This can be done for the following reasons:

• A predecessor job or network does not run on all schedule dates of the successor job or network.

• Some predecessor jobs are also schedule-dependent.

To define schedule dependencies for an input condition

1. On the Input Conditions Maintenance screen, type S in the line command input field of the selected condition.

2. Press ENTER.

   A Schedule Dependency Definition for Input Condition window opens.

   The fields contained in the window correspond to the fields of the Schedule Dependency Definition for Job window. They are explained in Maintaining Schedule Dependencies for a Job.

3. Make your definitions and choose PF5 to save your entries.

   The schedule dependency is allocated to the input condition.

4. Press PF3 to return to the Input Conditions Maintenance screen.

   The schedule dependency is indicated in the Sched.Dep. column.

Sending a Late Message to One or More Users

You can define recipients (users) to be informed in the case that the job could not be executed in the defined time range.

To send a message informing one or more users that the job could not be submitted

• In the Scheduling Parameters window, press PF9 (LMsg).

  A Message and Message Recipients window opens in which you can define message destinations.

  The fields contained in the window are explained in Field and Columns: Message and Message Recipients in the section End-of-Job Checking and Actions.

Viewing Job Accounting Data

You can view the start and end times, elapsed time and CPU time for previous runs of a job. The information is taken from the Entire Operations log file.

You can also generate reports from accounting data (see Example of Accounting Data as described in the section Reporting.

To display job accounting data

1. In the Scheduling Parameters window, press PF10 (Acct).

   A Date / Run Number Selection window similar to the example below opens:

   29.10.08 ***** Entire Operations ***** 15:32:20 Owner SN Job Maintenance Network BIG-1 +-------------------------------------------------------------------------+-- ! ! ! Scheduling Parameters ! ! Job JOB-014 !2 ! Tape Drives ==> ___ !1 ! !1 ! Estimated Elapsed Time ==> _________ Min. Average ==> 7.00 !1 ! History Elapsed Time ==> 2.00 12.00 ! ! !1 ! !2 ! Earliest +----------------------------------------------------+ !1 ! Latest St ! ! !1 ! Deadline ! Owner SN Network BIG-1 Job JOB-014 ! ! ! ! Date / Run Number Selection ! !2 ! Schedule ! ! ! ! ! From Date 10.07.07 00:00 to 10.07.07 16:00 ! !** ! ---PF1---P ! From Run 1____ to 99999 !12-- ! ! Help E ! !nu !g +----------- ! PF3 End !-------+ Enter-PF1---PF +----------------------------------------------------+1--PF12--- Help Add End Save Up Down Menu

   The window displays the time and run number interval.

   Enter dates, times and run numbers to specify the period and number range for which you want to view accounting data: see Fields: Range Specification for Accounting Data.

2. Press ENTER.

   A Job Accounting Data screen similar to the example below appears:

   29.10.08 ***** Entire Operations ***** 15:46:18 Owner SN Job Accounting Data Network DEMO-NET ------------------------------------------------------------------------------- Job Run JobId Date Start Stop Elapsed min CPU Time sec JOB1 748 1450 10.05.07 10:00:09 10:00:09 0.01 0.01 749 1783 12:00:30 12:00:31 0.01 0.01 750 1005 14:00:22 14:00:23 0.01 0.01 752 1867 10.05.07 12:00:16 12:00:16 0.01 0.01 757 3975 04.06.07 10:00:06 10:00:06 0.01 0.01 758 4314 12:00:17 12:00:18 0.01 0.01 759 4679 14:00:09 14:00:10 0.01 0.01 765 4085 10.06.07 14:08:57 14:08:57 0.01 0.01 -------- -------- Averages from 10.05.07 10:00 to 10.06.07 14:08 are 0.01 0.01 ******************************* Bottom of Data ******************************* Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- End Up Down

   The screen contains job execution time information collected by the Entire Operations Monitor. The job elapsed time is in minutes and the CPU time is in seconds. Average values are available at the bottom of the screen.

   For further information, see Fields and Columns: Reports in the section Reporting.

This section covers the following topics:

• Fields: Range Specification for Accounting Data

• Job Accounting Data: Operating System Considerations

Fields: Range Specification for Accounting Data

The fields of the Date / Run Number Selection window are described in the following table:

Field	Description
From Date ... to	Enter start (From) and end (To) dates and times to specify the time frame for which to display accounting data. Default is the current date, from midnight until the current time. For valid date and time input formats, see Date and Time Formats.
From Run ... to	Enter start (From) and end (To) run numbers to specify the number range for which to display accounting data. Default is from 1 to 99999.

Job Accounting Data: Operating System Considerations

BS2000

Since the BS2000 LOGOFF message does not contain seconds, the elapsed time cannot be calculated exactly.

UNIX

CPU time information is written to the SYSOUT of UNIX jobs. For this purpose, the shell times command is used. The output is enclosed in the messages EOR0303 and EOR0304.

Example:

%% EOR0303 - times - Begin
0m0.121s 0m0.025s
0m0.043s 0m0.066s
%% EOR0304 - times - End

Notes:

• With Entire System Server for UNIX Version 2.1.2 PL 4 and above, this output is used to determine the CPU time consumption of UNIX jobs. The CPU time is included in the Entire Operations accounting data.

• For Sun Solaris:

  The times command output is useful only if the script frame (*.BF) is executed under the Korn shell. Therefore, the *.BF scripts on Sun Solaris are started under the Korn shell.