how banca intesa sanpaolo uses consolidation and res suite to … · 2016-12-19 · intesa sanpaolo...
TRANSCRIPT
© 2014 IBM Corporation
How Banca Intesa Sanpaolo
Uses “z-centric” Workload Consolidation
and RES Suite to Optimize Business Services
Michele Zilli, Intesa Sanpaolo Group Services
Nico Chillemi, IBM
Marco Passerini, RES
zCircle – Milano Nov 8 / Roma Nov 10 - 2016
Session #2291
Abstract
"How to take advantage of IBM Workload Scheduler for z/OS zCentric and how to
design and automatically create jobs and schedules with the RES Suite"
"Intesa Sanpaolo Group Services, that serves the information system of Intesa
Sanpaolo, is often challenged to create new scheduling environments and reporting
systems, to automate new subsidiaries or merge multiple banks. Of course, the
creation of the new scheduling environments must be done in a short timeframe and
with zero risks. Combining IBM Workload Scheduler for z/OS environment, and its
ability to expand the automation into open systems (zCentric solution), with the RES
suite, Intesa Sanpaolo Group Services is able to satisfy the challenge, designing,
creating, and deploying new schedules, based on existing ones and user criteria."
1
IBM Workload Scheduler zCentric Configuration
Z/OS Domain
IWS z/OS
Agents
IBM Workload
Console
Websphere
Application
Server
IWS Distributed
zCentric Agents
IWS z/OS
Engine
Sysplex
IWS zCentric
Dynamic Agent
3
Overview of IBM Workload Scheduler environment in ISP
Ma
infr
am
e
Dis
trib
ute
d
IWS z/OS
zCentric agents
UNIX
WINDOWS
LINUX for
SYSTEMz
IBM
System i
Intesa Sanpaolo leverages
IBM Workload Scheduler for z/OS
and zCentric agents
to optimize end-to-end workload
automation & RES Suite
4
Having gone through
multiple banking institutes
merging, Intesa Sanpaolo
has faced all challenges
deriving from consolidation
projects.
They brought optimization
and efficiency into their
workload automation. High Availability & Scalability
Centralized job management
Easy to use and maintain
Advantages of zCentric solution
Banks must be “zero failure”
5
Mainframe
Distributed
High
Availability
cluster
zCentric agents
IWS z/OS
Hot Standby controller (mainframe)
High availability cluster (distributed)
All resources associated to zCentric
agents are «moved» to an alternative
active node
High availability
High Availability & Scalability
Scalability
> 1,360K IWS schedules total
> 8M daily jobs with 6 IWS z/OS Controller
Centralization simplifies management
6
Centralized job management
Modelling and monitoring of
end-to-end jobs from a
centralized point of control
Minimum additional total cost
of ownership to support
business growth
No need to build new skill to
incorporate new types of
jobs in the workflows
Centralization simplifies management
7
Single skill-set (reusage of
IWSz skill-set)
RES J-MAN/JADe allow to
write and clone distributed
jobs in an very simple way
Automatic deployment of fixes
through IBM Endpoint Manager
integration (bundled license)
Easy to use and maintain
Intesa Sanpaolo – some basic facts
74%
ISGS – Management Information
Systems
6 IWS subsystems
1 IWS subsystem
5 PWS subsystems
70.000 «master» schedules 1.350.000 «run time» schedules
29 clones for 29 environments >8M avg JOBs/day run
Specialistic
Business
(7)
Multi-Bank
Environment
(1)
Commercial
Clones
(21 banks)
Pro
d
Ma
infr
am
e
Op
era
tio
ns
Pro
d L
UW
Op
era
tio
ns
(z/c
en
tric
)
tota
l
Te
st
En
vir
on
me
nt
Scheduled > 1.2M JOBs z
On demand > 100 K PIF
Scheduled > 60K JOBs d
On demand > 4 K PIF
Scheduled > 60 K JOB
> 12 K JOBd
On demand > 14 K PIF IWS
sch
ed
ulin
g I
nfr
astr
uctu
re
8
daily a
vera
ge
ab
ou
t …
J-MAN & JADe/MP in ISGS
IWS, J-MAN & Jade/MP targets
1 • Provide developers with a tool to make them autonomous in developing IWS applications
2 • Make developers able to automatically create their own LUW and z/OS jobs
3
• Make changes to the IWS applications as much automatic as possible, based on developers requests (tool vs manual form)
9
Automatic management of changes in the batch flow
Scheduling Change Flows
Release Unit Definition
Modify IWS Sched & JOB definition z/centric
app
licat
ion
de
velo
pe
r
Modify request Life Cycle and Power Environments
ISP Change
Console
Ch
ange
Man
age
me
nt
Master Application Test
IWS & JOBLIB
Run-time
Automatic
UPLOAD
Master System Test
Automatic
UPLOAD
Master Acceptance Test
Automatic
UPLOAD
Master Production
Automatic
UPLOAD
Cloning objects
IWS & JOBLIB
Run-time
IWS & JOBLIB
Run-time
IWS & JOBLIB
Run-time
JADe/MP
J-MAN
10
J-MAN & JADe/MP in ISGS
BENEFITS
Same language and tools used by developers (requesting application creation and/or change) and the scheduling teams
(implementing them)
Reduction of manual activities in both request of change (developer) and change to the applications (scheduling)
Automatic syntactical and standards fulfilling checks, starting from the very first steps of the applications life-cycle
Industrialization of the creation of production environments clones for the 20 banks of the group
11
Analysis Development Pilot Rollout
6 months 6 months 3 months 3 months
Automatic management of open systems jobs
12
13
Automatic management of IBM Workload Scheduler applications
The IBM RES Suite tools – J-MAN & JADe/MP
• Meta-language: definition of processes related to application logic: Sequence of programs, file and tables used, …
• Basic information obtained from models, or standards, or automatically detected from program code (RES Docet/MP required – SW asset discovery)
• Automatic generation in the target processing language (JCL, unix shell, Powershell, Windows Bat) and Schedules (including Ct/M, IWS, CA/7, …) according to specific rules
• Reverse engineering to recover existing JOBs and Schedules
14
• syntax check
• automatic generation of documentation within the same batch object (files, tables, databases and programs used by the job)
• complete quality control (to identify and remove environment-related errors and mismatch between programs and jobs)
• an efficient and automatic tool for cloning objects for multiple target environments
• automatic fulfilling of requirements (including client site standards)
• propagation between different environments (e.g. Dev.-->Test – Test -->Prod
• help in the migration of tools (batch scheduler migration)
Through the ensuring of optimal performance: reduced cost of management, and general reliability
across all environments.
15
The IBM RES Suite tools – J-MAN & JADe/MP
Generating new jobs and schedules with JADe/MP:
as easy as … 1, 2, 3!
2) Configuring meta-domains and naming conventions
For each component, the administrator defines rules for the control of parameters to prompt the user for the
exeuction of JOBs, Scripts and batch streams (i.e. Naming convention rules).
1) Definition of the basic functional components
The administrator prepares the basic components through a UI Web administrator.
A component is a basic function (i.e file copy, sort, program run, ...) described by a standard formalized function, which
“hides” the complexity of the process from the user.
…extra … Interface to the change cycle and reverse
• modify an existing object
• “reverse” existing jobs/schedules within JADe/MP
• insert the modified object(s) into the change cycle (through a change-manager)
3) Develpment of JCL, Script and Batch Streams and schedules
The user chooses the components to be inserted (steps in jobs – jobs in schedules) - the tool automatically creates
the jobs (Scripts, Shell, JCL, …) and Batch Schedules
16
JADe/MP as easy as … 1, 2, 3! 1) Definition of the basic functional components – the ADM component
17
Admin. creates a skeleton of
step (script/Shell/Bat/JCL/…) for
the execution of a specific
function (i.e. Execution of a DB2
program) .
The admin. defines all the
parameters the users can choose,
and that will be subsequently
identified automatically by
JADe/MP and prompted for.
For each parameter, the admin. can specify the
required value and associated meta-domain in
which rules are pre-defined (i.e. naming
conventions, a list of allowed values).
Standardize the
construction of a JOB and
Batch Stream
17
18
The administrator can code specific
components for a script in different
languages.
The coding is done using the syntax of the
chosen language (no “meta-language”).
18
JADe/MP as easy as … 1, 2, 3! 1) Definition of the basic functional components – the ADM component
19
The user can choose the
component only after it has
been validated and
“published”.
The administrator can
preview components that will
be available to the users.
Logical grouping of
components are shown
here (palette)
A component can also be
(temporarily) invalidated
Only valid
components are
visible
Components are stored
in “Function Libraries”
19
JADe/MP as easy as … 1, 2, 3! 2) Configuring meta-domains and naming convention – the ADM component
A meta-domain allows to control the
usage of allowed parameters only.
It is possible to set up simple controls:
• Value checked for length, allowed
characters, type of data (date,
number, ...)
• A list of values from which the user
can select (domain tables)
• A range of values
• Control via a formula
• Call functions external to JADe/MP
Check of all
parameters = less
errors
20
JADe/MP as easy as … 1, 2, 3! 2) Configuring meta-domains and naming convention – the ADM component
User creates his job by
selecting those
components published and
made available by the
administrator, with a simple
drag-&-drop.
The order of execution of
each component can also
be changed simply via drag-
&-drop.
Build a job just
with drag/drop of
components 21
JADe/MP as easy as … 1, 2, 3! 3) Development of Script, JCL and Batch Streams - the USER component
For each added component, the user is
prompted for all the required extra parameters.
The user is guided through the development of
every single parameter:
• Description of a single value
• Mandatory verification
• Select from a list of allowed values
• …
Errors free jobs
and schedules!
22
JADe/MP as easy as … 1, 2, 3! 3) Development of Script, JCL and Batch Streams - the USER component
JADe/MP displays the JOB
while it is being developed.
Independence from the
target SCRIPT
language
The user is not required to have detailed knowledge of
any language (SCRIPT or JCL).
The basic functionality of JADe/MP allows to hide the
complexity of the target language
23
JADe/MP as easy as … 1, 2, 3! 3) Development of Script, JCL and Batch Streams - the USER component
Automatic
creation of
“batch streams”
Jobs to be executed by the batch flow are selected by the user.
The design of a z/OS or LUW “batch stream” is automatic,
based on the selection of JOBs prepared by the user
Only the basic information are
shown when selecting jobs .
Additional information, typically
related to the scheduling
environment, will be added
automatically during the
generation process.
The “batch stream template” is
displayed to the user as
defined by the administrator to
impose a standard structure
(i.e. Start and end nodes,
backup and restore, ....).
24
JADe/MP as easy as … 1, 2, 3! 3) Development of Script, JCL and Batch Streams - the USER component
Automatic
creation of
“batch streams” Calendar and Run Cycle definition
25
JADe/MP as easy as … 1, 2, 3! 3) Development of Script, JCL and Batch Streams - the USER component
A unique
Package for all
the
created/changed
objects
A package allows the user to collect objects of different types,
related to the same change or creation activity, in a single
package (jobs and schedules).
As part of a “change cycle”
PACKAGE, the objects are
promoted only if all the items
in the package are considered
“valid”.
26
JADe/MP as easy as … 1, 2, 3! 3) Development of Script, JCL and Batch Streams - the USER component
J-MAN the online editor
Comments about
usage of
resources
automatically
created in the
JCL
27
J-MAN Syntax Check / Environment Check / and Mismatch Check
Online Syntax
check …
… and much more
than a syntax
check:
Complete QA for
check of
environment and
mismatch pgm-job
28
J-MAN Change / Conversion / Cloning / Migration
Changes to a JOB, a list of JOBs
or to a schedule and all its JOBs
You can convert to multiple target environments at once
Schedule change, conversion/migration/cloning
29
Thank You
Your Feedback is Important!
Marco Passerini - RES
+39 335 7474 394 @MarcoPasseriniR
Nico Chillemi - IBM
+39 335 5999629
Michele Zilli – Intesa Sanpaolo Group Services
+39 340 0841 579