Team Committing and Replacing Project Mainframe Resources

Users can perform the following tasks on offline Compuware mainframe project resources:

• Commit (copy back) PDS and sequential datasets to z/OS.
• Update PDS and sequential datasets with versions from the mainframe.
• Compare PDS and sequential datasets to and merge with the mainframe version.
• Create and delete PDS members.

Important: Team Synchronization requires mainframe PDS datasets to have stats turned on so that Host Explorer can determine whether members have changed upon synchronization.

Note: This functionality applies only to offline mainframe projects.

Committing local resources to the mainframe

Local resources can be either committed to the mainframe, which involves checking for conflicts before committing, or they can be committed without checking for conflicts using the override and commit operation.

When a local resource within a Compuware mainframe project differs from its z/OS counterpart, a greater than symbol ( >) appears in front of the resource name as it is listed in the Project Explorer.

To commit local resources to the mainframe

Committing replaces a mainframe resource with your local version.

1. After making changes to your local resource, synchronize. Changed resources show the  icon indicating that there is a local change to be committed to the mainframe.
2. In the Team Synchronizing perspective or the Synchronize view, right-click the resource(s) you want to commit and select Commit. This option is not available if there is a conflict between the cached and the mainframe versions of the resource. Following the commit, the resource is removed from the Synchronize view.

Note: Alternatively, resources can be committed from the Project Explorer view. In Project Explorer, right-click the resource(s) you want to commit and select Team > Override and Commit to z/OS. The local version is compared to the mainframe version before committing. If there is a conflict, an error message appears.

To override the mainframe resource with a local resource

The override and commit operation overrides the mainframe resource with the local version without checking for conflicts. Be very careful in your use of this operation. It is best to double-click the resource to compare your local file to the mainframe version first.

1. After making changes to your local resource, synchronize. Changed resources show the  icon indicating that there is a local change to be committed to the mainframe.
2. In the Team Synchronizing perspective or the Synchronize view, right-click the resource(s) you want to commit and select Override and Commit. Regardless of whether the mainframe version has been modified, it will be overwritten with your local version. The resource is removed from the Synchronize view.

Updating local resources from the mainframe

Local resources can be either updated with the mainframe version, which involves checking for conflicts before committing, or they can be updated without checking for conflicts using the override and update operation.

To update a local resource with the mainframe resource

Updating replaces your local resource with the mainframe version of that resource, overwriting any changes you made to the local version.

1. Synchronize. Mainframe resources that differ from your local version show the  icon indicating that there is an updated mainframe version of the resource.
2. In the Team Synchronizing perspective or the Synchronize view, right-click the resource(s) you want to update and select Update. This option is not available if there is a conflict between the cached and the mainframe versions of the resource. The resource is removed from the Synchronize view.

To override a local resource with a mainframe resource

The override and update operation overrides the local resource with the mainframe version without checking for conflicts.

1. Synchronize.
2. In the Team Synchronizing perspective or the Synchronize view, right-click the resource(s) you want to update and select Override and Update. A confirmation message asks you to confirm the operation. Click Yes and the resource is removed from the Synchronize view.

Addressing conflicts between local and resources

At times, both the local and mainframe versions of the same resource may have been modified, resulting in a conflict. If a conflict exists, it is important to compare the versions and merge changes as necessary into your local file. After doing so, Host Explorer allows you to mark the local file as merged to change it from a conflicting state to an outgoing state so you can commit it.

To mark as merged

1. Synchronize. If both the local and the mainframe versions of the resource have been modified, the  icon indicates that there is a conflict.

2. In the Team Synchronizing perspective or the Synchronize view, double-click the resource to open both versions in the Compare Editor. Merge any needed mainframe changes into your local file, making your local file the most accurate version. Save the local file.

   Warning

   Note

   Any time you compare mainframe and local versions of a resource in the Compare Editor, the Synchronize view opens a cached version of the file rather than making a mainframe call. Therefore you may be not comparing your local file against the most current mainframe version. Consider synchronizing first if you think that changes may have been made to the mainframe version. Alternatively, right-click the resource in Project Explorer and select Compare With > Latest from z/OS.

3. Right-click the resource and select Mark as Merged to indicate that you have compared the versions and merged them. Commit is not an available option until you have marked the resource as merged. Selecting Mark as Merged changes the resource to a committable state and the  icon appears, indicating that there is a local change to be committed to the mainframe.
4. Right-click the resource and select Commit to commit the file to the mainframe. The resource is removed from the Synchronize view.

