Target Environment and Construction Paths › How to Set Construction Paths

How to Set Construction Paths

To set the construction paths, start the Construction Client, open a model, and select Code, then Environment. Select a business system or Referential Integrity triggers from the displayed list and select Detail, then Paths. You can also access the construction paths from the generation and packaging windows. Use a naming convention that reflects the application when setting paths for the various generated components. For example, use the same source path for load module and RI trigger source, so that all source code is grouped in one location. Use the same remote installation path so that the load module and RI trigger remote files (.rmt files) are in a single location.

Use the following rules when setting paths:

• Only remote installation is available in this release. Be sure to set the remote installation path to provide a location for the remote files.
• If the Construction Client appends the user ID to a path name, it is the name used to log on to the client.
• You must set construction paths before you generate remote files. Not entering a generation path results in an error that stops generation processing.
• The paths reference locations on the server machine, so you must enter the paths using the appropriate naming conventions and restrictions for your server. Using the incorrect path type results in an error.

  Paths are checked on the server and errors are reported before the path names are saved.

  Construction paths are associated with business systems as part of the business system for a model.

• You can provide temporary overrides of construction paths from the Generation Defaults window. Overrides are stored locally (on the Client).
• z/OS construction library definitions are included when complete models are transferred between encyclopedias. (z/OS construction library definitions are not included in subsets transferred between encyclopedias.)
• Construction paths for the DDL and Referential Integrity triggers are specified separately. These objects apply to an entire model and do not belong to a particular business system.