Pre-Con Ed: CA Workload Automation ESP Edition: Hints, Tips and Tricks

World®
’16
CA Workload Automation ESP Edition
Hints, Tips and Tricks
Steve Wotton, CA Technologies, Sr. Principal Consultant
MFX25E
MAINFRAME AND WORKLOAD AUTOMATION

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
In this session you will learn about ways to reduce manual
intervention and streamline your batch workflows.
By leveraging a variety of features, functions and techniques,
you can optimize your CA Workload Automation ESP Edition (CA
WA ESP) Procedures and CA WA ESP Applications to simplify and
automate your complex scheduling requirements.
Steve Wotton
CA Technologies
Sr. Principal Consultant

Agenda
SCHEDULE CRITERIA
DUEOUT PROCESSING
TEMPLATES
CONFIGURATION OPTIONS
1
2
3
4

Schedule Criteria
§ CA WA ESP Edition enables you to use free format, everyday
English, to specify schedule criteria when scheduling Events,
jobs and other tasks
§ CA WA ESP Edition has a built-in understanding of general
scheduling terms and you can add your own unique
scheduling terms to a calendar to include holidays and special
processing days/periods
Overview

Schedule Criteria
Overview
§ You can specify schedule criteria up to the year 2042 which is
a limitation in the representation of time on IBM z/OS systems
– Time in z/OS is represented by a 64-bit integer with the number of
microseconds since Jan 1, 1900, which will rollover on Sept 17, 2042
– IBM has defined a 128-bit time format available on newer hardware,
but many applications and software continue to rely on the 64-bit
format

Schedule Criteria
Overview

Schedule Criteria
Example
§ Run 9th day of month, only if the 9th is a Sunday, else run on
the first Sunday after the 9th day

Schedule Criteria
Example
§ Run every Friday except the first and last Friday of the month

Schedule Criteria
Example
§ Run 31st day of month but only in months that actually have 31
days
Hmmm……
Hmmm……
JOB PAY001
IF ESPSDD = “31” THEN RUN TODAY
ENDJOB
Check “Scheduled Date” variable to determine if the scheduled day is the 31st before selecting job

Schedule Criteria
Example
§ Run 1st Monday of month… but if the month starts on a
Saturday or Sunday, run on 2nd Monday of the month instead
JOB SOMEJOB
GENTIME FST 1ST DAY OF MONTH STARTING TODAY
IF FSTDAY = ‘SATURDAY’ OR FSTDAY = ‘SUNDAY’ THEN -
RUN 2ND MONDAY OF MONTH
ELSE RUN 1ST MONDAY OF MONTH
ENDJOB
Use GENTIME to determine the day of the week on which the current month starts, and depending on
the result, schedule the job to run either the 1st or 2nd Monday of the month
Runs 1st
Monday
Runs 2nd
Monday

Calendar Retain Count
§ Calendar Retain Count indicates how long a Holiday or Special Day is
stored on a calendar - default is 2 days after the date occurs
§ You must take into account how long a Holiday or Special day may
need to be referenced, to determine the Retain Count
§ Holiday and Special Day Instances are only deleted after the Retain
Count is reached and once a calendar update is made
Overview

Calendar Retain Count
Example
§ BLACK_FRIDAY PLUS 1 WEEK will only resolve if BLACK_FRIDAY is
retained for at least 1 week after the date specified
JOB PAY001
RUN BLACK_FRIDAY PLUS 1 WEEK
ENDJOB

DUEOUT Processing

NOW vs REALNOW
§ The term “NOW” in CA WA ESP refers to the scheduled time an
Event was triggered
§ The term “REALNOW” in CA WA ESP refers to the actual time an
Event was triggered
Overview

NOW vs REALNOW
§ A cyclic job runs every 1 minute until 4pm. If any step returns a
non-zero return code the job will stop processing, and once the
error has been resolved the job is restarted and the 1-minute
cyclic processing will continue
§ This example uses NOW, REALNOW and RERUNM commands
– NOW refers to the scheduled time of the Event while REALNOW refers to the actual
time the Event was triggered
– RERUNM (Rerun Multiple) command can be used to rerun one or more jobs in an
Application with execution dependencies reset to the state they were in before the
jobs ran, and then then rescheduled as their dependencies are satisfied
Example

