Rational Development and Test Environment

Rational Development and Test Environment Tobias Braun tobiasbraun@de.ibm.com 2012 International Business Machines Corporation 1

Agenda 1. Introducing RD&T 2. Licensing 3. Requirements 4. Use Cases 5. FAQ s 2012 International Business Machines Corporation 2

Announcing the Rational Development & Test Environment COBOL, PL/I, C++, Java, EGL, Batch, Assembler, Debug Tool IMS WAS CICS DB2 MQ RDz user RDz user z/os x86 PC running Linux RDz user ISPF user RDz & ISPF user RDz user Liberate developers to rapidly prototype new applications Develop and test System z applications anywhere, anytime! Free up mainframe development MIPS for production capacity Eliminate costly delays by reducing dependencies on operations staff 2012 International Business Machines Corporation Chapter 1: Introducing RD&T 3

RTCz Agent RD&T RDz Agent System z SW Stack z/os CICS MQ DB2 WebSphere IMS Assembler COBOL C/C++ PL/I Debug Tool System z Architecture Simulator x64 PC running Linux The Rational Development and Test Environment for System z consists of: System z Architecture Simulator (based on zpdt) System z Architecture Simulator provides System z architecture on Intel Capable of running any System z compatible operating system. z/os currently supported. provides great flexibility in running a customized environment Software stack provides a choice of IBM middleware test environments Actual middleware software (including z/os) Actual enterprise compilers Actual APIs (no simulation) RDz and RTCz agents Packaged for simplification Still need RTC and RDz client license(s) to activate <USB License Key*> 2012 International Business Machines Corporation Chapter 1: Introducing RD&T 4

Changes to RD&T V9.0 installer RD&T V9.0 now uses Installation Manager Separate installers provided Standard GUI mode Line mode IM logging enabled by default IM 64 bit libraries required for install IM install steps Check for and install IM version 1.6.2 Prompt for RD&T install location Check for RD&T install package pre-reqs Install RD&T artifacts Run RD&T installer RD&T customization steps still required Tailor system files Create and customize device map file 2012 International Business Machines Corporation Chapter 2:New Features in RD&T 5

RD&T V9.0 IM Installer RD&T Environment V 9.0, Tobias Braun, zhero 6 2012 International Business Machines Corporation Chapter 2:New Features in RD&T 6

Virtualization support RD&T Environment V 9.0, Tobias Braun, zhero With Rational Development and Test Environment for System z V9, you can install the product directly on the operating system used by the supported hardware platform selected (native installations) or you can use a supported virtualization technology to install virtual instances of the product on supported hardware platforms (virtual installations). Operating System requirements for native installations: Red Hat Enterprise Linux (RHEL) 6.3 SUSE Linux Enterprise Server (SLES) 11 SP2 OpenSUSE 12.1 Operating System platforms supported for virtual installations: Red Hat Enterprise Linux (RHEL) 6.3 SUSE Linux Enterprise Server (SLES) 11 SP2 The zbx Model 003 integrated software and hardware system Virtualization Technologies supported: VMWare vsphere 5 zbx version 3 2012 International Business Machines Corporation Chapter 2:New Features in RD&T 7

Parallel Sysplex on RD&T V9.0 Many processes Many 3270 sessions Many network connections 2012 International Business Machines Corporation Chapter 2:New Features in RD&T 8

Parallel Sysplex Sample system z/vm 6.2 volumes supporting multiple z/vm guests Coupling Facilities z/os images z/os 1.13.1 volumes supporting Common z/os IPL volume Unique system parms and page volumes Additional system facilities volumes Coupling facility volume Standalone sysres volume 2012 International Business Machines Corporation Chapter 2:New Features in RD&T 9

Agenda 1. Introducing RD&T 2. Licensing 3. Requirements 4. Use Cases 5. FAQ s 2012 International Business Machines Corporation 10

