E-GEN/iCAN

E-GEN iCAN

Analyze – Document – Navigate in Schedulers and in z/OS Production

© ISC Software 2011 -

Agenda

• About ISC

• E-GEN WorkStation – The multi-platform Roll-out Management Tool

• E-GEN iCAN

• Overview

• Interface & Features

• Collectors

• ROI, Use Cases

• Conclusion

• Appendix: Use Case


About ISC

• European Software Company

• Founded in 1986 in Brussels (HQ)

• Over 100 large customers

• Over 250 product instances

• Leader in Production Repositories

• Technological partnerships with

BMC, CA Tech, HP, IBM

• Consulting partnerships with

Sogeti, Aubay, Prodline…

• IBM “z/OS & LINUX Partners in

Development”


E-GEN/WS is a versatile multi-platform production release and documentation

tool. It centralizes the management and the distribution of all Scripts, JCL,

Scheduler input, documentation… towards any target environment.

Features:

• Homogeneously manage the corporate technical assets in one single place, based on functional

descriptions

• Manage the objects' life cycle – like Endevor, SVN or CVS, but for JCL and Scripts; link to any SCM

• Define rules & standards for each target environment, so as to provide for targeted release

• Generate multiple items for a given object (JCL, Scripts, .bat, Batchloader, Run book, Release doc,

Instructions…) and deploy directly into the target environment: z/OS, Unix, Windows, Test, Production…

• Windows Client and data entry forms with wizards, data validation

• Impact analysis and cross references between objects

• Link with RACF, TSS and LDAP.

• Multi-platform: Z/OS, Unix, Windows, LAMP web sites …

E-GEN WorkStation


E-GEN WS – Overview

AS400

LAMP Sites

…

z/OS

Unix / Linux

Windows

E-GEN WorkStation

Repository

• Process Descriptions

• Environments

• Generators

• Templates

• Standards

• Models

• Norms

• Rules

• …

GENERATE & DISTRIBUTE

• Scheduler Input (Batchloader, etc.)

• Batch: JCL, Script, .bat, .ksh, DDL, Pelican,

XML, XLS, CSV, TXT…

• Release doc, Run Book, Operator Instructions,

any kind of Documentation…

• Update Packages for LAMP web sites


E-GEN iCAN – Introduction

E-GEN iCAN is an active cartography and reverse documentation tool that collects all

production objects, scheduler databases, programs… for all those who need a structured view

of the production: Operators, Ops Engineers, Architects, Developers, Domain Managers…

Product History:

• 1994 – E-GEN MAP

o 1st Generation: A passive cartography tool for corporate technical assets

• 2004 – E-GEN MAP/Inventory

o 2nd Generation: A passive cartography and inventory tool

• 2011 – E-GEN iCAN (intelligent Cartography, Audit, and Navigation)

o 3rd Generation: A greatly enhanced active cartography and inventory tool

o Over two years of development:

- Overhauled interface and features

- Added a powerful, yet easy-to-use search & query engine

- Added the possibility to add "User" objects into the repository ( dynamic extension of data model)

- Added the possibility to generate multiple output formats (Excel (macro), XML, HTML…)


User Interface

Previous / Next / Home

Display Mode Selector

X-Ref: Uses / Used by

Run Book Generation

Object Selector

Graph controls

Export to VISIO

• Intuitive and easy-to-use

• Multiple display modes: graphical, text, 3270…

• Hyperlinks on objects, whichever the display mode

• Cross References

• Export to VISIO


Graphical Interface

Predecessors /

Successors

Object under

analysis

• Each node is a hyperlink, allowing you to navigate


Run Books

• Generate an HTML Run Book with hyperlinks

A click on any job directly

opens its detailed

description.

Every object in the

detailed layout is an

active link.


Export to VISIO

• The same application, exported to VISIO


3270 Interface

• Each item in red is a hyperlink, allowing you to navigate

• Procedures, Includes, SYSIN and SYSTSIN can be unfolded by clicking on '+'

• Any resolvable parms and variables are resolved in the expanded view.


Cross References

• Cross references are available for any repository object, in any display mode

Procedure

IKJEFT01 is

"Used by"

Procedure

IKJEFT01

"Uses"


Structured Text Interface

Predecessors

Each name in red

is a hyperlink,

allowing you to

navigate


Flat Text Interface

• Even in Flat text mode, each element name (Step card, DDname, DSN…) is a hyperlink, allowing you to navigate.

Each object name is a

hyperlink, allowing you to

navigate


Search Engine

Search (example):

• Find all jobs that have a Run Type clause

• Among those, find the ones that are governed by TWS Rules and display the chosen rule


Audit – Define your own criteria

• Define your audit criteria, including non-keywords (free text strings)

• Launch the audit

• Display the results

• Drill down as required Audit criteria:

Analysis of all existing

values for the DISP

parameter

Drill down

from the Audit results to

the very line of a JCL

Result:

All existing values,

with statistics


Collectors

ADABAS / NATURAL CA-IDMS JS3NET

APM / HS5000 CA-JOBTRAC LISTCAT

ASG-CORTEX PDB CA-SCHEDULER MQ SERIES

ASG-ZEKE CA-TNG RSD/EOS

ASSEMBLER CFT SMF

BETA 42 CICS TWS / OPC

BETA 92 COBOL XML

BETA 93 DB2 … BMC / CONTROL-D HDC

BMC / CONTROL-M

BMC / CONTROL-O IAM

BMC / ECS IMS DB/DC (DL1)

