Transporting Applications in Source Form › Using the Source Transport Utility › Setting Defaults › Source Transport Process

Source Transport Process

The Source Transport Utility operates in two phases:

1. Read and validate control statements.

   This phase enters the valid commands into a table for use in the second phase of execution. Generic version numbers (such as LAST and PROD) in the EXPORT commands are resolved to specific version numbers at this stage by looking up the entity occurrence in the dictionary. If two EXPORT commands refer to the same entity, as can happen when a generic version and an explicit version number are both used, only entry is made in the table. IMPORT commands are resolved in the second phase from the information in the external file.

2. Read or write the external source file.

   The second phase of operation begins when the OFF command is processed. If one is not present in the input stream, it is assumed at end‑of‑file.

   For an EXPORT run, the entities (programs, panels, members, and so on) are processed in the same order as the EXPORT commands were entered.

   For an IMPORT or PRODUCE run, the external source determines the order of processing. Each entity found on the source file is matched against the table built in the first phase to determine if it is to process. PRODUCE matches everything, but IMPORT operations can specify a particular version, system, or user. If the entity is processed, this is recorded in the table to avoid duplicate processing. Unmatched entities are counted for the final summary report.

The process affects both the reports, described later, and the trace facility, described next.