Beruflich Dokumente
Kultur Dokumente
Tobias Braun
tobiasbraun@de.ibm.com
Agenda
1. Introducing RD&T
2. Licensing
3. Requirements
4. Use Cases
5. FAQ‘s
IMS DB2
CICS
WAS MQ
RDz user
RDz user z/OS
x86 PC running Linux
RDz user
ISPF user
RDz user
RDz & ISPF user
Simulator
Virtualization support
• 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).
• Many processes
Agenda
1. Introducing RD&T
2. Licensing
3. Requirements
4. Use Cases
5. FAQ‘s
• 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.
RDz user
RDz user
RD&T may be IPLed on any HW
(no USB required, only network access)
RDz user RDz user
RD&T RD&T
(Server) (Server)
RDz user
RDz user
Hi Capacity
USB Key
License Server with RD&T V9.0
RD&T
license server
Agenda
1. Introducing RD&T
3. Licensing
4. Requirements
5. Use Cases
6. FAQ‘s
• 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
• 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
Agenda
1. Introducing RD&T
2. Licensing
3. Requirements
4. Use Cases
5. FAQ‘s
• TCP/IP
– RDz
– FTP
– NFS
– SMB
– NJE
• Dataset migration
– ADRDSSU
Web Service
Explorer
CICS
RDz Host Connect CICS
RSE MVS
Server
Remote RSE Client
Projects RTCz MVS
RTCz Build Toolkit
Miner
RTCz
Server
Agenda
1. Introducing RD&T
2. Licensing
3. Requirements
4. Use Cases
5. FAQ‘s
Common Questions
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.
• 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
RD&T limitations
• The RD&T environment does NOT support all System z function, such as:
MIDAWs
Physical Parallel, ESCON®, FCP, FICON®
Logical channel subsystems
and High Performance FICON channels
HiperSockets™
Coupling links and coupling facilities
Multiple I/O paths per device
List-directed IPL
Not all CHSC functions are supported
External Time Reference (ETR)
Some IBM System z Crypto Express2
Server Time Protocol (STP)
Some IBM 3088 CTC device
• Anyone needing any of the function outlined above should consider a traditional System z server.
Tobias Braun
tobiasbraun@de.ibm.com
+49 151 15162580
Backup
z/OS
Problems Encountered
Test LPAR
Project
Team 1. Shared resources combined
[April Maintain] with overlapping schedules
App can elicit conflicts, impede
innovation and slow code
delivery
Project
Team
[Prototype SOA] 2. Coordination of
environmental changes and
Test releases cause bottlenecks,
App
Data delays and additional
Project
Team overhead
[June New Func]
3. Shared test data is difficult to
…