IDUG NA 2008 Nick Griffin: Managing IMS in a New World

1

May 20, 2008 • 09:15 a.m. – 10:15 a.m.Platform: IMS

Nick R GriffinBMC Software

Session: K05

Managing IMS in a New World

2

2

Agenda• Review IMS - old world changes - new world changes• Changes in IMS Performance - old world vs. new world

changes• Changes in IMS Administration - old world vs. new world

changes• Changes in IMS Recovery - old world vs. new world

changes

3

3

IMS had a Simple beginning…

IMS played a big part in the first steps on the moon, as it has for the beginning of online business in the 70’s.

I was in this meeting the other day where the lecturer said “can anyone tell me what major event happened July 1969”? I raised my hand and said “IMS help take Apollo to the Moon”. Sadly no one else got it, but that’s the life of IMS. It’s behind the scenes in so many things that people are just not aware of.

Thus the saying -Do you bank? Do you use ATMs? Then you've used IMS. Nothing has ever compared to the reliability and speed of IMS.

4

4

Remember …statically defined terminals…

IMS TM

IMS DB

Mainframe

Up through the mid 90’s most IMS transactions were statically defined for specific terminals. Managing IMS was static and simple to comprehended. A terminal displayed a preset screen. The customer input data and pressed enter for a response. IMS received the 3270 data stream from VTAM, placed it into a queue and allowed a program to stripped the data, then retrieve or update a database. This was then sent back to the customers terminal basically the same way it arrived. This process occurred for all applications.

5

5

Verse the new worlds complexity…

Firewall

Apache

IIS

IIS

WebSphere

WebLogic

IMS TM

IMS DB

Mainframe

IMS Connect

Apache

WEB

WEB

WEB

WEB

With the introduction of the web IMS transactions became much more complex. Even though the internal IMS process stayed basically the same. Who and where the transaction came from became a difficult process to follow. Plus now there are applications running on the user side that alter data prior to IMS handling it. With all this complexity more time is needed outside of IMS while inside there are less resources available to manage it.

6

6

What is the new World?

XMLXML

ProgrammabilityProgrammabilityConnectivityConnectivity

HTMLHTML

PresentationPresentationTCP/IPTCP/IP

Technology

Technology

InnovationInnovation

FTP,FTP, EE--mail, Gophermail, Gopher

Web PagesWeb Pages

Browse Browse the Webthe Web

Program Program the Webthe Web

Web ServicesWeb ServicesIMS….

On Demand Business via Web

AccessView

Control

Key Message: IMS is continuing to address the latest technology as it evolves to address on demand business needs.As technology has evolved over the years, companies demand more and more from their business applications and information infrastructure. Internet technology provides more flexibility to view that information. XML usage is growing exponentially in transactions, purchase orders, invoices, and other forms. IMS XML DB allows the storage and retrieval of XML documents from existing or new IMS databases, while maintaining the security, stability and performance that only IMS and the IBM Mainframe can provide.

An Arcati study shows that 80% of all data resides on the mainframe. Utilizing this technology will allow the world to get to that data.

7

7

What are your GOALS?

• Drive greater business value through better management of technology and IT processes

• Proactively address business requirements• Reduce cost• Lower risk of

business disruption• Support business

growth and flexibility

Every day, in every industry around the world, software solutions enable IT to manage the complexity of diverse business services and processes in a way that provides a meaningful alignment of IT to a company’s operations—ultimately helping to lower costs, drive revenue and mitigate risk.

8

8

Integrated BMC IMS Solutions

Provide a complete comprehensive set of IMS solutions required to monitor, manage, and recover your critical IMS systems and databases.

System Administration for IMS

Database Performance for IMS

SYSTEM

IMSIMS

DATABASE

Backup and Recovery for IMS

DataManagement

Console

RECOVERY

System Performance for IMS

MAINVIEW for IMS

9

At one time IMS transaction simply retrieved data, manipulated it and updated the database within IMS. Now applications are much more complicated using Websphere, CICS, DB2 and MQ. With transactions coming from 3270, batch or the web.

10

Let’s walk-through a somewhat typical transaction flow in zOS…

A customer enters a request through a Websphere portal seeking information regarding his account – perhaps an account balance. This web-based query generates a request to WebSphere Application Server which issues a JAVA database call to DB2. A subsequent DB2 stored procedure calls a CICS transaction and then the CICS transaction requests data from IMS. Within IMS, the transaction retrieves the data and formats the information and places it on a WMQ queue which is then returned to the web-based interface.

