INFORMATION

The syntax for this command is as follows:

INFORMATION

Use this command to display an overview of the Developer to MCP generate process.

Processing:

  1. The Developer Builder creates the C85 sources files, Algol stubs, DMS source, MULTILANGS,LINCCNTL,LINCGLI, etc and transfers them via FTP to the host after logging onto the MCP Application Builder and selecting the system for generate.

  2. Developer Builder instructs the Application Builder to start the generate after all files have been transferred.

  3. The MCP Application Builder attempts to allocate a generate worker for the generate process. If insufficient workers are available or this is a scheduled generate, then the request is held in the internal generate queue.

    The MCP Application Builder then:

    • Verifies that all uploaded files are present, checks against ../FILEINFO directory file.

    • Commences generate process by creating the new linccntl, lincgli, lincform, and the multilangs files. ROC info is merged if these options are set for the generate.

    • Uses a CPA file to maintain its system and report state information. This is 'saved' at various stages of the generate process to provide restart points in the event of system or generate failure (CPA = checkpointarray).

    • Processes a BLD task to perform the compiles & binds.

    • BLD also uses a CPA file to maintain critical information about each system it compiles.

      MAKE: 1-n tasks based on the number of parallel generates settings:

      • Creates Ispec and segment method Algol Stubs (shells for C85 codefiles)

      • Creates GSD program and Algol Stub

      • Creates Bind Stream compile decks for C85 and compile decks for Algol stubs

      • Runs C85 and Algol compiles

      • Allocates codefiles to code libraries based on 'best' fit for size and number

      • Creates Bind decks for each code library

      • Runs Binder to create code libraries

  4. <system>/GEN: WFL generate process now commences, starting with the DAC process.

  5. Developer Builder allows certain ODT style commands to be sent to Application Builder who then uses DCKEYIN to process the requests. Developer Builder only enables these commands to be sent when the generate (report or system) is in a waiting state at which time the Send Server Command option within File is enabled. The commands that are supported are any AX, DS etc to a waiting task or a CLOSE <window name> or CLOSEDB <database name>.