My DB2 process is broken By Jeff Gross WW DB2/IMS Technical Support Manager
Abstract <ul><li>DB2 application or vendor product processing can fail for a variety of reasons due to no changes in the o...
Agenda <ul><li>Learn some of the DB2 product changes that can happen and how to manage this change. </li></ul><ul><li>Lear...
Changes to the product DB2 9 <ul><li>New features  </li></ul><ul><li>Parameter options change  </li></ul><ul><li>Command o...
New features affect implementation <ul><li>XML changed dramatically from DB2 8 to 9 </li></ul><ul><ul><li>XML Extender is ...
Parameter options change in DB2 9  <ul><li>Changes in BIND PACKAGE and BIND PLAN defaults </li></ul><ul><ul><li>The defaul...
Command output or actions are different  in DB2 9 <ul><li>DB2 drops certain indexes when a unique constraint is dropped. <...
SQL Reserved words change <ul><li>New words and term can become non-usable. </li></ul><ul><ul><li>AT </li></ul></ul><ul><u...
SQL Codes change! <ul><li>Adjust applications that depend on error information that is returned from DB2-supplied stored p...
Old features that are deprecated in DB2 9 <ul><li>Simple Tablespaces </li></ul><ul><li>XML Extender </li></ul><ul><li>Appl...
Recommendations for changing DB2 releases  (part 1 of 2) <ul><li>Be careful in using brand new featured that may change in...
Recommendations for changing DB2 releases  (part 2 of 2) <ul><li>Test thoroughly </li></ul><ul><ul><li>Make sure test subs...
Vendor changes <ul><li>z/OS changes affect our environments. </li></ul><ul><ul><li>New z/OS every September </li></ul></ul...
z/OS 1.9 Changes <ul><li>change to the way DFSMS handles recordsize </li></ul><ul><li>ALLOWUSERKEYCSA </li></ul>My DB2 pro...
z/OS 1.10 Changes <ul><li>Unable to read the active DB2 log in a non-data sharing </li></ul><ul><li>This ABEND is caused b...
Application Vendors <ul><li>Who is planning for upgrades to stay in sync with z/OS and DB2? </li></ul><ul><li>Does anyone ...
Tool Vendors (what should be done) <ul><li>Should probably be treated in the same manner as Application Vendors. </li></ul...
DB2 9 changes that affected CA Tools <ul><li>DB2 9 compressed indexes </li></ul><ul><li>Multiple versions of tablespace in...
Updating software in correct and efficient order is difficult to coordinate <ul><li>Here is a calendar for z/OS, DB2 and C...
Recommendation for Vendor changes <ul><li>Know the schedule </li></ul><ul><ul><li>Not only Release date, but End of  Servi...
Data Changes over time <ul><li>Objects become larger over time </li></ul><ul><li>Objects become disorganized  </li></ul><u...
Objects become larger over time <ul><li>When objects get larger, backups and reorgs need more resources </li></ul><ul><li>...
Objects become disorganized  <ul><li>DB2 objects can be organized in a particular order if a Clustering Index is used.  Ho...
Transaction rate grows <ul><li>Real time activities are affected. </li></ul><ul><li>Batch windows might be at the limit or...
Recommendation for what can be done to predict <ul><li>Of course, run appropriate Reorg schedule </li></ul><ul><ul><li>Use...
How can the process or application be less sensitive to time. <ul><li>At design time, code in processes to sense volume </...
What do  before  a problem is found. <ul><li>Ask the own of the process what are their recommendations. </li></ul><ul><ul>...
Type of error settings <ul><li>Are there Parmlib options? </li></ul><ul><li>Initialization options </li></ul><ul><li>Run t...
Type of documentation to capture. <ul><li>Job or started task output </li></ul><ul><li>DB2MSTR </li></ul><ul><li>Dump (SYS...
Best Practices for running process <ul><li>Ask the owner of the process what are their recommendations. </li></ul>My DB2 p...
What to do  when  a problem is found. <ul><li>Have a plan for failure </li></ul><ul><li>Get correct people involved </li><...
Have a plan for failure <ul><li>Have a simple plan that new people can use. </li></ul><ul><li>Have this plan/resource in a...
Get correct people involved <ul><li>As before, the first person involved can make all the difference in resolving an issue...
Capture information <ul><li>Follow the plan </li></ul><ul><li>If loop or hang, capture dump before cancel. </li></ul>My DB...
Contact process owner to get advice  <ul><li>Has anything changed to affect this process? </li></ul><ul><ul><li>OS </li></...
Give expectation as to resolution need. <ul><li>What  is the business impact to your company? </li></ul><ul><ul><li>Will t...
Summary <ul><li>I hope you found this presentation to get you thinking of what is happening at your site. </li></ul><ul><l...
Q&A <ul><li>Any other questions?  </li></ul>My DB2 process is broken.  Fix It!  Copyright © 2009 CA. All rights reserved.
Terms of This Presentation My DB2 process is broken.  Fix It!  Copyright © 2009 CA. All rights reserved. This presentation...
For Informational Purposes Only My DB2 process is broken.  Fix It!  Copyright © 2009 CA. All rights reserved. Certain info...
Upcoming SlideShare
Loading in …5
×

My DB2 Process is Broken! Fix It!

360 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
360
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This presentation is written with 10 years of Technical Support work providing the inspiration. Sometimes failure to software happens because of the unexpected, but many times, it happens due to the failure of maintenance, planning and lost knowledge of dependencies. The goal of this presentation is to not expose every possible failure, but to show the major reason for failure is a change in the environment and how this change should be managed. The scope of this presentation is software running on the z/OS platform with a connection to DB2.
  • .
  • Source is UPGRAD QI91517
  • Source is UPGRAD RI02220
  • These are some items that were found in the field after the CA DB Management Tools for DB2 for z/OS were released. Source is UPGRAD QI93079
  • My DB2 Process is Broken! Fix It!

    1. 1. My DB2 process is broken By Jeff Gross WW DB2/IMS Technical Support Manager
    2. 2. Abstract <ul><li>DB2 application or vendor product processing can fail for a variety of reasons due to no changes in the original application.  Learn what time and environmental changes can do to a process that used to run just fine. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    3. 3. Agenda <ul><li>Learn some of the DB2 product changes that can happen and how to manage this change. </li></ul><ul><li>Learn what changes Vendor can make. </li></ul><ul><li>What happens to data objects over time? </li></ul><ul><li>How can an application process design be less sensitive to change? </li></ul><ul><li>What to do before an application fails. </li></ul><ul><li>What to do when an application or vendor code fails. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    4. 4. Changes to the product DB2 9 <ul><li>New features </li></ul><ul><li>Parameter options change </li></ul><ul><li>Command output or actions can be different </li></ul><ul><li>SQL Reserved words change </li></ul><ul><li>SQL Codes change! </li></ul><ul><li>Old features deprecated </li></ul><ul><li>Recommendations </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    5. 5. New features affect implementation <ul><li>XML changed dramatically from DB2 8 to 9 </li></ul><ul><ul><li>XML Extender is deprecated </li></ul></ul><ul><ul><li>Drop any user-defined data types with the name XML to prevent problems with the new Version 9.1 built-in XML data type. You can recreate the existing user-defined data types with new names. </li></ul></ul><ul><li>Long names in DB2 7 </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    6. 6. Parameter options change in DB2 9 <ul><li>Changes in BIND PACKAGE and BIND PLAN defaults </li></ul><ul><ul><li>The default value for bind option CURRENTDATA is changed from YES to NO. </li></ul></ul><ul><ul><li>The default value for bind option ISOLATION is changed from RR to CS. </li></ul></ul><ul><ul><li>DBPROTOCOL(PRIVATE) to DBPROTOCOL(DRDA) </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    7. 7. Command output or actions are different in DB2 9 <ul><li>DB2 drops certain indexes when a unique constraint is dropped. </li></ul><ul><ul><li>If a table is in an implicitly-created table space, and a unique constraint on that table is dropped, DB2 drops the index that enforces uniqueness. </li></ul></ul><ul><li>Changes to -DISPLAY command location name length </li></ul><ul><ul><li>The length of the -DISPLAY command location name can be longer than 16 characters so that the location name can have a value of an IPV6 IP address. </li></ul></ul><ul><ul><li>Do you have any operations scripts dependent on this command? </li></ul></ul><ul><li>Automatic rebind of plans and packages created before DB2Version 4 </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    8. 8. SQL Reserved words change <ul><li>New words and term can become non-usable. </li></ul><ul><ul><li>AT </li></ul></ul><ul><ul><li>CLONE </li></ul></ul><ul><ul><li>DOCUMENT </li></ul></ul><ul><ul><li>KEEP </li></ul></ul><ul><ul><li>ROLE </li></ul></ul><ul><ul><li>ROW </li></ul></ul><ul><li>This would mostly affect an application. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    9. 9. SQL Codes change! <ul><li>Adjust applications that depend on error information that is returned from DB2-supplied stored procedures </li></ul><ul><ul><li>These stored procedures return more meaningful SQLCODEs and SQLSTATEs than they returned in previous releases of DB2. </li></ul></ul><ul><ul><ul><li>SQLJ.INSTALL_JAR </li></ul></ul></ul><ul><ul><ul><li>SQLJ.REMOVE_JAR </li></ul></ul></ul><ul><ul><ul><li>SQLJ.REPLACE_JAR </li></ul></ul></ul><ul><ul><ul><li>SQLJ.DB2_INSTALL_JAR </li></ul></ul></ul><ul><ul><ul><li>SQLJ.DB2_REPLACE_JAR </li></ul></ul></ul><ul><ul><ul><li>SQLJ.DB2_REMOVE_JAR </li></ul></ul></ul><ul><ul><ul><li>SQLJ.DB2_UPDATEJARINFO </li></ul></ul></ul><ul><li>Adju </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    10. 10. Old features that are deprecated in DB2 9 <ul><li>Simple Tablespaces </li></ul><ul><li>XML Extender </li></ul><ul><li>Applications that are compiled on unsupported compilers that do not support the COBOL COMP-5 attribute </li></ul><ul><li>Warning, these features going away in the future </li></ul><ul><ul><li>DDF Private protocol </li></ul></ul><ul><ul><li>Plans that contain DBRMs </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    11. 11. Recommendations for changing DB2 releases (part 1 of 2) <ul><li>Be careful in using brand new featured that may change in the next release. </li></ul><ul><li>Watch for older applications that might have features eliminated(deprecated) </li></ul><ul><li>Review IBM Install Guide </li></ul><ul><ul><li>DB2 8 has 5 pages of info </li></ul></ul><ul><ul><li>DB2 9 has 23 pages of info </li></ul></ul><ul><ul><li>DB2 X could have ?? </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    12. 12. Recommendations for changing DB2 releases (part 2 of 2) <ul><li>Test thoroughly </li></ul><ul><ul><li>Make sure test subsystem has same attributes as production subsystem </li></ul></ul><ul><ul><ul><li>Data sharing </li></ul></ul></ul><ul><ul><ul><li>Data size </li></ul></ul></ul><ul><ul><ul><li>If possible, stress test with high transaction rate </li></ul></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    13. 13. Vendor changes <ul><li>z/OS changes affect our environments. </li></ul><ul><ul><li>New z/OS every September </li></ul></ul><ul><li>Application Vendors </li></ul><ul><ul><li>How are applications integrated </li></ul></ul><ul><ul><li>SAP, PeopleSoft, Siebel and others </li></ul></ul><ul><li>Tool Vendors </li></ul><ul><ul><li>What should be done </li></ul></ul><ul><ul><li>How has changes affected CA </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    14. 14. z/OS 1.9 Changes <ul><li>change to the way DFSMS handles recordsize </li></ul><ul><li>ALLOWUSERKEYCSA </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    15. 15. z/OS 1.10 Changes <ul><li>Unable to read the active DB2 log in a non-data sharing </li></ul><ul><li>This ABEND is caused by a zero value in the RDISECTN field of the DB2 RDI control block. </li></ul><ul><li>IBM CSECT CUNMCNV </li></ul><ul><li>What will z/OS 1.11 reveal? </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    16. 16. Application Vendors <ul><li>Who is planning for upgrades to stay in sync with z/OS and DB2? </li></ul><ul><li>Does anyone have any real world stories they would like to share? </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    17. 17. Tool Vendors (what should be done) <ul><li>Should probably be treated in the same manner as Application Vendors. </li></ul><ul><li>Who is planning for upgrades to stay in sync with z/OS and DB2? </li></ul><ul><li>Does anyone have any real world stories they would like to share? </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    18. 18. DB2 9 changes that affected CA Tools <ul><li>DB2 9 compressed indexes </li></ul><ul><li>Multiple versions of tablespace in a mixed release (V8 NFM & 9 CM) Data Sharing group </li></ul><ul><li>Partition by Growth option </li></ul><ul><li>Routine name > 16 characters </li></ul><ul><li>Real Time Stats </li></ul><ul><li>Data Sharing group control block chaining </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    19. 19. Updating software in correct and efficient order is difficult to coordinate <ul><li>Here is a calendar for z/OS, DB2 and CA DB Mgmt Tools for DB2 for z/OS </li></ul><ul><li>Need to have a plan on when to upgrade. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.   Spring 2007 Summer 2007 Fall 2007 Winter 2007 Spring 2008 Summer 2008 Fall 2008 Winter 2009 Spring 2009 Summer 2009 Fall 2009 Winter 2009 Spring 2010 Summer 2010 Fall 2010 z/OS     z/OS 1.9       z/OS 1.10       z/OS 1.11       z/OS 1.12? DB2 DB2 9                       DB2 X?     CA   r11.5 SP1         r11.5 SP2     r12       r14?   App ??                              
    20. 20. Recommendation for Vendor changes <ul><li>Know the schedule </li></ul><ul><ul><li>Not only Release date, but End of Service date </li></ul></ul><ul><li>Ask the vendor how comfortable they are with the release </li></ul><ul><ul><li>Check on vendors latest maintenance package </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    21. 21. Data Changes over time <ul><li>Objects become larger over time </li></ul><ul><li>Objects become disorganized </li></ul><ul><li>Transaction rate grows </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    22. 22. Objects become larger over time <ul><li>When objects get larger, backups and reorgs need more resources </li></ul><ul><li>More objects means the DB2 Catalog must work harder. </li></ul><ul><ul><li>Typical Application from a vendor has 10,000 Tables and 20,000 Views </li></ul></ul><ul><li>Downstream processes may not be handle the greater volume. </li></ul><ul><li>Errors such as </li></ul><ul><ul><li>B37 (disk space) </li></ul></ul><ul><ul><li>S878 (Memory) </li></ul></ul><ul><ul><li>322 (CPU Time) </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    23. 23. Objects become disorganized <ul><li>DB2 objects can be organized in a particular order if a Clustering Index is used. However, the APPEND option on CREATE TABLE or ALTER TABLE statement will allow rows to be added at the end of object or partition. </li></ul><ul><li>This should affect the majority of the queries since the original purpose of clustering is to optimize data retrieval. </li></ul><ul><li>This disorganization can affect SQL CPU time and Buffer Pool size as more pages need be read. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    24. 24. Transaction rate grows <ul><li>Real time activities are affected. </li></ul><ul><li>Batch windows might be at the limit or asked to be reduced. </li></ul><ul><li>More real storage needed by processes. </li></ul><ul><ul><li>SQL processes </li></ul></ul><ul><ul><li>Application programs </li></ul></ul><ul><ul><li>Vendor tools </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    25. 25. Recommendation for what can be done to predict <ul><li>Of course, run appropriate Reorg schedule </li></ul><ul><ul><li>Use tool to determine when reorg should be performed. </li></ul></ul><ul><li>Have a Resource Manager monitor the processes </li></ul><ul><ul><li>Capture metrics on CPU and I/O </li></ul></ul><ul><ul><li>If a limit or threshold is passed, then investigation can begin. </li></ul></ul><ul><li>Product to assist are </li></ul><ul><ul><li>CA MICS Resource Management </li></ul></ul><ul><ul><li>CA JARS Resource Accounting </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    26. 26. How can the process or application be less sensitive to time. <ul><li>At design time, code in processes to sense volume </li></ul><ul><ul><li>If a transaction count goes over a certain limit, print a message. </li></ul></ul><ul><ul><li>If storage is sensed to be low, reduce activity </li></ul></ul><ul><ul><ul><li>Detector has new processes to sense memory constraints, shut down activity and automatically restart when constraint is eliminated. </li></ul></ul></ul><ul><li>If an object is a data store, plan an archive feature. </li></ul><ul><ul><li>Use a periodic cycle to categorize data. Could be monthly, quarterly or yearly. </li></ul></ul><ul><li>Recommendations? </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    27. 27. What do before a problem is found. <ul><li>Ask the own of the process what are their recommendations. </li></ul><ul><ul><li>Type of error settings </li></ul></ul><ul><ul><li>Type of documentation to capture. </li></ul></ul><ul><ul><li>Best Practices for running process </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    28. 28. Type of error settings <ul><li>Are there Parmlib options? </li></ul><ul><li>Initialization options </li></ul><ul><li>Run time options to gather trace or debug messages. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    29. 29. Type of documentation to capture. <ul><li>Job or started task output </li></ul><ul><li>DB2MSTR </li></ul><ul><li>Dump (SYSU or SYSM?) </li></ul><ul><ul><li>Make sure DD is (Mod,Catlg) for multiple dumps </li></ul></ul><ul><li>Is data needed? </li></ul><ul><ul><li>Image copy and Log </li></ul></ul><ul><li>Consistency in question? SYSLGRNX </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    30. 30. Best Practices for running process <ul><li>Ask the owner of the process what are their recommendations. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    31. 31. What to do when a problem is found. <ul><li>Have a plan for failure </li></ul><ul><li>Get correct people involved </li></ul><ul><li>Capture information </li></ul><ul><li>Contact process owner to get advice </li></ul><ul><li>Give expectation as to resolution need. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    32. 32. Have a plan for failure <ul><li>Have a simple plan that new people can use. </li></ul><ul><li>Have this plan/resource in a fail safe mode. </li></ul><ul><ul><li>Online is best with a local electronic copy </li></ul></ul><ul><ul><li>Doubtful that a printed copy is needed. </li></ul></ul><ul><li>Have this plan be reviewed and signed off by involved parties. </li></ul><ul><li>This is basic operation stuff.. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    33. 33. Get correct people involved <ul><li>As before, the first person involved can make all the difference in resolving an issue correctly. </li></ul><ul><ul><li>Experience </li></ul></ul><ul><ul><li>Training </li></ul></ul><ul><ul><li>Education </li></ul></ul><ul><ul><li>Communication Skills </li></ul></ul><ul><li>Have an escalation process. </li></ul><ul><ul><li>Who is called </li></ul></ul><ul><ul><li>For what expertise </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    34. 34. Capture information <ul><li>Follow the plan </li></ul><ul><li>If loop or hang, capture dump before cancel. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    35. 35. Contact process owner to get advice <ul><li>Has anything changed to affect this process? </li></ul><ul><ul><li>OS </li></ul></ul><ul><ul><li>DB2 maintenance </li></ul></ul><ul><ul><li>Process Maintenance </li></ul></ul><ul><li>Confirm actions taken </li></ul><ul><li>Ask what else they want done. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    36. 36. Give expectation as to resolution need. <ul><li>What is the business impact to your company? </li></ul><ul><ul><li>Will this process not running affect bringing up on-line systems? </li></ul></ul><ul><ul><li>Will a billing or accounting cycle be affected. </li></ul></ul><ul><ul><li>What is that cost to the down stream processes. </li></ul></ul><ul><li>How often are updates needed? </li></ul><ul><ul><li>How do you want updates? Email or Teleconference </li></ul></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    37. 37. Summary <ul><li>I hope you found this presentation to get you thinking of what is happening at your site. </li></ul><ul><li>Are there any experiences you would like to share? </li></ul><ul><li>I thank you for time and knowledge. </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    38. 38. Q&A <ul><li>Any other questions? </li></ul>My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved.
    39. 39. Terms of This Presentation My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved. This presentation was based on current information and resource allocations as of November 16, 2008 and is subject to change or withdrawal by CA at any time without notice. Notwithstanding anything in this presentation to the contrary, this presentation shall not serve to (i) affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CA software product; or (ii) amend any product documentation or specifications for any CA software product. The development, release and timing of any features or functionality described in this presentation remain at CA’s sole discretion. Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in this presentation, CA will make such release available (i) for sale to new licensees of such product; and (ii) to existing licensees of such product on a when and if-available basis as part of CA maintenance and support, and in the form of a regularly scheduled major product release. Such releases may be made available to current licensees of such product who are current subscribers to CA maintenance and support on a when and if-available basis. In the event of a conflict between the terms of this paragraph and any other information contained in this presentation, the terms of this paragraph shall govern.
    40. 40. For Informational Purposes Only My DB2 process is broken. Fix It! Copyright © 2009 CA. All rights reserved. Certain information in this presentation may outline CA’s general product direction. All information in this presentation is for your informational purposes only and may not be incorporated into any contract. CA assumes no responsibility for the accuracy or completeness of the information. To the extent permitted by applicable law, CA provides this document “as is” without warranty of any kind, including without limitation, any implied warranties or merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, lost investment, business interruption, goodwill, or lost data, even if CA is expressly advised of the possibility of such damages.

    ×