RD&T environment licensing RD&T Environment V 9.0, Tobias Braun, zhero RD&T is enabled via a USB key Key makes Unit Test feature operational USB key is shipped disabled, activated via Rational Key Center Physical delivery required for key and stack (DVDs) No electronic download available 2012 International Business Machines Corporation Chapter 3: Licensing 11 11

New RD&T V9.0 licensing options Rational Development and Test Environment for System z V9 offers a new, cost effective, flexible licensing option. Using the Resource Value Unit (RVU) metric, the Rational Development and Test Environment for System z V9 can be licensed in terms of the highest number of activated emulated Central Processors. This metric accommodates the dynamic nature of the software development lifecycle, enabling movement of users and activation of Development and Test Environments as needed to support maintenance, development and test activities. Rational Development and Test Environment for System z V9 includes two offerings: Rational Development and Test Environment for System z: The base Development and Test Environment, for development, test, employee education, or demonstration of applications that run on z/os. You can purchase base Development and Test Environment Authorized User Single Install licenses or RVU licenses, depending on intended usage. Rational Development and Test Environment for System z with Parallel Sysplex: Includes the base Development and Test Environment for development, test, employee education, or demonstration of applications that run on z/os, plus the IBM z Personal Development Tool virtual Coupling Facility that is packaged in the z/vm software distribution. The Development and Test Environment with Parallel Sysplex offering is targeted for enterprise teams, and thus only RVU licenses are offered. 2012 International Business Machines Corporation Chapter 3: Licensing 12

Use of Rational tokens RD&T Environment V 9.0, Tobias Braun, zhero Goals: License RD&T based on tokens. Enable per-cp pricing Enable pricing for monoplex or sysplex Behaviors consistent with current zpdt Implementation: RD&T Token monitor added. New license indicators on USB key indicate tokens are required Virtual z definition (device map) indicates #of CPs and mono/sysplex Communication via Unix signals and shared memory only. Logs provided by RD&T Token Monitor For non-token use of RDT, monitor runs but simply simulates token availability. zpdt suspends if tokens are not available zpdt 1. Read Dev map & USB key 2. Create Shared Memory 3. Start RD&T Monitor 4. Signal monitor of changes 5. Check heartbeat and Status 6. Terminate Monitor at end RD&T Token Monitor 1. Connect to shared memory 2. Init logging and wait for signal 3. Get all tokens at once a. Check out/in with linger time 4, Renew before linger expires 5. Repeat until signal to end Device Map #of CPs monoplex/sysplex USB Key Shared Memory Tokens avail: Yes/No Heartbeat timestamp Reason Codes Rational License Manager (FlexLM) 2012 International Business Machines Corporation Chapter 3: Licensing 13

z/os V1.13, including sub-features RD&T Environment V 9.0, Tobias Braun, zhero Selected z/os Software Products Licensed for Use with RD&T V9.0 WebSphere Application Server for z/os V7.0, V8.0, and V8.5 CICS Transaction Server (CICS TS) V4.1, V4.2, and V5.1 CICS Transaction Gateway V8.1 IMS V11.1 and V12.1 DB2 for z/os, V9.1 and V10 WebSphere MQ for z/os, V7.0 IBM Java SDK for z/os, V6.0, V6.0.1, and V7.0 COBOL V4.2 Enterprise PL/I V4.2.1 XL C++ V1.12 and V1.13 IBM Rational COBOL Runtime V6.0.1 (EGL) IBM Debug Tool V12.1 2012 International Business Machines Corporation Chapter 3: Licensing 14

Selected z/vm Software Products Licensed for Use with RD&T V9.0 Parallel Sysplex Edition IBM Directory Maintenance Facility for z/vm, function level 620 IBM Performance Toolkit for VM, function level 620 IBM RACF Security Server for z/vm, function level 620 IBM Remote Spooling Communications Subsystem Networking for z/vm, function level 620 IBM z/vm, version 6 release 2 2012 International Business Machines Corporation Chapter 3: Licensing 15

