2. 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
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
1. COPE Product Family COPE for IMS COPE for DBCTL COPE ICE for RDz Rick Jones
2. 2 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.
3. 3 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.
4. 4 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.
5. 5 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.
6. 6 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.
7. 7 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.
8. 8 Cope Value Proposition (continued)
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.
9. 9 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.
10. 10 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.
14. Customers using COPE
15. COPE TERMINOLOGY
The IMS control region in which COPE is executing
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
16. IMS SYSTEM
17. IMS SYSTEM WITH COPE
18. MULTIPLE IMS SYSTEMS WITH COPE
19. 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
20. 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
21. 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
22. 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
Import following objects anytime
23. 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
24. MFS CONSIDERATIONS
Only need to import changed members.
COPE accesses existing formats unless member has been imported
25. 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
26. COPE ADDITIONAL FEATURES BMC Delta Feature
Multi CICS Feature
TicToc Feature (HourGlass)
DB Sync Feature
DB2 Trace Feature
DB2 DBRM Manipulation Feature
IBM Debug Tool
27. 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
28. 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.
29. 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.
30. 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.
31. 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.
32. 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.
33. Objects processed by ICE The following objects may be moved or copied by ICE.
Program subroutine source
Program COPYLIB members
Stage 1 Source
Batch and BMP JCL
34. Objects processed by ICE The following Objects are automatically compiled for an Operation.
Stage 1 (Definitions are updated in executing system via DRD)
The following definitions are constructed for an Operation
DBRC database definitions
The following Databases are automatically created for an Operation
35. Additional Capabilities of the ICE Feature
36. RD/z and COPE ICE Interface (availability TBA)
37. COPE ICE for RDz Migrating System View (availability TBA)
38. COPE ICE for RDz Developer View (availability TBA)