Endevor
Reports

ce18
Endevor
reports are written in assembler language, which provides some flexibility when generating the reports. For example, you can select a subset of reports to be produced for a specific environment, system, subsystem, and stage.
2
When only one item exists in the group to be summarized,
Endevor
reports do not produce summary lines. Therefore, some reports that you generate can look different from those included as examples in this article.
To run these reports, during installation tailor the report JCL for use at your site.
Endevor
Reports
Several categories exist for
Endevor
reports:
  • Master Control File reports
  • Historical reports
  • Package reports
  • Footprint reports
  • Unload/Reload reports
  • Shipment reports
  • Archive reports
Master Control File Reports
These reports contain summary and detail information about the system, subsystem, type, and element definitions specified to the
Endevor
Master Control File.
  • CONRPT01
    System Inventory Profile
  • CONRPT02
    System Inventory Summary
  • CONRPT03
    Element Catalog
  • CONRPT04
    Element Activity Profile
  • CONRPT05
    Element Activity Summary
  • CONRPT06
    Element Catalog by CCID
  • CONRPT07
    System Definition Profile
  • CONRPT08
    Element Signed Out Profile - by System
  • CONRPT09
    Element Signed Out Profile - by User
  • CONRPT10
    Approver Group Definition
  • CONRPT11
    Approver Group Usage
  • CONRPT12
    Element Catalog by Retrieve CCID
Historical Reports
These reports summarize security violations and element activity recorded by
Endevor
. These reports are available if SMF logging is in use at your site. These reports are generated using the SMF records written during
Endevor
processing.
  • CONRPT40
    Security Violation Summary
  • CONRPT41
    Security Violation Profile
  • CONRPT42
    Element Activity Profile
  • CONRPT43
    Element Activity Summary
Package Reports
These reports provide detail and summary information about the status of all packages within a specified library.
  • CONRPT70
    Package Summary Report
  • CONRPT71
    Package Approver Report
  • CONRPT72
    Package Detail Report
Footprint Reports
These reports document footprint information placed in source and load modules by
Endevor
.
  • CONRPT80
    Library Member Footprint Report
  • CONRPT81
    Library CSECT Listing
  • CONRPT82
    Library ZAPped CSECT Profile
  • CONRPT83
    Footprint Exception Report
Package reports and Footprint reports are mutually exclusive. If you need both report types, submit two separate jobs or two separate jobsteps in the same job.
Unload and Reload Reports
These reports contain detail and summary information about system unload activity.
  • CONRPT50
    System Inventory Profile
  • CONRPT51
    Unload System Definition Profile
  • CONRPT52
    Unload Approver Group Definition
  • CONRPT53
    Unload Approver Group Usage
  • CONRPT54
    Element Catalog
  • CONRPT55
    Unload Package Summary Report
Shipment Reports
These reports contain package shipment and destination information.
  • CONRPT73
    Destination Detail Report
  • CONRPT74
    Package Shipment Report by Package ID
  • CONRPT75
    Package Shipment Report by Destination
  • CONRPT76
    Package Shipment Report by Shipments
Archived Package Reports
These reports provide detail and summary information for packages that are archived. These reports include:
  • CONRPT56
    Archived Package Summary
  • CONRPT57
    Archived Package Approver Report
  • CONRPT58
    Archived Package Detail Report
Requesting
Endevor
Reports
To generate
Endevor
reports, execute the BC1JRPTS job. To specify a report or set of reports, edit the appropriate DD statements in the JCL. Supply a correct job card and check all DD statements before running the job. Also, check the following DD statements, as noted in the JCL:
  • BSTINP
  • BSTPDS
  • BSTIPT
  • SMFDATA
The C1BR1000 program does not have to be called by an authorized program. However, users executing the unauthorized program must have the requisite security access to the
Endevor
data sets for the function requested. The caller security profile must have sufficient
Top Secret
,
ACF2
, or RACF access to the
Endevor
control files (catalog, master, package, base, delta), because the
Endevor
alternate ID facility is not available when running in an unauthorized mode.
To call the batch reporting program from a non-authorized program, specify:
EXEC PGM=C1BR1000
Generate Reports
The BC1JRPTS job stream contains a BSTINP DD statement used to pass report selection criteria to the report program. Before running this job, supply appropriate BSTINP input, specifying the statements that you want from the following tables.
Additional JCL statements may be used to specify selection criteria. For example, the Footprint Reports specifies an additional data set using a BSTIPT DD statement.
This tables list each BSTINP keyword and the reports to which it applies. When you run the reports, any keywords that do not apply for a given report are ignored. For additional keywords that apply when requesting:
  • Package Reports (CONRPT70-72), see Specifying Package Reports.
  • Archived Package Reports (CONRPT56-58), see Specifying Archived Package Reports.
  • Shipment Reports (CONRPT73-76), see Specifying Shipment Reports.
