Michał Weintraub michal_weintraub@bmc.com mwei@gmx.net Co nowego w MainView Nowe BMC Software Michał Weintraub michal_weintraub@bmc.com mwei@gmx.net

Problem: brak integracji User Application I M M V D B C I V T W A L A H O M I Dostęp do aplikacji

Idealne rozwiązanie: integracja Konta M V S I M S D B 2 C I V T A W A N L A N H O S M I N Pożyczki Bankomaty Monitory, które obserwują APLIKACJE, bez względu na to, gdzie pracują ich elementy

Idealne rozwiązanie: integracja NETVIEW Integracja i centralizacja

MainView SPOC Patrol Multi-Platform Mainframes Help Desk Operating Sys Pgm Patrol L a y e r 1 S t g 3 / N M C P I - U 6 . 2 n d u s A B c k p D F H HP OpenView Boole & Babbage also provides solutions for client/server and distributed environments. Today we will be addressing the traditional and parallel sysplex environments. Remedy Tivoli Tangram u.v.A Mainframes Multi-Platform LAN, WAN, PCs 17 20 17 17

Spójna architektura BMC Software: Patrol COMMAND/Post Integration System Spójna architektura BMC Software: Patrol COMMAND/Post Mid Level Managers Patrol/KM, ECS, ESS, HP-OpenView, SAP R/3, MQ, ... Element Management System ASA/390, ASA, JobView, MainView, SpaceView, Best/1 Network Elements NT Tandem,DEC, AS400 Etc. Standard Equipment Non Standard Equipment MainFrame Plex UNIX 20 11

Applications Management & Tuning MainView Desktop/Explorer Parallel Sysplex Seminar MainView dzisiaj Zintegrowana rodzina rozwiązań System Management dla MVS, CICS, IMS, DB2 i MQSeries MainView Applications Management & Tuning Automation Rules & Solutions VistaPoint MainView Desktop/Explorer AutoOPERATOR CPSM MVS CICS IMS MQ DB2 DBCTL Windows, OS/2, NT MainView Technologie Single System Image Single Point-of-Control Wspólny model danych Serwisy bazy Interoperability Wspólny GUI 3270, VTAM, EXCP Page 19

Parallel Sysplex Seminar MainView Od podstaw dla tradycyjnych instalacji i dla Parallel Sysplex Multiple System Support - zawarte Single System Image - zawarte Data Summarization - zawarte WLM Goal Mode Monitoring - zawarte Parallel Sysplex Monitoring - zawarte Page 20

MainView Base Technology Parallel Sysplex Seminar MainView Base Technology Logicznie połączone, ale oddzielne Dimensions End-User Application Data Multiple Systems Support Od początku Single System Image Data Summarization Page 22

Zintegrowana Application Dimension Parallel Sysplex Seminar Zintegrowana Application Dimension MVS Full Parallel Sysplex monitoring CICS Full CICSPlex monitoring IMS Full IMSPlex monitoring DB2 Full DB2Plex monitoring MQSeries Full multi-platform support N-Way Data Sharing monitoring (CF, WLM) Mix und Match Page 29

Zintegrowana Application Dimension Parallel Sysplex Seminar Zintegrowana Application Dimension Page 33

MainView/BBI BBI DATABUS SYSA SYSB The year was 1989 and IBM CICS Hursley laboratory was designing CICS to run on multiple platforms like the parallel processors. They needed something that could literally see and touch hundreds if not thousands of CICS' from one address space. They had nothing that could even come close to doing this. They knew all the leading vendors in performance management and automation were already doing multiple system monitoring so they came to each of us and asked us how we were doing that. FINALLY SOMEONE ASKED HOW WE WERE DOING IT INSTEAD OF WHAT DOES THE SCREEN LOOK LIKE!!!!! Boole & Babbage was the only vendor with a single LU6.2 cross domain link between systems . It did not matter how many users were logged on one system looking at a different system, there was still only one link required. You have to remember, this was 1989, there was no APPC/MVS yet.

MainView PROD SSI BBI BBI SSI DEV AutoOPERATOR AutoOPERATOR CICS IMS DB2 CICS V2 IMS DB2 CICS V3 MV MGR CICS MV MGR IMS MV MGR DB2 MV MGR MVS MV MGR CICS MV MGR IMS MV MGR DB2 MV MGR MVS SSI BBI BBI SSI AutoOPERATOR AutoOPERATOR NETVIEW NETVIEW BATCH BATCH MainView’s architected communications and the AutoOPERATOR Alert Management Facility’s queue structures and graphical interface enable a single person to truly monitor and manage multiple systems and subsystems from a single screen. Point and shoot problem investigation from a central location with online procedural documentation take all the guess work out it. DEV

Window Information line >W1 =APOVER==WKOVER ==(PRODUCTION CICSPROD)=17FEB95=14:30:00=CMF====14 Row Count Context Scope Form Name Date Product Time View Name Window Status

MainView architektura bazy Parallel Sysplex Seminar MainView architektura bazy Page 39

MVALARM Melduje przekroczenia wartości progowych dowolnego elementu na dowolnej VIEW Wszystkie wyjątki na jedny centralnym miejscu Hyperlink(skok) do VIEW, z której generowany jest alarm Jest automatycznie AO EVENT Type Może pisać na konsolę Single System Image If you have multiple products on multiple systems and you are interested in all exception conditions from BBI-3 data elements, you can now monitor a single MVALARM view. When an exception condition arises, you can hyperlink back to the view that produced that condition, even if the exception condition occurred in the past. Alarm messages can optionally be sent to the MVS console. Or, you can trigger an automated alert and/or action with AutoOPERATOR. MVALARM works with all installed MainView products, as long as they are communicated with the CAS to which MVALARM is connected. 3

SETALARM w MVMVS JCPU View Type in SETALARM but do NOT press ENTER yet Place the cursor in the field that you want to monitor (make sure thresholds are set) … and press ENTER Let’s take a look at how this works, using MVMVS’s JCPU view as an example. (click mouse) Type SETALARM, but don’t press ENTER yet. Place the cursor on a field with thresholds set. You can determine which fields have thresholds by looking at the online help. Press ENTER. The vertical position of the cursor indicates where MVALARM will automatically split the screen. 9

Alarm History ALARMH displays the 1000 most recent start and end messages in descending time order. 15

MainView Explorer Autodiscovery Objects/ Views Graphs & Statistics Alerts

Technologia i kierunki rozwoju Integracja I am pleased to tell you that the merger between BMC Software and Boole & Babbage is now complete and as previously committed, I would like to share with you some of our plans for the combined product lines. Obviously many of these plans are exactly that, plans and beyond the short-term deliverables it is difficult for us to commit to dates at this point, but we will happily keep you up to date with our progress as we move forward. Produkty Technologia i kierunki rozwoju Co planujemy kiedy?

Nowa BMC Software Obroty ponad $ 1.1 miliardów 4,400 pracowników 1,800 Field Channel & Services 1,600 R&D 10,000+ customer sites Ponad 18% obrotów inwestowane w R&D Akcje: BMCS So what does the new company look like? Well, we will have revenues in excess of $1 billion, and total employees over 4,000. Both BMC and Boole were very committed to delivery quality products and service to their customers, and invested huge amounts into the field organization and the Research & Development organization. There are now over 1,600 R&D engineers involved in researching and developing products and solutions. BMC now has over 10,000 customers in every major economy around the world.

System Management Space Systems Applications Network LAN/Desktop MVS Servers Middleware RDBMS Packaged In-House User Driven Service Level Management Prediction Performance Availability Recovery Production Management Scheduling Restart Output Tape Backup Administration Security Asset Software Distribution Configuration Change ….. If we look at this slide then we can see on the left hand side various systems management disciplines. These include Service Level Management, Production Management, Administration as an examples but there are others also, such as Help Desk. Along the top of the slide, we have tried to show the systems and applications that customers need to manage. Whether it be a home-grown application on OS/390, an ERP application on NT or the network, customers need to deploy the systems management disciplines across each of these environments. These include both standard based systems and non-standard systems and legacy systems

Niektórzy próbują robić wszystko. 70% tych projektów „tonie“ Systems Applications Network LAN/Desktop MVS Servers Middleware RDBMS Packaged In-House User Driven Service Level Management Prediction Performance Availability Recovery Production Management Scheduling Restart Output Tape Backup Administration Security Asset Software Distribution Configuration Change ….. CA, Tivoli Well, some vendors try to do it all. Their sales pitch is typically based around a framework which is complex to deploy and then tools that supposedly cover all of these environments and all of these disciplines. However, this approach has been tried and failed so many times already and we are now seeing failure occur in this approach once again. IBM have attempted to do this with SystemView, they then reinvented SystemView into SystemView II, then when this failed they acquired Tivoli and have the TME10 framework. CA are offering to “give away” the Unicenter framework. The lengths that some vendors will go to to get customers “locked in” to their technology.

