tws 8.6 new features (from the 2013 european tour)

© 2012 IBM Corporation

TWS for z/OS V8.6New Features

1

Domenico ChillemiExecutive IT [email protected]


TWS Configurations Overview

33 © 2012 IBM Corporation

TWS z/OS Configuration

Centralized Modeling and Control for z/OS only scheduling TWS for z/OS Engine

– Owns the scheduling database, drives all the scheduling activities, and implements all Scheduling control logic TWS for z/OS Server

– Manages communication with TWS components located outside the Controller Addtess Space TWS for z/OS Agents

– Receives jobs to be executed by Engine, interface JES and SMF, sends back events to the Engine.– Connected to Engine via XCF, Shared DASD, TCPIP or SNA.

Sysplexz/OS Domain

TWS for z/OSAgents

TWS for z/OS Engine

TWS for z/OSHot standby Engine

Scheduling DataBase

Scheduling Plan

TivoliWorkloadConsole

Info Mgmt

TWS for z/OS/ES

A

Monitoring ALLSYSTEMSCITY1 CITY2

CITY3

ISPF

WebsphereApplication

Server


Centralized Modeling and Control for Distributed only scheduling TWS Distributed Engine

– Owns the scheduling database, collects events from the underlying Agents and resolves cross-domain dependencies

TWS Distributed Agents – Intelligent agents capabale to work autonomously– Connectivity to ERP applications

TWS Distributed Hybrid Configuration


Distributed Domain

TWS DistributedEngine

TWS DistributedDomain Manager

TWS Distributed Agents

Scheduling DataBase

Scheduling Plan


Server

TWS DistributedDomain Manager on zBX


Centralized Modeling and Control from z/OS environment for all Enterprise scheduling (z/OS and Distributed)

TWS End-to-End Hybrid Configuration Plan Based end to end

Z/OS Domain

TWS z/OSAgents

TWS z/OSEngine

TWS DistributedDomain Manager on zBX



TWS DistributedAgents

Tivoli Workload Console


ServerSysplex


Centralized Modeling and Control from z/OS environment simple http protocol

TWS End-to-End Hybrid Configuration zCentric end to end

Z/OS Domain

TWS z/OSAgents

Tivoli Workload Console


Server

TWS DistributedzCentric Agents

TWS z/OSEngine

Sysplex


Manage small z/OS batch environments through a Distributed Master Domain Manager

TWS End-to-End Hybrid Configuration d-Driven end to end


Distributed Domain

TWS DistributedEngine

z/OS withd-driven agents

TWS DistributedDomain Managers

Scheduling DataBase

Scheduling Plan


Server


Mixed TWS End to End Configuration

WAS

TWS for z/OS

TWS Distributed

TWSWeb Console

TDWC

Cross Dependencies


End to End Continued Evolution


PeoplSoftOracle

SAP

How Version 8.6 contributes to the end-to-end evolution

JCL//JOB1 JOB//LIB DD DSN//ST1 EXEC IEB Script

Echo 1Cmddirv

ERP

Workloads

Agents

Engines

JCL//JOB1 JOB//LIB DD DSN//ST1 EXEC IEB



ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1CmddirvJCL

//JOB1 JOB//LIB DD DSN//ST1 EXEC IEB

XAM

ainframe

Distributed

2001

Plan-based end-to-end and MVS XA

z/OS Trackers FTA and SA

z/OS ControllerMaster Domain

Manager

2006

WebUI and Multimaster, Broker

zCentric

2009

zCentric end-to-end

Broker






ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

PeoplSoftOracle

SAP

ERP

http://3.bp.blogspot.com/_qHYW251Fd2I/TI4JkJxyZ-I/AAAAAAAABgc/8Obj_OrWihc/s1600/Power7.jpg


Dynamic zCentric end-to-end and iSeries support

PeoplSoftOracle

SAPJCL//JOB1 JOB//LIB DD DSN//ST1 EXEC IEB Script

Echo 1Cmddirv

ERP

Workloads

Agents

Engines




ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv



XAM

ainframe

Distributed

2001




Manager (+ Broker)

2006

WebUI and Multimaster

zCentric

2009

zCentric end-to-end

z/OS SA

z/OS Controller

