Skip to content

IDz Projects and Subprojects

You can link your personal development libraries on the z/OS mainframe to any desired IDz project. When you do this, ZMF for Eclipse permits integrated ZMF checkouts to and checkins from IDz projects. This lets you take advantage of the mainframe development tools of IDz while working with ZMF-managed software assets.

IDz projects and subprojects are defined in the z/OS Projects perspective and are displayed in the z/OS Projects navigation view. They are logical rather than physical collections of resources that organize a development project for work with the mainframe development and debugging tools of IDz. Projects and subprojects point to the physical resources that are displayed in the Remote Systems view.

Because IDz projects and subprojects are not physical containers for files, you must map these logical resources to physical libraries before you can perform physical operations on them. For example, if you want to check out a ZMF component into an IDz project, you must first link one or more physical containers to that project so the checkout operation can have a physical target for the component.

Important

You cannot check out a ZMF component directly into an IDz subproject. A project must be linked to a physical container, such as a PDS library or an zFS folder, so that checkout to a subproject can copy the checked out component into a library or folder to which the subproject is pointing.

IDz Project Structure

IDz projects consist of subprojects, which point to libraries, which contain files or members that serve as software components in your application.

  • MVS Subprojects contain native z/OS PDS libraries
  • z/OS Unix Subprojects contain z/OS Unix zFS folders and files.

IDz projects allow you to work with PDS and zFS files collectively. However, many operations — such as component build procedures — cannot be applied to these different file systems in the same way. For this reason, most work with IDz projects occurs at the subproject level. Libraries and files or members, for example, are linked to subprojects, not projects, and the file system of the resource must match the file system supported by the subproject type.

Personal development libraries on the z/OS server must be connected to an IDz project before you can work with them in IDz. Once this is set up, you can use ZMF for Eclipse to check out components from a ZMF baseline library into a personal development library and its associated IDz project at the same time.

PDS development libraries in the native z/OS file system must be linked to an IDz project through an MVS subproject. zFS development libraries in the z/OS Unix System Services (USS) file system must be linked to an IDz project through a z/OS Unix subproject.

Back to top