Inni mają produkty na części problemu Systems Applications Network LAN/Desktop Legacy Servers Middleware RDBMS Packaged In-House User Driven Service Level Management Prediction Performance Availability Recovery Production Management Scheduling Restart Output Tape Backup Administration Security Asset Software Distribution Configuration Change ….. Vendor C Vendor C Vendor D Vendor E Vendor F Vendor B Vendor B Network Management Vendors At the other extreme we see a collection of vendors offering point products. These are often just looking at a single discipline on a single platform. Vendor A

BMC Software “classic”: End-To-End Service Level Management Systems Applications Network LAN/Desktop Legacy Servers Middleware RDBMS Packaged In-House User Driven Service Level Management Prediction Performance Availability Recovery Production Management Scheduling Restart Output Tape Backup Administration Security Asset Software Distribution Configuration Change ….. BMC Software At BMC, we believe that we differ from both these approaches because we focus on Service Level Management, but we do it across all platforms and applications and we handle each part of the Service Level Management process. In essence BMC are focused on the end-user and helping our customers increase the availability and performance of their applications to their customers. We have the best of breed tools in these areas, and they are integrated together into a single solution.

Razem: największy dostawca zajmujący się wyłącznie Systems Management Systems Applications Network LAN/Desktop Legacy Servers Middleware RDBMS Packaged In-House User Driven Service Level Management Prediction Performance Availability Recovery Production Management Scheduling Restart Output Tape Backup Administration Security Asset Software Distribution Configuration Change ….. And, also we are expanding into the production management arena, Areas such as job scheduling and output management also have a fundamental effect on end user service levels and availability, which is why BMC recently announced the intended acquisition of the best of breed vendor in this area, New Dimension Software.

Products: Integration and Immediate Value added! So, let’s take a look now at what integration you can expect between the ex-Boole & Babbage products and the BMC products. As you can see from this slide, we think that we have added immediate value to our customers current investments through some of this integration work.

Co dodaje B&B do ASA? Enterprise Console Enhanced Enhanced Enhanced Availability Recovery Performance ERP Apps Enhanced Database Enhanced Enhanced Middleware Let’s take a look at the overall picture. Here you see a representation of the three legs of BMC’s Application Service Assurance strategy, namely Availability, Performance and Recovery. And on the left hand side you will see many of the areas that these products cover, for example ERP applications, databases, System 390 etc. Well, the areas in green is what Boole & Babbage products add to the ASA strategy. They enhance existing solutions in some areas, such as management of SAP R/3 and middleware, and in other areas they are the solution, for instance availability and performance for the OS/390 environment. You’ll also see along the top the Enterprise Console stripe, this is where COMMAND/POST fits and becomes the point of entry and point of integration for all of the BMC product lines. This is something that was missing in the past from ASA but now BMC has the leading Enterprise Console available anywhere. BackOffice Boole Boole Enhanced System/390 Boole Boole Enhanced Storage

COMMAND/POST - PATROL So, let’s take a look in a little more detail at some of the plans for COMMAND/POST and PATROL.

COMMAND/POST i PATROL były silne w różnych segmentach rynku Organization Size The first thing to say is that there is relatively little overlap between these products. COMMAND/POST was positioned as managing legacy systems, home grown applications, OS/390 systems and other non-standard systems. PATROL on the other hand did an excellent job of managing standards based systems, whether they be Distributed Servers, Databases, packaged applications or newer e-business related services. It is also true that COMMAND/POST was typically used by the large enterprises in a centralized management capacity but was starting to scale down to the smaller environments. Whereas PATROL was often deployed at the domain level, or a single application level, although multiple customers had also been using PATROL at the Enterprise level. Note: COMMAND/POST adds legacy management capabilities, network management,OS390 connectivity, ETE business service views, advanced event management, Enterprise level automation in a highly scalable architecture with a focus on the operations management disciplines. PATROL COMMAND/POST Servers, Databases, Packaged Apps OS/390, Network, Non-standard apps IT Environment

Siła kombinacji jest oczywista COMMAND/POST + PATROL Organization Size When these solutions are put together, we see a complete and unique coverage of the Service Level Management market. From the Centralized large Enterprise to the distributed or smaller customer, as well as with both standards-based and non-standards based applications, services and systems. In short, COMMAND/POST and PATROL provide End to End and Top to Bottom management of the Enterprise. Servers, Databases, Packaged Apps Legacy, OS/390, Network, Non-standard apps IT Environment

W najbliższym czasie: Connect PATROL for COMMAND/POST (GA) Connect PATROL for MAX/Enterprise (Beta) Connect BEST/1 for CP (dev) and MAX/E (dev) New Dimension Software pending integration Connect ECS (in design) PATROL KM for Control-M available (Control-M & ECS - multi-platform scheduling) This unique combination is one of the reasons that we wanted to ensure that the products were integrated as fast as possible. And we are pleased to announce the immediate availability of Connect PATROL for COMMAND/POST. We have already been through an extensive beta test with about 12 companies taking part and we are pleased to say that the product is now generally available. We have also developed Connect PATROL for MAX/Enterprise, and this entered beta at the beginning of April. We also have Connect BEST/1 in development, that we expect to be available within 30 days and we are looking at developing Connect ECS, that will allow COMMAND/POST to integrate with the New Dimension multi-platform scheduling products. And, just as an aside, for those customers of the New Dimension products and PATROL, there is a PATROL Knowledge Module already available for Control-M

connect PATROL (dzisiaj) Single Physical Console - NT or UNIX Patrol Console COMMAND/POST Console COMMAND/POST Server connect Patrol So, what is Connect PATROL. Well, here is a graphical interpretation of the product and how it fits into the overall architecture. Essentially, we wanted to be able to quickly and easily get PATROL and COMMAND/POST to integrate from an alert and event management perspective and also to allow our customers to use a single physical console to access both products. Patrol KM Non-Patrol managed elements Patrol KM Patrol KM Patrol KM Patrol KM Patrol KM Patrol KM Patrol KM

connect PATROL Auto-discovery agentów PATROL & KMs z COMMAND/POST Automatyczna komunikacja wydarzeń przez PATROL KMs do COMMAND/POST Automatyczna interpretacja i korelacja wydarzeń (w tym i od PATROL) przez COMMAND/POST Synchronizacja stanów objektów w COMMAND/POST i PATROL Some of the major feature of the product are: Easy to install - installation takes about 2 minutes. Auto-discovery of PATROL agents and KMs by COMMAND/POST. Once discovered, COMMAND/POST will then subscribe to these agents to look for any events or state changes. When is sees a PATROL generated event, COMMAND/POST already knows exactly how to interpret this event and translates it into a common format. And finally, the events are kept synchronized between COMMAND/POST and PATROL so that if an operator was to manually close an event at the COMMAND/POST console, then this automatically be reflected on the PATROL agent or console.

connect PATROL Features (cont.) Context-sensitive launching of PATROL Operator Console from CP Explorer No changes are required to PATROL agents Installed on the COMMAND/POST server Provided to COMMAND/POST customers at no charge So, the product is installed, has automatically discovered the PATROL agents and is interpreting the events and presenting them to the operator - what next? Well, what next is that the operator may need access to the PATROL console from the COMMAND/POST console. Not only have we provided that capability, but we have also provided the ability to launch the PATROL console in context with the event that is being worked upon, that means - if an event from the PATROL KM for ORACLE is being investigated by the operator, then with a single click from COMMAND/POST, the screen representing that ORACLE server within PATROL is launched and available. As an aside, this product requires absolutely NO changes to the PATROL agents, is installed very quickly on to the COMMAND/POST server and believe it or not, is provided free of charge to all COMMAND/POST or MAX/Enterprise customers.

Connect PATROL in Action Here is a quick screen shot from the product showing that from the COMMAND/POST alert display, the operator accesses directly to the correct PATROL screen with a single click.

