Rational Developer for System z

Mapping local files to remote resources

To be able to synchronize files in a local project to a remote system, you first need to map the local files to remote resources (MVS™ data sets or z/OS® UNIX System Services files).

Before you begin

Before you can map resources in a local project to resources on a remote system, you must allocate the remote data sets (on MVS) or create the files (on z/OS UNIX) to which the local files are to be mapped. Local files must map to a sequential data set (for example, HLQ.QUAL.SDSNAME), a partitioned data set member (for example, HLQ.QUAL(MEMNAME)), or a z/OS UNIX file (for example, /path1/path2/file.ext). See the related topics for information on allocating MVS data sets.

About this task

To map local files to remote resources, do these steps:

Procedure

  1. Double click the .RemoteMapping file in the project. This action opens the Pushable Manifest Editor. This editor displays two tree views:
    • On the left is the tree of resources in the local project.
    • On the right is the list of resources in the remote system to which the project has been connected.
  2. You can map local and remote resources manually or by browsing to find them.
    • To enter them manually, do these steps:
      1. Specify the name of the remote system in the Host field.
      2. Select either MVS or z/OS UNIX as the type for each resource you want to map.
      3. Enter the location (that is the MVS data set name, member name, or z/OS UNIX file name) of the remote resource.
    • To map resources by browsing for them, do these steps:
      1. Expand the tree on the right.
      2. Select the data set, member, or z/OS UNIX file you would like a local resource to map to.
      3. Find the local resource on the left.
      4. Click the <--- button. You may have to expand the left side of the view to see this button. Clicking the button sets the Resource Type (MVS or z/OS UNIX) and Remote location (remote data set, member , or file) and the Host (remote system).
  3. Save the .RemoteMapping file after making changes.

Results

If you have automatic build enabled you will see any errors in the file appear in the Problems view. If automatic build is not enabled you may invoke the build by choosing Project > Build Project from the menu bar. If the Problems view is not visible, you can open it by selecting Window > Show View > Problems. Clicking on any error in the Problems view will highlight the line that must be corrected in the Pushable Manifest Editor.
Note: Remember that you must build the project for the Problems view to update.

Feedback