JOB CYCLIC
RUN DAILY
CCCHK RC(1:4095) FAIL STOP
RELEASE (REPEAT.CYCLE)
ENDJOB
JOB REPEAT.CYCLE TASK SELFCOMPLETING
RELDELAY 1
ESP RERUNM APPLICATION(CYCLIC.0) ROOTJOBS(CYCLIC+)
ESP AJ REPEAT.CYCLE APPLICATION(CYCLIC.0) RESET EARLYSUB('REALNOW PLUS 1 MINUTE')
RUN DAILY
ENDJOB
JOB END.CYCLE LINK PROCESS
EARLYSUB 4PM
ESP AJ ALL COMPLETE APPL(CYCLIC.0)
RUN DAILY
ENDJOB
NOW vs REALNOW
Example
Rerun all jobs in this
Application beginning
with job CYCLIC
Reset RELDELAY time
to 1 min from when
command issued

Late Prediction
§ Late Prediction is an extension of the DUEOUT or LATESUB
processing and provides advanced warning provided when a
Job is predicted to be late
§ Provides notification when a job that was originally predicted
to be late is once again on time
§ Supports cross Application dependencies by propagating
anticipated times through External jobs to provide notification
Overview

Late Prediction
§ Late Prediction is activated by specifying LATEPRED
Initialization Parameter
– Provide notification if a job’s Due-out time is within the next 5 hours
and the job is predicated to go overdue by more than 3 minutes
– Notification does not occur if overdue state falls outside of the
boundaries
LATEPRED ON(5,3)
Overview

Late Prediction
§ Provide notifications based on late predictions
Example
JOB A HOLD
RUN DAILY
DURATION 40
RELEASE B
ENDJOB
JOB B
RUN DAILY
DURATION 40
DUEOUT EXEC NOW PLUS 2 HOURS
NOTIFY LATEPRED(1,5) USER(SWOTTON)
ENDJOB
Provide notification if
Job is predicted to be
late by 5 mins or more
and Dueout time is
within 1 hour
At 10:00, AET is 11:20 and DUEOUT is 12:00
STATUS: Not Late
STATUS: 10 mins late but Don’t Notify since
more than 1 hour until Dueout time
STATUS: 20 mins late - Send Notify since
there is 1 hour or less until Dueout time
arrives and job is more than 5 mins late
Start Time: 10:00
Due-out Time: 12:00

Templates

Templates
§ A Template is an element of CLANG you can use to specify
repetitive commands or statements once
§ Parameters, positional or keyword, are passed to the Template
and through an iterative process, the Template is expanded
TEMPLATE BILLING(1,JOBNAME)
JOB %JOBNAME
RUN DAILY
ENDJOB
ENDTEMPL
BILLING BILLJOB1
BILLING BILLJOB2
JOB BILLJOB1
RUN DAILY
ENDJOB
JOB BILLJOB2
RUN DAILY
ENDJOB
Overview

Templates
§ Create a Template that
passes parameters for the
Jobname and any
successor
§ All jobs have the same Run
Frequency and Tag field
APPL BILLING
JCLLIB 'WOTST01.DEMO.CNTL'
TEMPLATE BILLING (1,JOBNAME, NEXTJOB())
JOB %JOBNAME
RUN DAILY
TAG 'BILLING JOB'
IF NEXTJOB NE '' THEN RELEASE (%NEXTJOB)
ENDJOB
ENDTEMPL
BILLING BILLJOB1 NEXTJOB(BILLJOB2, BILLJOB3)
BILLING BILLJOB2 NEXTJOB(BILLJOB4)
BILLING BILLJOB5 NEXTJOB(BILLJOB6, BILLJOB7)
BILLING BILLJOB8
Example

Templates
§ When downloaded via Workstation, a Template does not expand
or resolve graphically until the CA WA ESP Procedure is Simulated
Example

Configuration Options

Generating and Processing an Application
Event Triggers
Application
Generation Phase
Application
Process Phase
Application Generation Phase
• Reads the CA WA ESP Procedure
• Determines which jobs are scheduled today
along with their requirements
• Creates the job-flow
Application Process Phase
• Assesses whether predecessor and
time dependencies have been met
• Determines whether Resource
requirements have been met
• Re-triggers Event to submit job and
perform further processing
Overview