RD&T License Key Server RD&T Environment V 9.0, Tobias Braun, zhero RDz user RD&T may be IPLed on any HW (no USB required, only network access) RDz user RDz user RD&T (Server) RD&T (Server) RDz user RDz user RDz user License Server with RD&T V9.0 RD&T license server Hi Capacity USB Key RD&T (Server) RD&T (Server) RD&T (Server) 1 USB key + license server can support entire enterprise deployment or configure separate servers and USB keys for departmental monitoring RDz user RDz user RDz user 2012 International Business Machines Corporation Chapter 3: Licensing 16

Agenda 1. Introducing RD&T 3. Licensing 4. Requirements 5. Use Cases 6. FAQ s 2012 International Business Machines Corporation 17

RD&T machine specifications Processor Recommended configuration is Generation 3 Intel i7 2.6 GHz Quad-core or equivalent At least 1 Linux core is required for each set of 3 z/os cores implemented. For standard installations, a 4-Core system with 1 core devoted to Linux and 3 cores devoted to z/os is recommended. For Parallel Sysplex installations, an 11-Core system with 3 cores devoted to Linux and 8 cores devoted to z/vm and its guests is recommended RAM 2 GB to 4 GB of RAM required per emulated Central Processor (CP) for z/os 1 GB per processor core allocated to Linux For those using the Parallel Sysplex capability, 1 GB per coupling facility 2012 International Business Machines Corporation Chapter 4: Requirements 18

RD&T machine specifications (cont.) Disk space 50 GB to 100 GB of disk space is required for z/os. There should also be twice as much disk space available as the total required memory defined for the Rational Development and Test Environment for System z instance. For those using the Parallel Sysplex capability, an additional 54 GB of disk space is required to hold the zvm software distribution, the sample system, and to implement the sample configuration that comes with the Parallel Sysplex capability. Depending on how much software you load into each z/os system running in a Parallel Sysplex configuration, you may need up to 220 GB per z/os system. Network 100MB / 1GB Ethernet adapter (shared by Linux and z/os) Wireless (OK for Linux, not recommended for z/os) USB Required for hardware key License server may used 2012 International Business Machines Corporation Chapter 4: Requirements 19

Agenda 1. Introducing RD&T 2. Licensing 3. Requirements 4. Use Cases 5. FAQ s 2012 International Business Machines Corporation 20

Accessing Existing z/os Data RD&T Environment V 9.0, Tobias Braun, zhero Multiple data types Sequential files, PDS s, PDSE s, HFS, ZFS, DB2 databases, IMS databases, VSAM files, ICF Catalogs Multiple ways to access data TCP/IP RDz FTP NFS SMB NJE Dataset migration ADRDSSU DASD volume migration Complete volumes (3380 or 3390) are transferred. This includes IPL text, volume labels, VTOC, and unallocated space. The logical contents of the volume are not examined. Data sets on the volume are not recognized. The utility copies and transfers all the tracks on the volume. RD&T DASD Migration Utility zpdtmsrv, hckd2ckd 2012 International Business Machines Corporation Chapter 5: Use Cases 21

RD&T based build Development on RD&T with host-based SCM: Copy code and data to RD&T as needed Use RDz or other methods to run a standard compile/debug cycle When tests and changes are complete, merge changes back to mainframe RD&T Host RDz Web Service Explorer Host Connect CICS CICS Remote Projects RSE Client RSE Server MVS Build tools MVS SCM Build tools 2012 International Business Machines Corporation 22 22

Distributed SCM and Build Development on RD&T with distributed SCM: SCM manages movement of code to and from mainframe. Builds may be done either on RD&T or on mainframe (depending on SCM). Test outputs installed by SCM on RD&T. Use RDz or other methods to run a standard compile/debug cycle RD&T Host Web Service Explorer RDz Remote Projects Host Connect RSE Client RSE Server RTCz Miner CICS MVS RTCz Build Toolkit CICS MVS Rational Team Concert /z Client RTCz Build Toolkit RTCz Server 2012 International Business Machines Corporation 23 23