So when the user experiences a performance problem, they will likely identify what is being done with the Websphere portal, but it is unlikely they will provide any technical information regarding subsequent transactions within zOS. This is the challenge we confront today: How to we quickly isolate WHERE in the business transaction the performance problem is occurring? How do we quickly relate component transactions to understand the flow of the process executed by the user?

11

11

MAINVIEW Transaction Analyzer The Mainframe Component› Part of the MAINVIEW family

– Benefits from common infrastructure and communication– Integrates well with existing BMC monitoring solutions– Leverage your existing investment

› Near real-time analysis– Analyzes business transactions that have recently ended (within

sub-seconds)

› Goal is pervasiveness across all z/OS systems– Currently supports DB2, CICS, IMS & Websphere MQ

MAINVIEW Transaction Analyzer is a new, integrated solution within the MAINVIEW family of products and provides out-of-the-box analysis of complex transactions throughout the zOS enterprise.

MAINVIEW Transaction Analyzer is designed to provide pervasive management of transaction workloads throughout zOS, crossing subsystem types, such as CICS, DB2, IMS, WAS and MQ, as well as system and subsystem boundaries to provide a comprehensive picture of what is occurring within the user transactions from end to end.

BMC Software has also initiated a similar project for the distributed systems environment with the intent to deliver true end-to-end transaction management for the enterprise.

12

12

MAINVIEW Transaction Analyzer - Benefits

MVTA provides:• Problem analysis and diagnosis of the mainframe components

of business transaction problems• Analysis and correlation of transaction performance data

across the mainframe subsystems• Analysis and correlated transaction performance data• The components of transaction performance by subsystem –

Transaction flow and contextMVTA Delivers:• Rapid problem determination – reduce search and analysis

time • Rapid problem isolation - understand impact and scope• Rapid problem resolution - reducing outage time

As you know, MV Transaction Analyzer (MVTA) is a relatively new addition to our MV family of products; it GA’d last December. Basically, MVTA is an analytic and diagnostic tool. You would use it to identify the root cause of transaction performance problems. It isn’t a MV console or a MV monitor; it provides our customers with the ability to display a consolidated and logical view of transaction activity on their mainframes.

MVTA’s primary strength is its ability to correlate transaction data supplied by the underlying MV monitors to show a complete transaction path no matter how many subsystems have been touched or how many sync points have been taken. Correlation is done on demand, in near real time, to minimize the system overhead incurred on the system. In other words, MVTA is not constantly correlating transaction data.

MVTA will correlate and consolidate the components of a transaction as it flows through CICS, DB2, IMS and/or MQ as well as across multiple LPARS or z/OS systems. As soon as each component or UOW of a transaction is completed and is captured by a MV monitor its accounting record is sent to MVTA where it’s kept in a Data Store. A search or correlation request will retrieve the relevant information from the Data Store and display it in an easy to read format.

Finally, since the data that MVTA displays originated from the underlying MV monitors we can hyperlink, with context, from MVTA to a MV monitor anywhere in the sysplex to display detailed subsystem information to help determine the root cause of a problem. Hyperlinking across the sysplex is possible due to the architecture of the MV Infrastructure and the Communication Address Spaces (CAS).

Analysis and correlated transaction performance data - leveraging data from the underlying MAINVIEW monitors (CICS, DB2, IMS and/or DBCTL).

The components of transaction performance by subsystem - enabling rapid identification of the subsystem responsible for delaysHyperlinks into MAINVIEW - for detailed diagnosis and problem resolution Rapid problem determination - reducing the time technicians spend finding and analyzing problemsRapid problem isolation - enhancing the technicians ability to understand the impact and scope of problemsRapid problem resolution - reducing outage time for critical business applications

13

13

CICS Summary

This is a summary of CICS components resulting from search request. We’re going to look at the group including transaction MCB1 running in region MTACE22D.

The maximum elapsed time for this group is over 18 minutes. Click on the Count column to see all 12 components. MV thresholds are being used

14

14

MCB1 – Correlated View

Now let’s identify all related components. This process is called correlation.

We can see that MCB1 invoked WebSphere MQ and IMS, but did not involve DB2. We can get more information on any of these components, transferring directly into MAINVIEW for WebSphere for the messages or MAINVIEW for IMS for the IMS component. If there had been a SQL call to DB2, we could have transferred directly to MAINVIEW for DB2.

