domenica 8 aprile 2012

Solution to control and manage Mainframe Applications

Business need

Managing mainframe applications is often a complicated activity. This is due to several reasons. Over the years, most of the companies had to face the ups and downs of their economica and technical life, and this turmoil modifyed companies' structure, increasing the applications layers complexity. One of the possible reasons is the continuous evolution of application environment (introduction of innovative technologies, coexistence of new developments with traditional applications developed many years ago and still fundamental assets of the companiy, etc.). Another reason can depend from external factors (companies consolidations and mergeing..with consolidation of different application environments) or internal ones (loosing personnel with high skill on existing applications due to personnel cuts or retirements, use of vendor applications instead of in-house developments, etc.) Based on these pains, several customers ask us to develop a solution able to control application at runtime level. Such a solution will allow us to control both the existence of an application (physical presence on DASD) and applicaton activity (calls to load modules). This should be possible for batch activities, IMS activities and CICS activities.

Architectural Diagram

Following a summary schema to describe how we implemented the solution. A TADz agent is active on each system and it collects usage data. Data about physical presence of applications load modules is also collected. Collected data is then inserted into the central repository, matching the information about application (application name and related libraries/modules). Product is able to catch and collect application info on batch, IMS, and CICS environments. Its possible to monitor and control USS/Unix environments, too.

Prerequisite Software

IBM Tivoli Asset Discovery for z/OS V7.5 (5698-B39) is the software product required to seup the solution. This product is able to identify all load modules libraries and to intercept all the calls to load modules, and this data is compressed and optimized, so it uses a very small amount of space. Data is collected in a central database on DB2 z/OS, so DB2 for z/OS (V8 or later) is required only for one LPAR where we decided to place the central environment.

Available resources to get more info about the solution

Technical references

Fabio Riva - zClient Architect IBM - Fabio is the IT Architect who partecipate to the development of this solution. In order to get more info, please send an email to:fabio.riva@it.ibm.com

Sales references

Paola Monteferri - European Tivoli for System z Primus - In order to get more info, please send an email to:MONTEFER@it.ibm.com

Customer references

In order to get more info, please send an email to:fabio.riva@it.ibm.com

More detailed info

In order to get more info, please send an email to:fabio.riva@it.ibm.com

Nessun commento:

Posta un commento