Build

The build functionality generates impacted components of one or more selected tasks at the same level in the life cycle. Additionally, the build functionality can generate impacted components of tasks at a selected level within a selected assignment or release container. If the impacted components do not exist at the selected level to build at, then the impacts will be loaded to that level. For example, if a build is run on a selected task that has 10 impacts, the selected task will be generated along with the 10 impacts to that task. When the build process completes, the view from which the build action was started view will include the additional 10 impacts. To see the impacted components before running a build, see to the .

To build impacted components

  1. Since the build may generate components, the compile diagnostics in the Problems view can assist with diagnosing the generate failures. To allow viewing of compile diagnostics, ensure that the compile will be processed using the Compuware Shared Services COBOL or PL/I Language Preprocessor and that Compuware Shared Services PTFs are current. The preprocessor step is explained in the Compuware Shared Services User/Reference Guide.
  2. Do one of the following:
    1. From a view that supports tasks (with the exception of the ISPW Set view), right-click one or more tasks and select Build.
    2. From the ISPWContainers view, right-click one assignment and select Build at Level and then select the level to build tasks on.
      A confirmation dialog box appears.

  3. Do one of the following:

    • To start the build process, click Yes.
    • To start the build process and not display this dialog box in the future, click Yes, Don't Ask Again.
    • To cancel the build process, click No.
  4. Look at the Console view to see information about the progress and results of the build.

  5. If there are any generate failures, after the build has completed see to the Problems view to view compile diagnostics. Then do the following:

    1. Do either of the following in the Problems view to open the source in an editor and position the cursor at the line of code that caused an error:
    2. Double-click the error or right-click it and select Go to.
    3. Right-click a problem marker and select Go to Source Listing.
      If not already opened, the source opens in the default editor, positioned to the selected problem.
    4. Make any necessary changes to the program and click save.gif or, from the File menu, select Save.
    5. From a view that displays tasks, perform the build action again.

    Note: Users can also show compile diagnostics from a view that displays tasks, by selecting the task or tasks and either clicking showcompilediagnostics.jpgor right-clicking and selecting Show Compile Diagnostics.

  6. If desired, in a view that displays tasks, right-click the task that was generated and select View Generate Listing to view the compiled source listing that the IBM compiler generated.
  7. If desired, from the Console view following a build failure, open the job output in an editor as follows:
    • To view the generate job output, click the job ID's hyperlin
    • For any build failures, view the output of a DD by clicking the link for the DD from the list of the JES job DD name hyperlink
  8. If desired, open the set within the Set view by clicking on the set ID's hyperlink, which will show the tasks that were processed, along with the set information such as the set log.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*