This is the result of correlating CICS transaction MCB1. The complete explanation (from the MVTA Sharepoint site) is:

These modules are CICS/IMS/MQ related modules.Transaction MCB1 places a Message on a MQ Inquiry Queue which then triggers transaction MCB2.Transaction MCB2 then places Messages on 2 MQ Message Queues, which triggers transactions (MCB3 & MCB4), and places 1

Message on a MQ Waiting QueueTransaction MCB3 begins execution and upon completion of execution a Message is then placed on a MQ Reply Queue, which

will eventually trigger transaction MCB2.Transaction MCB4 then places 4 Messages on 4 MQ Message Queues, which then triggers transaction MCB5 and IMS PSB

CSQ4ICB3. Upon completion of execution a Message is then placed on a MQ Reply Queue, which will eventually trigger transaction MCB2.

Transaction MCB5 begins execution and since there are 3 MQ Message Queues to execute upon, transaction MCB5 is called for each Message placed on its MQ Trigger Queues. Upon completion transaction MCB5 places a Message on a MQ Reply Queue which will eventually trigger transaction MCB2.

IMS PSB CSQ4ICB3 begins execution and reads an IMS Database to provide Credit Account Information for the Customer Credit Check. The information from the IMS Database in placed on a MQ Reply Queue, which will eventually trigger transaction MCB2, the IMS PSB CSQ4ICB3 awaits additional Messages placed on its MQ Message Queue.

After transaction MCB2 MQ Waiting Queue has been triggered, MCB2 then places a Message on the MQ Reply Queue, a MQ Response and a MQ Dynamic Queue, which then triggers transaction MCB1.

Transaction MCB1 then formats all of the information from the MQ Reply, Response and Dynamic Queues, and then displays that information as Credit Check Analysis Information to the End User viewing the CICS?MQ User Interface Panel.

Transaction MCB1 then awaits a keyboard response of PF5 to invoke another Credit Check Inquiry, thereby Steps 1 – 8 are repeated, and if a response of PF3 is received transaction MCB1 terminates.

Notes: The IMS PSB CSQ4ICB3 is triggered by the IMS/MQ Bridge PSB CSQTRMMN. Transaction MCB1 can be invoked to perform Steps 1- 8 through an MQ Batch Interface as well.All of the triggering performed in Steps 1 – 8 are performed through MQ Process Definitions, that is, each Message Queue has a

MQ Process defined, and when a Message is received on the MQ Message Queue, the MQ Process is invoked, which has a Named Transaction to execute, so that is how each transaction is invoked.

Functionality Note: The MQ Counts/MQ Seconds displayed under MVTA is only provided through MVCICS, since the MQ information is provided to MVCICS through the CICS/MQ Interface. The IMS/MQ Interface does not report any MQ Count/MQ Seconds activity to MVTA. This lack of support for the IMS/MQ interface should be resolved in MVTA V2.1.00 MQ Support.

15

15

MCB1 – Topology Map (v2.2)

*** This is v2.2 only.

If we select “Build annotated topology map” from the list of actions we saw earlier, MAINVIEW Transaction Analyzer maps the components of this very complex transaction graphically.

16

16



SYSTEM

DATABASE

Backup and Recovery for IMSRECOVERY


DataManagement

Console

Integrated IMS Solutions


IMSIMS

17

17

Component Architecture

Multiple products/solutions run in the same console

With the complexity of IMS applications and products to manage them we introduced a console manager that will control all products under one umbrella.

18

18

One Place To LOGON To Manage The Enterprise

• Sign on once and use • Manage credentials for all connections

• Users create connection from either a shared list of connection definitions or a private definition

The console manager allows for one signon to all products with complete security to allow only the right people to get in.

19

19

One Place For Workflows• Automating complex repetitive tasks• Advice on tool selection• Consistency in tool usage• Optimal parameters are calculated

Workflows walk users through the complex decisions of how to resolve a problem.

20

20

One Place For All z/OS Datasets

When working within the Console Manager there is no need to jump from window to window for creating/editing JCL.

21

21

One Place To Browse All the JES Queues

• Provides JES Queue browsing services to the console user• Users can view jobs on all the connected hosts from a

single view• The default view shows all jobs belonging to the user• The user can supply different job name filtering criteria

• Not a replacement for SDSF

All JCL execution processes and output can be monitored directly from the JESLOG.

22

22

Cross Interface Linking –Mainview Explorer• Mainview Explorer Launch in context

