job scheduling request users guide (04142008).doc

7/30/2019 Job Scheduling Request Users Guide (04142008).doc

1/8

Job Scheduling Request Users Guide

IndexOverviewTemplate FieldsGuidelinesHow to get a template

How to complete a templateHow to submit a templateDefinitions

AcronymsContact Information

OverviewNew Jobs and Jobstreams (applications on the Mainframe) should be requestedby completing an Excel template and sending it as an attachment to the Job

Scheduling Services (JSS) team. After the spreadsheet of request(s) has beenchecked by JSS, it is put through a process that will auto-generate the jobs andjobstreams into TWS/d (the distributed environment). For requests on theMainframe, manual entry will be done by the JSS staff. The spreadsheets will bestored in a central location where the JSS staff can access them for historicalpurposes.

Template FieldsThere are different fields for the job template and the jobstream/applicationtemplate.

For jobs the template fields are as follows:SPREADSHEET COLUMN DESCRIPTION

A Workstation Name

B Job Name

C Job Description

D Recovery Options (will default to Stop)

E Script / Command

F Task Type / NT Command

G Task Type / NT Script

H Task Type / UNIX Command

I Task Type / UNIX ScriptJ Start Time (HH:MM)

K Logon (always Maestro)

L Comments


2/8


For jobstreams the template fields are as follows:

SPREADSHEET COLUMN DESCRIPTION

A Workstation Name

B Jobstream Name

C Jobstream Description

D Start Time (HH:MM)E Priority (will default to 10)

F Carry Forward (always checked)

G Run Cycle / Sunday

H Run Cycle / Monday

I Run Cycle / Tuesday

J Run Cycle / Wednesday

K Run Cycle / Thursday

L Run Cycle / Friday

M Run Cycle / Saturday

N Run Cycle / EverydayO Run Cycle / Weekdays

P Run Cycle / Workdays

Q Run Cycle / Freedays

R On Request

S Other

T Predecessors

U Dependencies

V Job #01

W Job #02

X Job #03

Y Job #04Z Job #05

AA Job #06

AB Job #07

AC Job #08

AD Job #09

AE Job #10

AF Job #11

AG Job #12

AH Job #13

AI Job #14AJ Job #15

AK Job #16

AL Job #17

AM Job #18

AN Job #19

AO Job #20

AP Comments


3/8


Guidelines

These guidelines are provided to ensure that all documents use the same style,format, and standards. Consistency in documentation makes it easier for users toutilize the templates and for JSS when processing the request(s).

When creating a document please follow these guidelines.

How to get a template

You can download Job/Jobstream request templates by going to the JSS website at: www.doit.wisc.edu/job_scheduling and click on the link for JobRequests. Youll find links to the templates, this Users Guide, FAQs and more.

How to complete a template

JOBS

Workstation

The workstation (or server) where the job will run.Example: SFQA.

Job Name

The name of the job. There is a 40 character limit and the first six are reserved

for naming standards set by JSS.Example: SFGR__UWJT9007where SF is the Area Code for all SharedFinancial jobs, GR is the sub-Area Code for Grants, and the two underscores arereserved for future use. The remainder of the job name is one the customerchose to uniquely identify the job in the system.The first character of the job name must be a letter, and it can containalphanumeric characters, dashes (-), and underscores (_).

Job Description

The description of the job, which can be up to 64 characters in length.

Example: Load UW_EX_SFD_APPT and UW_EX_SFD_PMT


4/8


Recovery Options: Action (default is Stop)

The recovery options should a job fail or abend. The default is Stop, which willstop the job from continuing and not start any jobs waiting on this job tocomplete. Other options are to continue and rerun. Selecting Continue will ignore

the condition or status of the failed or abended job and will continue with the nextjob(s). Selecting Rerun will continue to rerun the job as many times as it takes torun successfully or manually canceled.

Script / Command

The name of the file that the job executes and any options or arguments. Thereis a 4096 character limit.

Task Type (default is UNIX and Script)

Either UNIX or Windows and Script or Command.

Logon (default is maestro)

The userid that the job runs under; will always be maestro.

Comments

Enter any comments that you think are needed to better define the job beingrequested.

JOBSTREAMS

Workstation

The workstation (or server) where the jobstream will run.Example: SFPRDEV.

Jobstream Name

The name of the job. There is a 16 character limit and the first six are reserved

for naming standards set by JSS.Example: SFGRN_UWJT9007where SF is the Area Code for all SharedFinancial jobs, GR is the sub-Area Code for Grants, N is the frequency code andthe underscore is reserved for future use. The remainder of the jobstream nameis one the customer chose to uniquely identify the job in the system.The first character of the jobstream name must be a letter, and it can containalphanumeric characters, dashes (-), and underscores (_).


