Rational® Developer for System z® has built-in tools
and functions that locate program dependencies on the MVS™ file system by using the specified SYSLIB
as the search path. Some of the tools that use SYSLIB as the search
path include project build, remote syntax check, content assist, show
dependencies, and open copy member. When you store your source files
in the Rational Team Concert™ for System
z source control repository, you can choose to extract a subset
of the source file base into the file system location specified by
your data set prefix on z/OS® (your z/OS sandbox). However, if your
programs depend on members that Rational Developer
for System z searches for
using SYSLIB as the search path, those members will not be found unless
you manage the dependencies manually.
The simplest method for managing dependencies is to make sure that
all of your dependencies are always loaded into your z/OS sandbox by organizing the common artifacts
(copy members) that your programs depend on into a set of common zComponent
projects. To manage dependencies using this method, complete the following
tasks:
- 1. Create a z/OS project
with two (or more) MVS subprojects
- Use one subproject as your working set subproject that will contain
the programs you are modifying. Use the second subproject as your
dependency management subproject to contain the common members on
which your programs depend.
- 2. Load files to the working set subproject
- Use the Load zFiles to z/OS wizard to load
the members you intend to modify (for example, programs) to the working
set subproject. See Loading artifacts to Rational Developer for System z.
- 3. Load files to the dependency management subproject
- Use the Load zFiles to z/OS wizard a second
time to load the copy members or include files on which your programs
depend to the dependency management subproject. After the files are
loaded, any incoming changes from the source control repository to
any common member will appear in the Pending Changes view.
If you accept the changes, they will appear in your dependency management
subproject and the corresponding members will appear in your z/OS sandbox.