• Select from appropriate views for the current object

If a resolution requires MAINVIEW data to assist in problem determination a user can easily launch a MAINVIEW Explorer window to continue working with in the required MAINVIEW product.

23

23

Installation and Auto-Discovery

• Data Management Console automatically discovers each IMS and the corresponding components

• Simplifies the install process

• The Console can be up and running quickly

• Easy to add new IMS systems

To help simplify the install process the Console Manager finds all IMS subsystems within a SYSPLEX and created the object information the user needs without any data entry. Objects would include transaction, database, etc… Plus the Console manager applies the most efficient out-of-the-box thresholds for all objects. So when the install is complete the user is ready to start utilizing the product.

24

24



SYSTEM

DATABASE


DataManagement

Console

RECOVERYSystem Administration for IMS



IMSIMS

25

25

Remember when …. Application changeAdding, changing, and deleting databases online without stopping IMS can be done using the online change function. To use online change, you must do the following:

1. Allocate the required new data sets.2. Run a MODBLKS system definition if additions, changes, or deletions to the system definition DATABASE statements need to be made.3. Run the necessary DBDGEN, PSBGEN, and ACBGEN.Note: All changes to ACBLIB members resulting from the ACBGEN execution are available to the online system after the online change.4. Run the Security Maintenance utility if IMS security must be defined for new databases.5. Allocate the database data sets for databases to be added.6. Load your database.7. If dynamic allocation is used in an MVS environment, run the dynamic allocation utility.8. Use the Online Change utility to copy your updated staging libraries to the inactive libraries.9. Issue the operator commands to cause your inactive libraries to become your active libraries.

If a database in an MVS environment needs to be reorganized because of changes to the active ACBLIB data set, /DBR must be issued to deallocate the database prior to the /MODIFY COMMIT command that introduces the ACBGEN changes. The commands /DBR, /DBD, or /STA DATABASE must be completed for any databases to be changed or deleted prior to issuing the /MODIFY COMMIT command.

In the old days making an application change in IMS was not a simple task. In some cases it required a complete IMS SYSGEN which not only took several hours to setup, but required an outage to use.

26

26

True Dynamic Resources DELTA PLUS

The DELTA IMS products were introduced in 1983 and allow and IMS to be completely GEN free for objects like transactions, databases, logical terminals, applications and route codes. These are truly dynamic resources that can be changed immediately without and IMS outage or multiple steps.

27

27

What is DELTA PLUS?

• SYSPLEX exploitation• Synchronized change across

IMSPLEX• Global IMS commands

• Resource management• XREF feature• Utilities

• Change management• History File• Enhanced Editor• Grouping of changes

They can also be batched for implementation at one time. This product can implement change management with scheduled updates. The biggest benefit is being able to coordinate changes across IMS subsystems so applications can be synchronized. This would eliminate possible U3033 abends.

28

28

IMS Subsystem3270 Terminal

Communications Controller

Web Browser

z/OS

IMS Transaction

Manager

IMS Message Queues

IMS Database Manager

z/OS CommunicationsServer / VTAM

Websphere ApplicationsServer for z/OS

EnterpriseJavaBeans

IMS ResourceAdapter

Open Transaction Manager

Access (OTMA)

MessageFormatService (MFS)

DL/I

Application

TCP/IP

TCP/IP

Database Definitions

Application Definitions

Terminal Definitions

IMS Connect

Long Short

IMS DBIMS DB

We have talked about the complexity of transactions coming in from outside of IMS, but no matter where they come from they end up in one bottleneck. That bottleneck is the IMS Message Queue. If you have overflows or runaway transaction and fill any of these queues IMS abends. The most IMS will give you is a percent of full message which maybe to late.

29

29

Message Management Message Advisor

Message Advisor automatically manages the IMS message queues. No longer will there be any chance of an IMS abend due to queues filling up. Destination can be monitored to see who the highest users are, so you can insure applications are running and being used correctly.

30

30

Message Advisor Features

• Queue Protection Facility• Message overflow protection• Invalid message protection• HIPERASSIST feature

• Message Management Utilities• DISPLAY• UNLOAD• DEQUEUE• REQUEUE

Message management has 4 main commands, DISPLAY, REQUEUE, DEQUEUE and UNLOAD. Each of the commands will be discussed. QPF is the code used to protect the message queues from overflow situations and thus prevent outages of IMS. Message Advisor manages the checkpoints so that a user can easily determine which one to use during a REQUEUE command. The IMS command interface is available for use while in the ISPF area of the product. Shared Queues is fully supported by Message Advisor.