zCentric






ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

PeoplSoftOracle

SAP

ERP

2011V8.6

PoolDynamic Pool

Broker

iSeries support

Dynamic DM




PeoplSoftOracle

SAP



Echo 1Cmddirv

ERP

Workloads

Agents

Engines




ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv



XA

Mainfram

e

Distributed

2001




Manager

2006


zCentric

2009

zCentric end-to-end

z/OS SA

Master Domain Manager (+ Broker)

2011


Distributed-driven end- to-end






ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

PeoplSoftOracle

SAP

ERP

V8.6

PoolDynamic Pool

Broker

iSeries support

Dynamic DM





Distributed-driven end- to-end

Cross-dependencies and multi-engines monitoring view

PeoplSoftOracle

SAP



Echo 1Cmddirv

ERP

Workloads

Agents

Engines




ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv



XAM

ainframe

Distributed

2001




Manager

2006


zCentric

2009

zCentric end-to-end

z/OS SA


Manager (+ Broker)






ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

ScriptEcho 1Cmddirv

PeoplSoftOracle

SAP

ERP

2011V8.6

Dynamic DM

PoolDynamic Pool

Broker

iSeries support



http://www.clker.com/clipart-cloud-12.html

http://www.clker.com/clipart-cloud-12.html

http://www.clker.com/clipart-hugecloud.html


Business benefits

Matching job requirements to available resources

Controlling and optimizing use of resources

Automatic discovery of scheduling environment resources

Automatically following resource changes

Requesting additional resources when needed

---------- ISPF ----------

Controller

Trackers

Mai

nfra

me

Dis

trib

uted

Dynamic zCentric end-to-end : key points

ScenarioAs a standard practice in the workload automation discipline, the insurance company has the target to optimize available

resources, and implement load balancing policies where possible. The company has adopted the zCentric end-to-end solution for its simplicity, and they would like to exploit brokering capabilities.

Pool: Cluster of machines, selected by the user; jobs are balanced across available agents.

Dynamic Pool: Group of machines automatically identified to match a set of user defined resource requirements. Jobs are distributed according to user polices.

Broker: Backward compatibility with old broker.

Implement the broker technology in the zCentric end-to-end solution.

Dynamic Domain Manager

Three main scenarios for three typology of Dynamic Domain Manager

http://it.123rf.com/photo_7412023_fast-moving-bus-lights-blurred-over-modern-city-background.html


Dynamic zCentric end-to-end : dynamic pool

Three types of Dynamic Pools, to implement three types of scenarios:

Dynamic Pool: Group of machines automatically identified to match a set of user defined resource requirements. Jobs are distributed according to polices defined by the user. Also possible to establish an order in the machines, and implement a failover mechanism.

Operating Systems requirements

CPU utilization

Logical Resources

Workload balance

CPU utilization

Logical resource


Scenario A rocket company's IT environment is based 80 percent on a distributed network and the other 20 percent on a z/OS system. They do

job scheduling with Tivoli Workload scheduler in the distributed networks. In the z/OS environment they schedule partly with a non-IBM product and partly run native JCL jobs in the JES environment. They like the way Tivoli Workload Scheduler works and would like to have the opportunity to manage some of this workload from their distributed scheduler.

Distributed-driven end-to-end : key points

Mai

nfra

me

Dis

trib

uted

• Easy z/OS agents installation and configuration (through HTTP, optionally SSL)

• No Symphony mechanism• High availability, sysplex

support• Creation of jobs by

definition • TWS Variable definition • Retrieve of joblog

Reuse skills and procedures already in place while extending the automation to additional workloads

Business benefitsExpand the reach of TWSd automation to mainframe

jobs, with minimum additional TCO

Broker


Evolve multi-master configuration, liking cross activities

Consolidate management and monitoring of workloads spread across multiple masters

Business benefits

ScenarioAn enterprise organization comprises multiple activities; some of them are run in different sites or involve different

organizational units; others require different skills to be run. For these reasons scheduling environments must be kept separated.

Nevertheless, none of these environments is completely isolated from the others but most of the times they need to interoperate to exchange or to synchronize on data and activities.

Cross-dependencies : key points

HTTP connection between engines, SSL secure

Remote workstation