Other short-term deliverables June 99 - NT user interface for PhonePoint Multi-node support for large Enterprises Light edition for smaller customers Add email support June 99 - TCP/IP OS/390 connectivity Part of command OS/390 - requires AO July 99 - New NT-based rule builder Reduces time to implement Service Management Focus More “legacy” management solutions out of the box So what else are we delivering for COMMAND/POST customers? Well, first of all we will see a whole new version of PhonePoint coming out before the summer - this includes a brand-new graphical user interface based on NT as well as some extended high-end support for our largest customers. We are also looking at making available a “light” edition with less functionality that we may make available to our smaller customers. During the summer this year, we should see a whole new Graphical User Interface for COMMAND/POST, even further reducing the time to implement the system and also providing a focus on delivering Service Level Management quickly and easily. You should also expect us to deliver more “legacy solutions” ready for plug-and-play. And finally for this slide, an increased level of integration between COMMAND/POST and the MainView suite of products. This is effected by the delivery of a TCP/IP based communication directly from AutoOperator to COMMAND/POST.

COMMAND/POST Explorer Sep 99 - Automatically Map your Services Multi-server connectivity Enhanced graphical facilities Advanced selector for easier desktop manipulation Context sensitive application launching PATROL integration as standard! PATROL console & Explorer shipped on same CD, single install In September of this year, you should see us deliver a whole new and major release of Explorer. One of the most compelling features of this release is the ability to automatically map your services and systems and to keep the map up to date automatically as your environment changes. This is based on information that will be in the COMMAND/POST database, but will be the first solution of it’s kind to automatically map business services. There are several other major features in this release, but the PATROL integration will be shipped as standard and customers will now have access to a pre-defined icon to launch PATROL from CP Explorer. We also intend to ship the PATROL console and the COMMAND/POST Explorer console on the same CD so that customers can run a single installation program and install both products. These have been a few highlights of what we’re working on but what about the longer term, what does the future hold?

Medium Term projects E-T-E response time Standard Applications In House developed C/s & legacy Central Repository and Real-Time reporting COMMAND/POST 4.2 Service-focused agents Before I talk about this slide, you should be clear that these are areas that are under research or development, but I am making no commitments as to when these may be available. One of the major areas that we are working on at the moment is the End to End Response Time Management arena. Our research so far has shown there to be a number of smaller players in this arena but we believe that they all have part of the solution and not the whole. Collecting the information needs to be performed in multiple different ways depending on whether we are looking at standard apps, in house c/s apps or legacy apps. BMC is looking at all of these methods and we intend to deliver the first solution that covers all areas and propel us to leadership in the ETE Response Time market. We are also researching a central repository for our Distributed Systems products, this would bring together the information from PATROL, COMMAND/POST, BEST/1 and others and provide a single, very powerful reporting package. COMMAND/POST 4.2 is in design stages, even further increased performance, ease of use and service management features are being looked at And finally, we are looking towards the future with our agent technology and looking to develop a new Service-focused agent. Talking about agent technology, now would be a good time for me to talk about the plan for Boole & Babbage Power Modules customers.

Service Assurance Agents Other Appliances e-business Applications Databases This chart shows a couple of things, on the vertical it shows the type of environments that agents can be used to managed. Whether that be from distributed operating systems, to database, application or even e-business environments, we believe that you have a need to manage these today. For the future, we think that you may be called upon to managed a whole new class of devices, systems such as Web terminals, set-top boxes, hand-held devices or other appliances that will go to make up our world. On the horizontal, we see some of the disciplines that a service focused agent could perform. Whether that be Event Management and Automation, or detailed performance management, predictive capacity planning, root cause analysis or auto-recovery, these are all areas that will be needed in the future. One of the final goals we believe for organizations is to be able to manage their systems and applications against a pre-determined “Desired State”. Distributed O/S Event Automation Performance Management Prediction Root Cause Analysis Auto Recovery Desired State

Where are we today? PATROL BEST/1 “Ensign” Other Appliances e-business Applications BEST/1 Databases So where are we today on this chart? Well, PATROL and Ensign (another name for the Boole & Babbage Power Modules) are focused at delivering event automation and some performance management. PATROL does this across a much broader range of environments than Ensign, taking into account packaged applications and e-business. We also have the BEST/1 technology that extends the performance management capabilities of PATROL and pushes into the predictive technology arena. Again, this is performed for distributed OS, databases and applications. “Ensign” Distributed O/S Event Automation Performance Management Prediction Root Cause Analysis Auto Recovery Desired State

Short-term < 6months PATROL supplemented with BEST/1 collectors Other Appliances e-business PATROL Applications Databases In the next 6 months, you will see PATROL extended to cover the performance management arena in much greater depth and also you will see us extending PATROL into other systems and devices as well as other disciplines. Distributed O/S Event Automation Performance Management Prediction Root Cause Analysis Auto Recovery Desired State

Common Agent Technology Medium-term - Y2000 Common Agent Technology Other Appliances Service Assurance Agent e-business Applications Databases And then in the medium term, BMC will be delivering a new generation of service management agent, that will be covering all the disciplines of Service Management across the current platforms and many newer ones as well. When the new agent is available, and this is not likely to be until mid-2000 at the earliest, then it will set the new standard for the industry. This truly will be a defining moment in service management but for existing PATROL and Power Module customers, they will be well positioned to tale immediate benefits that the new agent provides. And, good news once again, the new service agent will be provided free of charge to customers that are on active maintenance at the time of availability. Distributed O/S Event Automation Performance Management Prediction Root Cause Analysis Auto Recovery Desired State

Choices for PM customers Service Assurance Agent Future So, let me reiterate the choice for Power Module customers. You can stay with the Power Modules and upgrade to the Service Agent when it becomes available in 2000. Or, you may wish to take immediate advantage of some of the benefits of PATROL and then upgrade to the Service Agent in the future also. The choice is yours, but we wish to help you make that choice with some recommendations from us. Power Modules PATROL v3.3 GA April Today

How to make the choice? If Power Modules are not widely deployed and/or you need more applications/database management functionality you would like performance management capability of BEST/1 then Switch to PATROL If you have not widely deployed your current Power Modules, and/or you need more applications or database management solutions and/or you would like to take advantage of the performance management functionality that BEST/1 will be adding to PATROL, then we suggest you switch to PATROL.

How to make the choice? If Power Modules are widely deployed then Stay with Power Modules and move to common agent in the future On the other hand, if your Power Modules are already widely deployed and you are happy with the current functionality, then we suggest that you stay where you are and continue to use and deploy the Power Modules.

How can BMC help? This is a “cost-neutral” transaction equivalent KMs will be provided free of charge maintenance will stay at Power Module prices Our technical staff are ready to help We will provide functional comparisons of the agent technology BMC wants to help you make this choice and also to make this as easy as possible for you. So we have added some sweeteners to this decision. First, we are making your decision a cost-neutral one. This means that if you wish to swap to PATROL, then you will be provided a one to one swap of PATROL KMs for your Power Modules. A UNIX Power Module means a UNIX KM and so on. Also, any Ensign admin consoles, will be swapped free of charge for PATROL developer consoles. And one final part about cost, is that you will continue to pay maintenance as if you were still running the Power Modules. SO, truly for all software licensing and maintenance costs, there will be no difference between running your existing Power Modules or moving to PATROL. So now, cost is not an issues, you can focus on the feature set and functionality. We will be training our technical staff to assist you in the decision and also will be providing direct comparisons between the Power Modules and the Knowledge Modules. We hope that we have made this as easy as possible for you. We have taken a very customer centric view of this situation and hope that you feel so too.

BOTTOM LINE ! Two Companies with a similar Focus Immediate benefit through Product Integration COMMAND/POST is the strategic Enterprise Console Full Engineering, Marketing, Support & Sales employment geared to higher customer satisfaction The Power House in Application Service Management So let me summarize what we have talked about today. First, we showed that both Boole & Babbage and BMC had a very similar focus from a corporate perspective and that both companies are very complimentary to each other. Second, we are immediately delivering product integration and will be continuing to leverage the strengths of our products for the future. COMMAND/POST and many other Boole products help to flesh out the ASA strategy and in fact COMMAND/POST becomes the strategic Enterprise Console for the whole company. BMC is trying to keep all engineering, marketing, support and sales people, showing a true commitment to customer satisfaction and delivering quality throughout the company. And finally, I’m sure you will agree with me that we have just created a new Power House in Application Service Management. BMC is the undisputed leader in this market place and intends to continue to push the boundaries of product development and support to provide you, our customers with unparalleled solutions today and in the future. I hope you have found this presentation useful, and I will be happy to discuss anything in further detail now.

MainView MVS CICS DB2 AutoOperator

MainView dla MVS Nowa nazwa: MainView dla OS/390

Nowy Release Od pierwszego dnia: OS/390 2.7 Fibre Channel support w CPSTAT Nowy EXPORT Command Nowa opcja MVBATCH (API do Data Bus) TIME - nowe opcje Nowe VIEWs dla STEP Workload Manager (WLM) enclave/job VIEWs

