This topic lists and describes some useful Rational Team Concert™ for System z® terms, resources,
artifacts, and views, especially as they relate to Rational® Developer for System z.
Rational Team
Concert for System z is
a team collaboration tool that supports cross-platform development
and features native hosting of the Jazz™ Team
Server for System z on z/OS® and Linux® for System
z. Rational
Team Concert for System
z includes an integrated set of collaborative software delivery
lifecycle tools for System z development,
including source control, change management, and build and process
management.
Rational Team
Concert for System z extends
the features and functions of Rational Team Concert. To learn
more about Rational
Team Concert for System
z, see the Getting Started, Tutorial, and Glossary sections of
the product help or in the online information center at http://publib.boulder.ibm.com/infocenter/rtczhelp/v2r0m0/index.jsp.
You will find the following Rational Team Concert for System z terms used in the
help content for the integrated products:
- Data set definition
- A Jazz model object that
is stored in the Rational
Team Concert for System
z Jazz repository. It contains
all of the information related to a given data set on a z/OS system. Every data set that a build process
references must correspond to a data set definition.
- Data set prefix
- Rational Team
Concert for System z uses
a data set prefix, together with the data set name (indicated in the
data set definition), to identify the data set you want to allocate
to Rational Team
Concert for System z.
With your own prefix, you can modify Rational Team Concert for System z artifacts in isolation
from other contexts.
- Repository workspace
- A (source control) workspace that holds a developer's private
copy of the source file base.
- Sandbox
- An unstructured location on the file system to which you can extract
a source file base from a source control system.
- Translator
- Describes a single build step; namely, the step wherein a translator
executable program is invoked with the required inputs and outputs.
Inputs and outputs are the same as z/OS data sets, so a translator
definition must reference multiple data set definitions. For example,
a COBOL program that contains SQL statements and runs in a CICS environment
must go through several build steps. Depending on the COBOL compiler
version you use, these steps might include the following:
- DB2 precompile
- CICS precompile
- COBOL compile
- Link-edit
- DB2 bind
- Workspace
- A location on a file system with an Eclipse-oriented structure
that contains a collection of resources (files, folders, projects).
- zComponent
- A logical group of artifacts that share a common context; for
example, all of the artifacts in a zComponent might comprise part
of some application.
- zComponent Project
- A specialized Eclipse project that contains source or build artifacts
(such as build scripts or link-edit files), along with metadata that
describes how these artifacts should be organized and built when you
extract them to the z/OS file
system.
- zFile
- An Eclipse file that represents a member of an extended partitioned
data set (PDSE) on MVS™.
- zFolder
- An Eclipse folder that is associated with a PDSE on MVS. During a build, zFiles in a given zFolder
are extracted to the data set that is associated with that zFolder.