Shadow job

Lookup table

TWSd

JOB BTWSz

JOB A

B SHADOWdependency

Bind request and status notification

Bind

Status notification

Arc

hite

ctur

e an

d de

finiti

ons

Sync

hron

izat

ion

mec

hani

sm

Easier mapping of workflows spanning multiple engines.


New “remote” workstation to represent the remote environment running the job that we want to involve in the cross-dependency

“Shadow” job (on the remote workstation) to mirror the remote dependent job

Dependency between the job and the shadow job

Lookup table

Definitions

Shadow job

Identify the shadow job

Identify the remote job by its key

How to react to a failed bind

Dependency criteria resolution

Cross-dependencies : key points


Cross dependencies implementation on TWSz (1/3)

TWS PARMLIB

– Remote Controller

ROUTOPTS HTTP(ZT01CROS:'10.3.20.1'/521/Z)

HTTPOPTS TCPIPJOBNAME('TCPIP')HOSTNAME(10.3.20.2)

HTTPPORTNUMBER(531) ...

– Main Controller

ROUTOPTS HTTP(ZT01CROS:'10.3.20.2'/531/Z)

HTTPOPTS TCPIPJOBNAME('TCPIP')HOSTNAME(10.3.20.1)

HTTPPORTNUMBER(521) ...



Remote Controller

Main Controller


Provide an aggregated view of cross-engines workload, for easy monitoring and immediate perception of workload ongoing status

Business benefits

ScenariosAn enterprise organization consists of a headquarter where central office accounting department is located, and

multiple branch offices located all over the world, where several administrative departments carry out accounting activity. The central office is in charge of the company's entire accounting workload. Therefore, the Tivoli Workload Scheduler operator must verify that all the workload processing for the company proceeds smoothly and without errors and needs an aggregated and comprehensive workload management

Multi engines monitoring feature represents one step forward in consolidation of activities spanning multiple scheduling environments

It provides an aggregated vision and monitoring of workloads running on different engines

Multi-engines monitoring view


Definition

Create a New Task and select Multiple Engines Monitor Task.

Then Select the engines which you want to be involved in the query.

Define filtering

Select columns

Run the task



Batch Modernization


Modern challenges in the batch processing

http://www.google.com/imgres?imgurl=http://www.lincwebhosting.co.uk/images/ftp.png&imgrefurl=http://www.lincwebhosting.co.uk/features_ftp.html&usg=__tmdl3BtGbXn-fWb1AYV2V65_cnc=&h=128&w=128&sz=13&hl=it&start=79&zoom=1&tbnid=2KW6WV2u_5vByM:&tbnh=91&tbnw=91&ei=H3RKTfjyPIOYhQeO0tTIDg&prev=/images%3Fq%3Dftp%26hl%3Dit%26sa%3DG%26biw%3D1276%26bih%3D789%26gbv%3D2%26tbs%3Disch:1&itbs=1

http://www.google.com/imgres?imgurl=http://cursos.cdtc.org.br/file.php/1/imagens/logo_sql.gif&imgrefurl=http://detodounpoco-tag.blogspot.com/2010/10/manual-sql.html&usg=__sQL2TYHolyOLfvVCA6ShForntPw=&h=472&w=838&sz=34&hl=it&start=183&zoom=1&tbnid=E4W4YOEb-Ray6M:&tbnh=117&tbnw=208&ei=-XNKTam3BImLhQfRgK3xDg&prev=/images%3Fq%3Dsql%26hl%3Dit%26biw%3D1276%26bih%3D789%26gbv%3D2%26tbs%3Disch:1&itbs=1&iact=hc&vpx=934&vpy=255&dur=1281&hovh=168&hovw=299&tx=295&ty=162&oei=2XNKTZHOPI_qOYzVhOoP&esq=9&page=9&ndsp=23&ved=1t:429,r:22,s:183


Examples of batch modernization

How Version 8.6 contributes to the Batch Modernization

Transform: batch applications using

modern languages (ex. COBOL to Java)

Re-use: existing applications with

business oriented Web Services

TWA V8.6 helps supporting transformation and re-using projects

• Invoke scheduling services as Java API• Through zConnector, now running also on z/OS