BSTINP Keywords for MCF and Historical Reports
Keyword
01
02
03
04
05
06
07
08
REPORT
x
x
x
x
x
x
x
x
ENVIRONMENT
x
x
x
x
x
x
x
x
SYSTEM
x
x
x
x
x
x
x
x
SUBSYSTEM
x
x
x
x
x
x
x
ELEMENT
x
x
x
x
x
x
x
TYPE
x
x
x
x
x
x
x
x
STAGE
x
x
x
x
x
x
x
x
DAYS
x
x
SEARCH MAP
x
x
x
x
x
x
x
x
PACKAGE ID
Keyword
09
10
11
12
40
41
42
43
REPORT
x
x
x
x
x
x
x
x
ENVIRONMENT
x
x
x
x
x
x
x
x
SYSTEM
x
x
x
x
x
x
SUBSYSTEM
x
x
x
x
x
x
ELEMENT
x
x
x
x
x
x
TYPE
x
x
x
x
x
x
STAGE
x
x
x
x
x
x
DAYS
x
x
x
x
x
SEARCH MAP
x
x
x
x
x
x
x
x
PACKAGE ID
BSTINP Keywords for Unload, Archived Package, Package, and Footprint Reports
Keyword
50
51
52
53
54
55
56
57
REPORT
x
x
x
x
x
x
x
x
ENVIRONMENT
x
x
x
x
x
SYSTEM
x
x
x
x
x
x
SUBSYSTEM
x
x
x
x
x
x
ELEMENT
x
x
x
x
x
x
TYPE
x
x
x
x
x
x
STAGE
x
x
x
x
x
x
DAYS
x
x
SEARCH MAP
x
x
x
x
x
x
PACKAGE ID
x
x
x
DESTINATION ID
CONNECTION ID
PRODUCT
Keyword
58
70
71
72
73
74
75
REPORT
x
x
x
x
x
x
x
ENVIRONMENT
x
x
x
SYSTEM
SUBSYSTEM
ELEMENT
TYPE
STAGE
DAYS
SEARCH MAP
PACKAGE ID
x
x
x
x
x
x
x
DESTINATION ID
x
x
x
CONNECTION ID
PRODUCT
Keyword
76
80
81
82
83
REPORT
x
x
x
x
x
ENVIRONMENT
x
x
SYSTEM
SUBSYSTEM
ELEMENT
TYPE
STAGE
x
DAYS
SEARCH MAP
PACKAGE ID
x
DESTINATION ID
x
CONNECTION ID
PRODUCT
BSTINP Syntax
BSTINP selection statement syntax is shown next. With the exception of ENVIRONMENT, which is required for most reports, all statements are optional and default to ALL.
The statements are freeform. The statements can be coded anywhere between columns 1 and 72 of the input card-image line. Multiple statements can be coded on a line. A single statement can span multiple lines. Each keyword or name must be completely contained on a single line.
Masking can be used with the following parameters: ENV, SYS, SUB, ELE, TYP, and STA. For environment names, name masking is only valid for historical reports.
The syntax is as follows:
REPort {
nn
} ... .
  • REPort {
    nn
    } .
    .. .
    Specifies the reports that you want.
    nn
    is the two digits of the report ID, and can be repeated up to 21 times. Separate multiple report numbers by one or more spaces.
    Example: REPort {nn} syntax
    REPORT 04 05 83.
    If no REPORT command is entered, all reports, except for Package reports, are produced.
    Remember the Package reports and Footprint reports are mutually exclusive. If you want both report types, submit two separate jobs (or two separate jobsteps in the same job).
  • ENVironment
    environment-name
    .
    Identifies the single environment for which the reports are produced. This command is required for all reports except 55 through 58, 70 through 76, and 80 through 82.
  • SYStem
    system-name.
    Limits the report to information for the systems indicated by system-name, which can be a complete or generic name. For example:
  • SYSTEM ACCTGL
    Selects the single system named ACCTGL.
  • SYSTEM ACCT*
    Selects all systems beginning with the characters ACCT.
    If a SYSTEM statement is omitted, all systems are selected.
  • SUBsystem
    subsystem-name.
    Limits the report to information for the subsystems indicated by subsystem-name. If omitted, all subsystems are selected.
  • ELEment
    element-name.
    Limits the report to information for the elements indicated by element-name. If omitted, all elements are selected.
  • TYPe
    type-name.
    Limits the report to information for the element types indicated by type-name. If omitted, all types are included.
  • STAge
    stage-id.
    Limits the report to information for the stages indicated by stage-id. If omitted, both stages are included.
  • DAYs
    n
    .
    Limits the report to the activity recorded during the last n days.
    Default
    : Activity recorded during the last seven days.
  • SEArch ENVIRONMENT MAP.
    Tells
    Endevor
    to search the map, beginning at the specified stage, when producing the report.
  • PACkage
    id package-id
    .
    Limits the report to the packages with the specified IDs.
  • DEStination i
    d destination-id
    .
    Limits the report to the destinations with the specified IDs.
  • CONnection
    id connection-id
    .
    Limits the report information to the connections with the specified IDs.
Input Command Summary
When you run a report job, the first page of output is an Input Command Summary. This summary lists each BSTINP DD statement input to the job, and then lists the values used for each selection statement. If your BSTINP selection statements contain syntax errors, these are listed in this report and the run is terminated.
If you select any of the Footprint reports (80-83), a separate one-page listing summarizes the statements input following the BSTIPT DD statement.
Report Extract Phase Summary
Following the Input Command Summary, the reporting program produces an Extract Phase Summary, which lists the total number of items extracted for each selected report. Additionally, the report lists the sort control parameters used to invoke the sort program, and the completion code returned by the sort. This value should always be 0000.
Name Masking
To help you more easily find information and process requests, you can use name masking. By substituting a name with the asterisk wildcard character (*), a character with the percent sign placeholder (%), or by using both together, it is much faster and easier to find information and process requests.
SCL Statement Syntax Rules
Endevor
uses IBM standards for representing syntax.
Special rules apply when manually coding long-named Elements in a report request. If a batch report request was not produced using the foreground panels and a long-named Element is coded for input, the following syntax rules apply:
  • The code can be in columns 1 through 72. Columns 73 through 80 are ignored.
  • Beginning and ending quotes are required on each line.
  • Where an Element name continues onto the next line, a comma must follow the ending quote to indicate that the name continues on the next line.
  • The last continuation line requires a period to indicate the end of the element name.
For more information about how to specify long-named Elements and examples, see Rules for Coding Blanks in Element, USS File and Path Names in Rules for Coding Syntax.