Agenda 1. Introducing RD&T 2. Licensing 3. Requirements 4. Use Cases 5. FAQ s 2012 International Business Machines Corporation 24

Common Questions RD&T Environment V 9.0, Tobias Braun, zhero 1. What is the maximum number of developers a RD&T server can support? This can vary depending on the underlying hardware and development activity. Desktops can typically support 3-5 users. Server class machines can support up to 15-25 users. 2. How can I get test data for use in RD&T? Customers can use existing tools like IDCAMS, DB2 utilities, etc. to extract test data and then download it to the RD&T machine. RD&T provides a DASD volume migration utility that can download an entire 3390 DASD volume onto the RD&T machine. 3. Can I run other levels of the middleware provided? RD&T is supplied with a standard set of software middleware, compilers, and runtimes. The included license covers this software at the supplied versions. Special license terms and conditions for other versions/ releases of software may be created as long as the requested software is currently in service and remains in service 6 months from the sales date. 4. Can I use other IBM tools in the RD&T environment? ESW zotc or zmlc tools (like PD tools) currently are not licensed for use with RD&T. Passport Advantage products can be used in the RD&T environment. Exceptions to these rules are handled on a case by case basis with individual IBM product owners. 5. Can I run third party software? Yes, if the third party license allows this. Customers must work with their software vendor to determine licensing considerations. 2012 International Business Machines Corporation Chapter 6: FAQ s 25

Common Questions (cont.) RD&T Environment V 9.0, Tobias Braun, zhero 6. Does RD&T require linux skills? Linux skills are required to setup the host linux operating system and to allocate linux resources for the System z architecture simulator. Some linux networking skills are helpful. Linux program installation and maintenance skills are also required. 7. Does RD&T require system programming skills? z/os does require system programming skills to set up the development and/or testing environments. IBM recommends setting up one RD&T instance and then cloning that configuration to other instances. 8. What about security? RACF is installed, but with minimal configuration. The sample configuration guide has suggestions for basic security. Security is a site choice. The ability to customize z/os on a platform designed for individuals or small teams may: Provide better testing opportunities Provide customization for individual productivity gains Provide opportunities to learn about z/os fundamentals 2012 International Business Machines Corporation Chapter 6: FAQ s 26

RD&T installation and configuration documentation IBM Rational Development and Test Environment for System z Quick Start Guide (GI13-1802-03) IBM Rational Development and Test Environment for System z USB Hardware Device Quick Start Guide (GI11-9147-02) Installation: System z Personal Development Tool Redbooks Basic instructions for installation/ configuration of Linux, zpdt, and starter z/os system References System z Personal Development Tool Volume 1: Introduction and Reference (SG24-7721-05) System z Personal Development Tool Volume 2: Installation and Basic Usage (SG24-7722-05) System z Personal Development Tool Volume 3: Additional Topics (SG24-7723-05) System z Personal Development Tool Volume 4: Coupling and Parallel Sysplex (SG24-7859-02) Configuring z/os with IBM Rational Development and Test Environment for System z - z/os 1.13 (SC14-7281-04) Contains basic instructions and examples for z/os system customization Isolate base configuration files from customized files Store user data on a separate disk Configure TCP/IP settings Configure security for critical system files Create user IDs Other minor but common changes to z/os System programmer assistance will be required to replicate specific conventions, security models, subsystems, etc 2012 International Business Machines Corporation Chapter 6: FAQ s 27

