In this post, I want to outline the RDz considerations to keep in mind when upgrading RTC from 3.x to 4.0.
The information below is applicable to the following releases:
- RTC 3.0, 3.0.1, 3.0.1.x, 4.0
- RDz: 8.0.3.x, 8.5
This is the Eclipse based client that can be shell shared with the RDz Eclipse client. For the two products to interact they need to shell share.
This is the server piece of the CLM product (in which RTC is an application along with RQM and RRC). The server can run on various different platforms and the clients connect to it via a web browser or an eclipse IDE.
This is part of the RTC product that is installed on the platforms that code needs to be built on. In the case of mainframe development, it is installed on the zOS system.
This is the Eclipse based client that can be shell shared with the RTC Eclipse client. Obviously for the two products to interact they need to shell share.
RDz server side code:
This is code that must be installed onto the z/OS system so that the RDz client can talk to it. There are various parts to this such as the RSE (Remote System Explorer) that enables the RDz client to interact with the z/OS file system. There is also the Job Monitor that allows RDz to get notification on jobs running on the z/OS system. This enables a job to be submitted via the RDz Eclipse client and the Eclipse client being able to monitor the job and report back its status.
RTC/RDz Integration – What is it exactly?
The integration is achieved by first installing the two clients using shell sharing. Shell sharing means that they can coexist but there is no specific targeted integration yet between the two products. One can use the RTC functionality and the RDz functionality in the same client but there is no specialized integration going on. What is available from RTC 2.0 and onwards is some meaningful integration between the two clients. This is provided via an installable feature that is shipped with the RDz product. It is the ‘glue’ that allows the RDz Eclipse client and the RTC client to become aware of each other and work together.
With RDz 8.5, there is a change with the API that RTC uses to communicate with RDz (i.e. the API changed). Thus, there are two RTC/RDz Integration features shipped with RDz 8.5. One allows RTC 4.0 to talk with RDz 8.5 and the second one allows RTC 3.x to talk with RDz 8.5. Based on the version of the RTC client, pick the correct integration feature to install in your environment.
Now, what integrates with what exactly?
The only combination of clients that will NOT work is RTC 4.0 + RDz 8.0.3.x. Another way to say this is that RTC 4.0 pre-req’s RDz 8.5 if you want to use the integration feature. All other combinations work and have been tested either by RTC test team or by the RDz test team.
RDz Server side code (mainframe)
- The RSE shipped with RDz 8.0.3.x will work with RTC 3.x and 4.x
- The RSE shipped with RDz 8.5 will work with RTC 4.x
RTC server compatibility
There is N-1 client compatibility. Thus, an RTC 3.x client will work with an RTC 4.0 server and obviously a RTC 4.0 client will not work with a RTC 3.x server
We recommend the following combinations of client and build tool kit combinations when the server has been upgraded to RTC 4.0
- RDz 8.0.3.x client + RTC 3.x client would use RSE + build tool kit 3.x
- RDz 8.5 client + RTC 4.x client would use RSE + build tool kit 4.x
I’m upgrading my RTC environment(clients and server) to 4.0, what do I have to upgrade?
On the client side, you will need to upgrade the RDz clients from 8.0.3 to 8.5 and use the RTC/RDz integration feature provided shipped with RDz 8.5.
On the server side, specifically the RSE, the 4.0 RTC / RDz 8.5 client integration will work with the RDz 8.0.3.x RSE. Naturally, any server-side dependent features for 8.5 will not work, so the user is restricted to 8.0.3 functionality for anything that is related to server side function.
Additionally, on the server side, there may be build toolkits installed. Any 3.x RTC client should continue to use a 3.x build toolkit. Any 4.0 RTC client should use a 4.0 build tool kit.