Nowy Release Nowe Easy menus Realtime Enqueue views Kto używa jakich zbiorów, kto czeka MVScope widzi również taśmy MVScope device range extensions MVScope BBDTMSDP PARMLIB member

Nowy Release SYSPROG jako started task Nowe i ulepszone serwisy SYSPROG Common Storage Monitor ulepszony

Release Highlights JESTATR view and the BBDTQRJ0 PARMLIB member Improvements in SSI usage through weighted averages Data Collector performance improvements New line commands

Release Details Product Name Changed to MainView for OS/390 Supports OS/390 release 1.2 and up Product code (Service Point Attach Name) remains MVMVS New Initial Menu New Easy Menus and Summarized Views

Release Details Primary focus was to provide EPILOG equivalent functionality Project consisted of Multiple Parts: Job Step Data Collection Batch Report Capability Enhanced Queries with Date and Time aliases and masking Reduction in size of History files

Nowy Initial Menu

‘What’s New’ Online

Nowe Easy Menus EZM390 Easy Menu Initial Screen remains MVMVS EZMJOBS View ma wszystkie VIEWs dla JOBs (Address Spaces) EZMDEVS View ma wszystkie VIEWs dla płyt i taśm

New EZM390 Easy Menu

EZMJOBS Easy menu

EZMDEVS Easy Menu

New Summarized Views Summarized Views added for all Job related views Intelligent Hyperlinks based on number of rows Step Data Column added Consistent with new Job Step Views Start with summary and drill down

Job Step Data Collection

Job Step Views 22 new Job Step Views that start with “JS” Easy Menus hyperlink to Summarized Views

JSOVERZ View The JSOVERZ view is sorted by Total Delay %, descending. It has hyperlinks to most other job step views, filtered on the unique job and step number, but one can also hyperlink on the ‘Stepname’ field to go to the EZMJS menu for a specific jobname and step. Job steps that are currently active at the time of PAS initialization will be given a default step number of ‘1’ to avoid the overhead of swapping address spaces in during initialization. Note that the job step views do not filter out the job steps that are no longer active. This is intentional. The purpose of the views is to report job step activity and delay during the interval, regardless of whether the step is still active. In all job step views, for steps that are currently active the jobname and stepname will be displayed in green. Steps that are ended will be displayed in blue, unless the step abended, in which case it will be displayed in red. This makes it easier to identify active or terminated steps without looking for the ‘step status’ column.

JSOVERZ View (continued) More data can be seen in the JSOVERZ view when paging to the right. Note that the program name is not available for job steps that were currently active when the PAS was initialized. Also, the step start time for steps that are currently active at PAS initialization time all indicate the time that the job step record was created as opposed to the actual step start time because the true purpose of the time values is to indicate the time when we started sampling the job or step. This is consistent with the job start time you’ll see displayed in some job views.

EZMJS Easy menu Select ‘Detail’ option to hyperlink to the JSINFO view for the selected job and step number.

JSINFO View JSINFO view is a detailed view similar to the JINFO view, but the left hand column displays the step number and program name, start and end times and dates, return code and abend code, if applicable. It hyperlinks to most other job step views, consistent with the JINFO view.

JSTERMZ View The JSTERMZ (and JSTERM) views have no address space view equivalent. JSTERMZ is sorted by step number within jobname and filtered to include only those steps which have terminated during the interval. Its purpose is to report the total elapsed step time, step start and end times, completion code and abend code, if applicable, all in a concise view. This example shows the termination data for all job steps that have ended over an eight interval duration. The view can also be used with a jobname parm to see all steps that have ended for a single jobname during the selected duration.

JSABENDZ View

Controlling Job Step Monitoring Why ? Limit amount of data written to history data sets and avoid unnecessary collection of data for jobs that need not be monitored How ? BBDJST00 Parmlib member Where Documented ? MainView for OS/390 Users Guide Unlike Epilog, which is a historical reporting tool that relies on SMF records, Mainview for OS/390 must be able to both display information for the current interval and previous intervals using data that it has collected and stored itself. In the interest of performance and reducing DASD space used, we strive to keep the data that is written to history at a minimum. Most often, customers will be interested in reporting only certain long-running batch jobs at the job step level. At the same time, it’s completely redundant to sample single step jobs at the step level (the values for the job step will be the same as those for the job). The solution? Provide the customers with a way to select which jobs will be monitored at the step level and document its use in the Mainview for OS/390 Users Guide.

Nowy rozkaz EXPORT Requirements Produkty BBI powinny móc drukować i eksportować wyniki Format podobny do formatu na Eksport na PCeta i obróbka w EXCELu

EXPORT Command (cont.) Competition Candle’s EPILOG allows printing of on-line ad hoc queries and historical reports. Candle’s EPILOG also allows batch reports which is not directly addressed by the EXPORT command.

EXPort Command (cont.) Saves View data in a data set or prints to SYSOUT. Saves all rows of a view, and all included columns of a view, not just the screen image. Export primary command is entered on the Information Display screen of the view to print.

EXPORT Command

EXPORT command Dialog LIBRARY (PDS): A cataloged, partitioned data set with a three-level data set name in the format: 'project.group.type'. Also enter the Member name. If the width of the view exceeds the LRECL of the data set, view data is truncated on the right. Other partitioned or sequential data set: Enter any fully qualified data set name by enclosing it in apostrophes. If you omit the apostrophes, your TSO prefix is left-appended to the data set name. If you enter "other" data set name, you can optionally specify a volume serial. The system catalog is not used when volume serial is specified. If specified, this field overrides the LIBRARY field.

EXPort Command Data sets must be pre-allocated Can be any width, will be truncated on the right if not wide enough Comma Separated Values (CSV) format supported for download to spreadsheet program Export Options: Disposition: If a PDS is specified, any existing member is always replaced. If a sequential data set is specified, Append adds the output to the end of the data set; Replace overlays the existing sequential data set. Output format: ASIS formats the report in rows and columns much as they appear on the screen. CSV is a comma separated format for use when downloading the output to a spreadsheet program. Lines/Page: For ASIS output format only. Specify a 1 to 3 digit number indicating how many lines to print on each page. Pages are separated by a report title and page number. Specify a 0 to print a single heading line and all lines on one page. Sysout Class: Prints the output directly to sysout. When specified the sysout class overrides any other data set specifications.

MainView Batch reporting Requirements To be able to submit batch jobs to get historical performance reports

MainView Batch Reporting Competition Some of our users use Candle’s Epilog to obtain batch historical performance reports.

MainView Batch Reporting The Batch reporting feature is an ISPF dialog to generate JCL. It is entered from the new OS/390 Performance and Control Menu (next slide) Batch reporting uses the EXPORT command under the covers - so the same rules as to what can print are observed

New MVBatch Option

Batch Report Dialog The MainView Batch Reports dialog generates and manages JCL for printing the results of queries. Setup: The setup panel records information that is not likely to change. Generate: The generate panel records information specific to each report. JCL generated in this step may be submitted. Edit/Submit: Information about each report is saved in an ISPF table so reports can be resubmitted. Browse: Each JCL member is listed with it's report data set. The report data set can be selected for viewing under browse.

MainView Batch Setup Report headings and other installation settings. If Autocust is performed using the same hilevel, some settings will be filled in. The Setup panel records information that does not change often. Job Statement Information: Enter a job card that conforms to your installation standards. Report Title: Enter a title line to print at the top of reports. MainView Clist Library: Enter the name of the library containing the MainView clist. MainView Clist Name: Enter the name of the MainView Clist. MainView BBLINK Library: Enter the name of the MainView BBLINK library. CAS SSID: Enter the four character CAS Subsystem ID. Library to save JCL: Enter a Library name for saved JCL. Temporary Workfile Unit: Enter a unit name for temporary data sets.

Batch Reports - Option 1 Generate

Generate JCL The Generate MainView Batch Reports JCL panel records information needed for a report. JCL Member name: Enter a name for this JCL. Report Description: Optionally enter a description for this report. Report format: Enter ASIS to print reports that look like the screens. Enter CSV for comma separated fields to download to a spreadsheet program. Output data set: Enter a sequential data set, or partitioned data set member name for report output. Supply volser if data set is not catalogued. Entering a Sysout class overrides the data set specification.

Batch Report Queries Each line must be a complete query and will generate a report. There is room for 16 queries. The extensions to the ‘TIME’ command permit JCL to be independent of when submitted. Diagnostics are not performed when panel is generated-misspellings will result in ‘View Not Found’ report.

Batch Reports - Option 2 Edit/Submit