31

31

IMS Connect Management Energizer for IMS Connect

IMS Connect is a BLACK BOX that has only minimal information about it’s status. Yet it is becoming essential to eBusiness. This chart is an example of the Exit Detail statistical information using a horizontal bar chart. The statistic is the Current Message Rate in transactions per second flowing through each exit.

32

32

Energizer for IMS Connect

• Intelligent management of IMS Web Transactions• DataStore Router• Workload Governor• Exit Services• Security Services • Statistics & Diagnostics

User controlled distribution of web workloadDynamic workload balancing

WLM SYSPLEX Routing ServicesStatistical model

Directed transaction routingAffinities

Transaction codeClient id (TMEMBER or TPIPE)

Resource AvailabilityDatastore status

Options can be changed dynamicallyWorkload GovernorProtects against overload of IMS System

Runaway applications Unexpected volumeClient code receives status codeUser specified acceptable transaction rates

Warning levelRejection level

33

33




SYSTEM

DATABASE

DataManagement

Console

RECOVERYBackup and Recovery for IMS



IMSIMS

34

34

When Availability is Critical, Recovery is Crucial!

Unplanned downtime is an unfortunate fact of life...Up to 80% of all unplanned downtime is caused by software or humUp to 80% of all unplanned downtime is caused by software or human an error*error*Up to 70% of recovery is Up to 70% of recovery is ““think timethink time””!!

*Source: Gartner, “Aftermath: Disaster Recovery”, Vic Wheatman, September 21, 2001*Source: Gartner, “Aftermath: Disaster Recovery”, Vic Wheatman, September 21, 2001Recover

30%

Analyze30%

Investigate20%

Diagnose20%

How many of you have mission-critical systems? How many of you have e-business applications? Did you know that industry analysts estimate that each minute of database downtime could cost your business up to $96K? That’s $6M/hour.

Unfortunately, unplanned database downtime is a fact of life. And 80% of unplanned downtime is caused by software or human error. McGladrey and Pullen estimates that 50% of all businesses who experience a critical system outage of 10 days or more will NEVER recover. In those 10 days, the average business loses 2 - 3% of its annual revenue. For every 8 hours of outage, the average business loses 1/2 point of market share, which will take a full 3 years to recover. Database downtime can also result in lost customers. If you lose a customer, it costs 14 times your initial investment to get them back. If you CAN get them back.

And industry research shows that the average DBA has less than a year of experience.

So Are you ready to recover from unplanned downtime? Are you confident you can recover from any type of outage? Do you know how to minimize your time to recovery?

35

35

Recovery Advisor Exceptions

Solutions

DBRC

• No IC in nn days• IC/Backout/Recovery Needed • PRILOG not catalogued• No SECLOG• Change Accum not available• DB not in CAGRP• HALDB Not Initialized• No ADS defined/available

… and many more

• Image Copy• Change Accum• Recover• CHANGE.CAGRP ADD

… and many more

Check for:• Backout needed• Image Copy needed• Recovery needed• No valid IC within nn days• Assets not catalogued• No SECLOG entry• No CA run exists• DB is not in any CAGRP

… and many more

Thresholds

EMAIL

Recovery Advisor allows you to monitor the crucial recovery data stored within the IMS RECON datasets to ensure that your recovery SLAs can be met. Recovery Advisor is a scheduled task that processes against the RECON according to established thresholds and reports any exceptions found. The exception information can be received by email and WTO. Solutions will be recommended for each exception.

36

36

Recovery Exception List

This screen provides an example of the Exception List at the RECON level. A Full Function DBD exception has been highlighted and has two exceptions:•HDAM RAA DEFINITION TOO SMALL•RECOVERY NEEDED

Others•Image Copy Needed•Recovery Needed•No Image Copy in X days

37

37

Monitor Recovery View

•The Monitor Recovery view is an automatically refreshable view. The refresh can be both modified or paused.•The table on the left of the view list recovery job steps that have been or are running within the value provided in the Show jobs field.

•The job name, job progress, and status are indicated in the table.•Three buttons are available to obtain additional information about each row: View Activity, View Failures, and View Objects.

•Job details are provided on the right of the view and include additional information about the row highlighted on the left.•The Object Phase Summary pie chart provides information with regards to all the databases being recovered. The pie slices represent database phases and provide a quick view of how many recoveries are complete, how many are still scheduled, and how many are currently being processed.