Creating and deleting PDS members

To create a new PDS member

A new PDS member can be created either locally or on the mainframe.

Create a new PDS member on the mainframe as follows:

1. In Host Explorer, right-click a PDS dataset and select New Member. The New Member dialog box appears.
2. Enter a member name and click OK. The new member opens in the editor and appears in Host Explorer view. Edit the file as needed and save it.
3. Synchronize. The Synchronize view shows the  icon to indicate that a new mainframe file exists in a dataset you have copied locally.
4. Right-click in Synchronize view and select Update to copy the file locally.

Create a new PDS member locally as follows:

1. Right-click in Project Explorer and select New > PDS Member File in a Compuware Mainframe Project, then click Next. The New PDS Member File dialog box appears.
2. Expand the target project and select the parent dataset folder and enter a member name.
3. Click Finish. A new, empty member file is created locally and appears in the editor. Once you have synchronized, the Team Synchronizing perspective or the Synchronize view shows the  icon to indicate that there is a new file that needs to be committed to the mainframe.
4. Right-click and select Commit to commit the file to the mainframe.

To delete a PDS member from the mainframe

PDS members can be deleted locally or from the mainframe.

Delete a PDS member from the mainframe as follows:

1. In Host Explorer, right-click the PDS member and select Delete. The Delete dialog box appears. click Delete. A message indicates the results of the delete operation.
2. Click Done.
3. Synchronize. If this file existed locally, the Synchronize view shows the  icon to indicate the deletion of the file from the mainframe.
4. In the Team Synchronizing perspective or the Synchronize view, right-click the PDS member and select any of the following:

• 
  
  • Update: Deletes the local version of the file.
• 
  
  • Override and Commit: Overrides the deletion of the mainframe file, keeps the file locally, and commits it to the mainframe as a new member.
• 
  
  • Override and Update: Deletes the local version of the file.

Delete a PDS member from the local project as follows:

• Right-click the PDS member in Project Explorer and select Delete.

Synchronizing mainframe and local resources

Because other users may have edited the mainframe version of a resource after you copied it locally, it is vital that you compare your local version to the mainframe version before committing your changes to z/OS. If you don't, you may overwrite another user's changes. Host Explorer's synchronization functionality determines whether any changes have been made to either the mainframe or the local version of a resource. It is good practice to sync before committing resources so that resources are not inadvertently overridden.

The following icons are used in the Team Synchronizing perspective and the Synchronize view:

 Indicates that a local resource has been modified.

 Indicates that the mainframe resource has been modified since you downloaded it.

 Indicates that there is a conflict between the local and mainframe versions of a resource as both have changed.

 Indicates that there is a new local PDS member that needs to be committed to the mainframe.

 Indicates that a new PDS member exists on the mainframe in a dataset you have copied locally.

 Indicates that a PDS member has been deleted from the mainframe.

To synchronize mainframe and local resources

To take any of the actions outlined in the sections above, first open the Team Synchronize perspective or the Synchronize view.

1. Ensure that mainframe PDS datasets have stats turned on so that Host Explorer can determine whether members have changed.
2. From the Window menu, do either of the following:
   • 
     
     • Select Open Perspective > Other > Team Synchronizing and click OK. The Team Synchronize perspective appears.
   • 
     
     • Select Show View > Other > Team > Synchronize and click OK. The Synchronize view appears.
3. In the Team Synchronizing perspective or the Synchronize view, click . The first time you click this button, the Synchronize dialog box appears.
4. Select Synchronize with z/OS, then click Next.
5. On the subsequent dialog box, expand the workspace and select the project(s) to synchronize against, then click Finish. The Synchronize view populates with the datasets and/or members that have changed since you downloaded them from the mainframe.

Note: To synchronize selected resources rather than an entire project or workspace, right-click the resource(s) and select Team > Synchronize with z/OS.

Other available operations

• To replace a Compuware mainframe project resource with the version just prior to the current version, right-click the resource in Project Explorer and select Replace with>Previous from Local History.
• To replace a Compuware mainframe project resource with a historical version, right-click the resource in Project Explorer and select Replace with > Local History. Then select the previous version date from the list and click Replace.