MainView Batch JCL Member List The Edit/Submit panel displays a table of previously generated report JCL. Line commands are listed at the top of the panel. Directional arrows <<< or >>> above the list indicate that additional information is available. Scroll right or left to display the information. The member names are the JCL member names saved in the JCL dataset specified on the Setup panel.

MainView Batch JCL Member List (Right hand panel) Right hand panel shows the member name of the report JCL and the JCL data set specified on the setup panel

Batch Report Dialog Option 3 Browse Reports

Browse MainView Reports

Batch Output Formats (asis) Training Report CMD> TIME * * 5D;CON ALL;INCLUDE SYSTEM;DEV;WH (DXGSER=BAB*) REPORT PAGE 1 06JAN1999 08:31:02 MainView Batch Report PAGE 1 DEV==============(ALL======*=======)06JAN1999==08:30=1575M=MVMVS======5709 Volser SSI Dev LCU Actv Resp IOSQ CUB DPB DB Pend Disc Conn %Dev %D ------ System Num --- Rate Time Time Dely Dely Dely Time Time Time Util Rv BAB410 CXTSTJ 022A 028 0.0 1.4 0.3 0.1 0.9 0.0 BAB410 CXTSTJ 022A 028 0.0 14.1 3.7 1.9 8.6 0.0 BAB410 CXTSTJ 022A 028 0.0 9.5 1.4 1.7 6.4 0.0 BAB410 CXTSTJ 022A 028 0.0 1.8 0.5 0.1 1.1 0.0 BAB410 CXTSTJ 022A 028 BAB410 CXTSTJ 022A 028 0.0 2.5 0.4 0.1 2.0 0.0 BAB410 CXTSTJ 022A 028 0.0 1.3 0.3 0.1 0.9 0.0 BAB410 CXTSTJ 022A 028 0.0 8.9 0.7 0.1 8.2 0.0

Batch Output Format (CSV) "Training Report ", CMD> TIME * * 5D;CON ALL;INCLUDE SYSTEM;DEV;WH (DXGSER=BAB*) REPORT PAGE 1, 06JAN1999 08:23:06 MainView Batch Report PAGE 1, DEV==============(ALL======*=======)06JAN1999==08:22=1567M=MVMVS======5676, Volser,SSI ,Dev ,LCU,Actv,Resp,IOSQ,CUB ,DPB ,DB ,Pend,Disc,Conn,%Dev,%D ------,System ,Num ,---,Rate,Time,Time,Dely,Dely,Dely,Time,Time,Time,Util,Rv BAB410,CXTSTJ ,022A,028, 0.0, 6.8, , , , , 0.5, 0.0, 6.3, 0.0, BAB410,CXTSTJ ,022A,028, 0.0, 2.0, , , , , 0.9, 0.2, 0.9, 0.0, BAB410,CXTSTJ ,022A,028, 0.0, 1.3, , , , , 0.3, 0.1, 0.9, 0.0, BAB410,CXTSTJ ,022A,028, 0.0, 1.3, , , , , 0.4, 0.1, 0.9, 0.0, BAB410,CXTSTJ ,022A,028, 0.3, 2.4, , 0.0, , 0.5, 0.9, 0.1, 1.4, 0.1, BAB410,CXTSTJ ,022A,028, 0.0, 1.7, , , , , 0.5, 0.2, 1.1, 0.0,

Batch Output Format (CSV imported to EXCEL)

Historical File TIME Command Capabilities Timeframe Masking History Data Set Compression

TIME Command’s New Requirements More like EPILOG Relative symbols for the end date, such as YESTERDAY Better able to handle large timeframes with many intervals Able to mask out unwanted portions of the timeframe, such as weekends and night shifts Performance improvements in historical access have been achieved by reading only the record types necessary to populate the view being shown, thanks to Shameem Usmani. The use of relative symbols for the end date facilitates running MV390 in batch mode so that reports can be generated for “last week” without specifying the end date for each week’s run. Timeframe masking (eliminating unwanted intervals) not only matches a feature available in EPILOG and considered essential by ATT, but also improves response time by not reading in data for unwanted intervals.

Rozkaz TIME rozszerzony TIME date time duration dowmask todmask date: end date of the timeframe time: end time of the timeframe duration: length of the timeframe (into the past) dowmask: day-of-week mask todmask: time-of-day mask New, optional parameters implement the timeframe masking enhancement to MainView historical access. Omitting the day-of-week mask and time-of-day mask results in defaulting to a mask of “24x7”. This is equivalent to the functionality available prior to this enhancement.

New Relative Symbols for End Date "*-nnn" - nnn days prior to today, up to 365 days "TODAY" or "TDAY"- today's date, equivalent to specifying "*" "YESTERDAY" or "YDAY"- yesterday's date "LASTSUNDAY" or "LSUN" - last Sunday's date "LASTMONDAY" or "LMON" - last Monday's date "LASTTUESDAY" or "LTUE" - last Tuesday's date "LASTWEDNESDAY" or "LWED" - last Wednesday's date "LASTTHURSDAY" or "LTHU" - last Thursday's date "LASTFRIDAY" or "LFRI" - last Friday's date "LASTSATURDAY" or "LSAT" - last Saturday's date "ENDOFYEAR" or "EOY" - the last day of the previous year

New Relative Symbols for End Date "ENDOF MONTH" or "EOM" - the last day of the previous month "LASTWEEKDAY" or "LWKD" - the most recent weekday prior to today "LASTWEEKENDDAY" or "LWKED" - the most recent weekend day prior to today "FIRSTOFMONTH" or "FOM" - first day of the current month "FIRSTOFWEEK" or "FOW" - first day of the current week (Monday) "FIRSTOFYEAR" or "FOY" - first day of the current year "FIRSTWEEKDAY" or "FWKD" - first day of the current week, equivalent to "FIRSTOFWEEK" "FIRSTWEEKENDDAY" or "FWKED" - first day of the most recent weekend (Saturday)