• Enable wrapping existing scheduling services with web services• Edit and submit jobstreams with variable substitution

• Embrace scheduling of Java and Web Services

Reduce costs

offloading MIPS to zAAP

Enable easy remote access to scheduling

services

Re-use of existing processes running rather than encouraging a re-

write

zConnector:Batch as a service for applications

http://3.bp.blogspot.com/_aaZ1rYGME-U/TSjWNrY-djI/AAAAAAAABCo/FdU8MKZiQT0/s1600/Circular%2BForms%2Bby%2BRobert%2BDelaunay.jpg


Examples of batch modernization

Integrate: legacy applications with new

applications

TWA V8.6 helps supporting integration projects

SAP

Oracle

PeopleSoft

Web Service

File Transfer

Database

Java

J2EEClient Server

Mainframe Batch

• Application plug-ins to extend the automation to potentially any new job types

How Version 8.6 contributes to the Batch Modernization

http://3.bp.blogspot.com/_aaZ1rYGME-U/TSjWNrY-djI/AAAAAAAABCo/FdU8MKZiQT0/s1600/Circular%2BForms%2Bby%2BRobert%2BDelaunay.jpg


Application Plug-ins : details

What we offer to 3° parties (Clients, BP, System Integrators) for new Application Plug-ins implementation

• Tivoli Workload Scheduler Integration Workbench

• Takes you through the creation of your plug-ins

• Two main phases:

• Panels creation (AUIML file)

• Execution method creation (JSDL)

Application Plug-in (jar file)

• After deployment of new Application Plug-in, you will be able to manage the new job type in the same fashion as all other TWA job typesd creation (JSDL)

http://www.suuntomania.info/wp-content/uploads/2009/03/regalo-un-suunto.gif


Application Plug-ins : details


TWS Plug-in support result


Batch Modernization: Job executors

Direct interface with TWS for specific typical and emerging workloads No need to “invent” a JCL to run such workload types Simple interface//JOBRECkeyword(value)keyword(value)//END JOBREC

Examples– SQL executor

//JOBRECJOBTYPE(/database)STATEMENT20(SELECT * FROM SYSTOOLS.POLICY)DBNAME(DBWEB)DBTYPE(DB2)...//END JOBREC

– File Transfer executor//JOBRECJOBTYPE(/file transfer)TRANSFERTYPE(DOWNLOAD)SERVER(server address)LOCALFILE(C:\file1.txt)REMOTEFILE(/file1.txt)...//END JOBREC

32


Smarter Batch, Cloud and usability


Batch Cloud Scenario Example

A very big cross platform batch application needs to run once a year

A huge number of distributed servers is necessary

TWS agents currently installed cannot cover all the demanded resources

0

10

20

30

40

50

60

70

80

Jan Mar May Jul Sept Nov

% CPU% Memory% Storage

Currently installed TWS Agentsservice level capability


Automatic inventory of all elements

Update configuration and service

Create virtual machines across all hypervisors from one console

Manage performance of virtual machines as a group for a business workload

IBM SmartCloud Orchesrtator will help deploying the right software in each virtual image

– What is needed only when it is needed

TWS will manage this on demand batch environment just for that critical day

Hardware Management

Console(HMC)

Unified Resource Manager

Management NetworkData Network

PowerHypervisor

System xHypervisor

WASApacheDB2

System zHypervisor

zManager takes care of cloud hardware resources

IBM S C O

WOW (What Only When)IBM SmartCloud Provisioning realizes the “service on demand” cloud

infrastructure


Cloud and workload automation

Require App service

Tivoli Workload

Automation

CloudRequire Infrastructure

Oth

er re

ques

tsCloud accelerates the need for workload automation

Value proposition

TWS has moved to the center between the request for business services and the demand for Cloud infrastructure and resources: it allows to manage mission-critical, end-to-end workloads through fluid and elastic cloud resources

Capabilities

TWS v8.6 provides IBM SCO integration for Immediate provisioning of workload

automation ready environment, for temporary demand

Elastic provisioning of workload automation resource for intermittent demand

Business Value

Reduce resource, installation and customization costs and increase productivity Adapt quickly in the context of limited resources

36


Batch Cloud: Self-service online catalog (TWS 8.6.1)

