Rational Developer for System z

Creating a subproject definition file

Subproject definition files define the set of resources required to build a single load module and are located in the root project definition folder or one of its subfolders.
Subproject definition files must be encoded in UTF-8 and have an extension of *.hbpsd. They are XML files containing the following tags:
<SUBPROJECT-STRUCTURE>
  <WSED-VERSION>7.0.0.0</WSED-VERSION>
  <SUBPROJECT>
    <SUBPROJECT-NAME>mySubproject</SUBPROJECT-NAME>
    <SUBPROJECT-NATURE-LIST>
      <SUBPROJECT-NATURE>com.ibm.ftt.projects.zos.zosnature</SUBPROJECT-NATURE>
    </SUBPROJECT-NATURE-LIST>
    <SUBPROJECT-PROPERTIES-LOCATION>pathName</SUBPROJECT-PROPERTIES-LOCATION>
    <SUBPROJECT-TYPE>zos-subproject</SUBPROJECT-TYPE>
    <FOLDER-LIST>
      <FOLDER>
        <FOLDER-NAME>hlq.name.type</FOLDER-NAME>
        <FOLDER-TYPE>pds</FOLDER-TYPE>
        <FOLDER-STATE>
          <STATE-IS-OFFLINE>false</STATE-IS-OFFLINE>
          <PHYSICAL-FOLDER>
           <FOLDER-NAME>hlq.name.type</FOLDER-NAME>
            <FOLDER-PHYSICAL-PATH>hlq.name.type</FOLDER-PHYSICAL-PATH>
            <FOLDER-TYPE>pds</FOLDER-TYPE>
          </PHYSICAL-FOLDER>
        </FOLDER-STATE>
      </FOLDER>
    </FOLDER-LIST>
    <FILE-LIST>
      <FILE>
        <FILE-NAME>name.ext</FILE-NAME>
        <FILE-EXTENSION>ext</FILE-EXTENSION>
        <FILE-NAME-NO-ENTENSION>name</FILE-NAME-NO-EXTENSION>
        <FILE-TYPE>pds | sequential</FILE-TYPE>
        <FILE-STATE>
          <STATE-IS-OFFLINE>false</STATE-IS-OFFLINE>
          <PHYSICAL-FILE>
            <FILE-NAME>name</FILE-NAME>
            <FILE-PHYSICAL-PATH>hlq.name.type/name.ext</FILE-PHYSICAL-PATH>
            <FILE-TYPE>pds-member | sequential</FILE-TYPE>
          </PHYSICAL-FILE>
        </FILE-STATE>
      </FILE>
    </FILE-LIST>
  </SUBPROJECT>
</SUBPROJECT-STRUCTURE>
The subproject definition file contains three kinds of tags:
Note: The following list defines tags for which you need to set specific required or optional values. For a complete description of the subproject definition tags, see the subproject definition schema under Related References.
<WSED-VERSION>
The version of the schema syntax. This tag is required and must be 7.0.0.0 as shown.
<SUBPROJECT-NAME>
Is required and specifies the name of the subproject, such as MYSUB.
<SUBPROJECT-NATURE>
Is required and must be com.ibm.ftt.projects.zos.zosnature, as shown.
<SUBPROJECT-PROPERTIES-LOCATION>
Is optional and points to the subproject properties definition file for this subproject. Specify a path name relative to the PROJECT-HOME directory. If this tag is included, the properties file it refers to overrides the default properties defined for the system connection. If this tag is omitted, the default properties for the system are used. Default system properties are set by selecting the MVS™ Files node for a system in the Remote Systems view and clicking Properties from the pop-up menu.
<SUBPROJECT-TYPE>
Is required and must be zos-subproject, as shown.
<FOLDER-LIST>
Contains one or more <FOLDER> tags, which define partitioned data sets in the subproject:
<FOLDER-NAME>
Is required and must specify the fully qualified name of a partitioned data set on the remote system, such as LONGWEL.COBOL.SOURCE.
Note: For any file name in the subproject definition file, you can specify the substitution variable <;HLQ> for the high-level qualifier. This variable is replaced by the user's user ID at connect time. By using the <HLQ> substitution variable in a subproject's file references, a single subproject can contain a different set of files according to which project instance file refers to its parent project. See the figure at the end of this topic for an example of how to use this substitution variable in a subproject definition file.
<FOLDER-TYPE>
Is required and must be pds, as shown.
<FOLDER-STATE>
<STATE-IS-OFFLINE>
Is required and must be false, as shown.
<PHYSICAL-FOLDER>
<FOLDER-NAME>
Is required and specifies the fully qualified name of the partitioned data set on the remote system, such as LONGWEL.COBOL.SOURCE.
<FOLDER-PHYSICAL-PATH>
Is required and specifies the fully qualified name of the partitioned data set on the remote system, such as LONGWEL.COBOL.SOURCE.
<FOLDER-TYPE>
Is required and must be pds, as shown.
<FILE-LIST>
Contains one or more <FILE> tags, which define partitioned data set members or sequential data sets in the subproject:
<FILE-NAME>
Is required and specifies the fully qualified name of the file resource on the remote system, including the mapped extension, such as A.B.COBOL/HELLO.cbl for a partitioned data set member on MVS where A.B.COBOL is the partitioned data set name and HELLO is the member name.
<FILE-EXTENSION>
Is required and specifies the extension defined by the file system mapping. **COBOL data sets, for example, have a .cbl extension.
<FILE-NAME-NO-EXTENSION>
Is required and specifies the fully qualified file name without the extension, such as HELLO.
<FILE-TYPE>
Is required and must be either pds-member or sequential, as shown.
<FILE-STATE>
<STATE-IS-OFFLINE>
Is required and must be false, as shown.
<PHYSICAL-FILE>
<FILE-NAME>
Is required and specifies the file name, such as MYPGM.cbl.
<FILE-PHYSICAL-PATH>
Is required and specifies the fully qualified file path, such as LONGWEL.TEST.COBOL/MYPGM.cbl.
<FILE-TYPE>
Is required and must be either pds-member or sequential, as shown.
The following figure illustrates how to set up a subproject definition file:

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)