Loading artifacts to Rational Developer for System z

Loading artifacts to Rational® Developer for System z® involves loading your Rational Team Concert™ for System z repository workspace into an Eclipse workspace. If you have not already, you must create and share a zComponent project before you complete the steps below. You can create a sample zComponent project by completing the steps in the tutorial, Using the Rational Build Agent and Antz build extensions to compile a COBOL application.
Note: During the load, artifacts will be reloaded into the local eclipse workspace. If you have local changes that have not been checked in, they could be overwritten.

Complete the following steps to load artifacts from Rational Team Concert for System z to Rational Developer for System z. (These steps use examples from the tutorial as illustrations.)

  1. From the Team Artifacts view, right-click a repository workspace or a component in a repository workspace and select Load zFiles to z/OS.
  2. For this example, expand the AntzBuildScenario component subdirectories until the Hello.cbl node is visible and select Hello.cbl.
    Load zFiles to z/OS panel with Hello.cbl selected
  3. Click Next.
  4. Select the MVS™ subproject you want to load the Hello.cbl program into. (For this example we selected mvssub.)
    "Select an MVS Subproject" panel
  5. Click Next.
  6. On the Specify Build Context panel, click Browse, select the build definition listed and click OK.
    "Select build definition" panel

    The Load zFiles to z/OS wizard obtains the data set prefix from the build definition if it is specified and adds that prefix to each data set member that is created on the host and loaded into the subproject. A data set prefix must be defined in the build definition before you can continue. By default, the repository workspace that is specified in the build definition will be used. If you want to use your own repository workspace, you must choose it explicitly in the build context selection page.

  7. A build definition typically specifies the prefix that the team build uses. To make sure that you can work on your artifacts in isolation, change the prefix that is specified in the build definition to your own prefix. To modify the prefix, select teamz.scm.dataset.prefix from the Build Properties list and click Edit.
  8. On the Select Property Type panel, select String from the list of new property types and click OK.
    "Select Property Type panel" showing list of options for type of new property
  9. On the Edit Build Request Property panel change the value from MASAO.BLD to your prefix and click OK. (For this example, we changed the value to BGREEN.BLD.)
    "Edit Build Request" panel showing value changed to BGREEN.BLD
    Important: Make sure that the credentials you used to make the RSE connection to the host have the authority to create and modify a data set with the prefix you set in the value field.
  10. Click Next to view the summary page.
  11. On the summary page verify that your zFile is being loaded to the proper location on MVS and then click Finish.

Verifying that the load was successful

Confirm that the Hello.cbl program appears in the Remote Systems view in the expected location.
Remote Systems view showing Hello.cbl in My Data Sets

Next, from the z/OS Projects view, confirm that the Hello.cbl program is contained in the MVS subproject.

z/OS Projects perspective showing Hello.cbl in the MVS subproject

Edit the COBOL file from the MVS subproject in the z/OS Projects perspective and save the change. The remote member and local zFile will be in sync. You can open the same COBOL file from the zComponent project to verify that your saved change appears there.

If the Load zFiles to z/OS wizard ends in error, open the .log file in the .metadata folder in your Eclipse workspace for additional information.