5/8


Jobstream Description

The description of the job, which can be up to 64 characters in length.Example: Load UW_EX_SFD_APPT and UW_EX_SFD_PMT

Start Time (HH:MM)

Use the 24 hour clock to specify the time the jobstream should start.Example 19:30for 7:30pm

Priority (default is 10)

If a priority of anything other than 10 is requested please justify in thecomments.

Carry Forward (default is checked)

If checked, the jobstream is eligible to be carried forward to the next productionday if it has not completed before the end of the day.

Run Cycle (day(s) of the week/month/year)

Specify whether the job is an on-request job, the day(s) of the week/month/year,weekdays, workdays, or freedays by checking the appropriate boxes.

Definitions: Sunday through SaturdayChecking any of these boxes will schedule the jobstream to run on

that particular day of the week.

EverydayChecking this box will schedule the jobstream to run every day,even on holidays.

WeekdaysChecking this box will schedule the jobstream to run on weekdaysonly, even on holidays.

HolidaysEnter a Y or N in this box to specify whether a jobstream willschedule on a holiday. The default is Y; specifying an N will requireJSS to add a second calendar to the jobstream (holidays).

On RequestChecking this box will not schedule this jobstream on any day.


6/8


OtherChecking this box will require the requestor to add information intothe Comments box for further clarification of the schedule.

Examples: Jobstream runs M-F

Check the boxes for Monday, Tuesday, Wednesday, Thursday,and Friday or the box for weekdays.

Jobstream runs every day of the week, including holidaysCheck the box for Everyday

Jobstream runs on Tuesdays and Thursdays, but not on holidaysCheck the boxes marked Tuesday and Thursday, enter an N in thebox for holidays.

Jobstream runs on Student CALC nights only

Check the Other box and enter information in Comments.

Jobstream runs the third Thursday of every month (or quarter)Check the Other box and enter information in Comments.

Predecessors and Dependencies

Specify any predecessors and/or dependencies to the job and/or jobstream beingrequested. This can be jobstreams, jobs, files or resources.

Any external jobstreams listed as a dependency must complete successfullybefore this jobstream may launch. Specify by workstation name and jobstream

name.Any external jobs listed as a dependency must complete successfully before thisjobstream may launch. Specify the workstation name, jobstream name and jobname.

Any file dependency that must exist before this jobstream may launch needs tobe identified by workstation name, file name and qualifier. More than one filedependency can be specified.

Any resource dependency that must be available before the jobstream maylaunch needs to be identified by workstation name, resource name and numberof units needed. More than one resource dependency can be specified.

Any dependencies (flow) within the jobstream should be specified in theComments.


7/8


Jobs (1-20)

List each job that should be included in the jobstream in the order they shouldrun. If any order other than sequential is requested, the flow should be listed inthe Comments. Better yet, a flow chart can be attached to the email sent to JSS

and if this is done enter See Flow Chart xxxxx in the comments for thejobstream being requested.

Comments

Enter any comments that you think are needed to better define the job beingrequested.

How to submit a template

Download the template from the Job Scheduling Services website and open the

template in Excel.

Do not change the headings in lines 1-2, rearrange the columns or in any otherway alter the entries of the template that is downloaded. This may cause errors inprocessing and those types of changes, discovered during the Job SchedulingServices Quality Assurance step, will warrant your request may be rejected in itsentirety.

No cell or entry is required; however, without entries for a workstation, jobstreamname and description in the jobstream definition or entries for a workstation,

jobstream name, job name and description, the job definition cannot be

completed.

Complete the cells you want populated, starting in line 3 and attach it to an emailto Job Scheduling Services. In the email, you should include such details as thedate of implementation and detailed setup instructions, to include predecessorsand dependencies. One recommendation is to use the "Job Scheduling RequestForm - New", complete some of the details that are generic to the request and inthe comments state "See attached template". Submit the form, which shouldopen a new email with the form included, then attach the template and send it toJob Scheduling Services.

Definitions

Definitions are coming!


8/8


Acronyms

CAS Customer Application ServicesFAQ Frequently Asked QuestionsJSS Job Scheduling Services

OPC Operations Planning & ControlTWS Tivoli Workload Scheduler TWS/d Tivoli Workload Scheduler DistributedTWS/z Tivoli Workload Scheduler MainframeXFER The term used when referring to the secure transfers processz9 The model of the Mainframe put into production on May 26, 2008

Contact Information

Job Scheduling Services = [email protected]

job scheduling request users guide (04142008).doc

Documents