Skip to Content

Default language.

Report Definition Dialog

The WRPT system consists of four dialog-driven screens. These screens allow you to define the following:

  • Report Definition
  • Selection Criteria
  • Presentation Format, including the report columns, labels, and column sizes
  • Sort Options.

Changes you make using any phase of the Report Definition dialog are saved when all phases of the dialog have been completed. Press End to move on to the next phase of the dialog or Cancel to cancel all changes and exit. When all four phases of the dialog have been completed, a generated Batch Job ready to be edited and submitted is displayed.

If Component Type support is activated, reports can be saved and re-used when needed. For example, a Daily report could be created to report on all the Code Pipeline activity during the previous 24 hours, and this report could be saved in a production-level PDS. The Daily report could then be run as part of the regular daily housekeeping, or it could be run on demand by using the SU command alongside the Code Pipeline Task for a Task List or Work List.

Executing the Reporting Function Dialog

This section provides an example of how to execute the reporting function dialog and includes steps for specifying the following:

To execute the reporting function dialog, enter the command WRPT from any screen within Code Pipeline. The Code Pipeline Report Definition - General Specifications screen is displayed as shown in the following figure.

Code Pipeline Report Definition - General Specifications Screen

                 Report Definition - General Specifications               
Command ===>                                                                   
                                                                               
Confirm and/or Change the General Report Specifications.                       
                                                                               
  Report Type : TASK          (TASK,USER,HIST)                                 
  Group Code  :                                                                
  Destination : R             (E-Extract, C-Comma Separated, R-Standard)       
  Lines/Page  : 60                                                             
  Heading     : HEADING TEST                                                   
  Extract File: USER003.NEW.FILE2                                              
                                                                               
Press End to save and continue, or Cancel                                       

Input Fields

The following table describes the Input Fields on the Code Pipeline Report Definition- General Specifications panel:

Fields

Description

Report Type

There are three different report types TASK, USER, and HIST. Each of these report types will allow different types of data to be displayed.

  • TASK—Generates reports about active Code Pipeline tasks. This provides information similar to that provided by using the online WORK command.
  • USER—Generates reports from the M.U table reporting on users that are defined to Code Pipeline.
  • HIST— Generates reports from the Operations History table reporting on Code Pipeline operations like Promote and Delete.

Group Code

The Group Code of a specific group of components can optionally be entered to further refine a report.

Destination

The following are the three destinations:

  • E (Extract)—Specifying E extracts the report data into an extract file using null values as field delimiters.
  • C (Comma Separated)—Specifying C extracts the report data into an extract file using commas as field delimiters.
  • R (Standard)—Specifying R causes the report data to be generated and printed in the SYSUT2 DD from the JCL.

Lines/Page

The number of lines per page when the report Destination is set to R.

Heading

A heading that will be used while creating the report. This is only used when the report Destination is set to R.

Extract File

The destination extract file to be used when the report Destination is set to E or C.


 

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

BMC AMI DevX Code Pipeline 22.01