Scribd
Upload
229 views

Jobtrac Basics: Getting From Here .

JobTrac is a software tool used by Zurich North America to submit and control production jobs. It works by scanning schedules defined in a dataset daily to determine if jobs should run based on their defined dependencies, time criteria, and processing period. Jobs are then loaded to a checkpoint and released once all predecessor conditions are met.

Uploaded by

Nayyar Alam
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
229 views

Jobtrac Basics: Getting From Here .

JobTrac is a software tool used by Zurich North America to submit and control production jobs. It works by scanning schedules defined in a dataset daily to determine if jobs should run based on their defined dependencies, time criteria, and processing period. Jobs are then loaded to a checkpoint and released once all predecessor conditions are met.

Uploaded by

Nayyar Alam
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 64

Done-

JobTrac Basics
Getting from here…..

to there…...
Agenda- JobTrac Basics

 Overview
 What it is…How to Get there
 How it works
 Who is responsible

 Detail
What it is….

 JobTrac is the software tool used to


submit and control the running of
production events on any platform.
What it is…. How to Get
There...

 JobTrac is the software tool used by


Zurich North America to submit and
control the running of production events
on any platform.

 Access to JobTrac is obtained by


executing the “JT” clist (TSO JT) on the
mainframe.
How it Works….
Schedules Are Defined To Jobtrac
in a PDS dataset ( SCL Library )

Jobs Released
Schedules ( SCLs ) Are
Scanned every 24 hours
via the Jobtrac Master
event

Once all dependencies


If processing
have been met
period meets
( Predecessors, Time,
today’s criteria
etc. )

Jobs Loaded To
Checkpoint
How it Works….
Schedules Are Defined To Jobtrac
in a PDS dataset ( SCL Library )
Sample of Schedule Control Language

Also known as the SCL, this is where all of the jobs are defined
to Jobtrac. The SCL is a PDS library that contains all of the
various SCLs ( Members )defined to the Jobtrac SCL Library.
Business Group
Event Name
Columns 1-8

This is where the event ( Job ) is defined to


Jobtrac with it’s dependencies.
Where the time parameters for a job are
Action Indicator defined.
Column 9 Options include:

T = Target Time
S = Start Time
A = Abort Time
Time Field
Columns 10 - 13
The time the event is scheduled to Start, the Target time specified
for a job, and or the Abort time specified for the job. Start time is
the only required field. Start time is generally coded as ASAP unless
a specific time parameter is needed.
Holiday Action
Column 14
Date event is Scheduled
Columns 15 - 18
The type of event being submitted.
Event Type Options include:
Column 19
E = environmental/Rexx IMOD
D = Dummy job
blank = job/schedule
C = Command
Execution Dependencies
Columns 20 - 24
Specifies conditional requirements.
Options include:
Resource
Column 25 “+” = Successors
“-” = Predecessors
“R” = Resource conditions
“=“ = Conditional(wait if
there)
This is where predecessor and
successor event names are
Dependency Event
defined. Additionally, this
Names is where all of the paramters
Columns 26-58 for the distributed events
are displayed. ISP standard
is to code one predecessor or
successor per line.
Specifies when event is added to
the checkpoint. Options include: Process Period
(59 - 68)
EOM = End of month
Workdays = Every workday
=.TWTFS. = Tues, Wed, Thur,
Fri and Sat only
MANY others
This field is no longer used. Predecessor Count
Jobtrac automatically determines Column 70
how many predecessors an event may
have at schedule load time.
Defines how many datasets must be Dataset Count
created to trigger event. Column 71
Maximum Condition Code
Columns 72 - 75

Maximum condition code allowed for any step.


Jobtrac also has the ability to track step level
condition codes, but this is defined in another area
within Jobtrac.
Locations signify the production datasets that a particular
job will run from. Locations are also used for different
holiday calendars if needed. The datasets are defined to
their locations in the startup parameters of Jobtrac.
Version Number
This is where specific versions of jobs (79 - 80)
can be defined. The default is 01, but if
multiple events have the same jobname,
hardcoded versions are required.
How it Works….
Schedules Are Defined To Jobtrac
in a PDS dataset ( SCL Library )

Schedules ( SCLs ) Are


Scanned every 24 hours
via the Jobtrac Master
event
Master SCL Member
This is where all of the SCLs are defined to Jobtrac. The Master scan
event typically runs once a day in the morning and evaluates all of the
SCLs to determine whether or not the SCLs should be evaluated for the
day’s processing. Typically, all of the SCLs that are defined to the
Master are evaluated everyday based on a DAILY process period.
How it Works….
Schedules Are Defined To Jobtrac
in a PDS dataset ( SCL Library )

Jobs Released
Schedules ( SCLs ) Are
Scanned every 24 hours
via the Jobtrac Master
event
Once all dependencies
If processing have been met
period meets ( Predecessors, Time,
today’s criteria etc. )

Jobs Loaded To
Checkpoint
From SDSF or ISPF, type TSO JT to
invoke Jobtrac.
List all events
Job/Sched
Name
Time/Date event Job/Sched will be
Submitted and/or flagged late.
Successor(s)
(* = multi)
Job Dependency
codes
Common Dependency
Codes
Common Dependency
Codes
Status of Job
Masking
Limits Display to Only PMS Events
Selecting the detail of the event
Event Detail Screen
Start Time
Dependency Codes
This is where the dependency codes for each
event are displayed once the jobs are loaded
to the checkpoint.
Production Member Name
This is where the production member name for each event are displayed
once the jobs are loaded to the checkpoint. This is assumed to be the
same as the Event name, unless an alternate JCL member has been defined
in the SCL.
Maximum Condition Code Allowable for The Job
This is where the maximum condition code for each event is displayed on
the checkpoint. This is based on the code that is defined in the SCL
for the highest acceptable condition code for this particular event.
Business Group. This is where a job’s business group name is defined.
Temp Member. This is where the temporary member name is displayed if
the job is running out of Jobtrac’s temporary JCL facility. If a job
fails, the Operator is able to insert a temporary one-time override for
the job in order to correct the error.
Predecessor Count. This is where the number of predecessors for the job
are defined. In this example, PMSAW100 has 001 predecessor and you can
See the predecessor name in the lower left hand corner.
Predecessors. This field shows the predecessors that are defined for the
event and the status of the predecessors.
Successors. This field shows the successors that are defined for the
event and the status of the successors.
Display business group info
General information

 JobTrac schedules are generally loaded


everyday at approximately 08:00 AM.
 JobTrac is a successor based scheduler, but it
does handle predecessor requirements
 JobTrac is a Computer Associates software
product
 JobTrac is implemented at all ISP supported
companies

You might also like