New Relative Symbols for Duration "nnnD" - up to 416 days "nnW" - up to 59 weeks "TODAY" or "TDAY" - intervals back to midnight (today's intervals)" "MONTH" - one month back from the end date All are converted to “nnnnH” under the covers Prior to this enhancement, the largest quantum of time permitted to be entered for the timeframe duration was an hour. These new symbols permit larger durations to be entered more conveniently, but leave the current maximum duration, “9999H”.

Example Using Relative Symbols TIME ENDOFMONTH 23:59 MONTH Displays data from all available intervals from last month Note that the interval that ends at 00:00 on the first of the month is not included TIME FIRSTOFMONTH 00:00 MONTH would include the interval that ends at 00:00 on the first of the month.

Timeframe Masking Permits limiting the intervals displayed from the timeframe To only those intervals ending on certain days of the week To only those intervals ending within a certain portion of the day Specification is done via masks Day-of-week mask Time-of-day mask

Day-of-Week Mask Primitive form is a string of seven “Y”/”N” flags with the first flag representing Sunday, the second Monday, etc. “NYNYNYN” specifies a mask of Mondays, Wednesdays, and Fridays “NNYNYNN” specifies a mask of Tuesdays and Thursdays

Day-of-Week Mask Symbols "EVERYDAY" or “EVDAY” - Same as "YYYYYYY" "MONDAYS" or “MONS” - Same as "NYNNNNN" "TUESDAYS" or “TUES”- Same as "NNYNNNN" "WEDNESDAYS" or “WEDS” - Same as "NNNYNNN" "THURSDAYS" or “THUS” - Same as "NNNNYNN" "FRIDAYS" or “FRIS” - Same as "NNNNNYN" "SATURDAYS" or “SATS” - Same as "NNNNNNY" "SUNDAYS" or “SUNS” - Same as "YNNNNNN" "WEEKDAYS" or “WKDAYS” - Same as "NYYYYYN" "WEEKENDS" or “WKENDS” - Same as "YNNNNNY"

Time-of-Day Mask Primitive form is a string of nine characters of the form ss:ss-ee:ee where “ss:ss” and “ee:ee” are the start and end times of the mask in twenty-four hour notation “08:01-12:00” specifies a mask from 8:00 a.m. until noon

Time-of-Day Mask Symbols "ALLDAY" or “AD” - Same as "00:01-00:00" "PRIMESHIFT" or “PS” - Same as "08:01-16:00" "SWINGSHIFT" or “SS” - Same as "16:01-00:00" "GRAVEYARDSHIFT" or “GS” - Same as "00:01-08:00"

TIME Popup

TIME Command for Power Users

Results The above view has a WHERE filter on it of: WHERE ASGNAME==*MASTER*

History Data Set Compression Activated at PAS initialization time in MV390 2.5.0 and CMF 5.3.0 only AutoCust compression step has been removed Beta sites have experienced a 5-6/1 compression ratio Other products like MVMQ use the same compression routine Will probably use PCE compression in future

BMC Integration Plans Short Term Smartbatch Allows Jobs on one image to spawn steps that run as other jobs on other images in parallel Is an IBM product jointly developed with BMC Will use the power of BBI-3 to summarize by Smartbatch token across images API to Smartbatch will be handed over to San Jose R&D in August

BMC Integration Plans Longer Term Possibility of feeding historical performance data to BEST1 Will be using the PCE component to compress the historical files even more

MainView for DB2

DB2 Products MainView (San Jose) MainView for DB2 - performance monitor RxD2/LINK - REXX to DB2 interface RxD2/FlexTools (uses LINK) - Catalog queries / Explain DB2 Performance (Houston) DB2 Activity Monitor - performance monitor APPTUNE - SQL and object analysis by application OPERTUNE - Perform actions DB2 can’t do DB2 Performance / Admin (Austin) Patrol SQL Explorer - Explain product - MVS & C/S DASD MANAGER - space analysis, utility JCL / execution Catalog Manager - RxD2/FT plus much more DB2 Utilities (Austin) Lots of them - REORG PLUS, LOAD, etc. XBM - Extended Buffer Manager

MVDB2 5.1.0 - CICS TS support CICS TS 1.2 CICS/DB2 nowy interface - major impact Support dodany w “kawałkach” po MVDB2 5.1.0 GA Final updates in PUT 9803 - BPD1271 / 1274 Plus one small fix in PUT 9901B - BPD1333 CICS TS 1.3 Nasze testy nie wykazały konieczności poważniejszych zmian

CICSR BOOLE AND BABBAGE---------- CICS DB2 RCT SUMMARY ------------- RX AVAILABLE SERV ==> CICSR INPUT 20:08:23 INTVL=> 5 LOG=> N TGT==> DB2HHH PARM ==> CICS52C1,SORT=RCT ROW 1 OF 22 SCROLL=> CSR EXPAND: USERS, LINESEL(CICSE), CMRTASK DB2CONN Name .......RCTHH Connection Start Time .......28MAY 13.46.51.92 CICS Job Name ...CICS5201 CICS Auth ID ....CICS52C1 DB2 Subsystem ID ..DB2H Create Thread Err ..ABEND Err Dest ..CSMT,****,**** Statistics Dest ...CSSL Connect Error ....SQLCODE Standby Mode ...RECONNECT Non-term Release ....NO Purge Cycle (m,s) ...0,30 No. Plan Entries ......22 No.Tran Entries .....76 Current Tasks ..........4 Max Tasks Used .........4 Max Task Limit .....160 INDOUBT THREADS ........0 -------- THREADS -------- WAITS/ DB2 AUTH THD TXID PLANNAME CURR ACTV PROT MAX TWAIT OVERFLW CALLS COMMITS CHECKS RUSE -------- -------- ---- ---- ---- ---- ----- ------- ------- ------- ------ ---- *COMMAND 0 0 0 1 POOL 0 0 0 0 0 *POOL DSN8CC0 0 0 0 5 YES 0 0 0 0 0 ABCD ABCDXYZZ 0 0 0 1 YES 0 0 0 0 0 A100 TEST 0 0 0 1 POOL 0 0 0 0 0 DBBS DBBSRVR 0 0 0 2 YES 0 0 0 0 0 D8CS DSN8CC0 0 0 0 2 YES 0 0 0 0 0 H000 TSMPL03 2 2 1 25 YES 0 278 278 278 145 TSMA TSMPL10 0 0 0 1 YES 0 0 0 0 0 TSMB TSMPL11 0 0 0 1 NO 0 0 0 0 0 TSMC TSMPL12 0 0 0 1 YES 0 0 0 0 0 TSM2 TSMPL02 0 0 0 1 YES 0 0 0 0 0 TSM4 TSMPL04 0 0 0 1 YES 0 0 0 0 0 TSM5 TSMPL05 0 0 0 1 YES 0 0 0 0 0 TSM6 TSMPL06 0 0 0 1 YES 0 0 0 0 0 TSM7 (DYN) 0 0 0 1 POOL 0 0 0 0 0 TSM9 TSMCOM9 0 0 0 1 YES 0 0 0 0 0

CICSE BOOLE AND BABBAGE---------- CICS DB2 RCT ENTRY ------------- RX AVAILABLE SERV ==> CICSE INPUT 20:08:49 INTVL=> 5 LOG=> N TGT==> DB2HHH PARM ==> CICS52C1,H000 ROW 1 OF 33 SCROLL=> CSR EXPAND: USERS, LINESEL(DUSER), CICST DB2Entry Name ...............H000 DB2CONN Name ...............RCTHH CICS Connect ID .........CICS52C1 CICS Auth ID ............CICS52C1 DB2Entry Install time ...28MAY 13.46.51.20 - - - - THREAD COUNTS - - - - TYPE .......................ENTRY Current Threads ................2 AUTH String ..............ACCTDEP HWM Threads ....................4 PLAN NAME ................TSMPL03 Thread Limit ..................25 PLANExitname ............******** Protected Threads ..............0 TCB PRIority ................HIGH HWM Protected Threads ..........4 DRollback ....................YES Protected Thread Limit .........5 THREADWait ...................YES Thread Reuse Count ...........145 DB2 Accounting Type ..........UOW Thread Terminations ..........134 Number of WAITS ................0 DB2 CALLS ....................278 - - - TASK (TCB) COUNTS - - - COMMITS ........................0 Current Tasks ..................2 READ-ONLY COMMITS ............278 HWM for Tasks ..................4 ROLLBACKS ......................0 Tasks on ReadyQ ................0 AUTHORIZATIONS ...............278 HWM Tasks on ReadyQ ............0 Total Transactions ...........278 TRANIDS................. H000 H001 H002 H003 H004 H005 H006 H007 H008 H009 H010 H011 H012 H013 H014 H015 H016 H017 H018 H019 - - - - - - - - - - - - - - THREAD RESOURCE ANALYSIS - - - - - - - - - - - - - ---SINCE CREATE THREAD--- THD# STATUS TOT CPU #COMMITS #ABORTS ELAPSED TXID PLAN TASK USERID ---- ------- -------- -------- ------- -------- ---- -------- ----- -------- 0 ACTIVE 1,827 us 0 0 48 s TSM3 TSMPL03 837 BOLPJE1 1 ACTIVE 2,014 us 0 0 48 s TSM3 TSMPL03 836 BOLPJE1

DB2 5.1 Issues IBM dodaje dużo nowych funkcji Wbudowuje funkcje z DB2 6.1 w 5.1 ! Web site tracking www.software.ibm.com/data/db2/os390/v5apar.html Niektóre PTFy od nas: Lockout/Thread new DDF Ids - BPD1205/1210 (9802) ZPARM S0C7 - BPD1317 (9901A) Nowe statystyki dynamic cache jeszcze nie Accounting for parallel thread subtasks (rollup) Fixes in progress

MVDB2 5.1 Enhancements Show largest CT/PT in EDMPL,FREE BPD1342 (CAND) Package accounting reports from SMF FILTYP=PAK1ST BPD1349 (9901C) Compress BBI3 history data sets BPD1272 (CAND) Available to test Enabled in MVDB2 6.1 TSUMR - Trace summary by CORRID Good for CICS BPD1273 (9803) MVDB2 / MVCICS trace hyperlinks In progress now - HONESTLY

DB2 6.1 Plany IBM ESP test zaczął się we wrześniu 1998 Idzie powoli (dużo zmian, problemy) GA przewidziane na czerwiec 1999 Czy użytkownicy chcą przed Y2K? Być może “polityczne GA” (Dlaczego tyle retrofit w DB2 5.1?) Nie ma żadnej pojedyńczej “feature”, dla której byłoby warto Pozycjonowanie na przyszłość?

DB2 6.1 Major Features (1) “DB2 Universal Database Server for OS/390” Object-Relational support (tak jak UDB) Large objects: BLOBs, CLOBs, DCLOBs (pictures, fingerprints, books, audio, ....) 2GB column 64GB data set (DFSMS 1.5 Extended Addressability) 16TB table spaces (254 data sets * 64GB) 4000 TB max (254 table spaces * 16TB) Triggers / cascading SQL / UDTs / UDFs Reduce DB2 DBM1 storage constraints Buffer pools i EDM pool mogą być w data spaces New buffer pool sizes - 8K and 16K

DB2 6.1 Major Features (2) Ulepszenia w “distributed” Nowa nazwa: “Network Computing” Ulepszenia w performance i capacity SQLJ (JAVA embedded SQL) Data sharing - GBP duplexing (reliability) Ulepszenia w narzędziach Query prediction / query governor W Goal Mode dane o DB2 --> WLM DB2 Buffer Pool Tool kosztuje

MVDB2 6.1.0 Beta Entry - 8 kwietnia 1998 Aktualnie TYLKO DB2 6.1 sites Support dla DB2 3.1, 4.1, 5.1 and 6.1 (!) DB2 6.1 support Pełna toleracja Dużo wykorzystania gotowe, dużo jeszcze do zrobienia Schedule Controlled Release w czerwcu (dla DB2 6.1 GA) Chyba dłuższy CR (czy będzie dużo migracji na DB2 6.1?) Może użyjemy czasu CR by dodać integrację z BMC

DB2 6.1 Exploitation Już gotowe: Nowe buffer pools Data space usage - EDM, buffer pools Views 4 nowe, 14 ulepszonych - statystyki 2 ulepszone buffer pool views 7 ulepszonych GBP views ZPARM pokazuje większość nowych parametrów DB2 DUSER / STRAC / TSTAT - nowe class 3 waits

DB2 6.1 Exploitation Still to be Done More accounting fields in DUSER / trace / thread views Update detail trace pop-ups Add a few new monitors Update the PR reports RxD2 - support catalog changes? May just stabilize FlexTools since Catalog Manager does more

MVDB2 6.1.0 Current Enhancements BBI3 history compression New statistics views for authorization checks and “routines” PR - DB2 table indexes / reports improved for data sharing PR - combined 4K / 32K buffer statistics into one set of totals Deleted one table DMRSBFFR, added data to DMRSTAT Changed accounting tables Updated our report members in BBPARM Easier for reporting / queries PR - data migration - yes, ALTER - no

MVDB2 Trace Query Plans for MVDB2 5.1.1 rollout cancelled Need to reevaluate and prioritize When DB2 6.1 support further along BMC integration activities prioritized Still a high priority to access trace data from BBI3! Consider expanding functionality MVDB2 application trace DB2 AM accounting files Hyperlinks to IMS and CICS transaction data

BMC Integration Plans MainView survives and grows ! More complementary products to sell with MainView for DB2 Aggressive plans for integration and new DB2 products Many opportunities - plans still incomplete Wait for official announcements Use only to present general direction and excitement DB2 just became much more important Only a small piece of the pie at Boole, a big piece at BMC And DB2 is strategic for IBM in the marketplace

DB2 for OS/390 Number of sites growing 10,000 licenses DB2 objectives “Enterprise server for network computing solutions” Exploit trend toward (re-)centralization Enterprise server Centralized processing of massive amounts of data Exploit parallel technology for capacity and reliability Distributed access: web, open systems Compatibility with other DB2 family members (NT, etc.) Extend SQL: objects, rules Data warehouse support data mining, OLAP, recursive SQL (V7)

Integration Merge DB2 AM with MVDB2 High degree of functional overlap Market - BMC sold to DBAs, Boole sold MainView Maintain and enhance MVDB2 features Ensure data offered by DB2 AM is covered Migrate more BBI2 displays to BBI3 Keep application trace, reporting from DB2 tables Include selective DB2 AM features Accounting and Statistics files For those who want to bypass SMF Batch reporting from these files Evaluate need for individual IFCID tracing Add hyperlinks, especially to APPTUNE Stabilize DB2 AM over time

Integration OPERTUNE z MVDB2 i AAO OPERTUNE wykonuje rzeczy, których rozkazy DB2 nie potrafią Zmienić ZPARMs, wykonać checkpoint, dodać log online, etc. AAO daje dużo więcej KONTROLI 8 gotowych rozwiązań w AAO MVDB2 - wyjątki startują AAO API to OPERTUNE (PTF)

Integration OPERTUNE with MVDB2 Support API to OPERTUNE in MVDB2 Add actions to MVDB2 views Invoke OPERTUNE commands Invoke “Kill thread” when the DB2 command doesn’t do the job ZPARMs are the biggest opportunity Port ZPARM data to BBI3 Add actions to change them During MVDB2 6.1.0 CR?

Integration MVDB2 Invoke SQL Explorer SQL Explorer ma lepszy Explain Tuning recommendations Tekst, który można zrozumieć Informacja z “ukrytych” tabel Prędzej czy później wszystkie nasze produkty będą wołać ten sam API do wspólnego Explain

Integracja APPTUNE w BBI3 APPTUNE “łapie” i zapisuje SQL i dane o objektach, według APLIKACJI i je sumaryzuje Uzupełnia MVDB2 Dane w VIEWs BBI Lepsza integracja z MainView Dostęp przeglądarką (MainView Explorer)

Integration APPTUNE with MVDB2 APPTUNE has getpages per table space! MVDB2 call API to add getpages and hit ratios to our object data Adds BBI3 history perspective for APPTUNE users Addresses competitive issue with Candle Object data for current threads? Add object list quickly (no counts) / Research other Hyperlink to APPTUNE for object / plan history Hyperlink to APPTUNE for SQL statement analysis From current thread / from application trace See what that SQL statement has done historically

Integration DB2 Utilities and RxD2 BMC DB2 utilities will be using RxD2 Front end object selection Optional JCL generation Common customers do it today Interface to integrate with AO Use RxD2 to access DB2 tables in execs RxD2 - part of Enabling Technologies

MainView for CICS

MainView for CICS Version 5.3 and Beyond John Barnard Manager, MainView for CICS April, 1999

MVCICS 5.3 Content MainView Front-End EZMENU Changes CFLOW changes Task Related Views CREVIEW CTS 1.3 Support

MainView Front-end New Front End for CICS What about other fullscreen products? IMS, DB2 How about Window only products? MQSeries, MVALARM The MVCICS Front-end can also be used Not MVMVS

MVCICS Front-End

EZCSSI

EZCTASK - Task Menu

EZCICS

EZCFAST

EZCMTASK

CWOVERD/CWOVERDS Forms

New CORT Suspend Reasons

New CORT Suspend Reasons (cont)

Task Related Views Nowa metodologia zbierania danych: Koncentracja na informacji o CICS Tasks Task Lock Contention File Utilization DSA Utilization Detail Trace data Dużo nowych VIEWs

Task Information Collect meaningful data Make support compatible with CMR full screen (with the expands) Collect at least the same information Provide orderly display of voluminous amounts of data Several detail forms TASKXPN5 (MRO/ISC) not yet handled New Data is not recorded in History

TASK

TaskD Primary Form

TaskD1 Elapsed Time Components

TaskD2 Suspend Time Components

TaskD3 Storage Utilization

TaskD4 Call Statistics

TaskD5 Terminal/Fepi

TaskDA Storage Addresses

TASKLCK - Task Lock Contention Intended to show all Lock Types Today we have one - ENQUEUE We plan to include other locks as we can DB2 for example

TASKFIL - Task File Usage Same Information as CMR History The difference is that it is real time Note, no counts by access request type Read, Write, Browse etc That will come later

TASKDSA - Task DSA Usage Decompose DSA usage by Subpool One record for each Pool for each Task CDSA/ECDSA, UDSA/EUDSA SDSA/ESDSA,RDSA/ERDSA CICS stats aren’t consistent across pools N/A type columns are marked as ‘-’

TASKDSA

Task Trace Information Nothing more than Detail Trace records 8K buffer allocated in CICS if trace is on Trace Selector code copies buffer Buffer can wrap Facility is intended to help resolve program loops Where loop involves CICS calls

TASKTRD

CREVIEW

EZCREV

CREVIEW/EZCREV Replaces the CMR REVIEW screen Contains every SIT Parameter For every supported release Ordered by CICS defined category Multiple categories are grouped onto detail forms Form names: CREVD?? Also includes alphabetical list of Sit Parameter Names Hyperlink to detail form containing the parameter

EZCREV There are no actions for CREVIEW Plan is to provide SET action Any settable value (SPI) New Form(s) to include only settables

EZCREV Hyperlinks

CREVDE - Storage Management

CTS 1.3 Support Mostly toleration Nothing should break TSUT screen denotes long TS Queue Name QUEUE actions won’t work for long names TSQUEUE for long TS names TASKLCK will Show Global ENQUEUES CREVIEW will show CTS1.3 parameters

CTS 1.3 - TSQUEUE TSUT Screen would need ‘fixing’ for 16 byte names General philosophy is NOT to enhance the full screen mode Hence, a TSQUEUE View is needed Tabular and one detail delivered

CTS 1.3 - TSQUEUE

CTS 1.3 - TASKLCK Need indicator to denote Global Enqueue Lock Type field ENQGLBL Full Screen ENQUEUE screen will not denote global Enqueue 06JAN1999 09:36:15 ----------- INFORMATION DISPLAY --------------------------- COMMAND ===> SCROLL ===> CSR CURR WIN ===> 1 ALT WIN ===> >W1 =TASKLCK===========BCVCP53C=*========06JAN1999==09:36:15====MVCICS========3 CMD Task Target Tran S Lock H HoldWait Short Lock Suspend Suspend El --- Id Id T Type W Time Name Type Time T 26 BCVCP53C JNL2 S ENQUEUE H 03:10:31 CMRJRNL EKCWAIT 00:00:03 03 63 BCVCP53C PATQ S ENQGLBL H 02:44:56 TSQTMPNQ EDF 02:41:43 02 22 BCVCP53C CSZI S ENQUEUE H 03:10:37 1892D15C FEPRM 00:36:08 03

CTS 1.3 - CORT and TASK 5.3 Provides full set through CTS1.2 5.3+ will provide more for CTS 1.3 Socket I/O, Web Interface, CTBS, others The basic detail forms are too small CORT will contain some 15 new fields TASK will contain some 70 new fields

CTS 1.3 Exploitation Requirements VSAM RLS Show ENQ Models (RDO) TSQ Models Coupling Facility Data Tables WEB Interface Document Templates and TCP/IP services Internet-inter ORB (IIOP) Display request model data Discard request model action

CTS 1.3 Exploitation Requirements Collect new monitoring statistics CICS Function Code knowledge internal tables (Like trace) Understand source for DPL requests EXCI, CBTS, Net etc CBTS data in views Possibly new views

MVCICS Futures 5.3.1 dot release Followed by a 5.4 release

New Monitors for 5.3+ Added at Customer request Also to round out CMR monitors Delivery promised Beginning with MVCICS 5.3 (after Beta) Through GA Into MVCICS 5.4 Beta, CR and GA

5.3+ Monitor List Some have been completed and are in test Monitor construction is ongoing Some have been completed and are in test Largest Free OSCOR low Largest Free LSQA low CICS time-of-day clock not updated Enqueue conflicts Waiting tasks/enqueue Journal waiting for WTOR DB2% of aborts/tran DB2% of waits/tran DB2 not attached MRO/ISC links % in use Total waits for MRO/ISC VTAM ACB not open Page-in rate

5.3.1 Task Related Views Summary Views For CICSPlex enabling TASKZ TASKLCKZ TASKFILZ TASKDSAZ TSQUEUEZ

5.3.1 Active Files Views Isolate specific File types from TASKFIL Same data as TASKFIL view Organized by File Name, not Task Identifier ACTIVFIL, CICSFIL, DB2FIL, ADBASFIL, DTCOMFIL DBCTLFIL, SAPFIL, SUPRAFIL, IDMSFIL, GENERFIL MQFIL, SYS2KFIL Example Follows

5.3.1 Active Files Views

5.3.1 Migrate Screens CICSPlex Enabled Use power of Single System Image Customization Add value to data Up Through CTS 1.3

5.3.1 Migrate Screens Most Useful Views first CPROG, CTRAN, CFILE, CONNECT CSESS, CTERM, TCLASS Each View Set will include: Actions One or more detail forms A summary form

CPROG

CPROGD Detail

CPROGZ (Summary) Summary action against all instances

CPROGZ (Summary) Now Expand Instances Hyperlink on the Count Field

CPROGZ (Expand)

CTRAN

CTRAND Detail

CTRANZ (Summary)

CONNECTD Detail

BMC Integration Short Term To be delivered with 5.3.1 Replace TMON with CMRDETL as primary CICS input to modeling Need to ensure that all relevant TMON fields are in the 6E record We have most of them Add value if we can

BMC Integration Longer Term Extremely tentative Provide DBCTL data for CICS transactions Provide Coupling Facility data For CICS direct Logger Shared TS VSAM RLS Global Enqueue Coupling Facility Data Tables To other subsystems from CICS transactions DB2 IMS MQS

Integracja z BMC Extremely Tentative Work Flow Analysis Follow UOW through CICS CICS to CICS TOR-AOR DPL CICS-FOR External to CICS Web-CICS EXCI Into DB2, DBCTL, MQS Celem jest pełny Application Monitoring Realtime i historia

BMC Integration EASE Again, Extremely Tentative Enterprise Application Suites Explorer Provides Visualization of applications NT GUI platform

MainView SPOC Patrol Multi-Platform Mainframes Help Desk Operating Sys Pgm Patrol L a y e r 1 S t g 3 / N M C P I - U 6 . 2 n d u s A B c k p D F H HP OpenView Boole & Babbage also provides solutions for client/server and distributed environments. Today we will be addressing the traditional and parallel sysplex environments. Remedy Tivoli Tangram u.v.A Mainframes Multi-Platform LAN, WAN, PCs 17 20 17 17

Spójna architektura BMC Software: Patrol COMMAND/Post Integration System Spójna architektura BMC Software: Patrol COMMAND/Post Mid Level Managers Patrol/KM, ECS, ESS, HP-OpenView, SAP R/3, MQ, ... Element Management System ASA/390, ASA, JobView, MainView, SpaceView, Best/1 Network Elements NT Tandem,DEC, AS400 Etc. Standard Equipment Non Standard Equipment MainFrame Plex UNIX 20 11

Applications Management & Tuning MainView Desktop/Explorer Parallel Sysplex Seminar MainView dzisiaj Zintegrowana rodzina rozwiązań System Management dla MVS, CICS, IMS, DB2 i MQSeries MainView Applications Management & Tuning Automation Rules & Solutions VistaPoint MainView Desktop/Explorer AutoOPERATOR CPSM MVS CICS IMS MQ DB2 DBCTL Windows, OS/2, NT MainView Technologie Single System Image Single Point-of-Control Wspólny model danych Serwisy bazy Interoperability Wspólny GUI 3270, VTAM, EXCP Page 19

Co dodaje B&B do ASA? Enterprise Console Enhanced Enhanced Enhanced Availability Recovery Performance ERP Apps Enhanced Database Enhanced Enhanced Middleware Let’s take a look at the overall picture. Here you see a representation of the three legs of BMC’s Application Service Assurance strategy, namely Availability, Performance and Recovery. And on the left hand side you will see many of the areas that these products cover, for example ERP applications, databases, System 390 etc. Well, the areas in green is what Boole & Babbage products add to the ASA strategy. They enhance existing solutions in some areas, such as management of SAP R/3 and middleware, and in other areas they are the solution, for instance availability and performance for the OS/390 environment. You’ll also see along the top the Enterprise Console stripe, this is where COMMAND/POST fits and becomes the point of entry and point of integration for all of the BMC product lines. This is something that was missing in the past from ASA but now BMC has the leading Enterprise Console available anywhere. BackOffice Boole Boole Enhanced System/390 Boole Boole Enhanced Storage

Nowa BMC Software Obroty ponad $ 1.1 miliardów 4,400 pracowników 1,800 Field Channel & Services 1,600 R&D 10,000+ customer sites Ponad 18% obrotów inwestowane w R&D Akcje: BMCS So what does the new company look like? Well, we will have revenues in excess of $1 billion, and total employees over 4,000. Both BMC and Boole were very committed to delivery quality products and service to their customers, and invested huge amounts into the field organization and the Research & Development organization. There are now over 1,600 R&D engineers involved in researching and developing products and solutions. BMC now has over 10,000 customers in every major economy around the world.

Razem: największy dostawca zajmujący się wyłącznie Systems Management Systems Applications Network LAN/Desktop Legacy Servers Middleware RDBMS Packaged In-House User Driven Service Level Management Prediction Performance Availability Recovery Production Management Scheduling Restart Output Tape Backup Administration Security Asset Software Distribution Configuration Change ….. And, also we are expanding into the production management arena, Areas such as job scheduling and output management also have a fundamental effect on end user service levels and availability, which is why BMC recently announced the intended acquisition of the best of breed vendor in this area, New Dimension Software.

(na które znam odpowiedź) Uff! To było dużo! Pytania? (na które znam odpowiedź)

PowerPoint Logo Clip Art Logo for PowerPoint Presentation Use Only Hold the shift key down while resizing to insure accuracy. Logo With Tagline for PowerPoint Presentation Use Only Hold the shift key down while resizing to insure accuracy.