Modern Mainframe Development and ALM V23 Columns V5.Indd
Total Page:16
File Type:pdf, Size:1020Kb
Modern Mainframe development and Application Lifecycle Management Cost-effective and easy to implement Enterprise-wide ALM for both mainframe and non-mainframe environments Table of contents Traditional or Modern Mainframe Development .............................................................................5 Program Editor ............................................................................................................................6 On the mainframe ................................................................................................................6 Non-mainframe alternative .................................................................................................6 File System ..................................................................................................................................7 On the mainframe ................................................................................................................7 Non-mainframe alternative .................................................................................................7 Versioning System .......................................................................................................................9 On the mainframe ................................................................................................................9 Non-mainframe alternative .................................................................................................9 Compile Procedure ...................................................................................................................10 First conclusion .........................................................................................................................11 Enterprise-wide Application Lifecycle Management .....................................................................11 IKAN ALM: Bringing Both Worlds Together .....................................................................................12 IKAN ALM Overview ...................................................................................................................12 IKAN ALM Architecture ..............................................................................................................13 Conclusion ........................................................................................................................................14 For More Information .......................................................................................................................15 Related Document ...........................................................................................................................15 2 Modern Mainframe development and ALM Management Many of you have a huge mainframe legacy, sup- porting the key operations of your company. At the same time, innovation drives you to other summary platforms, especially for customer and end-user applications. Today, it is unimaginable that appli- As a CIO, you are confronted with major cations are not available through the Web or via challenges: you have to ensure business mobile devices. continuity and protect your company’s for- mer IT investments, and at the same time, Protecting that mainframe legacy to ensuring business continuity and at the same time being you need to innovate, master the risks and innovative by supporting Web and mobile applica- be cost-efficient. Unfortunately, the bud- tions, at an acceptable cost and while mastering gets to accomplish all that keep on getting the risks, is no child’s play. smaller. Mainframes are mainly used as back-end machines, and the front-end is mostly served through the Web Software applications play a key role in or mobile devices. your company’s revenue plans, but they are becoming more complex and have to That means that you not only have to manage your keep pace with the ever changing business mainframe legacy, but also the new frontends and, most of all, the dependencies between those two. needs. Applications play a major role in Revenue Growth Cost Efficiency Smaller Budgets Shorter and more complex Application Life Cycle Modern Mainframe development and ALM 3 An additional serious concern is where to find the IKAN ALM is IKAN’s flagship product that takes care of resources that still have mainframe skills or who are will- all previously mentioned challenges. It is innovative, ing to acquire them? protects your legacy, masters the risks and is cost-ef- ficient. On top of that, it supports both mainframe and The answer lies in understanding the changing role and non-mainframe systems. use of mainframes, and in finding out how today’s tech- nology can be used to support both mainframes and The objective of this white paper is to explain in more distributed environments. detail how IKAN ALM can radically improve your main- frame lifecycle management, and especially how This is where Application Lifecycle Management (ALM) the developed applications can be deployed on the enters the game. ALM is used to manage the different mainframe. steps in your application’s lifecycle. It is easy to find mainframe-based or PC-based ALM solutions. However, First, we will explain how traditional development is done finding one and the same ALM solution that handles both on a mainframe and how the same work can be done environments is almost impossible. using the currently available PC-based tooling. Secondly, we will explain what enterprise-wide Application Almost … as there exists IKAN ALM. Lifecycle Management stands for, and, finally, we will show how IKAN ALM can be used as a single point of con- trol to protect your mainframe investments and combine the best of both worlds. Note: A detailed technical explanation of how IKAN ALM works, can be found in our technical white paper “Integrating IKAN ALM and Mainframes”. 4 Modern Mainframe development and ALM Traditional or Modern Mainframe Development Conceptually, there is no difference in how a developer develops a program for mainframes, Windows, Linux or mobile devices: The software program needs to be developed, needs to be built/compiled and needs to run. To develop a program, the developer needs a programming language and an editor. Once it is written, the program needs to be saved and/or versioned, and compiled. The following lists up the main differences between developing programs for mainframe on a mainframe or on PC: Mainframe PC Programming languages On mainframes, COBOL and PL/1 are the For Windows, Linux and Mobile, .NET and most popular programming languages Java are widely used. Program editor IBM z/OS developers use ISPF as editor or .NET users use Visual Studio and Java development environment developers mostly use an Eclipse-based editor File system IBM z/OS programmers save their pro- Under Windows a standard Windows grams in a PDS (Partitioned Data Set) directory is used Versioning system On IBM z/OS, CA-Panvalet, CA-Librarian, .NET developers use Visual Source Safe or Serena ChangeMan, MSP Data Manager Team Foundation Server, and Java devel- and IBM SCLM are used as version control opers use CVS, SUBVERSION or GIT systems Compile procedure On IBM z/OS, programs are compiled For .NET and Java, the code is built to to translate source programs into load obtain an executable modules In the next sections, we will explain how a developer works on the mainframe and how that same work can be done using PC-based tooling. Each of those sections covers a specific part of the developer’s role. Once the development is done, the developer’s job is finished and the ALM system will take over to do the final compile on the mainframe. IKAN ALM can help you to complete the application lifecycle, by providing fully automated services to compile/build and deploy/promote to test and production environments. Modern Mainframe development and ALM 5 Program Editor On the mainframe Non-mainframe alternative On IBM z/OS, the most commonly A today’s alternative for writing used editor is ISPF (Interactive COBOL, PL/1 or even JCL ISPF, System Productivity Facility). are Eclipse-based editors run- ISPF provides developers ning on a PC. features for application develop- ment and for administering the Basically, an Eclipse-based or z/OS operating system. The features include: .NET editor offers the same functionality as ISPF and some additional benefits like: • Browse - for viewing data sets and Partitioned Data Set (PDS) members • Automatic code completion • Edit - for editing data sets and PDS members • Syntax checking, helping you out with writing correct • Utilities - for performing data manipulation opera- code while you type tions, such as: • Debugging, with step-by-step, break points, variable • Data Set List - which allows the User to list and inspection, etc. manipulate (copy, move, rename, print, catalog, • Navigation capability (click on an object, go to its delete, etc.) files (called "data sets" in the z/OS definition; find where an object is used and the hier- environment). archy of calls leading to it; etc.). • Member List - for similar manipulations of mem- bers of PDSs. When using an Eclipse-based editor, the mainframe com- • Search facilities for finding modules or text within plexity is completely hidden from the developers and members or data sets. they can use the same Eclipse-based editor as their peer • Compare facilities for comparing members or data Java developers. sets. Another advantage is that by using one and the same ISPF is mostly used as development environment or edi- Eclipse