38

38

Recovery Activity View

The View Activity screen appears when you press the View Activity button on the Monitor Recovery view.This view is automatically refreshed similarly to the Monitor Recovery view. View Activity provides two tabs of information: Log Input and Active Objects. If Log Input processing has completed, the view automatically displays the Active Objects tab. However, either tab can be requested at anytime. The Active Objects tab contains detail information about the objects that the Recovery utility is processing. Objects that are scheduled or completed will not appear in this view. Each object has a progress bar to help confirm the task is progressing. This view can be useful in spotting a job delay due to database recovery processing.

39

39

View Recovery Failures

If the Monitor Recovery view indicates a status of warning or errors, the View Failures button will present a window with more information about which database experienced non-zero return codes. Only objects with non-zero return codes will appear on this view. This screen is not automatically refreshed, but can be refreshed at request by pressing the Refresh button. The JES Viewer button is available on this screen. When pressed, it will execute the JES Viewer, which will provide output information about the Recovery job.

40

40



SYSTEM

DATABASE


DataManagement

Console

RECOVERY




IMSIMS

41

41

Remember when ……PCP reports

As an old DBA I remember when we spent ever Monday reviewing all the database statistical reports to insure we would make it through the week. Hours of time was spent, but it was easy to miss changes in trends. We even used SAS to create reports of the information, but we still had to research weeks of data to insure no growing problems were evident.

42

42

Database I/O Management DBA Toolkit

For those of you who own any MAXM, FP or BRSI solution this function of the DBA Toolkit is FREE to you. It offers:•Database Trending Charts•Repository management vs. PDX•Statistical information from LOAD, UNLOAD, PCP, SUI, ICP, CAP•Plus JOB information•Control Block disassembly for DBD and PSB•DBD mapping with complete segment Topology•JCL GeneratorThis is a chart of the specific statistics of an HDAM database. We can review the I/O rates.

43

43

Database Space Management DBA Toolkit

This is a chart of the specific statistics of an HDAM database. We can review the space or capacity information.

44

44

FAST PATH Space Management

The same space and I/O information is available for Fast Path.

45

45

The Maturity and Management Challenge

60%

30%

With all of this information easily readable at the palms of ourhands we are still in REACTIVE mode. We need to continue to progress to be PROACTIVE and finally actually adding VALUE to the process.

46

46

Proactive Database Management - Advisor

The Advisor Exception list is the “Radar Screen” that provides the PROACTIVE notification that a problem is coming. You no longer have to read and research reports. Advisor does that for you. Out of thousands of database you only have to be concerned about the ones that need action. You can schedule your weekends around just the ones that require your time.

47

47

Forecasting the Future

All of this is done by forecasting towards a given threshold. You can forecast as far out as you need. Most customers look at problems that will be occurring in the next 30-45 days.

48

48

Fastest Reorg is NO Reorg at all! -Advisor

• As each unload step starts, Advisor looks at the database to determine if maintenance is necessary

• If Advisor determines that a reorganization is required, then it allows the unload to continue

• If Advisor determines that a reorganization is not required, then the step is terminated with your choice of a Return Code or User Abend

• Conditional Reorg & Conditional Image Copy• Full Function Feature - Prevents unnecessary maintenance

saving time, resources, and $$$

•Your normal reorganization schedule starts executing

•You tell Advisor that you want to use the Conditional Reorganization feature

But why stop there when all of this can be automated. There is no need to run a Reorg unless it’s needs. The majority of databases are static so why spend the CPU on unnecessary overhead. Plus if the reorg is not running there will be no chance of failure. So the weekends will be quieter and the production windows will be smaller.

49

49

Will there be a world in the future without IMS?

Knowledge from the beginning to late 1800 could be measured in about 3 inches. From 1900 to 1950 it about doubled to 6 inches. From 1950 to 1975 it increased about 10 fold. Since then knowledge growth has be growing at such a rate it can’t be calculated. Yet IMS is still going strong. So if IMS could take the first spaceship to the moon I am sure it will be around to help pilot the future ones.

50

50

K05Nick Griffin

[email protected] Software

51

51

Nick GriffinBMC Software

[email protected]

Session K05

Managing IMS in a New World

IDUG NA 2008 Nick Griffin: Managing IMS in a New World

Documents

Transcript of IDUG NA 2008 Nick Griffin: Managing IMS in a New World