Differences in Rational Developer for System z operations after sharing artifacts to Rational Team Concert for System z

When Rational® Developer for System z® resources are shared to Rational Team Concert™ for System z, or Rational Team Concert for System z resources are loaded into a Rational Developer for System z MVS™ subproject, a link is created between the data set member referenced in the MVS subproject and the corresponding zFile in the zComponent project. Rational Developer for System z automatically keeps the contents of the data set members and their corresponding zComponent files in sync. A change to either one will be reflected in the other.

When this link is established, Rational Developer for System z operations, such as rebuilding MVS subprojects and syntax checking, operate differently than they do prior to sharing artifacts to Rational Team Concert for System z.

Differences in rebuilding MVS subprojects

When an MVS subproject containing data set members shared to Rational Developer for System z is rebuilt using the Rebuild Subproject context menu option, the build processing is delegated to Rational Team Concert for System z. A build, as specified by the build context, is submitted to the Jazz™ Team Server for System z.

Important: Before you rebuild the MVS subproject, check in all local changes to your repository workspace. The build will run against the code in the repository workspace that is defined in the build definition. To check in your changes, switch to the Pending Changes view, select the child node of the component with your pending changes, right-click and choose Check-in all from the context menu.

When the build process is complete, the build results will be available in the Builds view in the Rational Team Concert for System z client. The Builds view is available from the work items perspective or from the Window menu. From the Window menu, select Show View -> Other -> Team Build -> Builds. You can monitor progress from the Builds view while the build is running.

Builds view

Differences in syntax checking

Remote syntax checking of data set members with associated zFiles operates differently than syntax checking of data set members without zFile associations. Rather than getting the parameters for the syntax check from Rational Developer for System z property groups, a syntax check of a shared data set member will obtain its properties from the language definition associated with the corresponding zFile. See About Rational Team Concert for System z language definitions. for detailed steps on how to create a language definition. In addition to the standard values that must be specified for language definitions and translators, syntax checking requires the designation of one translator as the syntax check translator that is used for compiling. Each translator you define for compiling should be used to check syntax.

To specify that a translator be used for syntax checking:
  1. From the Team Artifacts view, expand the Project Area node for your project area.
  2. Expand the Language Definitions node.
  3. Expend the Translators node, locate the translator you want to use for syntax checking and open it.
  4. Scroll down to the bottom of the translator editor and select the Use for Syntax Check.

Feedback