CA7 ISMF/VTOC

CA-AUTOSYS JCL

CA-DISPATCH JCL GCOS8

Our R&D dept. can

create any custom

collector, on request


Create your own collector !

• Integrate any type of data into the repository, regardless of their origin, in the shape of flat

files

o ANY FLAT FILE

o CSV

o XML

• Read those flat files, and aggregate them into the iCAN repository

o Collect the data and assign them to new data objects

o Create links between the new objects and previously existing ones

• The queries / procedures used to transform the data are your custom collector, and can be

shared or scheduled for general use, as required.

• The newly aggregated data can be queried, viewed, charted, tweaked and you may run audits

against it, just like for any other data in the repository.

• Generate your customized output files (Flat files, CSV, XML, HTML, Graphs…).


• Server installed on Unix / Linux

• ISC-made repository on the Unix/Linux

server (license-free)

• Collector batch jobs collect local flat files

that have previously been extracted and

transmitted from the Host

• Communication with workstations via

TCP/IP

• Link with LDAP

• Import / export iCAN objects between

servers

z/OS Server

Unix / Linux Server

Windows Server

• Server installed on the Host (STC)

• Repository in a VSAM KSDS

• Collectors run as batch jobs


TCP/IP

• Link with RACF / TSS


servers

• z/OS Server is mandatory for DB2

collection

• Server installed on Windows

• ISC-made repository on the Windows

server (license-free)

• Collector batch jobs collect local flat files

that have previously been extracted and

transmitted from the Host


TCP/IP

• Link with LDAP


servers

Windows Client • Client installed on Windows

workstations (~15 MB)

• iCAN/z administration for all server

types

• Ad-hoc collector batch jobs are

launched from Workstations

• Communication with servers via TCP/IP

• User interface for all users

Client-Server Architecture

TCP/IP


Easy to implement

The entire process takes less than one day:

• Install the iCAN server on

o z/OS or

o Unix or

o Windows

• Install a client on a workstation

• Define one or more collect(s)

• Start the desired collect (Batch process )

• Once the collect has ended iCAN is operational, results are ready for viewing


ROI & Added Value

• The ROI is less than 1 year in any case

o No additional fee depending on CPU power or number of users.

• Examples of indirect savings / added value:

o No upgrades for any reason, except for additional collectors – no hidden clauses nor small print

o Add any type of data to the repository and tweak / audit / search / x-ref / share / schedule it flexibility and time

savings; may eliminate the need for yet another tool

o Simply extract files from z/OS and send them to the iCAN server for collection and analysis MIPS/MSU savings

o Generate Run Books from collected objects and distribute them via Intranet always up-to-date; time savings on

data entry, less errors due to obsolete documentation or data entry errors

o Generate any type of output file save time @ reformatting data output from proprietary formats / reports into

reusable data for corporate reporting

o Audit / Query on any repository object estimated time savings of 5' to 10' per query query without tool (i.e.

using REXX, ISRSUPC…)

o Database doesn't require any specific make full portability

o Customize the GUI and Run Book layout make it YOUR tool


Use Cases…

E-GEN iCAN allows you to verify any kind of element:

o Against any internal or imported reference (list, table, catalogue…)

o Via an ad hoc procedure, which verifies the compliance with an existing norm or rule

Sample verifications :

o JOBNAME Composition: e.g. the 3 first JN characters = App Code

o Intra-Step / Intra-Job / … file naming convention

o Search for unused files (dead ; only created but never reused…)

o Which apps run in class "A" ?

o Report addressees: are they still valid / present in company ?

o FORMS names used in the JCL external correspondence table of usable EOS Forms

o Allowed / forbidden values

o Inventory

o …

See appendix (p.26) for a use case


E-GEN iCAN – The Global solution


Install

Populate

Understand

Manage

Use

Produce an immediate ROI

Benefits

In a single word: iCAN EASILY


Questions?

Contact us !

• www.iscsoftware.com

• [email protected]

• +33 (0) 1 41 19 22 00


Appendix

Quality Assurance with E-GEN iCAN

A QA use case – illustrated via the PDCA matrix

Plan: Define objectives and the

required process, to produce

the results that correspond to

the clients' requirements and to

corporate policy.

Do: Enact the process.

Check: Supervise & measure

the process and its result vs.

policy, objectives and product

requirements, and report

results.

Act: Take any required action,

in order to permanently

enhance the process

performance.


Step 1 – Plan

• Define the scope of action

• In our example, we want to verify the report addressees

• Information source: the NAME parameter in

the OUTPUT cards of the JCL


Step 2 - Do

• Produce an exhaustive list of report addressees, in order to check them and confirm whether they're valid.

• Use iCAN's query engine to produce the list:

Search for a NAME at

JOB level and at

STEP level


Step 3 – Check

Search all JCLs that

have ££MAINT as a

report addressee, at

JOB level and at

STEP level

list of report

addressees

• Check the list of report addressees, and select one addressee; in our example ££MAINT

• Search for all JCLs, in which this addressee appears


Step 3 – Check

• ££MAINT is found in 2 JCLs

• Click on any job in the list to fetch its details


Step 4 – Act

• After finding out where ££MAINT is used, we must find out whether this particular addressee is still valid, or if it needs to be

changed or discarded.

• We can now verify it against an up-to-date addressee list, which can be imported into

the repository (or which may already have been imported in Step 2).

E-GEN/iCAN

Documents

Transcript of E-GEN/iCAN