TWS provides a self-service front-end for business users to trigger and control ad-hoc tasks

TWS v8.6 + FP1 provides a web-based portal, also available on smart devices:

Menu of pre-defined cataloged business services Easy-to-use self-service interface Control of end-to-end business service lifecycle

Provide agility, speed and efficiency through smart devices support

Value proposition

Capabilities

Business Value

Streamline request of business services through easy-to-use online catalog Submit ad-hoc service from anywhere at anytime


New Output Collector component (std task) automatically retrieves z-centric job outputIt Automate and control the entire job log collection process for the z centric agents.

This is done by:

1 Retrieving the joblog from the agent (or the dynamic domain manager)

2 Building an header containing run time information for every joblog released in the z-centric environment

3 Sending to the JES for output management tool to archive

The output collector (new of TWS 8.6.1)

Highly customizable

A joblog header template sample comes with the installation (EQQOUCH)

You can edit it and copy it selecting the variables considered useful

TWS TWS v8.6+FPv8.6+FP


Writing sysout to JES

When a job completes successfully or in error, its

joblog is automatically collected and written to JES

39


Adding a header

You can define in the TWS for z/OS controller

parameter library a template for the joblog

header.

40


ScenariosCustomers require to rapidly navigate across ISPF TWS Dialogs, to accelerate operations, increase speed-up and more confidence with the product interface.

Usability: new ISPF panels

One scrollable view for all Application Description

object information

Action bars


TWS for z/OS 8.6 new panels implementation very easy

Logon procedure– ISPPLIB

• Include the new panel library SEQQGENU//ISPPLIB DD DISP=SHR,DSN=TWS.V8R6.SEQQPENU// DD DISP=SHR,DSN=TWS.V8R6.SEQQGENU

– EQQTMPL• Include this new ddname in the logon procedure pouinting to

the library SEQQLENU//EQQTMPL DD DISP=SHR,DSN=TWS.V8R6.SEQQLENU

TWS ISPF– From 0.8 set


Usability: Tivoli Dynamic Workload Console

XML support for application plug-ins

Easy to unload definitions (engines, tasks)

Easy to import unloaded information


Usability: Operating On Demand

Controller

Current Plan

TWS

Plan

TDWC

TDWC

http://images.google.it/imgres?imgurl=www.mbs.com.mk/MBSWEB.nsf/ThinkPad.jpg&imgrefurl=http://www.mbs.com.mk/MBSWEB.nsf/1f00cf09a71c0993c12569c400302fd3/070b8a2f1071a6bec1256b8e003d2d66%3FOpenDocument&h=178&w=200&prev=/images%3Fq%3Dthinkpad%2B%252B%2Bjpg%26svnum%3D10%26hl%3Dit%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8

http://images.google.it/imgres?imgurl=www.mbs.com.mk/MBSWEB.nsf/ThinkPad.jpg&imgrefurl=http://www.mbs.com.mk/MBSWEB.nsf/1f00cf09a71c0993c12569c400302fd3/070b8a2f1071a6bec1256b8e003d2d66%3FOpenDocument&h=178&w=200&prev=/images%3Fq%3Dthinkpad%2B%252B%2Bjpg%26svnum%3D10%26hl%3Dit%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8


TWS 8.6 End to End deep technical event available on request

For organizing the event you can contact:

Your local IBM Sales Team

Or

●Domenico Chillemi – [email protected]●Paola Monteferri – [email protected]


TWS zCentric Proof of Technology

Half day/One day going deep on Tivoli Workload Scheduler 8.6

The End to End zCentric features will be tested performing a specific Hands-On session

– zCentric Static jobs (available from TWS 8.5)– zCentric Dynamic jobs (available from TWS 8.6)

Batch Modernization examples will be also tested during the hands on– an application plug-in example (available from TWS 8.6)

Other important recent TWS features will be tested– New TWS for z/OS ISPF Panels(available from TWS 8.6)– Conditional Dependencies (available from TWS 8.5)

Last generation batch management with Cloud– Demo of the latest Tivoli Dynamic Workload Console tasks within TWS 8.6– Self Service Catalog new feature, a strong cloud example in TWS 8.6


tack

kiit

os

tak