Loading artifacts to Rational® Developer
for System z® involves loading
your Rational Team Concert™ repository workspace into an Eclipse workspace. If you
have not already, you must create and share a zComponent project before
you follow the steps for loading artifacts. You can create a sample
zComponent project by following the steps in the tutorial,
../../com.ibm.team.concert.tutorial.doc/topics/tut_rtcz_scen6.html.
Important: During
the load, artifacts are reloaded into the local Eclipse workspace.
If you have local changes that have not been checked in, they might
be overwritten.
Complete these steps to load artifacts from Rational Team Concert to Rational Developer for System z.
- From the Team Artifacts view, right-click
a repository workspace or a component in a repository workspace and
select Load zFiles to z/OS.
Note: You can also start
the Load zFiles to z/OS wizard if you right-click
an MVS™ subproject in the z/OS
Projects view and select or if you
right-click a zComponent project in the Project Explorer view
and select .
- In the Load zFiles to z/OS wizard, expand
the zComponent projects, select the files (called "zFiles") you want
to load, and click Next.
- Select the MVS subproject
to which you want to load your files and click Next.
- If no build context is established, click Browse to select
a build definition. If a build context has already been established
for the repository workspace, the build definition and build properties
will automatically be listed in the Specify build context panel.
Click Next.
- Verify the z/OS® member
names and click Finish.
Attention: The first time you add a zFile to a remote Rational Developer for System z project, the following
three properties are automatically set:
- local.codepage
- remote.codepage
- transfer.mode
The setting of the properties results in an outgoing change set
being added to your Pending Changes view. This is normal. The next
time you add the same zFile to a Rational Developer
for System z project, these
properties will not change.
Working in a personal workspace
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 is used. If you want to use your own repository
workspace, you must specify it explicitly in the build context selection
page.
A build definition typically specifies the prefix that
the team build uses. To work on your artifacts in isolation, change
the prefix that is specified in the build definition to your own prefix.
To modify the prefix, complete the following steps:
- On the properties tab in the Build Definition editor,
select the teamz.scm.dataset.prefix property
from the Build Properties list and click Edit.
- On the Edit Build Request Property panel,
change the Value field to your prefix and click OK.
(For this example, we changed the value 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.
- Click Next to view the summary page.
- On the summary page, verify that your zFile is loading to the
specified location on MVS and
then click Finish.
Verifying that the load was successful
Confirm
that your files are in the
Remote Systems view in
the expected location.
Next,
from the z/OS Projects view, confirm that the
files are contained in the MVS subproject.
As
a test, edit a file from the MVS subproject
in the z/OS Projects perspective
and save the change. The remote member and local zFile should be in
sync. You can open the same file from the zComponent project to verify
that your saved change appears there.
Tip: If the Load
zFiles to z/OS wizard ends in error, open the error log
view by selecting and selecting for additional information.