Concurrent Event Processing
§ Event Initiators enables you to provide dedicated classes of
initiators to specific Events and are often used to prioritize
and stream critical Event processing
§ We recommend that you create six Event Initiators, which
enables CA WA ESP Edition to process six concurrent requests
– You can add more event initiators to meet your performance
requirements and workload volume
Overview

§ Use the EICLASS Initialization Parameter to create an Event Initiator Class
specifying an identifying class number and number of initiators
• EICLASS display command provides:
– Number of Initiators for each class
– Number of Initiators active
– Max number of allowed Initiators
– Number of Events and jobs each
initiator has processed to date
Overview

§ Use the EICLASS parameter in an Event to specify in which
Initiator Class and Event should process
Example

Procedure Caching
§ Procedure Caching can improve CPU usage and processing
speed for CA WA ESP procedures that have over 400 jobs
§ Procedure caching allows you to keep an original cached copy
of a CA WA ESP procedure to reduce I/O during processing
§ A cached copy of the CA WA ESP procedure is stored in the
APPLFILE
Overview

§ To turn on procedure caching for all Procedures, add the
following Initialization Parameter:
– PCACHE ON
§ To turn on procedure caching for certain Procedures, such as
those containing large Applications, add the following
Initialization Parameter:
– PCACHE ENABLE
§ Then, add the CACHE operand to the INVOKE statement in
either the Event or Application
Procedure Caching
Overview

Procedure Caching
§ Each time the PAYROLL Application is invoked, the DATES
procedure is also invoked containing symbolic variables required
by the jobs in the Application
§ The DATES procedure will be cached in memory to speed access
APPL PAYROLL
JCLLIB 'CYBER.JCL.CNTL'
INVOKE 'CYBER.SYMBOLS.CNTL(DATES)' CACHE
JOB PAYJOB1
RUN WORKDAYS
ENDJOB
Example

Results
In this session we discussed ways to reduce manual intervention and streamline your batch workflows by
making use of a variety of features, functions and techniques related to:
• Maximizing schedule criteria
• Streamlining job dependencies
• Providing proactive Dueout notifications
• Reducing code through iterative Templates
• Enabling configuration options to improve CPU usage and minimize file i/o
Summary
A Few Words to Review

Questions?

Recommended Sessions
SESSION # TITLE DATE/TIME
MFX26E
CA Workload Automation ESP Edition: SLA Management
and Business Continuity
11/14/2016 at 1:00 pm
Jasmine B
MFX31E
Better Big Data Analytics with CA Workload Automation
for Hadoop
11/14/2016 at 3:00 pm
Jasmine B
MFX24E
Wobtrigs and File Triggers with CA Workload Automation
ESP Edition
11/15/2016 at 11:00 am
Jasmine B
MFX33E
Best Practices for setting up CA Workload Automation
ESP Application Procedures
11/15/2016 at 1:00 pm
Jasmine B

You Are Cordially Invited……..
CA Workload Automation & CA Process Automation
Where? South Seas E
When? Tuesday, November 15th
Time? 4:30pm – 6:00pm
Customer & Partner Reception

Must See Demos
Modern
Workload
Automation
CA WLA DE
MF and Workload
Automation
Seamless
Application
Automation
Agents & Advanced
Integrations
MF and Workload
Automation
CA Conversion
as a Service
CA Workload
Automation
MF and Workload
Automation
Innovations:
Mainframe
Workload
Automation
CA WLA CA 7 & ESP
MF and Workload
Automation

Thank you
Stay connected at communities.ca.com

Pre-Con Ed: CA Workload Automation ESP Edition: Hints, Tips and Tricks

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (6)

Similar to Pre-Con Ed: CA Workload Automation ESP Edition: Hints, Tips and Tricks

Similar to Pre-Con Ed: CA Workload Automation ESP Edition: Hints, Tips and Tricks (20)

More from CA Technologies

More from CA Technologies (20)

Recently uploaded

Recently uploaded (20)

Pre-Con Ed: CA Workload Automation ESP Edition: Hints, Tips and Tricks