RD&T limitations RD&T Environment V 9.0, Tobias Braun, zhero The RD&T environment does NOT support all System z function, such as: Physical Parallel, ESCON, FCP, FICON and High Performance FICON channels Coupling links and coupling facilities List-directed IPL External Time Reference (ETR) Server Time Protocol (STP) MIDAWs Logical channel subsystems HiperSockets Multiple I/O paths per device Not all CHSC functions are supported Some IBM System z Crypto Express2 Some IBM 3088 CTC device RD&T does not produce an environment equal to a larger System z. Some aspects of a larger system are unlikely to be met in any very small environment. Inability to verify and enhance the scalability of a program Inability to run application programs that require hundreds of MIPS. A RD&T system is not recommended for very fine-level performance tuning that is sensitive to memory location, cache functions, and pipeline optimization. In addition, the RD&T platform does not nearly have the same quality of service as does a mainframe in terms of availability and connectivity. Anyone needing any of the function outlined above should consider a traditional System z server. 2012 International Business Machines Corporation Chapter 6: FAQ s 28

Tobias Braun tobiasbraun@de.ibm.com +49 151 15162580 2012 International Business Machines Corporation 29 29

Backup 2012 International Business Machines Corporation 30

Provisioning Using ADRDSSU 1. Create user storage on RD&T system Allocate linux disk space to hold a 3390 volume dump and to hold a reformatted volume dump. alcckd /z/user01 -d3390-3 alcckd /z/user02 -d3390-3 alcckd /z/user03 -d3390-3 2. Activate user volumes on RD&T system Update devmap or issue awsmount for new volume(s). Ipl z/os system. Initialize new volume(s) with label and VTOC. Vary new volume(s) online. 3. Create source dump on source system A normal ADRDSSU job is used to dump the source volume. 4. Xmit dump on source system Create xmit formatted dump. 5. Send dump to RD&T system Send the xmit-formatted dump using an ftp connection from source z/os to target z/os. (May use intermediate FTP node.) 6. Receive dump on RD&T system Pre-allocated datasets on the receiving z/os system. One data set is the target of an ftp transfer from Linux (or some other source) and the other is for the output of the TSO RECEIVE function. This last data set is then the input to a RESTORE job. 7. Format dump on RD&T system Use TSO to reformat the dump into the original format created by ADRDSSU. 8. Restore the volume on RD&T system Restore the z/os volume. 2012 International Business Machines Corporation Chapter 5: Use Cases 31

Provisioning Using the DASD Migration Facility 32 Start server program on z/os START MIGRATER Start client program on linux hckd2ckd 192.168.2.211:3990 /z/syscfg v SYSCFG 2012 International Business Machines Corporation Chapter 5: Use Cases 32

Typical z/os Testing Architecture Organized by project team, vertically scaled, sharing resources, limited automation Project Team [April Maintain] Project Team [Prototype SOA] Project Team [June New Func] Project Team [Dec Sys Upgrade] z/os Test LPAR App App App Test Data Problems Encountered 1. Shared resources combined with overlapping schedules can elicit conflicts, impede innovation and slow code delivery 2. Coordination of environmental changes and releases cause bottlenecks, delays and additional overhead 3. Shared test data is difficult to manage and can lead to over testing or incorrect test results 2012 International Business Machines Corporation Chapter 5: Use Cases 33

QA/ Integration Test LPAR RD&T Environment V 9.0, Tobias Braun, zhero Delivery Organized for Flexibility and Speed Organized by application team, horizontally sliced, dedicated resources, highly automated Project Team [April Maintain] LPAR z/os LPAR Project Team [Prototype SOA] Project Team [June New Func] Project Team [Dec Sys Upgrade] RD&T RD&T LPAR Data Data Data Integrated Test Data Problems Encountered 1. Shared resources combined with overlapping schedules can elicit conflicts, impede innovation and slow code delivery 2. Coordination of environmental changes and releases cause bottlenecks, delays and additional overhead 3. Shared test data is difficult to manage and can lead to over testing or incorrect test results 4. Provisioning, managing, and synchronizing project test environments including data Data 2012 International Business Machines Corporation Chapter 5: Use Cases 34