Differences in IBM Developer for z/OS operations after sharing artifacts to Engineering Workflow Management

Some functions perform differently after you share resources from IBM® Developer for z/OS artifacts to IBM Engineering Workflow Management (EWM).

When IBM Developer for z/OS resources are shared to Engineering Workflow Management, or Engineering Workflow Management resources are loaded into an IBM Developer for z/OS MVS™ subproject, a link is created between the data set member in the MVS subproject and the corresponding zFile in the zComponent project. IBM Developer for z/OS automatically keeps the contents of the data set members and their corresponding zComponent files in sync. A change to either one is reflected in the other.

When the link between the data set member in the MVS subproject and the corresponding zFile in the zComponent project is established, IBM Developer for z/OS operations, such as rebuilding MVS subprojects and syntax checking, operate differently than they do before sharing artifacts to Engineering Workflow Management.

Differences in rebuilding MVS subprojects

When an MVS subproject containing data set members shared to IBM Developer for z/OS is rebuilt using the Rebuild Subproject menu option, the build processing is delegated to Engineering Workflow Management. A build, as specified by the build context, is submitted to the Jazz® Team Server for System z®. Before you rebuild the MVS subproject, check in all local changes to your repository workspace. The build is a personal build that runs using the code in your repository workspace.

When the build process is finished, the build results are available in the Builds view in the Engineering Workflow Management 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 IBM Developer for z/OS property groups, a syntax check of a shared data set member obtains its properties from the language definition associated with the corresponding zFile. See z/OS® 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. Use the translators you define for compiling to check syntax.

To use a translator 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 to the end of the translator editor and select the Use for Syntax Check.

Differences in editing PDS members

When you create a member of a PDS in ISPF in MVS, and set the data set profile option PACK ON to use direct access storage devices (DASD) more efficiently, and attempt to edit the members of the data set in Engineering Workflow Management, the members are not readable because of the packed format. There is no way to unpack and expand the data using the editors in Engineering Workflow Management or in IBM Developer for z/OS. Unpacking must be done before you attempt to edit the members. For more information about using PACK ON, see the ISPF User's Guide.