"COPE Product Family COPE for IMS COPE for DBCTL"
COPE Product Family COPE for IMS COPE for DBCTL COPE ICE for RDz Rick Jones Dave Evans 405-288-2016 STANDARDWARE THE COMPANY • Standardware specializes in IMS application development and testing technologies that support Fortune 500 enterprises in maximizing the business value invested in IMS applications and databases by increasing the efficiency of application delivery. • Our reputation is founded on a proven track record of accelerating project delivery, increasing developer productivity and software quality, improving time to value while reducing development costs. 2 WHAT IS COPE? • COPE is an Application Virtualization development and testing environment for IMS. • Provides IMS development environment virtualization that enables many applications to be developed and tested at the same time while maintaining complete independence between each environment. • Not a simulator, emulator or system replicator and has all the functional capabilities of IMS. • Maximizes the cost effectiveness of development and test activities by enabling many development environments to be created on request with an existing preconfigured IMS. 3 WHAT IS COPE? (continued) • Optimizes systems execution costs and enabling application developers and testing personnel to work independently to access an accurate representation of production IMS resources which frees up the IMS administrator from repetitive development support tasks. • Enables IMS application developers and testers to work independently and cost efficiently in their own sandbox. • Reduces the cost of development by enabling a project team to share a single IMS and by freeing up systems programmers from continual development project support tasks. • Accelerates development projects, reduce project and resource costs and free up IMS systems administrators to focus on priority production issues. 4 WHAT IS COPE? (continued) • Optimizes the cost of IMS development by enabling many developers and testers to work at the same time within a single IMS while maintaining isolation between each work load. • Satisfies the demand for immediate access to IMS resources throughout the development life cycle by immediately creating sandboxes which developers and testers can use to progress toward the next project check point. • Executes efficiently within an existing IMS managing developer and tester access to accurate, production representative IMS resources pre-configured by the IMS administrator. 5 PROBLEM IMS DEVELOPMENT FACES TODAY • IMS developers have tight dependencies on IMS systems administrators to set up, configure and populate test systems with representative test data and resources on a day to day basis. • Project costs and are at risk where constrained IMS systems administration resources are at a premium. • Project deadlines are at risk when IMS systems administrators need to focus on production priorities. • Project costs escalate when test system resources require additional processing capacity to ensure separation from production workloads. 6 COPE VALUE PROPOSITION • COPE Users are IMS application developers, quality assurance testers and IMS systems administrators who need to develop and test IMS applications in an IMS environment that accurately represents the target production deployment system. • IMS developers can set up and run their own test cases without needing to go back to the systems administrator. • COPE administrators can create and IMS Developers can use test environments as needed. • IMS systems administrators can create a test system for a development project in a single shot. 7 COPE VALUE PROPOSITION (continued) COPE enables… – IMS systems administrators to plan and perform one time creation, configuration and population of a single IMS test region for all the developers on a particular project to fit with project deadlines and production priorities – IMS project costs to be minimized by optimizing test load execution for existing processing capacity. 8 TYPICAL BUSINESS SCENARIOS • New line of business requirements with near in delivery horizons require that IMS shops frequently need fast cost efficient project turn around when updating and modernizing IMS applications and data. • When project costs and deadlines are tight IMS developers and testers need to work efficiently and independently without being continually dependent on systems administration actions and internal shop procedures to get access to the system resources they need to make progress. • IMS Systems administrators are often in demand and perpetually have to balance the priorities and resources required for production operations with the need to support the resource requirements of internal project development teams. 9 TYPICAL BUSINESS SCENARIOS (continued) • With COPE… – IT managers can accurately control project capital budgets and workload execution costs knowing that the cost effectiveness of development and test activities are optimized for the existing processing configuration avoiding expenditure surprises as project efforts ramp up. – IMS Systems administrators are able to plan ahead to configure and populate a single IMS region with accurate production representative data for all the developers on a project to use so that when project development is in full swing their time is freed from repetitive requests for resource set up and configuration. 10 24 IMS Control Regions 1 IMS Control Region CUSTOMERS USING COPE COPE TERMINOLOGY • Physical System – The IMS control region in which COPE is executing • Logical System – All Logical Systems share the same IMS subsystem – Each Logical System contains a set of databases and PSBs that have names which may or may not match databases and PSBs in other Logical Systems IMS SYSTEM DBD C DBDLIB ACBGEN PSB O PSBLIB DYNALLOC M RESLIB ACBLIB P STAGE 1 I DYNALLOC MFS L FORMAT E DBRC RECON R S PGMLIB IMS CONTROL BMP BMP MPP MPP REGION DB2 TABLES DL1 DATABASES IMS SYSTEM WITH COPE C DBDLIB ACBGEN DBD O PSBLIB PSB M COPE P RESLIB ACBLIB DYNALLOC I DYNALLOC STAGE 1 L FORMAT MFS E R RECON DBRC S PGMLIB IMS CONTROL BMP BMP MPP MPP REGION DB2 TABLES DL1 DATABASES MULTIPLE IMS SYSTEMS WITH COPE C DBDLIB ACBGEN O PSBLIB M COPE RESLIB ACBLIB P COPE ISPF I DYNALLOC L FORMAT E R RECON S PGMLIB Lsys Lsys IMS CONTROL BMP BMP 1-n 1-n REGION DB2 TABLES DL1 DATABASES OVERVIEW OF COPE BASE FEATURES • Each Logical System can have its own DBD and PSB definitions even though they share the same names as other Logical Systems • Databases and PSBs may be ‘EXCLUDED’ from COPE • COPE maintains separate source libraries for each Logical System but shares a single set of load libraries for the Physical System (Psys) • COPE maintains separate Stage 1 source members for each Logical System but generates a single combined Stage 1 member for IMS OVERVIEW OF COPE BASE FEATURES (continued) • COPE maintains separate DYNALLOC definitions for each Logical System and allows you to generate individual DYNALLOC members. • COPE fully supports DBRC • COPE lets any number of CICS sub-systems or batch jobs access the DL1 databases associated with a logical system at the same time • If you use COPE you do not have to change application code in any way or recompile application programs COPE ADMINISTRATOR • Define Logical Systems to COPE • Specify tokens that represent Logical Systems – Re-linkedit IMS modules • Generate a Stage 1 source member • Coordinate Development Groups • 1st line of support for COPE DATA BASE ADMINISTRATORS • May use COPE facilities (full capabilities) • May use the External Interface (Import members (new or replacements)) • Import IMS objects in following sequence – Stage 1 – DBD – PSB • Import following objects anytime – Dynalloc – MFS PROGRAMMERS • No changes need to be made to run programs in a logical system • There are extensive tracing facilities for DL/I and DB2 • Can invoke COPE functions from a IMS MFS screen • COPE requires little to no learning curve for Developers, Testing and Training personnel MFS CONSIDERATIONS • Only need to import changed members. • COPE accesses existing formats unless member has been imported COPE DB2 SUPPORT • COPE assumes applications use unqualified table names. Multiple versions of tables have different qualifiers • COPE can use the same DB2 subsystem for all Lsys’s or can access multiple DB2 systems associated with groups of Lsys’s without any program changes or re-linkediting of applications • COPE manages the plans for each application in each Lsys. No RTT is required COPE ADDITIONAL FEATURES • BMC Delta Feature • COMPUWARE Xpediter • VIA-SOFT SmartTest • CICS Feature • Multi CICS Feature • TicToc Feature (HourGlass) • DB Sync Feature • HALDB Feature • SPOC Feature • ODMA Feature • DB2 Trace Feature • DB2 DBRM Manipulation Feature • IBM Debug Tool COPE ICE for RDz Product Overview (available 3Q 2010) The thought is that using COPE ICE you may not have to have as much system programmer involvement. We can automate many of the steps. David Myers Rational Developer for System z Product Line Manager Installs into a single COPE managed IMS System. Provide a application identification interface by system. Allow Developers or DBA’s to move related parts of the application system into a COPE managed Logical System for development and testing. COPE ICE migrates the necessary components automatically and reports back to RDz when all resources (including Data) are available for developers or testing personnel COPE ICE for RDz Feature • If a developer requires a new environment to be created for testing a change, considerable work must be performed before it becomes available. • COPE has the ability to automatically clone entire environments. Developers can be assigned a cloned environment and may then change components that override the cloned specifications. Changes in applications PSBs DBDs etc are easy to implement. • The COPE ICE Feature allows the environment required for testing one or more applications to be created together with the data that the applications require. After the initial setup, the environment creation process is designed to be automatic and not require the intervention of Database Administrators or Systems Programmers. COPE ICE for RDz Feature • The advantage of ICE is to minimize the unnecessary creation of unused pieces of a large system and to reduce the requirement for skilled technicians as well as reducing the errors that inevitably occur when many components have to be compiled. • Depending on the number of applications, environments may be created in hours or days when weeks or months were required without ICE. COPE ICE Setup • One or more copies of the ‘production’ IMS system have to be created using COPE tools. This involves importing IMS definitions (DBD PSB Stage 1 etc) and recompiling them so that they can run in a COPE IMS Physical System. • An ICE Discovery process is initiated that extracts information from the imported Logical System definitions from the initial setup and automatically loads it into an ICE dictionary. The dictionary is updated with database and DB2 table creation JCL constructed for the initial test system. COPE ICE Setup • After the Discovery process an ICE Operation can be defined for a Collection of program or database objects to be copied to a Logical System. The Operation may be Analyzed to determine its scope and correctness and then Executed to create a new COPE environment. • An ICE Execution operation generates many jobs that copy source and load definitions from one COPE Logical System to another and also create databases and DB2 tables. The generated jobs execute in the correct sequence and are designed to be restarted in the event of unforeseen problems. • Recovery from incorrect operations is built into the system. COPE ICE DATA MODEL FOR COLLECTION DEFINITION • Every Lsys has multiple subsystems in it. Each subsystem has multiple application programs. Each program has a PSB which references multiple DBDs. Application Programs access DB2 tables. • ICE allows Collections of Subsystems, Programs, Tables, PSBs or DBDs within a Lsys. OBJECTS PROCESSED BY ICE The following objects may be moved or copied by ICE. • Program Source • Program subroutine source • Program COPYLIB members • DBD source • PSB source • Stage 1 Source • Dynalloc source • Load modules • DBRM modules • MFS • Batch and BMP JCL OBJECTS PROCESSED BY ICE The following Objects are automatically compiled for an Operation. •DBDs •PSBs •Stage 1 (Definitions are updated in executing system via DRD) •Dynalloc •Plans •MFS The following definitions are constructed for an Operation •DBRC database definitions The following Databases are automatically created for an Operation •DB2 Tables •DL/1 Databases ADDITIONAL CAPABILITIES OF THE ICE FEATURE ICE supports different DB2 subsystems for different Logical Systems, or all Logical systems may share a single DB2 subsystem. If table prefixes are coded in the application, ICE has the capability of removing them before a Bind is made. All DL/1 database organizations are supported. Recovery from any Operation is supported. Recovery reverses the changes made between the pair of Logical Systems defined in an Operation. The ICE dictionary may be entirely refreshed from a COPE Logical System or changes to individual components may be specified manually. A ‘Snippit’ mechanism is provided for Delete/Unload/Load JCL creation for DL/1 Databases and DB2 tables. RD/Z AND COPE ICE INTERFACE (availability TBA) RDz is organized into different perspectives and views within each perspective. The different perspectives take most (if not all) of the window of the Eclipse instance. The views within each perspective relate to the function (or type) of perspective. An example is the z/OS Project perspective which shows views (or tabs) for Remote Systems, z/OS File System Mapping, Properties etc with each view showing detail relating to the z/OS project perspective. COPE ICE has it’s own perspective and views depending on how ICE is being used. There should be an ICE admin perspective which would show COPE system related information such as Application System Group view, Migrating Systems Status view, Total number of Lsys’s view (with details about the LSYS i.e. PSBs, DBDs, Libraries allocated etc), and other system information a COPE ICE admin person would need. COPE ICE for RDz Migrating System View (availability TBA) COPE ICE for RDz Developer View (availability TBA) For additional information Rick Jones firstname.lastname@example.org Dave Evans email@example.com www.standardware.com