AldonRM UserGuide V18

Rocket Report Manager
User Guide
Version 1.8
January 2017
RM-18-UG-02
Notices
Edition
Publication date: January 2017
Book number: RM-18-UG-02
Product version: Version 1.8
Copyright
© Rocket Software, Inc. or its affiliates 2008-2017. All Rights Reserved.
Trademarks
Rocket is a registered trademark of Rocket Software, Inc. For a list of Rocket registered trademarks go
to: www.rocketsoftware.com/about/legal. All other products or services mentioned in this document
may be covered by the trademarks, service marks, or product names of their respective owners.
Examples
This information might contain examples of data and reports. The examples include the names of
individuals, companies, brands, and products. All of these names are fictitious and any similarity to
the names and addresses used by an actual business enterprise is entirely coincidental.
License agreement
This software and the associated documentation are proprietary and confidential to Rocket Software,
Inc. or its affiliates, are furnished under license, and may be used and copied only in accordance with
the terms of such license.
Note: This product may contain encryption technology. Many countries prohibit or restrict the
use, import, or export of encryption technologies, and current use, import, and export regulations
should be followed when exporting this product.
2
Corporate information
Rocket Software, Inc. develops enterprise infrastructure products in four key areas: storage, networks,
and compliance; database servers and tools; business information and analytics; and application
development, integration, and modernization.
Website: www.rocketsoftware.com
Rocket Global Headquarters
77 4th Avenue, Suite 100
Waltham, MA 02451-1468
USA
To contact Rocket Software by telephone for any reason, including obtaining pre-sales information
and technical support, use one of the following telephone numbers.
Country Toll-free telephone number

United States 1-855-577-4323
Australia 1-800-823-405
Belgium 0800-266-65
Canada 1-855-577-4323
China 400-120-9242
France 08-05-08-05-62
Germany 0800-180-0882
Italy 800-878-295
Japan 0800-170-5464
Netherlands 0-800-022-2961
New Zealand 0800-003210
South Africa 0-800-980-818
United Kingdom 0800-520-0439
Contacting Technical Support

The Rocket Community is the primary method of obtaining support. If you have current support and
maintenance agreements with Rocket Software, you can access the Rocket Community and report
a problem, download an update, or read answers to FAQs. To log in to the Rocket Community or to
request a Rocket Community account, go to www.rocketsoftware.com/support.
In addition to using the Rocket Community to obtain support, you can use one of the telephone
numbers that are listed above or send an email to support@rocketsoftware.com.
3
iv
Table of Contents
Rocket Aldon Report Manager ..................................................................................... 1
Introduction to Report Manager .................................................................................... 1
Abbreviations............................................................................................................. 1
About Rocket Aldon...................................................................................................... 1
What's New in Version 1.8 ........................................................................................... 2
Technology .................................................................................................................. 2
Getting Started with Report Manager........................................................................... 2

Overview of Report Manager........................................................................................ 2
Report Input .............................................................................................................. 3
Report Output ............................................................................................................ 3
Saving, Reusing, and Organizing Report Parameters................................................ 4
Report Manager Licensing ........................................................................................... 4
Determining Current License Type ............................................................................ 4
Connection validation information .............................................................................. 6
Expiration of Test Drive Trial License ........................................................................ 6
Launching Report Manager .......................................................................................... 7
Installing Report Manager Required Fonts ................................................................... 8
Report Manager Home Page Legend ........................................................................... 9
Customize Button .................................................................................................... 10
Run Button .............................................................................................................. 10
Options Button......................................................................................................... 10
Help Button ............................................................................................................. 10
Report Categories ...................................................................................................... 10
Report Folders ........................................................................................................... 11
Closing Report Manager ............................................................................................ 11
Using Rocket Aldon Report Manager ........................................................................ 11

Running a Report ....................................................................................................... 11
Available Reports ....................................................................................................... 12
Saving Report Parameter Sets ................................................................................ 13
Creating New Report Designs ................................................................................. 13
Supplying Report Parameters .................................................................................... 14
About Report Parameters ........................................................................................ 14
Selection Criteria Parameters .................................................................................. 14
Date Parameters ..................................................................................................... 16
Output Control Parameters ...................................................................................... 16
Opening the Report Parameters Dialog ................................................................... 17
Using the Report Parameters Dialog ....................................................................... 17
Tips for entering report parameter values ................................................................ 17
v
Exporting Data from RM............................................................................................. 19
Customizing Reports .................................................................................................. 19
About Custom Reports ............................................................................................ 19
Customizing Report Content ................................................................................... 20
Customize Report Content Dialog ........................................................................... 21
Saving Reports .......................................................................................................... 23
About Saving Reports ............................................................................................. 23
Saving Report Parameter Sets ................................................................................ 25
Saving Custom Reports .......................................................................................... 26
Save Dialog ............................................................................................................. 28
New Folder Dialog ................................................................................................... 29
Managing Saved Reports ........................................................................................... 30
About the Report Storage Location ......................................................................... 30
Managing the Report Storage Location ................................................................... 30
Backing up Your Reports ........................................................................................ 31
LM(e) Report Samples ................................................................................................ 32

About LM(e) Report Samples .................................................................................. 32
LM(e) Task Reports ................................................................................................... 32
LM(e) Task Assemblies Associated with Release Report ........................................ 32
LM(e) Task Summary Report .................................................................................. 33
LM(e) Release Reports .............................................................................................. 37
LM(e) Release Summary Report ............................................................................. 37
LM(e) Java Compile Classpath Report .................................................................... 42
LM(e) Activity Reports ................................................................................................ 43
About LM(e) Activity Reports ................................................................................... 43
LM(e) Activities by Part Report ................................................................................ 43
LM(e) Activities by Release Report ......................................................................... 45
LM(e) Activities by Type Report .............................................................................. 47
LM(e) Activities by User Report ............................................................................... 49
LM(e) Activity Summary by Release Report ............................................................ 52
LM(e) Activity Summary by User Report.................................................................. 54
LM(e) Promotion Activities for Environment by Part................................................. 56
LM(e) Permissions Reports ........................................................................................ 58
LM(e) Authority Change History Report ................................................................... 58
LM(e) Permissions by Release Report .................................................................... 60
LM(e) Permissions by User Report.......................................................................... 62
LM(e) Role Change History Report ......................................................................... 63
LM(i) Report Samples ................................................................................................. 64

About LM(i) Report Samples ................................................................................... 64
LM(i) Task Reports .................................................................................................... 64
LM(i) Task Activity Time Log Summary Report........................................................ 64
vi
LM(i) Task Activity Time Log Report ........................................................................ 67
LM(i) Task Objects Report ....................................................................................... 69
LM(i) Task Summary Report.................................................................................... 70
LM(i) Release Reports ............................................................................................... 74
LM(i) Active Tasks Associated with Release Report ................................................ 74
LM(i) Release Summary Report .............................................................................. 75
LM(i) Activity Reports ................................................................................................. 80
About LM(i) Activity Reports .................................................................................... 80
LM(i) Activities by Object Report.............................................................................. 80
LM(i) Activities by Release Report ........................................................................... 82
LM(i) Activities by Task Report ................................................................................ 84
LM(i) Activities by Type Report ................................................................................ 85
LM(i) Activities by User Report ................................................................................ 87
LM(i) Activity Summary by Type Report................................................................... 89
LM(i) Activity Summary by User Report ................................................................... 90
LM(i) Promotion Activities for Environment by Object Report ................................... 92
LM(i) Promotion Activities for Environment by Task Report ..................................... 94
LM(i) Promotion and Checkout Activities by Object ................................................. 96
LM(i) Deployment Reports........................................................................................ 100
LM(i) Deployed Object History by Release Report ................................................. 100
LM(i) Deployment Sets by Release Report ............................................................ 102
LM(i) Permission Reports ......................................................................................... 105
LM(i) Permissions by Release Report.................................................................... 105
LM(i) Permissions by User Report ......................................................................... 107
Appendices ................................................................................................................ 108

Appendix A - LM Concepts ....................................................................................... 109
Appendix B - BIRT Overview .................................................................................... 110
Report Introduction ................................................................................................ 110
The Anatomy of a Report....................................................................................... 110
Appendix C - Valid Values for Report Parameters .................................................... 111
Selection criteria parameters ................................................................................. 111
Date Parameters ................................................................................................... 113
Output Control Parameters .................................................................................... 113
Appendix D - Report Options.................................................................................... 114
Report Tool Bar ..................................................................................................... 114
Report Table of Contents....................................................................................... 115
Run the Report ...................................................................................................... 115
Export the Report Data .......................................................................................... 115
Export the Report .................................................................................................. 115
Printing a Report on the Client ............................................................................... 115
HTML Print Format ................................................................................................ 116
PDF Print Format .................................................................................................. 116
vii
Pages to Print........................................................................................................ 116
Printing a Report on the BIRT Server .................................................................... 117
Report Navigation Bar ........................................................................................... 117
Appendix E - Accessing the LM Databases via Report Manager .............................. 119
Appendix F - Exporting from RM .............................................................................. 120
Exporting Report Data ........................................................................................... 120
Exporting the Data ................................................................................................ 122
Exporting a Report ................................................................................................ 122
Appendix G - Entering/Updating the RM License Information................................... 125
Entering License Information for the First Time ..................................................... 125
Updating License Information ................................................................................ 126
Appendix H - Known Issues ..................................................................................... 128
Browser Settings ................................................................................................... 128
Unpredictable Results Using the Microsoft PowerPoint Output Option .................. 128
Report Title Affects Export to Microsoft Excel ........................................................ 128
Appendix I - Licenses ............................................................................................... 129
Licenses ................................................................................................................ 129
License Agreement ............................................................................................... 129
Appendix J - Resources ........................................................................................... 130
RM ........................................................................................................................ 130
LM(e) .................................................................................................................... 130
LM(i) ...................................................................................................................... 130
Accessing Documentation on the Web Site ........................................................... 130
Adobe PDF ........................................................................................................... 130
BIRT Documentation ............................................................................................. 131
Tomcat Documentation ......................................................................................... 131
Appendix K - Customizing the Report Logo.............................................................. 132
Glossary .................................................................................................................... 133
Index .......................................................................................................................... 135
viii
Report Manager User Guide Rocket Aldon Report Manager
Rocket Aldon Report Manager
Introduction to Report Manager

Report Manager (RM) is a web-based accessory application for users of the Rocket Aldon Lifecycle
Manager (IBM i Edition) and Rocket Aldon Lifecycle Manager (Enterprise Edition) products.
The purpose of RM is to offer organizations that use Lifecycle Manager the ability to access and
display information stored in the products' databases, and to produce reports in a variety of possible
output formats.
Abbreviations
Throughout the remainder of this document, we will use short names to refer to the various Rocket
Aldon products, as described in the following table.
Product Name Short Name

Rocket Aldon Lifecycle Manager (IBM i LM(i)
Edition)
Rocket Aldon Lifecycle Manager LM(e)

(Enterprise Edition)
Rocket Aldon Report Manager RM
Rocket Aldon Security Server Security Server
About Rocket Aldon

Rocket Aldon provides application lifecycle management (ALM) for the business of IT. We offer
flexible ALM for complex environments; simplified ALM for complex work; and uncomplicated ALM
for complete visibility and collaboration.
For more than 30 years, we have been the experts in providing ALM solutions to ensure that
change management, collaboration, and compliance are applied consistently across all areas of IT
whether you develop using agile, waterfall, iterative or other hybrid methodologies. Through our
user-centric approach to process management and workflow automation, our change, release &
deployment, agile, and service management products help you focus on what you do best—
providing superior services, rapidly developing applications, and efficiently managing your IT
operations. Behind the scenes, we help you increase productivity, accelerate time-to-market, fully
understand your IT assets, and easily achieve compliance with regulatory standards.
Rocket Software (www.rocketsoftware.com) is a global software development firm that builds
enterprise products and delivers enterprise solutions in the following segments: Business
Intelligence and Analytics; Storage, Networks, and Compliance; Application Development,
Integration, and Modernization; and Database Servers and Tools. Rocket is engaged in business
and technology partnerships with IBM, EMC, Fujitsu, HP Enterprise Services, Datatel, Avaya,
Motorola, and many others. The company is headquartered in Waltham, Massachusetts, USA.
1
Getting Started with Report Manager Report Manager User Guide
For more information about us and our products, visit our web site at
http://www.rocketsoftware.com/product-families/rocket-aldon.
What's New in Version 1.8

This release of Report Manager includes the enhancements described here.
 Column headers have been incorporated into Permissions Reports exported to Excel
format.
 The LM(i) Promotion and Checkout Activities by Object Report has been updated with three
new groups that users can select: *PRM, *CHK, *CRT. Each group code includes activity
codes that are pre-selected for this report.
 Three new activity codes have been added to the LM(i) Promotion and Checkout Activities
by Object Report: ADD, ECK, and RST.
Technology
Report Manager is a web-based application that uses the following technologies:
 A web browser (must be installed on your local PC). Currently supported browsers are:
o Microsoft Internet Explorer Version 9 or higher (in compatibility mode);
OR
o Mozilla Firefox Version 16.0 or higher;
OR
o Google Chrome Version 20.0 or higher.
 Rocket Aldon Security Server (See Appendix E - Accessing the LM Databases via Report
Manager.)
 Apache Tomcat web server for Windows.
 Eclipse Business Information Reporting Tools (BIRT). (See Appendix B - BIRT Overview.)
 Java Runtime Environment (JRE).
 Java Database Connectivity (JDBC).
 Server running Windows 2008 Server, 64-bit; or Windows 2012 Server, 64-bit.
Note: Apache Tomcat and Eclipse BIRT have the following requirements:
 Must both be installed on the same computer, and that computer must be accessible to your
local PC via a TCP/IP network
 Must both be accessible to the server that hosts LM(i) and LM(e).
Note: BIRT, Apache Tomcat, JRE, and JDBC are installed along with the Report Manager.
Getting Started with Report Manager
Overview of Report Manager

RM is a web-based application designed to support organizations that use LM(i) or LM(e).
2
Report Manager User Guide Getting Started with Report Manager
RM allows users to produce reports containing detailed information about the status of parts or
objects that are under management by your Rocket Aldon products, and about the tasks associated
with the development of those items. Users can also produce reports that show the status of LM(i)
deployments and permissions.
Users access RM from a Web browser. From the browser window, users select a report to run,
identify the parameters necessary to generate the report, and indicate their preferences for the
resulting report output.
RM ships with a set of named, pre-defined report parameter sets for both LM(e) and LM(i). The
names of these parameter sets are the report names you see on the RM home page.
Except for the customizable reports, the layout of each report is fixed based on its pre-defined
report design file. Report design files are not visible on the RM home page. Read Available
Reports for more about report design files. Read About Custom Reports for more about customizing
eligible reports.
Report Input
When users run a report, they can request that all relevant data be included in the report, or they
can choose a subset of the available data by specifying a set of selection criteria. The selection
criteria consist of a range of possible values for each of several data elements in the report. Those
database records that meet all of the selection criteria are included in the report, while those that do
not are excluded.
Rocket Aldon designates the fields that are used as selection criteria for each report.
Users define report content by specifying values for each of three categories of report parameters:
1. Selection criteria parameters;
2. Date parameters (if they are present); and/or
3. Output control parameters.
Read About Report Parameters for more.
The size of your database - particularly the amount of activity information you have logged - can
affect the speed with which some reports return output. This is especially true of reports containing
activity-related information.
Report Output
A variety of output formats are available into which your reports can be rendered. Some of these
output formats are best for immediate viewing; other formats are better for embedding your reports
into other documents, presentations, or spreadsheets. The available report output formats and their
optimum use are:
Format Best used for...
HTML Immediate viewing
PDF Immediate viewing and saving
XLS Saving and embedding in documents
For more about report output options, read Appendix C: Report Parameters Permissible Values.
3
Saving, Reusing, and Organizing Report Parameters

In addition to running a report with a specific set of selection criteria, users can save their report
parameter choices for any report in the RM database, as a named report parameter set. Once a
parameter set is saved, users can quickly and easily run the corresponding report, without having to
re-supply any parameter values.
Saved parameter sets and custom reports are stored in the RM database in a
category/folder/subfolder structure, all of which the user can define. Each time users access the RM
home page, it reflects the structure currently defined in the RM database.
User-created report categories, folders, custom reports, and saved parameter sets have user-
defined names. A category can contain folders, custom reports, and saved parameter sets. A folder
can contain sub-folders and report parameter sets.
There is no limit to the number of folders, sub-folders, custom reports, and report parameter sets
that you can save. Up to 20 total report categories are allowed, including the shipped Reports
category.
As shipped, there is one Rocket Aldon-defined report category, named Reports, containing one
folder for LM(e) reports and another folder for LM(i) reports. Each product folder contains report
subfolders, which in turn contain that product's Rocket Aldon-defined report parameter sets. These
are the names you see in the list of product reports on the RM home page.
For more about saving report parameter sets, read Saving Report Parameter Sets. For more about
customizing reports, read Customizing Report Content and Saving Custom Reports. For more
information about the RM storage location, read the About the Report Storage Location topic.
Report Manager Licensing

This software and the associated documentation are proprietary and confidential to Rocket
Software, Inc., are furnished under license, and may be used and copied only in accordance with
The server component of Report Manager is licensed. There are two types of licenses:
 Test Drive Trial License
 Permanent License
A Test Drive Trial License has a fixed expiration date, whereas a Permanent License does not
expire. The purpose of a Test Drive Trial License is to give prospective users the opportunity to try
RM before making a purchase decision.
The RM license applies only to the RM server component. While either type of license is in effect,
there are no restrictions on who may access RM or how many simultaneous users are permitted.
The license validation string is provided to you in connection with downloading the RM server
component from the Rocket Community: https://support.rocketsoftware.com. Refer to the Report
Manager Installation Guide for more information.
The license validation string is entered after the RM server installation is completed. Once an RM
license has been validated, the validation can be updated if needed. (See Appendix G -
Entering/Updating the RM License Information.)
Determining Current License Type

After launching the RM client, you can determine which type of license is currently in effect. There
are two ways to check:
 Report Category Header
4
 About Report Manager dialog

Report Category Header
Notice the report category header for the Reports category. (See Report Manager Legend.)
 For a test drive trial license, the following text appears on the right end of the report category
header: "License expires in NN days on DD-Mon-YY", where:
o NN is the number of days remaining on the license;
o DD-Mon-YY is the date the license will expire.
(If the license expires on today's date, the text reads "License expires today.")
 For a permanent license, the right end of the report category header is blank.
The text "License expires..." is a link. If you click on the text, the Report Manager Test Drive dialog
appears. An example of the dialog for a Test Drive Trial License is shown below.
About Report Manager Dialog

The About Report Manager dialog also displays the license type. For a Test Drive Trial License, the
dialog displays "License expires in NN days on DD-Mon-YY", where:
 NN is the number of days remaining on the license;
 DD-Mon-YY is the date the license will expire.
(If the license expires on today's date, the text reads "License expires today.")
5
If this instance of RM has a Permanent License in effect, the About Report Manager dialog appears
as shown below.
Note the "Licensed Copy" text on the dialog.
Connection validation information

The About dialog indicates whether the server connection(s) you have configured are valid. In the
examples above, the connections are working. If RM could not validate a connection, one of these
messages would appear instead:
LM(i) connection problem OR
LM(e) connection problem OR
Security Server connection problem
Note: A valid connection does not imply that RM is fully operational, as this process does not
confirm that appropriate RM PTFs are installed. You must ensure that any necessary PTFs are
applied. Refer to your RM Installation Guide for more information about applying PTFs.
Expiration of Test Drive Trial License

If you launch RM after a Test Drive Trial License has expired, the following error message appears.
6
When this occurs and you intend to continue using Report Manager, contact your Rocket Aldon
Account Manager to obtain a Permanent License.
On the above display, the text "License Validation Error" is a link. If you click on the link, the
following is displayed.
Launching Report Manager

To launch RM, do the following:
 Ensure that Apache Tomcat is running on the computer that is hosting Report Manager. (For
more information about installing and starting Apache Tomcat, refer to the Report Manager
Installation Guide.)
 Open your browser
 On the browser's address line, enter
http://host:NNNN/RM
where:
o "host" is one of the following:
 The network name of the computer where RM is installed
 The IP address on your local area network of the computer where RM is installed
 "localhost" if you are invoking RM from the computer where it is installed
o "NNNN" is the TCP/IP port number that was configured for Apache Tomcat when it was
installed. If you do not know the correct host or port number, contact your System
Administrator.
7
Upon successful connection, the RM logo appears in the address line. If you are using the
Mozilla Firefox browser, the logo is also placed on each tab that is opened via RM.
The RM home page appears. (See RM Home Page.)
Installing Report Manager Required Fonts

When you launch Report Manager, the software checks to ensure that your client computer has the
required fonts installed. If not, a dialog appears that provides you access to the necessary font
resources, along with instructions for installing them:
Follow the instructions on the dialog to

install the necessary fonts.
8
Report Manager Home Page Legend

The RM home page looks like this:
1 The page heading with the Rocket Aldon logo.
The report category header for the "Reports" category. Note: If this instance of RM
is operating under a Test Drive Trial License, then the right end of the Report
2 category header will contain the text "License expires in NN days on DD-Mon-YY".
Otherwise, the right end of the header is blank. (See Report Manager Licensing.)
3 The open/close button for the report category. (See Report Categories.)
4 A report folder.
5 A list of reports in a report folder.
Buttons for customizing report columns. (Applies to eligible reports only - see
6 Customizing Report Content.)
7 Buttons for opening the Report Parameters dialog.
8 Links to report descriptions in the help.
9
9 Links to on-line help topics.
Customize Button
Clicking the Customize button for a report opens the Select Report Fields dialog, which is
used – for specific eligible reports – to include or remove columns of data in the report and to
supply a title for the custom report. For a list of reports that are eligible for customizing, read About
Custom Reports.
Run Button
The Run button is used to launch a report.
When the Run button for a report is green , a value has been entered or selected for all of the
report parameters that are relevant to the report type. The report is launched upon clicking the
green Run button or the report name.
When the Run button for a report is yellow , a value has not been entered or selected for
some or all of the report parameters that are relevant to the report type. If you click the yellow Run
button or the report name, the Report Parameters dialog is opened to give you the opportunity to
enter or select the missing parameters.
Options Button
Clicking the Options button opens the Report Parameters dialog, which is used to define the
subset of data to be included in the associated report.
Help Button
Clicking the Report Help button opens the on-line help topic for the associated report. The help
topic for each report describes the report content in detail.
Report Categories
A report category is a container that holds both reports and report folders. A report category can
either be "open" or "closed". An open report category is shown below.
An unopened report category appears as shown below.
To open a report category, click the "plus" button on the right side of the report category header.
10
Report Manager User Guide Using Rocket Aldon Report Manager
To close a report category, click the "minus" button.

A maximum of 20 report categories is allowed. RM ships with one category named "Reports"
already defined; users can define up to 19 additional report categories.
Report Folders
RM reports are stored in report folders. Report folders exist within a report category. A report folder
is a tree structure, similar to a file directory structure, and it can contain any number of reports and
sub-folders.
A report folder is identified by the presence of a folder icon located immediately to the left of the
folder name. There are two versions of the folder icon:
Indicates a report folder that is "closed", i.e., the contents are not shown.
Indicates a report folder that is "open". The included report folders and report, if
any, are shown indented below the folder name.
In addition to the folder icon indicating a folder, the folder name is shown in bold type.
To open a closed report folder, click once on the folder icon. To close an open report folder, click
once on the folder icon.
Closing Report Manager

To close Report Manager, simply close the browser.
Note: Apache Tomcat has a built-in timer that will cancel the session if there is no activity for 30
minutes. You can reset the time by clicking the browser's Refresh button.
Using Rocket Aldon Report Manager
Running a Report
In this context, running a report means running a particular report with a particular set of report
parameters. When you run a report, depending on the value specified for the Output Type
parameter, the resulting report will either be displayed in your browser or produced in an external
file. (See Appendix D - Report Options.)
To run an RM report:
 Launch Report Manager. (See Launching Report Manager.)
 Expand the list of report folders on the Report Manager home page until the desired report
name is exposed. Choose one of these ways to run a report:
o When the Run button for the report is green , a value has been entered or selected
for all of the report parameters that are relevant to the report type. The report is
launched upon clicking the green Run button.
11
Using Rocket Aldon Report Manager Report Manager User Guide
o When the Run button for the report is yellow , values for some or all of the report's
relevant parameters are missing. If you click the yellow Run button or the report name,
the Report Parameters dialog opens so you can provide the missing parameter value(s).
o Click on the report name. The result depends on the color of the Run button (see
previous two bullet points).
 After defining the new set of report parameters, you can:
o Run the report with the new parameter set by clicking the Run button on the Report
Parameters dialog; OR
o Save the new report parameters for the existing report; OR
o Define a new report parameter set by clicking the Save button on the Report Parameters
dialog.
After you run a report, return to the RM home page. Notice that the Report Parameters dialog
containing the parameter values you selected remains in focus. This feature allows you to see the
results of your choices before you decide whether to save the report parameter set.
Note: Even if you do not save the report parameter set, RM "remembers" the last set of report
parameter values used for each report for your entire Report Manager session. (An RM session is
everything that happens after you open RM in your browser, until you close the browser.) This way,
if you specify a particular set of parameters in a session, you can repeat that report at any time
during the session, with the same parameter set, by re-running the report.
Each time you run a report with the HTML output type, RM opens either a new browser window or a
new browser tab, depending on your browser's capabilities and settings. While the RM server is
collecting the data, a progress meter like this appears in the newly opened window:
When the server finishes collecting the data and formatting the report, the report itself appears in
the browser window.
Available Reports
RM ships reports for both the LM(e) and LM(i) products. The reports are organized in type
categories by product, as follows:
 LM(e) Task Assemblies  LM(i) Task Activity Time Log

Associated with Release Summary
Task Reports:  LM(e) Task Summary  LM(i) Task Activity Time Log
 LM(i) Task Objects
 LM(i) Task Summary
 LM(e) Release Summary  LM(i) Active Tasks Associated with

Release Release
Reports:  Java Compile Classpath
(supplemental)1,2  LM(i) Release Summary
12
 LM(e) Activities by Release  LM(i) Activities by Object

 LM(e) Activities by Type  LM(i) Activities by Release
 LM(e) Activities by User  LM(i) Activities by Task
 LM(e) Activities by Part  LM(i) Activities by Type
(supplemental)1,3
 LM(i) Activities by User
 LM(e) Activity Summary by
Activity  LM(i) Activity Summary by Type
Release
Reports:  LM(i) Activity Summary by User
 LM(e) Activity Summary by User
 LM(i) Promotion Activities for
 LM(e) Promotion Activities for
Environment by Object
Environment by Part
 LM(i) Promotion Activities for
Environment by Task
 LM(i) Promotion and Checkout
Activities by Object
 LM(i) Deployed Object History by

Deployment Release
Reports:  LM(i) Deployment Sets by
Release
 LM(e) Authority Change History  LM(i) Permissions by Release

Permissions  LM(e) Permissions by Release  LM(i) Permissions by User
Reports:  LM(e) Permissions by User
 LM(e) Role Change History
1 - Supplemental reports are reports that are run from within other reports by clicking a link.
2 - Link(s) for this supplemental report appear in the LM(e) Release Summary report.
3 - Link(s) for this supplemental report appear in the LM(e) Activities by Release, Type and User
reports.
Saving Report Parameter Sets

RM allows you to save multiple sets of named parameter values for any of the shipped reports. You
can also create folders in which to save your parameter sets. Using these features, you can easily
run the same basic report using any number of possible parameter value combinations, without
having to individually set the desired values every time. See Saving Report Parameter Sets.
Creating New Report Designs

It is possible, using facilities within the BIRT framework, to create your own custom report designs,
and add them to the set of report designs that are shipped with RM. Doing this requires a detailed
understanding of BIRT and a thorough knowledge of the structure of your LM product's database,
as well as close consultation with your Rocket Aldon Technical Support representative.
The task of creating new report designs is beyond the scope of this documentation. For more
information, please refer to the documentation for the BIRT product.
13
Supplying Report Parameters

About Report Parameters
For information about specific value requirements for individual report parameters, read
Appendix C.
The typical LM(i) and LM(e) product databases contain entries for many groups, applications,
releases, versions, tasks, environments, and so on. When running reports, you are likely interested
in a small subset of the information contained in the database.
To identify the desired subset of data to include in a report, you must supply information using a set
of report parameters. Each report has its own relevant set of parameters. There are three
categories of report parameters on each Report Parameters dialog:
The text immediately below the dialog

title identifies the report you have
chosen to run.
The dialog contains categories of
parameters, separated by horizontal
lines. The categories are:
 Selection criteria parameters
 Date parameters
 Output control options
The selection criteria parameters
appear in the upper portion of the
dialog.
When present, date parameters appear
in the middle portion of the dialog.
The output control options apply to all
reports, and appear in the lower portion
of the dialog.
Note: In some versions of Internet Explorer, an ‘x’ appears on a parameter as you make your
parameter selections to indicate where the browser is focused. The ‘x’ does not indicate a problem.
Selection Criteria Parameters

Use selection criteria parameters to choose a subset of the available data to include in a report. For
each parameter, you can:
 Make no selection; OR
 Drop down the selection list, if there is one, and choose a value; OR
 Type a special, specific, or generic value directly into the field. (Read Using Wildcards,
below.)
The Task name and Object name selection parameters have only an edit box; there is no drop-
down list.
14
The selection criteria fields vary by report, and might include one or more of the following fields:
 Group name
 Application name
 Release name
 Version name
 Task name
 Environment abbreviation
 User name
 Activity type
 Part name
 Object name
 Object type
 Scope of authorities
For detailed information about valid values for these fields, including exceptions and rules, read
Appendix C - Report Parameters: Valid Values.
About cascading selection criteria parameter relationships
Certain selection criteria parameters have what we call a cascading relationship. When a cascading
relationship exists, your value selection for one parameter limits the value choices available for
another parameter. For LM(i) reports, the Group, Application, and Release parameters have a
cascading relationship. For LM(e) reports, it is the Group, Application, Release, and Version
parameters that cascade.
When necessary, the Report Parameters dialog prevents you from supplying a value for a
cascaded parameter until you have supplied values for all parameters higher in the relationship.
Using Wildcards
The % wildcard character can be used in any selection criteria parameter field. The % wildcard
character, when specified, represents any one or more contiguous characters. Some examples of
wildcard usage are:
 A%C matches ABC, AXC, AXXC, AXXXXC, etc.
 A%B%C matches any value whose first letter is A, last letter is C, and has the letter B
anywhere in between the first and last letters.
 A% matches all values starting with the letter A
 %A matches all values ending with the letter A
 % matches all values (equivalent to *ALL)
About Validation of Selection Criteria Parameter Values
The values you enter or select for selection criteria parameters are applied using an SQL WHERE
clause. There is no validity checking for anything you type or choose in any of the combo or edit
boxes on the Report Parameters dialog. For example, if you supply a release name that does not
exist in the application(s) you specified, RM generates an empty report, rather than issuing an error
message. This also applies to parameters that you leave empty or supply a blank value.
15
Sort Order and Control Breaks

Unless otherwise noted in the individual report descriptions, the information retrieved from the
database is sorted into ascending order by the selection criteria parameters.
Date Parameters
OR
These fields appear only for specific reports. Use these options to limit the amount of information
selected for the reports (and thereby reduce the amount of time it takes to produce these reports).
Using these fields you can:
 Limit activity information to within a specific date range; OR
 Limit activity information to dates for some number of days up to and including the current
date.
Read Appendix C for detailed value requirements for the Date Range and Previous X Days fields.
Output Control Parameters

The fields in this dialog section apply to all reports. These parameters control the resulting report's
presentation and output format.
Output Type
The Output Type selection list offers you these report output choices:
 HTML - Renders the report in HTML and displays it in a browser window.
 PDF - Produces the report in a file that is compatible with Adobe Systems, Inc. Portable
Document Format (PDF).
 XLS - Produce the report in a file that is compatible with Microsoft Excel.
Note: The ability to produce a file that is compatible with the Microsoft Office products is a native
function of the BIRT tool. For information about which versions of Microsoft Office are supported,
consult the BIRT product documentation. Also, the associated Microsoft product must be installed
on the computer where the files will be opened or viewed.
See Appendix H: Known Issues for more information about limitations on some report output
formats.
Output Options
The Output Options parameter appears only when the Output Type field is set to either HTML, or
PDF.
If you choose the HTML output type, then you can choose to include or exclude some additional
navigation and tool bars in your report output. See Appendix D - Report Options for more
information.
If you choose the PDF output type, you can indicate whether or not the output should be scaled to
fit one report page on a PDF page. See Appendix D - Report Options for more information.
16
Opening the Report Parameters Dialog

To define the current parameter set for a report, do the following:
1. Launch Report Manager (see Launching Report Manager).
2. If necessary, expand the appropriate report storage area.
3. Expand the appropriate product and report folders until you locate the report you want.
4. Use one of these methods to open your chosen report's Report Parameters dialog:
a. Click the Options button near the right end of the line containing the report
name; OR
b. Click a yellow Run button ; OR
c. Click the report name when the associated Run button is yellow.
See Report Parameters Dialog.
Using the Report Parameters Dialog

Use the Report Parameters dialog to define the subset of information you want to include in the
report you have chosen to run.
The contents of the Report Parameters dialog vary depending on which report you choose to run.
For details about the parameters that can appear on the dialog, read About Report Parameters.
Tips for entering report

parameter values
 Read Appendix C for information
about the rules for specifying valid
parameter values.
 When supplying specific, generic, or
special values (rather than choosing
one from a drop-down list), indicate
that you are finished by pressing the
Tab key or clicking outside the field.
 The dependencies between fields
require the dialog to refresh itself
after each entry, so that RM can
build an appropriate list for the next
field.
 Wait for the dialog to finish
refreshing before choosing the next
value, or your selection will be lost.
17
To fill out the panel, follow these steps:
1. Supply a value for each selection criteria field in the top portion of the dialog. Starting with
the first field, do ONE of the following for each field, in order of appearance:
a. Drop down the selection list and choose a value; OR
b. Type a generic value with a wildcard and press the Tab key; OR
c. Type a specific value and press the Tab key; OR
d. Type one of the special values (such as *ALL or *NONE) allowed in the field and press
the Tab key.
2. For the reports that include a date parameter selection, select a date range or enter the
previous number of days.
To supply values for date parameters in the middle of the dialog, do ONE of the following:
a. To include activity for a contiguous set of days in a range, click the Date Range radio
button and select a From date and a To date. If you do not supply date information, the
beginning date is set to 1/1/2000 for LM(e) reports or 1/1/1990 for LM(i) reports. The
ending date is set to the current date. OR
b. To include activity for a number of days preceding and including today, click the
Previous X Days radio button and supply a number of days (up to 999). The default
number of days is 0, which resolves to the current date.
Click the arrow at the right side of the From or To fields to display a calendar control.
To select today's date, click Today.
Otherwise, to choose a date, use the month and year

selection arrows to navigate to a specific month and
year.
Click a day in the calendar to select that date.
Clicking None clears the date field. If you then type the
beginning and ending dates, use the format YYYY-MM-
DD.
Note: You cannot generate a report with a blank date

field.
3. To supply output control parameters that determine how your report renders, do the
following:
a. Drop down the selection list and choose an Output Type.
18
b. If you chose an output type of HTML, you can also fill or empty the toggle boxes to
include or exclude a navigation bar and a toolbar on your HTML report output. (A toggle
box looks like this when filled , and like this when empty .) The reporting tool
communicates your choices to the programs that process the HTML or PDF output.
c. If you choose an output type of PDF, you can also fill or empty a toggle box that controls
how your report pages flow in the resulting PDF.
d. If you choose the XLS output type, no additional output options apply.
4. When you have fully described the report content and output you want, and the dialog has
refreshed itself for the final time, then you can take ONE of the following actions:
a. Click the Run button, to execute the report; OR
b. Click the Save button, to store a reusable report parameter set; OR
c. Click the Cancel button, to exit without saving or running the report.
If you click Run, RM generates your report and renders it in the format you selected. (You are
prompted to supply a file name and storage location if you chose any output type other than HTML.)
If you click Save, the Save dialog appears so you can store a set of reusable report parameters.
(See Saving Report Parameter Sets.)
Exporting Data from RM

As a native function of BIRT, once you produce a report, you can export either the report image
itself, OR the data contained in the report. For a detailed description of the export functions, please
refer to the BIRT documentation. A brief description of these functions appears in Appendix F -
Exporting from RM.
Customizing Reports
About Custom Reports
Customizable reports have a field set that can be broadened or narrowed from the default column
set, based on the user's needs and / or preference.
Once you customize a report, its maintenance becomes your responsibility. During version
upgrades, RM does not upgrade custom reports with new features; they remain at the version level
that was in place at creation time. They will still run, but will not have new features. To use the latest
report features in a custom report, customize the shipped version of the report in the new release,
and save it.
The report descriptions for eligible reports include a list of additional fields that are available when
customizing the report. These fields are in addition to the default field set that appears in the
shipped report.
The following reports are eligible for customizing, and have a corresponding Customize button on
the home page:
 LM(e) reports:
o LM(e) Activities by Release
o LM(e) Activities by Type
o LM(e) Activities by User
19
o LM(e) Promotion Activities For Environment By Part

 LM(i) reports:
o LM(i) Task Activity Time Log
o LM(i) Task Objects
o LM(i) Activities by Object
o LM(i) Activities by Release
o LM(i) Activities by Task
o LM(i) Activities by Type
o LM(i) Activities by User
o LM(i) Promotion Activities For Environment by Object
o LM(i) Promotion and Checkout Activities by Object
Customizing Report Content

To customize a shipped report, take the following steps:
1. Navigate to the desired shipped report on the home page and click its Customize button.
2. The Customize Report Content dialog appears.
20
Note: This image is an example; the columns available for each eligible report vary. See your
chosen report's description for an explanation of the additional available fields that apply to that
report.
3. Supply a report title. The default title is the title of the report you are customizing.
Note: If you plan to export report data to Excel format, avoid using any special characters in
the report title. Both special characters and long report titles can interfere with the creation
of Excel sheet names during the export.
4. At first use, the field selection dialog shows the shipped report's default fields in the Selected
Columns pane on the right. (Once the report has been customized, the right pane shows
currently included fields.) The additional fields you can include appear in the Available
Columns pane on the left. Do ONE of the following:
a. To include an available field as a column in your report, select it in the left pane and use
the > button between the panes to move it to the right pane.
b. To exclude a field column that already appears, select it in the right pane and use the <
button between the panes to move it to the left pane.
Note: You can select and move multiple columns in either direction.
5. When you are satisfied with the field content, you can arrange the fields in the order in which
you want their respective columns to appear in the report, as follows:
a. To leave the field columns arranged in the order in which they currently appear, do
nothing and skip to the next step.
b. To reposition a field column toward the left side of the resulting report, select the field in
the right pane and click the Up button to move it, one position at a time, toward the top
of the Selected Columns list.
c. To reposition a field column toward the right side of the resulting report, select the field in
the right pane and click the Down button to move it, one position at a time, toward the
bottom of the Selected Columns list.
Note: You can select and move multiple columns in either direction.
6. When you are satisfied with the content and position of the report columns, click the Save
button to store your custom report. (See Saving Custom Reports for more information about
managing stored reports.)
Customize Report Content Dialog

The Customize Report Content dialog applies only to reports that have Customize buttons on the
Report Manager home page. Use this dialog to add fields to or remove fields from a customizable
report.
21
The title you want to appear on the report. The default

title is the original report's title. The field does not allow
you to type more than 64 characters.
Report Title Note: If you plan to export report data to Excel format,
avoid using any special characters in the report title.
Both special characters and long report titles can
interfere with the creation of Excel sheet names during
the export.
Available
Lists the additional fields you can include in this report.
columns
Selected
Lists the fields that are already included in this report.
columns
The right and left buttons apply to both available AND

selected fields. Highlight one or more fields in the
> Available Columns pane, and use the > button to include
< the highlighted fields in the report. Highlight one or more
fields in the Selected Columns pane, and use the <
button to remove the highlighted fields from the report.
The Up and Down buttons apply to the selected fields in

Up
the right pane, and allow you to arrange the columns in
Down
relation to each other.
Click this button to store your custom report in the report

Save
storage area. (See Saving Reports.)
Click this button to discard any changes made since you

Cancel
last saved and exit the dialog.
22
If you remove all fields from the Selected Columns pane, a message appears at the top of the
dialog to remind you that the pane cannot be empty:
You must include at least one column on the report.
Saving Reports
About Saving Reports
This section explains everything you need to know about saving reports. You can save report
parameter sets and custom reports. You can organize your saved reports in two different kinds of
containers. These are:
 Report categories; and
 Report folders.
Refer to the Report Manager Home Page Legend to see how report categories and report folders
appear on the RM home page.
Refer to About the Report Storage Location for more information about the actual location where
RM stores report materials.
Important! Be aware that all RM users are also sharing the same "save space." This means
that all custom reports, report parameter sets, report categories, and report folders created by any
one user are accessible to all users. Likewise, any reports created by any individual user remain
intact only if no other user changes it.
Following are some sample scenarios for saving custom reports and report parameter sets.
Case 1 - Replacing existing report materials with revised materials
 Initially, the Report Name field on the Save dialog defaults to the existing file name. Click the
Save button.
 Because a report with this name already exists in this container, you are prompted to
overwrite the existing report:
 Click Yes to overwrite the existing report; click No to return to the Save dialog so you can
change the name.
If you click Yes, the existing report is replaced with the new one, and the dialog where you
started reappears.
Overwrite with caution... A good rule of thumb is to avoid overwriting parameter sets
saved by others whenever possible. When in doubt, either save under a new name or save
in your own folder location.
Case 2 - Saving revised materials in the same report folder as the original materials
 Initially, the Report Name field of the Save dialog contains the name of the existing report
that you began with, and the Save dialog is focused on the report folder or category where
that report resides.
 Type a new name in the Report Name field.
23
 Click the Save button.

The report is saved and the dialog where you started reappears.
Case 3 - Saving new report materials in a different, existing report folder
 On the Save dialog, use the folder buttons to navigate to and open the folder where you
want to place the new report. (Read about the features of the Save dialog for more
information about the folder buttons, if necessary.)
 Supply a name for your new report in the Report Name field.
The new report is saved and the dialog where you started reappears.
Case 4 - Saving new report materials in a new report folder
 On the Save dialog, use the folder buttons to find the location in the existing report structure
where you want to create the new folder.
 To create the new folder inside an existing folder in the list, open the containing folder. To
create the new folder at the same level as the entries currently displayed in the Save dialog,
do not select any of the entries in the list.
 Click the New Folder button. The New Folder dialog appears.
 Supply a name for the new folder in the Folder Name field and click OK. The Save dialog
reappears, with the new folder available for selection as a storage location for your custom
report or parameter set.
 On the Save dialog, double-click the newly created folder to open it.
 Supply a name for the new report or parameter set in the Report Name field. (Because the
new report is in a different folder location than the original, you can use the original report
name if you prefer.)
 The new report is created, and the dialog where you started reappears.
Case 5 - Saving new report materials in a new report folder in a new report category
 On the Save dialog, use the Up One Folder button to navigate to the top of the report
folder structure. (The folder-level button turns gray when you reach the top to indicate that
you can go no further.)
 Click the New Folder button to create a new report category. The New Folder dialog
appears.
(Even though you are using the New Folder dialog, you are creating a new report category,
because you are at the highest level in the report folder structure.)
24
 Supply a new category name in the Folder Name field, and click OK.
The new report category is created and the Save dialog reappears so you can open the new
category in preparation for creating a new folder for your new parameter set or custom
report.
Note: You can create up to 19 new report categories, in addition to the Reports category.
The report categories appear in ascending, alphabetical order.
 Now create and open a folder in which to store your new parameter set or custom report,
using the procedure described in Case 4, beginning with the second bullet.
 When the Save dialog reappears opened to your new folder, click the Save button. The new
report is saved in the new folder in your new category, and the dialog where you began
reappears.
Saving Report Parameter Sets

To save a new report parameter set, do the following:
 Open the Report Parameters dialog for an existing report. (See Report Parameters.)
 Set the report parameters to the desired values. For example:
 Click the Save button at the bottom of the dialog. The Save dialog appears.
25
 On the Save dialog, navigate to and select the folder or category location where you want to
store the parameter set. (If you like, you can use the New Folder button to open the New
Folder dialog and create a new category or folder.)
 Accept the default Report Name, or supply a name you prefer.
 Click the Save button to store your new report parameter set in the location you have
identified.
Usage Notes
 Important! This version of RM includes a set of pre-defined LM(e) and LM(i) report
definitions. (See Available Reports.) You cannot save parameter sets for any of the pre-
defined reports within their original containing folder. If you try, the following message
appears:
Supply a different name, OR save it in a different folder location.

 To avoid confusion, create a separate report category in which to save your report
parameter sets and custom reports.
 Report parameter set names must be unique within a folder. However, to avoid confusion,
we strongly recommend that you use a name for your report parameter set that identifies the
original report. The restrictions as to name length, case-sensitivity, valid characters, and so
on are the same as for the Windows file system.
 Read About Saving Reports for more information about various possible save scenarios for
report parameter sets and custom reports.
 To learn more about the report storage location, read About the Report Storage Location.
Saving Custom Reports

To save a report you have customized, do the following:
 On the home page, navigate to the report you want to customize and click the Customize
button.
 On the Customize Report Content dialog, choose the additional fields you want included in
your report, and remove any fields you do not want to appear. Then click the Save button.
 The Save dialog appears.
26
By default, the Save dialog is oriented at same level in the report folder structure as the
report you are customizing.
 On the Save dialog, use the folder buttons to navigate to and select the folder or category
location where you want to store your custom report. (If you want, use the New Folder
button to open the New Folder dialog, and create a new category or folder.)
 Accept the default Report Name, or supply a name you prefer.
Notes:
o The default file name is constructed from the report title you supplied. Special
characters, ASCII control characters, and trailing periods or spaces are converted to
underscore characters in order to create a valid file name.
o You can never save over the shipped version of the report. A message appears with a
request for a different file name.
 Click the Save button to store your new custom report in the location you have identified.
Usage Notes
 Important! RM includes a set of pre-defined LM(e) and LM(i) reports and parameter sets.
(See Available Reports.) RM will not allow you to replace these default shipped reports
or parameter sets. If you try, the following message appears:
Alter your chosen file name, OR save to a different folder location.

 Report names must be unique within a folder. However, because multiple RM users might
be working with the same set of folders, we strongly recommend using a report name that
identifies the original report. The restrictions as to name length, case-sensitivity, valid
characters, and so on are the same as for the Windows file system.
27
 Read About Saving Reports for more information about various possible save scenarios for
report parameter sets and custom reports.
 To learn more about the report storage location, read About the Report Storage Location.
Save Dialog
Use the Save dialog to identify the location where you want to store a report parameter set or
custom report you have decided to save. You access the Save dialog in one of two ways:
 By clicking the Save button on the Report Parameters dialog; OR
 By clicking the Save button on the Customize Report Content dialog.
The contents of the dialog depend

on whether you launched it from the
Report Parameters dialog, or the
Customize Report Content dialog.
This sample reflects saving report
parameters.
Save In: This informational field at the top of the dialog reflects the target storage location. Initially,
it defaults to the name of the folder where the original report resides. (The original report is the
report from which you launched the Save operation.) If the originating report is not stored in a report
folder, the Save In field contains the name of the report category where the report resides.
Report Name: Represents the file name of the new custom report or report parameter set.
 For report parameter sets, this field defaults to the file name of the original report.
 For custom reports, this field defaults to the report title you supplied on the Customize
Report Content dialog. (Any special characters are converted to underscore characters (_)
to make a valid file name.)
The navigation buttons in the upper right corner of the Save dialog behave as follows:
Back button (colored either gray or green). Initially, the Back button is
gray, indicating there is no history for this instance of the Save dialog. If you
make any navigation moves on the dialog, such as moving up one level,
creating a new folder, expanding an existing folder, and so on, then the
Back button color changes to green. When the Back button is green,
clicking it once returns you to the previous state of the Save dialog. When
there is no more navigation history for this instance of the dialog (that is,
you've backed up as far as possible), the Back button color reverts to gray.
Important! If you have used the Folder Level button to move to the highest
level of the category/folder structure (that is, the Next Level ), then using the
New Folder button at this level creates a new report category instead of a
report folder.
28
Once you have created the new report category, you can create a new
folder in which to store your new report.
Folder level button. Click once to move to the next higher level in the
category/folder structure. The top-most level of the structure is the "Aldon
Report Manager Report Categories" level.
New folder button. Click once to access the New Folder dialog, which
allows you to create a new folder or report category.
 The main body of the dialog lists all of the folders and reports that reside in the target
storage location. The entries in the list are marked with one of these icons:
Represents a report folder.
Represents an RM pre-defined report. (You cannot re-use any of these

names within this folder.)
Represents a set of saved parameters for a report.
Usage Notes
 Clicking a report name in the dialog body sets the Report Name field to that value.
 Single-clicking on a report folder entry has no immediate action.
 Double-clicking on a report folder entry opens the folder to reveal its contents.
New Folder Dialog

Use the New Folder dialog to create a new folder or report category when you are saving a report
parameter set. You access the New folder dialog using the New Folder button on the Save dialog.
Folder name: Use this field to supply a name for the new folder.
Click OK to create your folder. The Save dialog reappears, showing the new folder so you can
select it if desired.
Click Cancel to return to the Save dialog without creating a folder or category.
Usage notes:
 New folders are always stored inside the folder identified by the Save In field that appears at
the top of the Save dialog.
 To nest folders from this dialog, click Cancel to return to the Save dialog. Then open the
folder where the new folder should reside, and click the New Folder button from there.
 You can create up to 19 report categories in addition to the Reports category.
29
Managing Saved Reports

About the Report Storage Location
Warning! When managing the report storage location, do not rename or delete any of the
following elements:
 The Aldon Report Manager Report Categories folder, OR its shipped contents, as follows:
o The shipped report parameter sets, or any of their containing folders;
o Any folder with an underscore prefix ( _ ); OR
o Any file with an extension of .rptdesign.
If you do, RM may no longer function properly.
The user interface for this version of Report Manager allows you to perform the following
maintenance activities in the report storage location:
 Saving new or revised report parameter sets; OR
 Saving new or revised custom reports; OR
 Creating new report folders; OR
 Creating new report categories.
Other maintenance activities, such as deleting or renaming report parameter sets, deleting or
renaming custom reports, deleting or renaming report folders, and deleting or renaming report
categories can be done only outside of the RM user interface. (See Managing the Report Storage
Location.)
Important! When you delete or rename a report parameter set, custom report, report folder, or
report category, that change applies to all users of this RM instance. Consequently, changes to the
report storage area should be made very carefully, and only in close consultation with other users.
If you accidentally delete or rename a shipped RM parameter set file, contact Rocket
technical support.
To manage the report storage location, you will need access to a console on the computer hosting
the Tomcat server that is serving RM. In addition, you will need sufficient authority to rename and/or
delete files and folders in the RM storage location.
Any saved report parameter sets that require it are converted during RM upgrades to remain
compatible with the new version.
Managing the Report Storage Location
To manage the contents of the RM report storage location, do the following:

 Make certain that no one, including yourself, is currently using RM.
 Log on with Remote Desktop to the computer that hosts Report Manager — that is, the
computer that hosts the instance of Tomcat that is serving RM to your users.
 Navigate to the logical drive where RM is installed (C:, D:, or another letter).
 Locate the folder named Aldon Report Manager Report Categories. This is the root folder
for the shared RM storage space. Notice these characteristics of the root folder structure:
o Each report category is a separate sub-folder in the root. The file system folder name
matches category name.
30
o The contents of these category sub-folders appear in each expandable report category
on the RM home page.
o Each category folder contains report folders and report parameter set files. The structure
mirrors what you see on the RM home page.
o Only the Aldon Reports category folder contains the shipped report parameter sets,
organized by product and report type. (Through the RM user interface, you can create
your own custom folders, custom reports, and report parameter sets in this shipped
report category, but you cannot replace the shipped parameter sets.) Any other category
folders you see here are custom categories belonging to your RM users. These contain
any custom folders, custom reports, and custom report parameter sets that your users
have created.
o Report parameter sets are stored in a file whose name reflects the report name you see
on the RM home page. These files have an extension of .rptparam. Rocket Aldon
determines the names of the shipped report parameter sets. Users assign names of
their own choosing when they save report parameter sets. (Users are not allowed to
overwrite the shipped report parameter sets when creating their own sets.)
 To delete a custom report or saved report parameter set, locate its .rptparam file, and delete
the file in the usual way.
 To rename a custom report or saved report parameter set, rename its .rptparam file in the
usual way.
When deleting or renaming, always make sure you are not altering a shipped report or report
parameter set.
Important! When you rename a custom report or a report parameter set in this directory, its name
is changed in the list of reports on the RM home page. However, the title of the report in the
designated output format is not affected.
 To delete a folder or category, locate the folder with the desired name and delete it in the
usual way. (Make sure you are not deleting a shipped folder or the Aldon Reports category
folder.)
 To rename a folder or category, locate the folder of the same name and rename it. (Make
sure you are not renaming a shipped folder or the Aldon Reports category.)
Deleted and renamed folders and categories are reflected in the list of reports on the RM home
page.
Backing up Your Reports

Any time you save a report parameter set or customize a report, you create new files in your report
storage location.
To ensure that your reports are preserved in the event of a system failure, you can add your report
storage location to your backup utility's list of folders that are backed up periodically.
Add the folder named Aldon Report Manager Report Categories on your RM server to your
utility's backup list. By default, this folder is located on the server computer's hard drive, at the root
level.
31
LM(e) Report Samples Report Manager User Guide
LM(e) Report Samples

About LM(e) Report Samples
This section contains a brief description of each of the LM(e) reports.
For a complete description of each of the data items included in the reports, please consult the
appropriate LM(e) documentation. See Appendix J - Resources.
Detailed descriptions of each report follow.
LM(e) Task Reports

LM(e) Task Assemblies Associated with Release Report
The LM(e) Task Assemblies Associated with Release Report provides an overview of the LM(e)
task assemblies that are associated with a given release. For each assembly included, the report
shows the number of parts in the release associated with the task assembly, part counts by
environment, the number of other releases associated with the task assembly, and the number of
parts in other releases that are associated with the task assembly. If the task assembly is linked to
an LM(i) task, the number of associated LM(i) releases appears, along with a count of LM(i) objects
for the task. The report is sorted by task assembly name within group/application/release
combination.
Linked Reports
From within this report, you can access these additional reports:
 LM(e) Task Summary Report (by clicking a task name);
 LM(i) Task Summary Report (by clicking a link in the Count column under LM(i) Releases);
 LM(i) Task Objects Report (by clicking a link in the Objs column under LM(i) Releases).
An example of the LM(e) Task Assemblies Associated with Release Report follows.
Header Section
Application - The qualified name of the application selected, in the format Group
Name/Application Name.
Release - The qualified name of the release selected, in the format Release Name(Version)
Release Type.
32
Report Manager User Guide LM(e) Report Samples
Report parameters - The group, application, release, and version selection criteria used to
generate the report, as provided on the Report Parameters dialog.
Details Section
The columns of information provided in the details section are as follows:

Task Name - The name of the task assembly associated with the
group/application/release/version combination described on this report page.
Part Counts - Environment part and release part count columns appear for the selected release
and all of its environments.
Note: If a release's total part count differs from the sum of its environment part counts, it is
because the total part count for the release includes parts that are associated with the release,
but not resident in any release environment.
Other Releases - Identifies the number of other LM(e) releases associated with the task, and
the total number of task parts associated with those releases.
LM(i) Releases - Contains a count of the number of LM(i) releases that have tasks linked to the
task assembly, and the number of objects associated with those tasks. (The LM(i) Releases
count columns are 0 if no LM(i) tasks are linked to this task assembly.)
Footer Section
Created On - Identifies the date and time when the report was generated.
LM(e) Task Summary Report

The LM(e) Task Summary Report briefly describes the current disposition of one or more LM(e)
task assemblies. The report contains one page for each task assembly that satisfies the report
selection criteria.
The report is sorted by group name, application name, release name and task assembly name. If
an LM(i) instance was defined for RM, this report will include information about related LM(i) tasks,
if any, along with report links for applicable LM(i) task, object, and time reports.
Linked reports
You can access the following reports from links within this report:
 LM(i) Task Objects Report (if a task link exists)
 LM(i) Task Activity Time Log Summary Report (if a task link and time data exist)
An example of the LM(e) Task Summary Report follows:
33
Header section
Ancestors - Identifies all the tasks from which the summarized task is descended. If the
assembly is not nested, this label does not appear.
Task - Identifies the specific task assembly that is summarized on this report page.
Task Description - Displays any descriptive text stored for the summarized task assembly.
34
Report parameters - Reflects the selection criteria choices used to generate this report, as
supplied on the Report Parameters dialog.
Details Section
This report section displays for you the information found in the task assembly properties settings,
and gives you an idea of the task scope by showing how many elements are associated with this
task.
Properties State - Describes the disposition of the summarized task assembly

(open, closed).
Attribute - A user-defined value that further describes this task
assembly.
Allow Part Instances - Indicates whether this task assembly can
include part instances as well as part definitions.
LM(e) Part Count - Indicates how many LM(e) parts are associated
with this task assembly.
LM(i) Object Count - Indicates how many LM(i) objects are associated
with this task assembly as the result of a task link. The count for the
root level task includes parts for all nested tasks; the count for a
nested task includes only its parts.
Associated LM(i) Task - Identifies an LM(i) task that is linked to this
task assembly.
Associated LM(i) Host - Identifies the IBM i server that hosts the LM(i)
instance where a task linked to this task assembly resides.
Associated LM(i) Library - Identifies the program library for the
associated task's LM(i) instance.
LM(e) Release Count - Indicates the number of LM(e) releases that
are associated with this task assembly.
LM(i) Release Count - Indicates the number of LM(i) releases that are
associated with the LM(i) task that is linked to this task assembly.
Note: Fields in this section containing LM(i) information do not
appear if no LM(i) task is linked.
Information for Associated LM(i) task task_name Section
Note: This report section is omitted if no LM(i) tasks are linked to this task assembly.
35
Properties This section describes an LM(i) task that has been deliberately
linked to the LM(e) task being summarized in this report. Much of
the information that appears in this section is similar to the
information for LM(e) tasks described in the Details section.
Additional fields are:
State - An indication of whether the status code reflects an
open or closed task.
Type - A code that helps further classify the nature of the
work to be done.
Status - A code that identifies the current disposition of the
task in the overall development workflow.
Priority - Identifies the level of importance assigned to the
task.
Manager - Identifies the person in charge of seeing that the
work is completed.
Keyword 1
Keyword 2
Keyword 3 - This line shows the contents of the three
keyword fields, if any. If these fields are blank, the line is
omitted.
Task statistics fields - These fields include information about
who entered the task and when; finish, closure, and re-open
dates; who requested the work and when; desired and
expected completion dates; and number of days open as of
the report date.
Hours If an LM(i) task link exists, this section contains information about
time logged against the LM(i) task associated with this LM(e) task
assembly. A link to the corresponding LM(i) Task Activity Time
Log Report also appears if data exists.
36
Releases Associated with Task Section
The LM(i) portion of this section is omitted if no LM(i) task link exists.
This section lists all LM(e) releases associated with the summarized task assembly, along with part
counts for each. Part counts are broken down by release and by release environment.
Notes:
 If a release's total part count differs from the sum of its environment part counts, it is
because the total part count for the release includes parts that are associated with the
release, but not resident in any release environment.
 The Allow Activity column applies only to LM(i) releases. If activity is allowed, then new
objects can be added to the linked LM(i) task and existing objects associated with the task
can be checked out. If activity is not allowed, then only promotion of LM(i) objects is
allowed.
If an LM(i) task link exists, then object counts for all applicable LM(i) releases also appear.
Each LM(i) release name links to its corresponding LM(i) Task Objects Report.
Footer Section
Created On - Identifies the date on which the report was generated.
LM(e) Release Reports

LM(e) Release Summary Report
The LM(e) Release Summary Report concisely describes the current state of a release. Included
are important release settings, key release activity, information about related releases, and a
summary of the environments in use. The report is sorted by group, application, release, and
version. One release appears on each report page.
Linked reports
This report contains links to these additional reports:

 LM(e) Java Compile Classpath Report (supplemental)
 LM(e) Task Summary Report
 LM(e) Activity Summary by Release Report
 LM(e) Task Assemblies Associated with Release Report
37
An example of the LM(e) Release Summary Report follows.
38
Header Section
Application - The qualified name of the application, in the format Group name/Application name.
Release - The qualified name of the release, in the format Release(Version) Type / (Level),
Type is either Base or Delta, and Level is a number that reflects the relationship of delta
releases to the base and to one another. (A base release is always level 0. Level information
does not appear for base releases.)
Description - The informational text associated with the release.
Promotion Path - A visual demonstration showing the flow of data between release
environments and across releases, consisting of:
 The environment abbreviations of all of the environments on this release's promotion path,
listed in order from lowest to highest, separated by arrows.
o A right arrow indicates the direction of flow in a promotion action within this release.
o An up arrow, if there is one, indicates a promote-to-parent promotion flow - that is, flow
between two or more releases of the same application. The arrow is followed by the
qualified environment name of the parent release's production environment, in the format
Environment Abbreviation(Version). This is the target environment for a promote-to-
parent action. (The Promote to parent action can occur only if the current release is a
delta release.)
 A diamond symbol between two environments in the promotion path — — means
that the originating environment does not allow promote-to-parent, even though the target
environment is on the logical promotion (and search) path.
 The path color is meaningful:
Red Red means no testing environments are defined (risky).
Yellow Yellow means one testing environment is defined (safer).
Green means two or more testing environments are defined (best

Green
practice).
39
Details Section
Properties table Summarizes key release characteristics. The left column of the
table describes key release rules in effect; the right column
describes rules in place for promoting when conflicts exist, and
the most recent change made that affects release contents.
Checkouts table The Checkouts table in the Details section presents checkout
statistics for the release. The left column of the table describes
key checkout-related rules in effect for the release; the right
column summarizes the current number of various kinds of
checkouts, and any existing or deleted acknowledgement
conditions.
Checkins and The Checkins and Promotions table in the Details section
Promotions presents information about release check-ins and promotions
table that have occurred to date. The left column of the table
describes key check-in and promotion rules that are in effect for
the release; the right column describes pending check-in or
promotion requests.
Task Summary The Task Summary table in the Details section provides
table information about the number of open and closed tasks
associated with the release.
40
Activity Log The Activity Log Summary table in the Details section describes
Summary table release activities.
Environments section
Properties The Properties table in the Environments section lists the release
table environments and presents key information about each. The first
environment row summarizes all individual developer environments that
contain checked out parts for the release. If this release is a delta release
that allows promote-to-parent activity, the last environment entry in the
table describes the release and version of the target promote-to-parent
environment.
The columns for displaying the key environment characteristics are:
 Environment - Identifies the environment's name abbreviation and
location code, in the format environment abbreviation(location
code).
 Type - Identifies the environment type.
 Shadowed - If filled, indicates that the environment has a shadow
location defined.
 Last Change - Identifies the date of the most recent activity that
changes the environment contents.
 Parts - A number that indicates how many parts are resident in the
environment.
Note: The part counts include parts that are marked for delete.
 Cnds - A list containing up to four single-character condition codes,
which indicate whether any Acknowledgement, Conflict, Failure, or
Request conditions currently apply to the environment.
 Tasks - The number of tasks that have associated parts resident in
this environment, and for which all parts are resident in at least this
environment.
Important! If a task has parts in more than one environment, the
task is counted only once. The count appears for the environment
that is lowest in the promotion path among the environments
containing a part instance. For example, if a task has parts in the
Integration, QA and Production environments, the task is counted
only once and the count appears in the Integration environment
column.
41
Related Releases section
Cross-release Notifications - Identifies any notification relationships for this release. The left
column lists releases that this LM(e) release notifies; the right column lists LM(e) releases that
notify this release, if any.
Associated LM(i) Release - If this LM(e) release is linked to an LM(i) release, the left column
describes the LM(i) release; the right column lists any additional LM(e) releases that are also
associated with that LM(i) release.
Footer Section
Report Parameters - Identifies the values used to generate this report, as supplied on the
Report Parameters dialog.
LM(e) Java Compile Classpath Report

This report is a supplemental report that is available from the Checkins and Promotions section of
the LM(e) Release Summary Report; it is accessible only by clicking a link within that report. The
link appears in that report as the last line item in the Checkins and Promotions column, if a
classpath has been defined for the release.
An example of the LM(e) Java Compile Classpath Report follows.
Header Section
Application - The qualified application identifier, in the form Group name/Application name.
Release - The qualified release identifier, in the form Release name(Version) Attribute.
42
Java Compile Classpath Directories Section
This section identifies all the folders where this application stores its user-defined Java classes and
packages for this release.
Footer Section
Report parameters - Identifies the values used to generate this report, as supplied on the Report
Parameters dialog.
Created On - Contains a time and date stamp that reflects when the report was generated.
LM(e) Activity Reports

About LM(e) Activity Reports
Note: If your database contains a large amount of activity information, it could take some time to
build LM(e) activity-related reports.
Each time a user of LM(e) performs some action that results in a change in the status of a part, an
activity log record is written to the LM(e) database. Activity log records identify the type of activity
(check out, promote, add, and so on), the user that performed the activity, the date and time the
activity occurred, and other details.
These LM(e) activity reports present detailed information recorded in the activity log:
 LM(e) Activities by Part
 LM(e) Activities by Release
 LM(e) Activities by Type
 LM(e) Activities by User
 LM(e) Promotion Activities for Environment by Part
These detail reports all present the same data; the difference is in the report selection criteria and
the sort order.
In addition to the detailed activity reports, there are also activity summary reports for LM(e):
 LM(e) Activity Summary by Release
 LM(e) Activity Summary by User
Note: Report Manager does not display LM(e) activity reports that contain no data.
LM(e) Activities by Part Report

The LM(e) Activities by Part Report does not appear in the list of available activity reports on the
RM main page. It is a supplemental report that is accessed only from the other LM(e) Activities by
<subject> reports, by clicking a part name.
Note: If the parent report from which you accessed this report used optional date parameters to
select information, then those same date parameters are used to select information for this report.
43
The report presents details of the activity recorded for a part associated with a release. The
information is sorted by the timestamp.
Report Links
If this report's LM(e) release is associated with an LM(i) release, then you can run the LM(i) Activity
Summary by Release by clicking the link in the Report Links section. If no LM(i) release is related,
then this link does not appear.
An example of the LM(e) Activities by Part Report follows.
The following report sections appear for each group/application/release combination whose parts
meet the selection criteria on the Report Parameters dialog.
Header Section
Application - The qualified application name, in the format Group Name/Application Name.
Release - Identifies the release to which the information in the Details section applies.
Report parameters - The group, application, release, part, and date information supplied on the
Report Parameters dialog that was used to select the information presented in this report.
Details Section
This section contains one detail line for each activity record associated with the selected part.
Timestamp - Identifies the date and time when the activity occurred, expressed in UTC time.
Activity - A 3-character code indicating the type of activity. (Refer to the LM(e) documentation
for a complete description of activity codes.)
Status - A three-digit status code indicating the completion state. A blank status indicates
success; FLD indicates failure; and HLT indicates that the user ended the activity. Refer to the
LM(e) documentation for a complete description of the error codes. (See Appendix J -
Resources.)
Part name - Identifies the part's path designator and part name.
Release - Identifies the release that contains the selected part instance.
44
From - The abbreviation of the environment where the part instance resided when this activity
started. A plus sign prefix indicates a developer environment.
To - The abbreviation of the environment where part instance resided when this activity ended.
A plus sign prefix indicates a developer environment.
By User - The profile name of the user that initiated the activity.
Within this report, you can:
 Hover the cursor over an activity code to see its text description.
 Hover the cursor over a release to see its fully qualified release name.
Footer section
Created On - A date and time stamp that identifies when the report was created.
LM(e) Activities by Release Report

The LM(e) Activities by Release Report presents details of the activity recorded for parts associated
with a release. There is one HTML report page for each selected group / application / release /
version combination. Within each release, the information is sorted by date and time.
Linked Reports
This report contains links to these supplemental reports:

 LM(e) Activities by Part Report, for each part (the part name is the link for this report);
 LM(i) Activities by Release Report, for an associated LM(i) release. (If no LM(i) release is
associated with this LM(e) release, the Report Links section does not appear.)
An example of the LM(e) Activities by Release Report follows.
The report contains one line for each activity record that meets the selection criteria.
Header section
Application - The qualified name of the selected application, in the format Group
Name/Application Name
45
Release - Identifies the selected release.

Report parameters - Identifies the group, application, release, version, and date values used to
select release activity log records from the database, as specified on the Report Parameters
dialog.
Details section
This report can be customized by including additional fields or excluding current fields. The shipped
report includes these field columns:
Activity - A three-character code that identifies the type of processing that resulted in an activity
log entry. (Refer to the LM(e) documentation for a complete description of activity codes. See
Appendix J - Resources.)
Status - Indicates whether the activity completed normally (blank), failed (FLD), or was halted
by the user (HLT).
Part name - Identifies the part that was processed during the logged activity.
Release - Identifies the release name and version number associated with the logged activity.
From - Identifies the environment in which the part instance processed resided at the beginning
of the logged activity. A plus sign prefix indicates a developer environment.
If the activity applies to a release but not an environment (such as the Activate activity), this
column contains only the version, without an environment. When both the From and To
environments are controlled AND in the same release, only the From environment name
includes the version.
To - Identifies the environment in which the part instance processed resided when this activity
ended. A plus sign prefix indicates a developer environment.
By User - The user profile name of the person who initiated the logged activity.
Comment - If a comment exists, it appears unlabeled, beneath the Release.
While viewing this report, you can hover the cursor over these data elements to see expanded
information:
 Timestamp (shows time to milliseconds);
 Activity code (shows the activity code description);
 Part name (shows the fully qualified part path and name);
 Release (shows the fully qualified name, in the format Group/Application/Release(Ver)).
Click on a part name to open its LM(e) Activities by Part report.
Additional Available Fields
In addition to the fields included in the shipped report as described above, the following fields are
excluded from the shipped report, but available for you to include in your own custom report:
46
Activity Code - Description - The activity code followed by text that explains what the code
means.
Status Code - Description - The status code, followed by text that explains what the code
means.
Group - The name of the product collection to which the application belongs.
Application - The name that represents the collection of software objects you are managing.
Release - The name associated with the application objects as they stand at a specific point in
time.
Version - The number associated with this edition of the application release.
Group/Application - The application name, qualified by the name of the group to which it
belongs.
From Version - The edition of the application release that applied at the beginning of the activity.
From Release (Version) - A combination of the release name and version number that applied
at the beginning of the activity.
From Environment Abbreviation - The short name of the environment that applied at the
beginning of the activity.
To Environment Abbreviation - The short name of the environment that applied at the end of the
activity.
Qualified Part Name - The full name of the part, including the path to its location.
Footer Section
LM(e) Activities by Type Report

The LM(e) Activities by Type Report presents details of the activities of a given type recorded for
parts processed in an application release. There is one HTML report page for each unique group /
application / release / version / type combination selected. The information is sorted by date and
time, and contains one activity type per page.
Linked Reports

 LM(e) Activities by Part Report, for each part included (the part name is the link);
 LM(i) Activities by Type Report, for an associated LM(i) release. (If no LM(i) release is
associated with this LM(e) release, this report link does not appear.)
47
An example of the LM(e) Activities by Type Report follows.
Header section
Release - Identifies the release associated with the selected activity log entry.
Activity - Identifies the activity code for the selected activity log entry.
Report parameters - Identifies the group, application, release, version, activity, and date values
used to generate this report, as supplied on the Report Parameters dialog.
Details section
by the user (HLT).
Release - Identifies the release associated with the logged activity.
48
information:
 Part name (shows the part's fully qualified path and name);
Activity Code - Description - Text that explains the activity code's meaning.
Status Code - Description - Text that explains the status code's meaning.
time.
belongs.
activity.
Qualified Part Name - The name of the part, qualified by its path location.
Footer Section
LM(e) Activities by User Report

The LM(e) Activities by User Report presents details of the activity recorded for parts processed by
a specific user. There is one HTML report page for each unique group / application / release /
version / user combination selected. The information is sorted by date and time.
49
Linked Reports

 LM(e) Activities by Part Report, for each part included (the part name is the link);
 LM(i) Activities by User Report, for an associated LM(i) release. (If no LM(i) release is
associated with this LM(e) release, this report link does not appear.)
An example of the LM(e) Activities by User Report follows.
Header Section
Release - Identifies the selected release.
User - Identifies the user whose activities appear in the report.
Report parameters - Identifies the group, application, release, version, user, and date values
Details Section
50
by the user (HLT).
Release - Identifies the release associated with the logged activity.
information:
 Part name (shows the part's fully qualified path and name);
Application - The name that represents the collection of software elements you are managing.
Release - The name associated with the application elements as they stand at a specific point in
time.
belongs.
51
activity.
Qualified Part Name - The name of the part, qualified by its path location.
Footer Section
LM(e) Activity Summary by Release Report

The LM(e) Activity Summary by Release Report shows the number of activity log records for each
release selected. For each group and application combination, the information is sorted by release
and version.
Linked Reports
The following reports are available from this report:

 The LM(i) Activity Summary by Type, if an LM(i) release is linked to any release selected for
this report. (If no LM(i) release is linked, then this link does not appear.)
 The LM(e) Activities by Type Report is available for any specific activity type that has activity
log records (the activity type code is the link).
An example of the LM(e) Activity Summary by Release Report follows.
52
Header Section
Application - The qualified application name, in the form Group name/Application name.
Release - Identifies the fully qualified release name, in the form Release name(Version)
Release type.
Report Parameters - Identifies the information used to generate this report, as supplied on the
53
Detail Section
The information that appears in the detail columns is as follows:

Activity - The three-character activity code associated with the activity log entry. Each activity
code that has records logged appears as a link so you can run its LM(e) Activities by Type
Report.
From - The environment abbreviation for the location where the part associated with this activity
resided when activity processing began.
To - The environment abbreviation for the location where the part associated with this activity
entry resided when activity processing ended.
Description - An explanation of the activity processing performed.
From - The earliest date and time when processing for this activity type occurred.
Until - The latest date and time when processing for this activity type occurred.
Count - The number of parts processed using this activity code for this release.
information:
 Date stamps (shows time to milliseconds, expressed in UTC time).
Footer Section
Created On - A date and time stamp that indicates when the report was generated.
LM(e) Activity Summary by User Report

The LM(e) Activity Summary by User Report shows the number of activity log records for each user
selected. For each group, application, release, and version combination, the information is sorted
by user. The report contains one page for each unique Group / Application / Release / Version /
User combination selected.
Linked Reports
Within this report, you can access these supplemental reports:

 LM(e) Activities by Type Report - to see the list of elements processed by that activity (the
activity code is the link).
 LM(i) Activity Summary by Type Report - to see activities for a linked LM(i) release. (This
link does not appear if no LM(i) release is linked.)
54
An example of the LM(e) Activity Summary by User Report follows.
Header Section
User - The user profile name of the person whose activities are summarized on this page.
Application - The qualified application name, in the form Group name/Application name
Release - The qualified release identifier, in the form Release name(Version) Type
Report Parameters - Identifies the information used to generate this report, as supplied on the
55
Detail Section
The information that appears in the detail columns is as follows:

Activity - The three-character activity code associated with the activity log entry. Each activity
code that has logged records appears as a link so you can run its Activities by Type report.
From - The environment abbreviation for the location where the part associated with this activity
resided when activity processing began.
To - The environment abbreviation for the location where the part associated with this activity
entry resided when activity processing ended.
Note: A string of three asterisks (***) in the From or To column means that the activity
occurred was logged in all of the release's controlled environments.
Description - An explanation of the activity processing performed.
From - The earliest date and time when processing for this activity type occurred.
Until - The latest date and time when processing for this activity type occurred.
Count - The number of parts processed using this activity code for this release.
information:
 Date stamps (shows time to milliseconds, expressed in UTC time).
Footer Section
LM(e) Promotion Activities for Environment by Part

The LM(e) Promotion Activities for Environment by Part Report presents a list of parts, in order by
part name, that have been promoted into a specified controlled environment.
These activity codes are considered by this report to be promotion-related activities:
 DLE - Delete from Environment
 PRM - Promote
 LOD - Loaded
 CKI - Checkin
 LBC - Checkin and Leave Checked Out
 PTP - Promote to Parent
56
 IMP - Import
 REP - Clone
 PRP - Promote to Parent
Linked Reports
Within this report, you can access the LM(i) Promotion Activities for Environment by Object report
for a linked LM(i) release, if a link is present for a release that was selected for this report.
An example of the LM(e) Promotion Activities for Environment by Part Report follows.
Header Section
Application - Identifies the selected application, in the format Group name/Application name.
Report parameters - Identifies the group, application, release, part, promote-to environment,
and date range values used to generate this report, as supplied on the Report Parameters
dialog.
Details Section
Part Name - Identifies the name of the part associated with the activity (fully qualified with its
location), and its part type.
Comment - Appears below the part name, and reflects the comment text associated with the
activity, if any.
Release - Identifies the release and version associated with the activity.
Activity - The code that identifies the activity.
Activity code - The text description that explains the activity code.
57
By User - Identifies the user profile name of the person who performed the activity.
From - Identifies the environment where the part instance resided at the beginning of the
activity. A plus sign prefix indicates a developer environment.
by the user (HLT).
time.
belongs.
activity.
Part Name - The unqualified name of the part.
Footer Section
LM(e) Permissions Reports

LM(e) Authority Change History Report
The LM(e) Authority Change History Report documents by group, application, and release any
changes in authority levels that have been recorded within the specified date range. For each
change, the report shows the authority setting before and after the change.
Note: Permissions for actions in LM(e) are defined in the Security Server instance associated with
LM(e).
An example of the LM(e) Authority Change History Report follows.
58
Header Section
Managing Product Instance - Identifies the instance of the product for which the report is being
generated (because Security Server can support multiple instances of LM(e)).
Report Parameters - Identifies the date range and release (expressed as
group/application/release) parameter values used to generate this report, as specified on the
Details Section
Date/Time - This column indicates the date and time that each authority setting was changed.
Role - This column identifies the particular role for which a change in authority has been
recorded.
59
Authority Level - This column shows the level at which each role authority is set. The authority
level can be derived from the product instance, application, release, or environment level.
Authority Setting - This column lists the available action for which the authority value has been
changed.
Before - This column indicates, for each authority level and setting, the specific authority before
the change.
After - This column indicates, for each authority level and setting, the specific authority after the
change.
Footer Section
LM(e) Permissions by Release Report

The LM(e) Permissions by Release Report documents which users and roles are authorized to
perform LM(e) functions in a given release. A filled box indicates that the user is authorized to
perform the associated function, and an empty box indicates that the user may not perform the
associated function.
LM(e).
An example of the LM(e) Permissions by Release Report follows.
Header Section
60
generated.
Application - Identifies the application associated with the release whose permissions are listed,
shown as group name/application name.
Release - Identifies the release associated with the listed permissions, shown as release
name(version).
Report Parameters - Identifies the group, application, and release parameter values used to
generate this report, as specified on the Report Parameters dialog.
Details Section
User - This column identifies the user whose permissions appear in the report. All permissions
appear across the row. User authorities can be set at the global, application, release, and
environment level. If authorities are set at the release level, they override application or global-
level settings. If authorities are set at the application level, they override global-level settings.
Product Instance /Group/App/Release (Version) Env- This column identifies the product
instance, group, application, release, version, and environment associated with the user and
role.
Role - This column indicates each user's assigned role for the associated permissions.
Permissions - Each column represents an LM(e) function with access that can be permitted or
refused for a user. The indicator box in the column is shaded if the user is permitted to perform
the associated function; it is white if the user cannot perform the associated function.
Note: Where there is no box, the authority is not appropriate for that managed object.
Footer Section
61
LM(e) Permissions by User Report

The LM(e) Permissions by User Report documents the permission settings for the role associated
with a user at the product instance, application, release, and environment levels. A filled box
indicates that the user is authorized to perform the associated function, and an empty box indicates
that the user is not authorized to perform the associated function.
LM(e).
An example of the LM(e) Permissions by User Report follows.
Header Section
generated.
User - Identifies the user whose activities appear in the report.
Group/Application - Identifies the group and application associated with the user whose
permissions are listed.
Report Parameters - Identifies the user, group, application, and release/version parameter
values used to generate this report, as specified on the Report Parameters dialog.
Details Section
62
Product Instance /Group/App/Release (Version) Env - This column identifies the product
instance, group, application, release, version, and environment associated with the user and
role.
Role - This column indicates the role from which this user's authority settings are derived for a
product instance, group, application, release, or release environment.
Permissions - Each column represents an LM(e) function that can be permitted or refused for a
user. The indicator box in the column is shaded if the user is permitted to perform the
associated function; it is white if the user is not authorized to perform the associated function.
No box means the authority is not appropriate for that level of role definition.
Footer Section
LM(e) Role Change History Report

The LM(e) Role Change History Report displays changes in assigned roles within the specified date
range for one or more users. For each change, the report shows the role assignment before and
after the change.
Notes:
 If a user's record has been deleted because the user is no longer active, you cannot select
that user in the Role Change History report parameters dialog. Their records still exist, but to
view those records, you must specify *ALL in the User field when you specify the report
parameters.
 When a user is added to the Security Server by the Copy User function, the roles assigned
at that time are not logged. Consequently, those roles do not appear on the LM(e) Role
Change History Report.
 Permissions for actions in LM(e) are defined in the Security Server instance associated with
LM(e).
An example of the LM(e) Role Change History Report follows.
Header Section
generated.
Report Parameters - Identifies the date range and user parameter values used to generate this
report, as specified on the Report Parameters dialog.
63
LM(i) Report Samples Report Manager User Guide
Details Section
Date/Time - This column indicates the date and time that each authority setting was changed.
User- This column identifies the user whose activities appear in the report.
Authority Level - This column shows the level (product instance, group, application, release, or
environment level) at which each role change occurred.
Before - This column indicates, for each user, the specific role assignment before the change.
After - This column indicates, for each user, the specific role assignment after the change.
Footer Section
LM(i) Report Samples

About LM(i) Report Samples
This section contains a brief description of each of the LM(i) report types. For a complete
description of each of the data items included in the reports, please consult the appropriate LM(i)
documentation. See Appendix J - Resources.
Detailed descriptions of each report follow.
LM(i) Task Reports

LM(i) Task Activity Time Log Summary Report
The LM(i) Task Activity Time Log Summary Report presents data regarding work done on an LM(i)
task. It shows time spent on a task by user and activity and by activity and user. The sort order is
task name, user name and time activity code; or task name, time activity code and user name.
Within each grouping, the data are sorted in ascending sequence by date. The activity codes are
user-defined and represent specific types of activity for which time was accrued to the task.
An example of the LM(i) Task Activity Time Log Summary Report is shown below:
64
Report Manager User Guide LM(i) Report Samples
.
Header Section
Task - Task name

Report Parameters - Task value used to generate this report, as specified on the Report
Parameters dialog.
Start Date - The earliest date activity was reported for this task
End Date - The latest date activity was reported for this task
Total Hours - The total hours reported for this task
Log Entries - The total number of time entries for this task
Users - The total number of users reporting time for this task
Activities - The total number of different time activity codes used for this task. (Note: In LM(i),
time activity codes are user defined.)
Total Hours Reported by User Section
This section of the report shows the hours reported against this task arrayed by time activity code
within user.
65
User / Activity - Hours are reported for each user against a task by time activity code. This
section lists the activity by time activity code for each user. The user name is shown followed by
an indented list of the time activity codes. Uncredited Accrued hours are the hours entered as a
lump sum on the LM(i) Task Budget panel.
Hours - The total number of hours reported for this combination of task, user and time activity
code.
First Activity - The date that activity was first reported for this combination of task, user and time
activity code.
Last Activity - The last date for which activity was reported for this combination of task, user and
time activity code.
Max Est % Complete - Each time a user enters activity against a task, he either enters an
estimated percent complete for the task or asks LM(i) to calculate the percent complete based
upon the total number of hours reported for this task divided by the hours budgeted for the
task. The value is recorded in each time activity record. The Maximum Percent Complete value
is the largest of these estimated percent complete values over all of the time activity entries for
this combination of task, user and time activity code.
Last Est % Complete - See Max Est % Complete, above. The Last Estimated Percent Complete
is the value found in the most recent time activity entry. If the field displays in red, it indicates
that the most recent value is less than the Maximum Estimated Percent Complete value. This
occurs when a user enters an Estimated Percent Complete value that is less than the Maximum
Estimated Percent Complete value; it indicates that the task is taking longer than estimated.
User Link - Each user name shown in this section is a link. If you click on the link, the LM(i) Task
Activity Time Log Report is produced. (See LM(i) Task Activity Time Log Report).
Total Hours Reported by Activity Section
This section of the report shows the hours reported against this task arrayed by user within activity
code.
Activity / User - The time entry activity code and user for which time entry activity is being
reported for this task. Uncredited Accrued hours are the hours entered as a lump sum on the
LM(i) Task Budget panel.
Hours - The total number of hours reported for this combination of task, time entry activity code
and user.
66
First Activity - The date activity was first reported for this combination of task, activity code and
user.
Last Activity - The last date for which activity was reported for this combination of task, activity
code and user.
Max Est % Complete - Each time a user enters activity against a task, he either enters an
estimated percent complete for the task or asks LM(i) to calculate the percent complete based
upon the total number of hours reported divided by the hours budgeted for the task. The value is
recorded in each activity log record. The Maximum Percent Complete value is the largest of
these estimated percent complete values over all of the activity log entries for this combination
of task, user and activity code.
Last Est % Complete - See Max Est % Complete, above. The Last Estimated percent Complete
is the value found in the most recent activity log entry.
Activity Code Link - Each activity code in this section is a link. If you click on the link, the LM(i)
Task Activity Time Log Report is produced for this combination of task and activity code. (See
LM(i) Task Activity Time Log Report.)
Footer Section
LM(i) Task Activity Time Log Report

The LM(i) Task Activity Time Log Report presents a detailed view of the time activity entries
reported for a task. The primary sort of the report is by task name. The entries for each task are
shown in descending time order, that is, most recent entry first.
An example of the LM(i) Task Activity Time Log Report is shown below.
Header Section
Task - The name used to identify the task.

Report Parameters - The task, user, and activity values used to generate this report, as
specified on the Report Parameters dialog.
67
Start Date - The first date on which time activity was reported for this task
End Date - The last date on which time activity was reported for this task
Total Hours - The total hours reported for this task.
Log Entries - The total number of time activity entries for this task.
Unique Users - The total number of different users for which hours have been reported for this
task.
Unique Activities - The total number of different time activity codes used in reporting hours for
this task. (Note: In LM(i), time activity codes are user defined.)
Detail Section
Date - The date the activity being reported occurred. Entries are sorted in descending date
order - that is, the most recent entry appears first.
User - The user for which the activity is reported.
Activity - The time activity code of the activity.
Hours - The number of hours reported in this time activity entry.
Estimated % Complete - Each time a user enters activity against a task, he either enters an
estimated per cent complete for the task or asks LM(i) to calculate the percent complete based
upon the total number of hours reported for this task divided by the hours budgeted for the
task. The value is recorded in each time activity record.
Comment - The comment entered by the user for this time activity entry.
Task - The identifier of the task associated with the activity.
Recorded Date/Time - The date and time when the activity took place.
Recorded By - The developer that performed the activity.
Activity Text - Text that describes the activity performed.
Footer Section
68
LM(i) Task Objects Report

The LM(i) Task Objects Report lists all the LM(i) objects that are associated with a task. In addition
to identifying the object, the release and environments where there exists an instance of the object
are also shown. The sort order of the report is group name, application name, release name and
task name. Objects for each task are shown in ascending, alphabetical order by object name.
An example of the LM(i) Task Objects Report is shown below.
Header Section
Task - Task Name

Application - Group Name/Application Name
Release - Release Name
Report Parameters - Group, application, release, task, and environment values used to
generate this report, as entered on the Report Parameters dialog.
Detail Section
Name - Object name.
Type - Object type.
Attribute - Object attribute.
Release - The qualified release name, in the format application abbreviation/release
abbreviation.
ENV - Environment location codes of the environments where an instance of the object is
resident. If the environment location code is in lower case, it indicates that the instance of the
object in this environment is not associated with the current task. If the environment location
code is in upper case, the instance of the object in this environment is associated with the
current task.
Text - Object description.
69
Task - The identifier of the task associated with the activity.
time.
Base Creation Date/Time - The date and time when the base application was created.
DVP - Identifies the location of the development environment.
ITG - Identifies the location of the integration environment.
QUA - Identifies the location of the test environment.
PDN - Identifies the location of the production environment.
Footer Section
LM(i) Task Summary Report

The LM(i) Task Summary Report gives a one-page summary of the current status of a task. The
sort order of the report is group name, application name, release name and task name. In addition
to the detail information about the task, the task hours information is also shown. A list of releases
with which the task is associated is included along with object counts by environment for each
associated release. If hours have been recorded for the task, a link to the LM(i) Task Activity Time
Log Summary report appears. Each associated release is also a link to the LM(i) Task Objects
Report for the associated release and task. Non-zero environment part counts are links to the LM(i)
Task Objects Report for that specific release environment.
An example of the LM(i) Task Summary Report is shown below.
70
Header Section
Task - The task identifier.

Task Description - A brief verbal summary associated with the task.
Report parameters - Reflects the parameter values used to obtain the report, as specified on the
Details Section
71
Properties This section shows you information that helps you evaluate task progress
and expectations.
State - The current state of the task (Open, Closed, Finished).
Type - A code that identifies what kind of work the task represents - for
example, a bug fix versus an enhancement.
Status - The A code that reflects the progress of the work being done to
satisfy the task.
Priority - A code that reflects a relative level of importance for the task.
Manager - The person in charge of seeing that the task is completed. If no
manager is assigned, the word "none" appears.
LM(i) Object Count - The number of LM(i) objects on which work for this
task has been done.
Task Added by - The user name of the person who entered the task into
the system.
Task Added - The date on which the requesting user entered the task.
Task Closed - If the task is closed, the date it was closed. If there is no
closed date, the value is spaces and the Closed Date label is suppressed.
Task Finished - If the task is finished, the date it was finished. If there is
no finished date, the value is spaces and the Finished Date label is
suppressed.
Task Re-opened - If the task has been re-opened after being closed, the
date it was re-opened. If there is no re-opened date, the value is spaces
and the Re-Opened label is suppressed.
LM(i) Release Count - The number of LM(i) releases containing objects
that are associated with this task.
Requested By - A name provided by the user who entered the task. If no
name is stored in the task definition, the word "none" appears.
Department - The company department to which the requesting user
belongs.
Wanted - A date that reflects when the requesting user would like the work
to be completed.
Expected - A date that reflects when management projects the work will
be done.
Days Open - A number that reflects the length of time the task has been in
the system without being resolved.
72
Hours If hours have been reported against this task, this section contains a link
to the LM(i) Task Activity Log Summary Report for this task.
Budgeted - The number of hours budgeted for this task.
Accrued - The total number of hours reported for this task.
Variance from Budget - The variance from the budgeted hours. If the
value displays in red, it indicates that the budget has been exceeded. This
occurs if an estimated percent complete is entered (not calculated) that is
lower than the calculated accrued budget variance.
Projected - The projected number of hours required to complete the task.
The value displays in red if the projected number of remaining hours
exceeds the budget.
Percent Accrued - Equals (Accrued Hours/Budgeted Hours) X 100. The
value displays in red if the result is more than 100, i.e., the accrued hours
exceeds the budget.
Estimated % Complete - An estimate of the percentage of the task that is
complete. It can either be calculated or entered by the user.
Releases Associated with Task Section
This section of the report has an entry for each release that is associated with the current task.
LM(i) Release - The release name, in the format Group Name/Application Name/Release Name
of any releases that are associated with the current task. Each release name in the list is a link
to that release's LM(i) Task Objects Report.
Object Counts by Release and Environment - The following columns of the associated releases
table reflect how many objects are affected and how they are distributed across the different
operating environments. Each environment count is a link to that environment's LM(i) Task
Objects Report. The Release count is a link to that release's LM(i) Task Objects Report.
Release - The total number of release objects that are associated with the current task.
DVP - The number of release objects that are associated with the current task and are located
in a developer environment.
ITG - The number of release objects that are associated with the current task and are located in
the release's integration environment.
QUA - The number of release objects that are associated with the current task and are located
in the release's quality assurance environment.
PDN - The number of release objects that are associated with the current task and are located
in the release's production environment.
Allow Activity Yes/No - A shadow box that Indicates whether activity is allowed for this release.
A filled box means Yes; a hollow box means No.
73
Footer Section
Created On - Identifies the date and time when the report was generated.
LM(i) Release Reports

LM(i) Active Tasks Associated with Release Report
The LM(i) Active Tasks Associated with Release Report gives the user an overview of the tasks
associated with a release. Only active (not finished) tasks are shown. For each task, the current
status of the task is shown along with the number of objects by environment. The sort order is task
name with group, application and release.
An example of the LM(i) Active Tasks Associated with Release Report is shown below.
Header Section

Report Parameters - The group, application and release selection criteria
Detail Section
There is one row in this section for each active task that is currently associated with the release. An
active task is a task whose status is either "open" or "closed". Tasks with a status of "Finished" are
excluded.
Task - The task name of the associated task. If the folder adjacent to the task name is yellow,
the task is closed. If the folder is green, the task is open.
Type - The task type code assigned to the task.
Stat - The status code assigned to the task.
Prty - The priority of the associated task.
CM - If the letters CM appear in this column, then the task is associated with a Community
Manager issue.
74
DVP - The number of this release's objects that are associated with this task and are resident in
a development environment. The value is displayed in red and includes retired objects.
ITG - The number of this release's objects that are associated with this task and are resident in
the release's integration environment. The value is displayed in red and Includes retired objects.
QUA - The number of this release's objects that are associated with this task and are resident in
the release's quality assurance environment. The value is displayed in red and Includes retired
objects.
PDN - The number of this release's objects that are associated with this task and are resident in
the release's production environment. The value Includes retired objects.
Rel - The total number of this release's objects that are associated with this task.
Other Rel Count - The number of other releases that are also associated with this task.
Other Rel Obj - The number of objects associated with other releases that are associated with
this task.
Created - The date the current task was created.
Age - The age of this task in days.
Due Date - The due date of this task.
Days Till Due - The number of days until this task is due.
Est % Comp - The estimated percent completion for this task.
Task Link
Each task name in the report is a link to the LM(i) Task Summary Report for the selected task. (See
LM(i) Task Summary Report.)
If you position the mouse over the task name, the task description is displayed.
Footer Section
LM(i) Release Summary Report

The LM(i) Release Summary Report provides a concise overview of the current status of a release.
Shown are the various settings on the release, key release activity, related releases and a summary
of the environments in use. The sort order is group, application and release, with one release per
report page.
An example of the LM(i) Release Summary Report is shown below.
75
Header Section

Release - Release Name (Release Abbreviation) | Release Type ("Base" or "Delta")
Unlabeled - Release Description
Promotion Path -
 The environment abbreviations of all of the environments on the promotion path for this
release.
 The "right" arrow indicates the direction of flow in a promotion action.
 If there is an "up" arrow it is followed by "Environment Abbreviation(Release Abbreviation)".
The environment abbreviation is the abbreviation of the production environment in the
parent release that would be the target of a promote to parent action. The release
abbreviation is the abbreviation of the parent release. (This can only occur if the current
release is a delta release.)
76
 Displayed in red if no testing environments are defined.

 Displayed in yellow if one testing environment is defined.
 Displayed in green if two testing environments are defined.
Details/Libraries Section
Release activated - If Yes, the release is activated. If No, the release is not activated. An
activated release is a release whose inventory of objects is ready to be used.
Allow changes to objects - If Yes, objects in this release may be checked out. If No, no check
outs are allowed.
Production libraries - The number of libraries defined for the production environment in this
release.
Release created - The date the release was created.
Last change date - The last date any object in the release was checked in or promoted.
Default OS target release - Defines the release of the IBM i Operating System to which
compiles/builds will be targeted. The value *APP means that the value for the release is taken
from the containing application.
Library group assignment - Defines the method by which library groups are assigned. The
possible values are:
 *MAP - Use the same library group assignment as the parent release
 *PROMPT - Library group assignment is manually assigned
 *PROGRAM - The name of a library group assignment program
Promote with conflict to - The environment abbreviation of the highest environment on the
promotion path an object can be promoted to when there is a release conflict condition on the
object. The value *NONE means no promotes are allowed when there is a release conflict
condition on the object.
Details/Checkouts Section
Multiple checkouts allowed - If Yes, more than one developer may have an individual object in
this release checked out at the same time. If No, each object in the release may be checked out
by at most one user.
Emergency checkouts authorized - If any LM(i) user has authority to perform emergency check
outs, the field is marked Yes. Otherwise, the field is marked No.
Comment required to checkout - If Yes, when performing a check out operation, the user must
provide a comment to be associated with the check out. If No, a comment is not required.
Task required to checkout - If Yes, for this release, each time a check out is performed, the user
must provide the task name of a task to associate with the checked out objects. If No, no task
name is required.
77
Request required to checkout - If Yes, objects in this release may be checked out only if there is
a current request checkout pending for the objects. If No, no request checkout is required.
Acknowledgement conditions deleted - The total number of acknowledgement conditions that
have been deleted by any user since this release was created.
Total normal checkouts - The total number of objects in this release that are currently or have
been checked out via a normal checkout (as opposed to an emergency checkout)..
Checkout request pending - The total number of objects in this release for which a checkout
request is pending
Current multiple checkouts - The total number of objects in this release for which there is a
multiple checkout condition.
Acknowledgements not deleted - The total number of acknowledgement conditions that have
not been deleted.
Total emergency checkout - The total number of objects in this release that are currently or
have been checked out via an emergency checkout.
Details/Promotions Section
Comment required to promote - If Yes, when performing a promote operation, the user must
provide a comment to be associated with the promote operation. If No, a comment is not
required.
Request required to promote to PDN - If Yes, objects in this release can be promoted to the
production environment only if a request promote is pending for the objects. If No, no request is
required.
Request required to install live to PDN - If Yes, objects in this release can be "installed live" to
the production environment only if a request install live is pending for the objects. If No, no
request is required.
Promote requests pending - The total number of objects in this release for which a promote
request is pending.
Install live requests pending - The total number of objects in this release for which an install live
request is pending.
Details/Task Summary Section
The number of tasks associated with this release whose task status is, open, closed and finished
and the sum of the three values. If the task counts are non-zero, there is a link to the LM(i) Active
Tasks Associated with Release Report.
Environments & Applications/Environments Section
78
Environments - This section lists all of the environments currently defined for this release. For
each listed environment, the columns are:
 Environment Abbreviation(Environment Location Code).
 Verify Status - Applies only to non-developer environments. The status can be either
"Verified", "Not Verified" or "Clean". The field is blank for developer environments. If the
Verify Status is "Not Verified", the text displays in red.
 Verify Date - Applies only to non-developer environments. If the Verify Status is "Verified",
the Verify Date is the date of the verification. The field is blank for developer environments.
 Objects - The number of objects resident in this environment irrespective of task.
 Conditions - The condition codes currently associated with this environment.
 Last Change - The date of the last change of any object in this environment.
 Tasks - The number of tasks currently associated with objects in this environment.
Important - If a task has objects in more than one environment, the task is counted only
once. The count appears for the environment that is lowest on the promotion path among
environments containing an instance of the object. For example, objects in a task are
resident in the Integration, QA, and Production environments. The task is counted only
once and that count is shown for the Integration environment because it is the lowest
environment on the promotion path containing an instance of the object.
 For the following 6 fields, each has one of three possible values:
o Yes - Indicated by a solid gray square.
o No - Indicated by a white square with a gray border.
o Select - Indicated by a square that is half white and half gray. If a field is marked as
"Select", the user is asked to choose when the promote action is invoked. "Select" is
valid only for the "CD" column.
 CP - Objects will be created in the environment upon promotion to the environment.
 CD - Objects that are dependents of the objects being promoted to the environment will be
created as part of the promote operation.
 AD - Objects being promoted to this environment will be auto-deployed.
 RP - A request to promote is required for promoting to this environment.
 RIL - A request is required for performing an install live from this environment.
 IL - An install live action will be performed for objects promoted to this environment.
Environments & Applications/Shared Applications Section
This release uses applications - A list of the applications that this release uses. If sharing is not
in effect, "None" is displayed.
Parallel Environments - If any applications are identified in the "This release uses applications"
field, Yes or No is checked to indicate whether test environments are included in the library list.
Applications that use this release - A list of the applications that use this release. If sharing is
not in effect, "None" is displayed.
79
Parallel Environments - If any applications are identified in the "Applications that use this
release" field, Yes or No is checked to indicate that test environments are included in the library
list.
Report Footer Section
Report parameters selections - Lists the group, application and release specified in the report
parameter set for this report.
Created On - A time stamp reflecting the date and time this report was created.
LM(i) Activity Reports

About LM(i) Activity Reports
Note: If your database contains a large amount of activity information, it could take some time to
build LM(i) activity-related reports.
Each time a user of LM(i) performs some action that results in a change in the status of an object,
an activity log record is written to the LM(i) database. Activity log records identify the type of activity
(check out, promote, add, and so on), the user who performed the activity, the date and time the
activity occurred, and other information.
These LM(i) activity reports present detailed information from the activity log:
 LM(i) Activities by Object Report
 LM(i) Activities by Release Report
 LM(i) Activities by Task Report
 LM(i) Activities by Type Report
 LM(i) Activities by User Report
 LM(i) Promotion Activities for Environment by Object
 LM(i) Promotion Activities for Environment by Task
 LM(i) Promotion and Checkout Activities by Object.
These detail reports present the same information; the difference is in the report selection criteria
and the sort order.
In addition to the detailed activity reports, there are also activity summary reports for LM(i):
 LM(i) Activity Summary by Type Report
 LM(i) Activity Summary by User Report.
LM(i) Activities by Object Report

The LM(i) Activities by Object Report presents details of the activity recorded for objects associated
with a release. There is one page in the report for each selected group, application and release.
Within each release, the data are sorted by object name, date, time, and user.
80
An example of the LM(i) Activities by Object Report is shown below.
Header Section
Application - The application name, in the format Group Name/Application Name.

Release - The release name.
Report Parameters - The group, application, release, object, object type, and date information
Details Section
There is one detail line in this report for each activity record that meets the selection criteria.
Timestamp - Date and time the activity occurred
Activity - A 3-character code indicating the type of activity. (Refer to the LM(i) documentation for
a complete description of activity codes.)
Error - A 2-digit error code for failed activities indicating the nature of the failure. A blank field
indicates a successful operation. Refer to the LM(i) documentation for a complete description of
the error codes. (See Appendix J - Resources.)
Object - Object name
Type - Object type
From Rel - The release name of the release the object was in at the beginning of this activity.
From Env - The environment abbreviation of the environment in which the object instance was
resident at the beginning of this activity. A plus sign preceding the environment abbreviation
indicates a developer environment.
81
To Env - The environment abbreviation of the environment in which the object instance was
resident at the conclusion of this activity. A plus sign preceding the environment abbreviation
User - The user name of the user that initiated the activity.
Version - The version number of the object instance at the conclusion of this activity.
Comment - The user-entered comment attached to this activity.
If you position the mouse over an activity code, a more complete activity code description appears.
If you position the mouse over an error code, a more complete description error code description
appears.
time.
Activity Description - Text that explains the nature of the activity performed.
Error Description - Text that explains the nature of the error.
Footer Section
LM(i) Activities by Release Report

The LM(i) Activities by Release Report presents details of the activity recorded for objects
associated with a release. There is one page in the report for each selected group, application, and
release. Within each release, the data are sorted by date, time and object name.
An example of the LM(i) Activities by Release Report is shown below.
Header Section
82

Report parameters - The group, application, release, and date information used to generate this
report, as supplied on the Report Parameters dialog.
Detail Section
indicates that the operation was successful. Refer to the LM(i) documentation for a complete
description of the error codes. (See Appendix J - Resources.)
Type - Object type
If you position the mouse over an activity code, a description of the activity code is displayed.
If you position the mouse over an error code, a description of the error code is displayed.
If you click on an object name, the LM(i) Activities by Object report is displayed for the selected
object. (See LM(i) Activities by Object Report.)
83
time.
Activity Description - Text that explains the activity code's meaning.
Error Description - Text that explains the meaning of the error code.
Footer Section
LM(i) Activities by Task Report

The LM(i) Activities by Task Report shows object activity by task. The data are sorted by task,
group, application, release, date, time, and user.
An example of the LM(i) Activities by Task Report is shown below.
Note: To conserve space, some of the detail records for this page of the report have been removed.
Header Section
Task - Task Name

Release - Group Name/Application Name/Release Name
Report Parameters - The task, group, application, release, and date information used to
generate this report, as entered on the Report Parameters dialog.
Detail Section
Note: To conserve space, some of the detail records have been removed for the above image.
84

Type - Object type
If you click on an object name, the LM(i) Activities by Release report is displayed for the selected
object. (See LM(i) Activities by Release Report.)
Task - The identifier of the task associated with the recorded activity.
time.
Footer Section
LM(i) Activities by Type Report

The LM(i) Activities by Type Report shows objects by activity type. For each group, application, and
release, the data are sorted on activity type, date, time, and user.
85
An example of the LM(i) Activities by Type Report is shown below.
Header Section

Report Parameters - The group, application, release, activity, and date values used to generate
this report, as entered on the Report Parameters dialog.
Detail Section
Type - Object type
86

time.
Footer Section
LM(i) Activities by User Report

The LM(i) Activities by User Report show object activity by user. For each group, application and
release, the data are sorted by user, date, and time.
An example of the LM(i) Activities by User Report is shown below.
Header Section

Report Parameters - The group, application, release, user, and date values used to generate
this report, as entered on the Report Parameters dialog.
87
Detail Section
Object - Object name.
Type - Object type.
time.
88
Footer Section
LM(i) Activity Summary by Type Report

The LM(i) Activity Summary by Type Report summarizes for each release the number of times each
activity type has been used. For each group, application, and release, the data are sorted on
activity type code.
An example of the LM(i) Activity Summary by Type Report is shown below.
Note: To conserve space, some of the detail records for this page of the report have been removed.
Header Section

Report selection parameters/Release - Group Name/Application Name/Release Name selection
criteria
Report Links Section
This section contains links to the listed reports.
89
Detail Section
Activity - A 3-character code that identifies the activity. If activity has been reported for this
activity code, the activity code is a link to the LM(i) Activities by Type Report for this activity
code. (See LM(i) Activities by Type Report.) For a complete description of the activity codes,
refer to the LM(i) documentation.
From - The environment abbreviation of the environment where the object instance resided prior
to the activity.
To - The environment abbreviation of the environment where the object instance resided
subsequent to the activity.
Description - A description of the activity code.
From - The earliest date for which activity was entered for this activity code.
Until - The latest date for which activity was entered for this activity code.
Count - The number of activity entries for this release and activity code. A value of zero
indicates that no activity has been reported for this release and activity code.
Footer Section
LM(i) Activity Summary by User Report

The LM(i) Activity Summary by User Report shows the number of activity log records for each user.
For each group, application, and release, the data are sorted by user.
An example of the LM(i) Summary by User Report is shown below.
90
Header Section

Report selection parameters/Release - Group Name/Application Name/Release Name selection
criteria
Created On - Date and time the report was created
Links Section
This section contains links to the listed reports.

Detail Section
There is one entry in this report for each user that initiated activity for the releases identified by the
selection criteria.
User - The user name of the user initiating the activity. The user name is a link to the LM(i)
Activities by User Report for this release and user.
Description - The description of the user.
From - The earliest date for which activity was entered for this user.
Until - The latest date for which activity was entered for this user.
Count - The total number of activity entries for this user.
Footer Section
91
LM(i) Promotion Activities for Environment by Object Report

The LM(i) Promotion Activities for Environment by Object Report presents a list of objects, in order
by object name, that have been promoted into a specified environment.
 ADD – Object added to release
 CRN – Object created non-resident
 CRT – Object created in environment
 DLE – Object deleted from environment
 LOD – Object loaded into PDN
 MGP - Object merged into parent release (reported in parent)
 PLV - Object promoted with leave resident option
 PRM - Object promoted
 PRP - Object promoted to parent release (reported in parent)
 ACT - Activation
An example of the LM(i) Promotion Activities for Environment by Object Report follows.
Header Section
Report parameters - Identifies the group, application, release, object, type, promote-to
environment, and date range values used to generate this report, as supplied on the Report
Parameters dialog.
92
Details Section
Object Name - Identifies the name of the object that was processed.
Object Description - The object description appears immediately below the object name on the
description line. If the description is blank, the information does not appear. (If there are no
descriptions, the description line does not appear.)
Comment - Appears below the object description on the comment line, and reflects any
comment text associated with the activity. If no comment text exists, the comment line does not
appear.
Object Type - The IBM i type associated with the object that was processed.
Release - Identifies the release associated with the activity.
Timestamp - Identifies the date and time when the activity occurred.
Activity - The code used to identify the nature of the processing performed.
Activity Description - A text description associated with the activity code.
Task - Identifies the task associated with the object that was processed.
Task Description - The explanatory text associated with the task appears below the task name
on the description line. If the description is blank, the information does not appear. (If there are
no descriptions, the description line does not appear.)
User - Identifies the user profile of the person who performed the activity.
From Rel - Identifies the release associated with the object instance at the beginning of the
activity.
From Env - Identifies the environment in which the object instance processed resided at the
beginning of the activity. A plus sign prefix indicates a developer environment.
To Env - Identifies the environment in which the object instance processed was placed during
the activity. Appears in the uncustomized report output only the output type is Excel.
Version - Identifies the object version number of the processed object.
93
Hover the cursor over the Error column to see a complete description of the code shown, if any.
Footer Section
LM(i) Promotion Activities for Environment by Task Report

The LM(i) Promotion Activities for Environment by Task Report presents a list of promotion-related
activities, by object name, for each task that has been promoted into a specified environment.
 CRN - Create non-resident
 CRT - Create in environment
 DLE - Delete from environment
 LOD - Load into PDN
 MGP - Object merged into parent release (reported in parent)
 PLV - Object promoted with leave resident option
 PRM - Object promoted
 PRP - Object promoted to parent release (reported in parent)
 ACT - Activation
An example of the LM(i) Promotion Activities for Environment by Task Report follows.
94
Header Section
Report parameters - Identifies the group/application/release, task, promote-to environment, and
date range values used to generate this report, as supplied on the Report Parameters dialog.
Details Section
95
Task name and description - Each set of activities is delineated by the name and description of
the task under which the set of objects was processed. If you requested *ALL objects AND
some objects were processed without a task, (no task) appears instead of a task name.
Comment - Any text comments the user entered when the activity was performed appear
immediately below the release.
Activity - The code associated with the activity during which the task was processed.
Object name - Identifies the object that was processed during the activity.
Object type - The IBM i type associated with the processed object.
Description - Appears immediately below the Object Name, and reflects the text description
associated with the object.
User - Identifies the user profile of the person who ran the promotion.
promotion.
Version - Identifies the object version number associated with the processed object.
Hover the cursor over the Error column to see the a complete description of the code shown.
Footer Section
LM(i) Promotion and Checkout Activities by Object

The LM(i) Promotion and Checkout Activities by Object Report presents a list of objects, in order by
object name, that have been checked out or promoted, for a specific controlled environment or for
all controlled environments in the designated release.
These activity codes are considered by this report to be promotion- and checkout- related activities:
Code Description Notes
ADD Object added to

release
CHK Object checked CHK is the only activity used for this report that is
out associated with a DVP environment. It appears in the
output when your Activity selection is *ALL
(regardless of your environment selection), and when
your Environment selection is *ALL.
96
Code Description Notes
CRN Object created

non-resident
CRT Object created in

environment
DLE Object deleted  Not available in the parameter selection list.

from environment
 Appears only when you set the Activity parameter
to *ALL.
 Used with From environment; all other activities
(except CHK) are used with To environment.
ECK Object checked

out with
emergency check
out
MGP Object merged (Reported in parent release.)

into parent release
PLV Object promoted

with leave
resident option
PRM Object promoted
PRP Object promoted (Reported in parent release.)

to parent release
RST Object restored

from archive to
development
Instead of selecting a single activity code or *ALL, you can select from three “group” codes. Each
group code includes activity codes that are pre-selected for this report.
Group Code Pre-selected Notes

Activity Code
*PRM • PRM • Promoted

• PRP • Promoted to parent
• PLV • Promoted with leave resident option
*CHK • ADD • Added to release
• ECK • Checked out with emergency checkout
• CHK • Checked out
• RST • Restored from archive to development
97
Group Code Pre-selected Notes

Activity Code
*CRT • CRN • Created non-resident

• CRT • Created in environment
An example of the LM(i) Promotion and Checkout Activities by Object Report follows.
Header Section
Report parameters - Identifies the group, application, release, object, type, activity code,
environment, and date range values used to generate this report, as supplied on the Report
Parameters dialog.
98
Details Section
Object Name - Identifies the name of the object that was processed.
Object Description - The object description appears immediately below the object name on the
description line. If the description is blank, the information does not appear. (If there are no
descriptions, the description line does not appear.)
Comment - Appears below the object description on the comment line, and reflects any
comment text associated with the activity. If no comment text exists, the comment line does not
appear.
Object Type - The IBM i type associated with the object that was processed.
Activity - The code used to identify the nature of the processing performed.
Activity Description - A text description associated with the activity code.
Task - Identifies the task associated with the object that was processed.
Task Description - The task's description text appears below the task name on the description
line. If the description is blank, the information does not appear. (If there are no descriptions, the
description line does not appear.)
User - Identifies the user profile of the person who performed the activity.
activity.
To Env - Identifies the environment in which the object instance resided at the end of the
promotion activity. A plus sign prefix indicates a developer environment (for example, for a
checkout action).
Version - Identifies the object version number of the processed object.
99
Hover the cursor over the Error column to see a complete description of the code shown, if any.
Total Objects - Identifies at the bottom of the report the total number of checked out or promoted
objects included in the report.
Footer Section
LM(i) Deployment Reports

LM(i) Deployed Object History by Release Report
The LM(i) Deployed Object History by Release Report provides a list of all objects installed at
target/locations for one or more designated releases over a given time period. These are all objects
in the application log that are associated with deployments whose activity code in the application
log is either Installed (INS) or Install Live (INL).
This report breaks by group/application/release, and is sorted by target, location, object name,
object type, and timestamp for each unique deployment set.
An example of the LM(i) Deployed Object History by Release Report follows.
100
Header Section
Application - Identifies the application name, in the format Group name/Application name.
Release - Identifies the release name.
Report Parameters - Identifies the group, application, release, target, location, and date range
parameter values used to generate this report, as specified on the Report Parameters dialog.
Details Section
101
Deployment Set - Appears in the subheading; identifies the number of the deployment set
associated with a group of deployed objects.
Profile - Appears in the subheading; identifies the name of the deployment profile used to
deploy the deployment set's objects. If n/a appears, the profile is associated with a deployment
set that no longer exists.
From Environment - Appears in the subheading; identifies the application environment from
which the listed objects were deployed.
Object Count - Appears in the subheading; identifies the number of objects associated with the
deployment set.
Target - The name of the target associated with the deployment set.
Location - The name of the location associated with the deployment set.
Object - The object name of the deployed object listed.
Object Type - The IBM i type code for the deployed object listed.
Version - The object version number of the deployed object listed.
Timestamp - Identifies the date and time that the deployed objects listed were installed.
User - Identifies the name of the user profile associated with the job that installed the set at the
location.
Error - If an error occurred with the object the code prints in this column. Reveal the error code
description by hovering the cursor over error code.
Footer Section
LM(i) Deployment Sets by Release Report

The Deployment Sets by Release Report provides information about the existing deployment sets
associated with a release for a given time period.
The report breaks by group/application/release, and is sorted by deployment set ID, and timestamp.
An example of the LM(i) Deployment Sets by Release report follows.
102
Header Section
Release - Identifies the selected release name.
Report Parameters - Identifies the group, application, release, target, location, and date range
report parameter values used to generate the report, as specified on the Report Parameters
dialog.
Details Section
103
Deployment set - Appears in the subheading, and identifies the number of the deployment set
associated with the deployment listed.
Profile - Appears in the subheading, and identifies the name of the deployment profile used to
perform the deployment listed.
Object Count - Appears in the subheading, and identifies the total number of objects associated
with the deployment set. (Note that some objects in a deployment might be installed on one
target/location, but not in other target/locations associated with the same set.)
Timestamp - The date and time of the deployment transaction. If not installed appears,
the set's last processed step precedes the Install step. If not backed out appears, the set's
last processed step precedes the Back Out step.
Target - The name of the target definition associated with the deployment set.
Location - The name of the location definition associated with the deployment set.
Status - The status of the deployment set at this target/location. Status codes are:
 New (NEW)
 Install requested (INR)
 Installed (INS)
 Installed, minor errors (INE)
 Install Failed (INF)
 Back out requested (BKR)
 Backed out (BKO)
 Back out minor errors (BKE)
 Back out failed (BKF)
 Finished (FIN)
Totals Section
Total deployment sets in release - Identifies the total number of deployment sets for the release
and time period.
Total deployments in release - Identifies the total number of deployments for the release and
time period. A deployment is defined as each unique combination of set/target/location. A
deployment set might include multiple deployments.
Total successful deployments in release - Identifies the total number of target locations for the
release and time period where deployments were successfully installed or backed out. (These
are records with status codes of INS, INE, BKO, BKE, FIN.)
Total failed deployments in release - Identifies the total number of target locations for the
release and time period where deployments failed during installation or backout. (These are
records that have a status code of INF, BKF.)
104
Total backed out deployments in release - Identifies the total number of deployments that were
backed out for the release/time period. (These are records that have a status code of BKO,
BKE.)
Total in-process deployments in release - Identifies the total number of deployments that were
in-process for the release/time period. (These are records that have a status code of NEW,
INR, BKR.)
Footer Section
LM(i) Permission Reports

LM(i) Permissions by Release Report
The LM(i) Permissions by Release Report documents which users and classes are authorized to
perform LM(i) functions in a given release or set of releases. The report also shows whether each
user’s permissions are derived from a user class and, if they are, where the associated class is
defined. A filled box indicates that the user is authorized to perform the associated function, and an
empty box indicates that the user may not perform the associated function.
Page breaks occur in the report at the conclusion of the list of users for each release.
An example of the LM(i) Permissions by Release Report follows.
Header Section
Application - Identifies the application associated with the release whose permissions are listed.
105
Release - Identifies the release associated with the listed permissions.

Report Parameters - Identifies the group, application, and release parameter values used to
generate this report, as specified on the Report Parameters dialog.
Details Section
Authority Type: User or Class & Definition Level - This column contains the name of the user or
user class. All authority settings appear across the row. It also shows the level at which the
user's authorities are set. User authorities can be set at the global, application, or release level.
If authorities are set at the release level, they override application or global-level settings. If
authorities are set at the application level, they override global-level settings.
Authority Source - This column indicates, for each user, the source from which this user's
authority settings are derived. Authority settings can be derived from a specific user record or
from a class record that is defined at the global application or release level.
If user authorities are set with a user class, this column also shows where the class is defined.
Most of the time, classes and users are defined at the same level. However, class authorities
can be defined at the global, application, and release levels. Users can also be associated with
classes at any level. For example, a class can be assigned authorities at the application level. A
user can be associated with that class at the release level. If the class is not defined at the
release level and the user is defined at the release level, the user's authorities will be derived
from the application-level class definition. In this case, the report would show the user's name
and "Release" in the Authority Type column, and class name and "Application" in the Authority
Source column.
Permissions - Each column represents an LM(i) function with access that can be permitted or
Footer Section
106
LM(i) Permissions by User Report

The LM(i) Permissions by User Report provides details for the authority records that exist for a user
and the actions that may be performed. It includes the source from which authorities are derived
and the level at which the authority is defined. The LM(i) entities for which the user or class has
permission settings are listed down the left side of the report, and the authority settings across the
top. A filled box indicates that permission is granted for the action; a blank box indicates that
permission is not granted.
This report prints one page for each user that matches the selection criteria specified.
An example of the LM(i) Permissions by User Report follows.
Header Section
Report Parameters - Identifies the user name and/or user class name parameter value and the
selected scope used to generate this report, as specified on the Report Parameters dialog.
Details Section
107
Appendices Report Manager User Guide
Authority Type: User or Class & Definition Level - This text identifies the user or user class
whose permission settings are summarized on this page. It also shows the level at which the
user's authorities are set. User authorities can be set at the global, application, or release level.
If authorities are set at the release level, they override application or global-level settings. If
authorities are set at the application level, they override global-level settings.
Authority Source: User or Class & Definition Level - This column indicates, for each user, the
source from which this user's authority settings are derived.
If user authorities are set with a user class, this column also shows where the class is defined.
Most of the time, classes and users are defined at the same level. However, class authorities
can be defined at the global, application, and release levels. Users can also be associated with
classes at any level. For example, a class can be assigned authorities at the application level. A
user can be associated with that class at the release level. If the class is not defined at the
release level and the user is defined at the release level, the user's authorities will be derived
from the application-level class definition. In this case, the report would show the user's name
and "Release" in the Authority Type column, and the class name and "Application" in the
Authority Source column.
User Authority Level - Global (*ALL), Named Application or Release - This column indicates
where the authority settings are enforced. The settings can apply globally, at the application
level, or at the release level. Release-level settings override application-level settings, and
application-level settings override global-level settings.
If the settings apply to all applications without specific application- or release-level settings, the
column contains *ALL/*ALL/*ALL. If the settings apply to all releases of an application without
specific release-level settings, the column contains the Group Name and Application Name,
followed by *ALL for the release. If the settings apply only to a specific release, the column
contains the group, application, and release names.
Permissions - Each column represents an LM(i) function with access that can be permitted or
Refer to Chapter 3, Defining Users, in the LM(i) Setup and Administration Reference, for
descriptions of the impact of each setting.
Footer Section
Appendices
This section contains supplementary information about Report Manager and related products. Use
this information to help you understand and achieve the best possible reporting results.
108
Report Manager User Guide Appendices
Appendix A - LM Concepts
In order to successfully use RM, you must be familiar with the following concepts for both LM(i) and
LM(e):
 Group - A collection of one or more applications.
 Application - A collection of one or more releases. By definition, every application must be
contained in a group.
 Release - The collection of parts or objects that, taken together, constitute a version of an
application. By definition, every release must be contained in an application.
 Environment - There can be multiple copies of an object while under development in LM.
For example, there can be a development copy, an integration copy, a quality testing copy,
etc. Each of these copies is said to be located in an environment. In RM, environments are
identified by their 3-character environment abbreviation. Environments are associated with
releases. Every release has at least one associated environment, known as the Production
Environment in LM(i). There can be up to 2 additional testing environments. Refer to the
LM(i) documentation for more information.
 Class - A class is a specific named set of defined permissions in LM(i), defined at the global,
application, or release level. Users assigned to a class have the specific LM(i) permissions
of that class. For example, there might be a class for Developers. Adding a user to the
Developer class automatically confers all of the permissions defined for the class to that
user. Assigning a user to a class makes it easier to assign permissions to groups of users
who perform similar job functions.
 Tasks - The description of a unit of work to be performed for the objects in a release. Each
task can be associated with zero or more releases.
 User - A person that is explicitly given access to use LM(i). The user must also be an
authorized user of the system hosting the LM(i) server. A user is uniquely identified by a
user name.
 Activity type - A 3-character code that indicates the type of activity that causes a particular
database record to be created. An example of an activity type code is "PRM" meaning
"Promote".
 Location - A named definition that describes local or remote IBM i computers in your network
that can receive deployments. Typically, users define one location for each physical or
logical (LPAR) system to which they want to deploy changed software.
 Target - A named definition that defines where deployed objects should be installed during a
deployment.
For a detailed discussion of each of these concepts, refer to the appropriate documentation for
LM(i). (See Appendix J - Resources.)
109
Appendix B - BIRT Overview

Report Introduction
BIRT is an Eclipse-based open source reporting system for web applications, especially those
based on Java and J2EE. BIRT has two main components: a report designer based on Eclipse, and
a runtime component that you can add to your application server. BIRT also offers a charting
engine that lets you add charts to your own application.
With BIRT, you can add a rich variety of reports to your application:
 Lists - The simplest reports are lists of data. As the lists get longer, you can add grouping to
organize related data together (orders grouped by customer, products grouped by supplier).
If your data is numeric, you can easily add totals, averages and other summaries.
 Charts - Numeric data is much easier to understand when presented as a chart. BIRT
provides pie charts, line & bar charts and many more. BIRT charts can be rendered in SVG
and support events to allow user interaction.
 Crosstabs - Crosstabs (also called a cross-tabulation or matrix) shows data in two
dimensions: sales per quarter or hits per web page.
 Letters & Documents - Notices, form letters, and other textual documents are easy to create
with BIRT. Documents can include text, formatting, lists, charts and more.
 Compound Reports - Many reports need to combine the above into a single document. For
example, a customer statement may list the information for the customer, provide text about
current promotions, and provide side-by-side lists of payments and charges. A financial
report may include disclaimers, charts or tables all with extensive formatting that matches
corporate color schemes.
The Anatomy of a Report

BIRT reports consist of four main parts: data, data transforms, business logic and presentation:
 Data - Databases, web services, Java objects all can supply data to your BIRT report. BIRT
provides JDBC, XML, Web Services, and Flat File support, as well as support for using code
to get at other sources of data. BIRT's use of the Open Data Access (ODA) framework
allows anyone to build new UI and runtime support for any kind of tabular data. Further, a
single report can include data from any number of data sources. BIRT also supplies a
feature that allows disparate data sources to be combined using inner and outer joins.
 Data Transforms - Reports present data sorted, summarized, filtered and grouped to fit the
user's needs. While databases can do some of this work, BIRT must do it for "simple" data
sources such as flat files or Java objects. BIRT allows sophisticated operations such as
grouping on sums, percentages of overall totals and more.
 Business Logic - Real-world data is seldom structured exactly as you'd like for a report.
Many reports require business-specific logic to convert raw data into information useful for
the user. If the logic is just for the report, you can script it using BIRT's JavaScript support. If
your application already contains the logic, you can call into your existing Java code.
 Presentation - Once the data is ready, you have a wide range of options for presenting it to
the user. Tables, charts, text and more. A single data set can appear in multiple ways, and a
single report can present data from multiple data sets.
110
Appendix C - Valid Values for Report Parameters

This topic describes the rules for entering acceptable values for each of the available categories of
report parameters.
Selection criteria parameters

This section describes the validity requirements for entries made in the selection criteria parameters
on the Report Parameters dialog.
Case sensitivity rules for selection criteria parameters
These case sensitivity rules apply when entering selection criteria values on the Report Parameters
dialog.
Case sensitive in:
Value type LM(i) LM(e)
Special values (such as *ALL, *NONE)
Specific and generic values, general X
Specific and generic values, Task parameter X
Group parameter:
 *ALL - Includes every group that is currently defined in the associated database.
 A specific group name selected from the field's drop-down list.
 Any subset of the currently defined groups in the associated database, defined by entering a
group name with or without wildcards.
 *NONE - Available for the LM(i) Task Summary Report only. This value provides a report of
tasks that are not assigned to any group, application, and release.
Application parameter:
 *ALL - Includes every application that is currently contained in the group(s) identified by the
Group parameter.
 A specific application name selected from the field's drop-down list.
 Any subset of the currently defined applications contained in the group(s) identified by the
Group parameter, defined by entering an application name with or without wildcards.
tasks that are not assigned to a group, application and release.
Release parameter:
 *ALL - Includes every release that is currently contained in the application(s) identified by
the Application parameter.
 A specific release name selected from the field's drop-down list.
 Any subset of the currently defined releases contained in the application(s) identified by the
Application parameter, defined by entering a name with or without wildcards.
111
tasks that are not assigned to a group, application, and release.
Version parameter:
 *ALL - Includes every version that is currently contained in the release(s) identified by the
Release parameter.
 A specific version name selected from the field's drop-down list.
 Any subset of the currently-defined version contained in the release(s) identified by the
Release parameter, defined by typing a name with or without wildcards.
Task parameter:
 *ALL - Includes every task that is currently associated with at least one of the releases
identified by the Release parameter.
 Any subset of the tasks associated with the release(s) identified by the Release parameter,
defined by entering a task name with or without wildcards.
Note: Task names are case sensitive in LM(e) reports.
Environment parameter:
 *ALL - Includes all environments associated with at least one of the releases identified by
the Release parameter.
 A specific environment abbreviation selected from the field's drop-down list.
 Any subset of environment abbreviations associated with any of the release(s) identified by
the Release parameter, defined by entering an environment abbreviation with or without
wildcards.
User parameter:
 *ALL - Includes every user defined in the associated database.
 A specific user name selected from the field's drop-down list.
 Any subset of the currently defined users, defined by entering a user name with or without
wildcards.
Type parameter:
 *ALL - Includes all activity types.
 A specific type code selected from the field's drop-down list.
 Any subset of currently defined activity types contained in the associated database, defined
by entering an activity type code with or without wildcards. For a complete list of the
currently defined activity type codes, see the appropriate documentation for LM(i) or LM(e).
(See Appendix J - Resources.)
Object Name or Part Name parameter:
 *ALL - Includes all objects or parts.
 Any subset of the object or part names in the associated database, defined by entering a
name with or without wildcards.
Object type parameter:
 *ALL - Includes all object types.
 A specific object type selected from the field's drop-down list.
112
 Any subset of the object types in the associated database, defined by entering an object
type with or without wildcards.
Date Parameters
This section describes entry requirements for the Date Parameters section's date range fields.
You must complete the selection criteria section before supplying values for the date fields.
From and
To parameters:
These fields are available when the Date Range radio button is activated.
 By default, the From date is initially set to a specific date, and the To date is set to the
current date.
 Use the Date Picker to select the From and To dates you want.
 Future dates are not allowed.
 Unrealistic month and day numbers are not allowed (for example, a month of 13 or a day of
32).
 Wildcards cannot be used in the date range fields.
 If you prefer to select a date rather than enter it, click the arrow at the right side of the fields.
Use the month and year selection arrows to navigate to a specific date, month, and year.
 Select Today in the lower left corner to select today.
 If you enter a date, use the format YYYY-MM-DD.
Previous X Days parameter:
This field is available when the Previous X Days radio button is activated.
 Up to three digits are allowed (a maximum of 999 days).
 Each digit must be a positive whole integer from 0 to 9.
 By default, the initial value is 0, which is interpreted as the current date, or today.
Output Control Parameters

This section describes validity requirements for the parameters that control your report output.
Output Type parameter
 You must choose one of the values in the dropdown list for this field.
Output Option parameter
 Either, both, or neither box can be darkened.
113
Appendix D - Report Options

An example of an LM(i) Activities by Type report is shown below.
When you invoke a particular report in RM with output type of HTML, the report is rendered in
HTML and displayed in your browser.
In addition to the formatted report, there are two optional outputs controlled by the Report
Parameters dialog, the Tool Bar and the Navigation Bar.
Report Tool Bar

The Tool Bar is shown at the top of the data display area, immediately above the Navigation Bar, if
shown. The Report Tool Bar is shown below.
The buttons on the tool bar are:
Toggle display of the Report Table of Contents on or off.
Run the report (regenerate the report with newly collected data).
Export the data contained in the report.
Export the report.
Print the report on the client.
Print the report on the server.
114
Report Table of Contents

Each report has an associated table of contents. The purpose of the table of contents is to list the
groups, applications, releases or tasks that are included in the report. The following is an example
of the LM(i) Release Summary report with the table of contents displayed.
You can control whether the report's table of contents is displayed by clicking the Table of Contents
toggle button , located on the Report Tool Bar. When visible, the table of contents is displayed
on the left side of the browser window. If the table of contents is displayed, clicking the Table of
Contents button once will remove the table of contents from the display. The remaining display is
shifted to the left to take up the space. Clicking the Table of Contents button again will cause the
table of contents to be re-displayed.
If you click on an entry in the table of contents, the report is positioned to the page that contains the
data associated with the selected table of contents entry.
Run the Report

Clicking this tool bar button will cause RM to re-populate the existing report to update any data that
has changed in the database. Upon completion, the updated report is re-displayed.
Export the Report Data

This option enables you to export the data that makes up the report to an external file. There are
numerous options that control what data is exported and the format of the exported data. See
Exporting Report Data.
Export the Report

This option enables you to export the report as formatted to an external file. See Exporting a
Report.
Printing a Report on the Client

This option enables you to print the current report to a printer on your computer, i.e., the computer
where the browser is running. When you click on the Print Report on Client button, the Print Report
dialog is displayed.
115
This dialog allows you to select the format of the printed report and the pages of the report that will
be printed.
HTML Print Format

This option of the Print Report dialog opens the current report in a new browser window and
invokes the default Print dialog for HTML documents. With the default print dialog, you can select
the printer to be used, set its properties and control which pages are printed. The printing is
performed by the browser by rendering the HTML used to create the report.
PDF Print Format

This option of the Print Report dialog converts the report to Adobe's Portable Document Format
(PDF) and opens it in a new browser window. PDF bookmarks are generated that match the entries
in the report table of contents. With this option, you can select how the PDF version of the report is
formatted. These choices correspond to the Page Display/Zoom Preferences settings in Adobe
Reader or Adobe Acrobat. The choices are:
 Auto - Use the setting defined in the document (Default)
 Actual Size - Print the document actual size
 Fit to Page - Scale the document to fit on the page where it is being printed
After opening the new browser window, the default Print dialog for PDF documents is opened. With
this dialog, there are number of options that control how the document is printed.
When customizing reports, the report title you supply might be truncated when generated as a PDF.
The field won't allow you to type more than 64 characters, but the amount that the PDF can actually
accommodate depends on the character width in a proportionally spaced font.
Note: In order for the PDF option to work, you must have Adobe Reader, Adobe Acrobat or an
equivalent installed on your client PC. If you do not have such a product installed, you can
download Adobe Reader from www.adobe.com.
Pages to Print
With this option, you can control which pages of the report are printed. The choices are:
 Print all pages
 Print only the current page (the page currently displayed in the browser)
 Print specified pages by entering specific page numbers (1, 3, 8, etc.) or a range of pages
(3-9).
When you have selected the desired options, click the OK button to launch the new browser
window.
116
If you click the Cancel button, control returns to the browser window containing the generated
report.
Printing a Report on the BIRT Server

This option enables you to print reports on the server where BIRT is running.
When you select the Print Report on the Server button, the Print Report on the Server dialog is
displayed.
The above dialog is a native BIRT dialog. In order for all of the above options to work correctly, the
server printer must be configured to support the options. For more information regarding the options
on this dialog, consult the BIRT documentation and/or your System Administrator.
Report Navigation Bar

Important - The contents of a page in an RM report is determined by control breaks based on the
selection parameters. Thus, pages as displayed in the browser do not necessarily correspond to
pages of a printed version of the report.
The Navigation Bar is shown at the top of the data display area, immediately below the Report Tool
Bar, if shown. An example of the Navigation Bar is shown below.
 The left side of the navigation bar shows the current page number and the total number of
pages.
 The four icons on the right side of the navigation bar control page-to-page movement:
Go to the first page of the report (disabled if the current page number is 1)
Go to the previous page of the report (disabled if current page number is 1)
117
Go to the next page of the report (disabled if current page is the last page)
Go to the last page of the report (disabled if current page is the last page)
 In the Go To Page area, you may enter a page number and then click
the green arrow. The report is positioned to the requested page. The page number you
enter must be in the range of 1 to the maximum number of pages in the report. If not, an
invalid page number error message is displayed.
118
Appendix E - Accessing the LM Databases via Report Manager

Important - This version of RM can access databases for the following versions of LM:
 LM(i) 8.1 and higher on i5/OS 6.1 or higher
 LM(e) 6.3A with Security Server 2.3A (IBM i)
 LM(e) 6.4 with Security Server 2.3B (IBM i)
 LM(e) 6.3B and higher with Security Server 2.3A (Linux)
To successfully use RM, each user must have access to the LM(i) and/or LM(e) database(s), along
with Security Server. In the current versions of these products, "general public" users have read
access to the database. Under typical circumstances, then, users can access RM if they:
 Have a supported web browser (see Technology);
 Have network access to a Windows computer where the RM application, Apache Tomcat,
Java Runtime Environment, and BIRT are installed;
 Have network access to the LM(i) and/or LM(e) server(s);
 Have network access to Security Server (only needed for LM(e) Permissions reports); AND
 Know the correct port number for accessing the RM application in the Apache Tomcat
server location.
Important - Because of the sensitive nature of the data in the LM(i) and LM(e) databases, Rocket
Aldon strongly suggests that users not be allowed to use RM over the Internet. Users should be
restricted to the facility's intranet. If remote access is required, we strongly recommend that it be
provided via a virtual private network (VPN) or equivalent.
The connection between RM and the database is provided by the Windows Service component of
Apache Tomcat. If a facility desires more robust access control, the security capabilities of Apache
Tomcat can be used. The setup and use of Apache Tomcat security is beyond the scope of this
document. For more information, visit http://tomcat.apache.org.
119
Appendix F - Exporting from RM

As a native function of BIRT, once you produce a report, you are able to export either the report
image itself or the data contained in the report. The following is a brief description of the steps
involved in exporting data and reports. For a complete description, please refer to the BIRT
documentation.
Exporting Report Data

The Export Data function enables you to export to a file on your local PC some or all of the data that
is contained in the associated report, i.e., the report from which the export operation was launched.
The Export Data function should not be confused with the Export Report function. (See Exporting a
Report.)
If you select the Export Report Data option of the Report toolbar (see Appendix D - Report Options),
the Export Data dialog is displayed.
The export operation exports some or all of the data fields defined by a result set. A result set is a
named collection of the fields available in a report. The available result sets are defined by Rocket
Aldon.
Available Result Sets
The available result sets for the associated report are listed in the drop-down list of the Available
Result Sets combo box. The combo box is initialized to a default result set that contains all of the
fields contained in the report. To select a different result set, click the down arrow of the combo box
and select the desired result set from the drop-down list.
Available Columns
The Available Columns list box lists the report fields that are associated with the result set that is
currently selected in the Available Result Sets combo box. You may export all or any subset of the
available columns of a report set.
120
Selected Columns
The Selected Columns list box lists the fields that will be exported in the current export operation.
To identify the columns that will be exported, you must "move" a column name from the Available
Columns list to the Selected Columns list, as follows:
 If you click the Add All button , all columns currently in the Available Columns list are
added to the Selected Columns list.
 To move individual columns from the Available Columns list to the Selected Columns list,
select the column name(s) in the Available Columns list and click the Add Selected button
.
 If you want to remove all of the columns in the Selected Columns list, click the Remove All
button .
 To remove selected columns from the Selected Columns list, select the column name(s) and
click the Remove Selected button .
 Once you have finalized the columns in the Selected Columns list, you can change the order
in the list by selecting a column name and using the Up button or the Down button .
 When you perform the export, the top to bottom order of the fields in the Selected Columns
list becomes the left to right order of the fields in the output file.
Export Format
Currently, the only export format supported is "csv" which is short for "comma-separated values". In
this format, each record in the file is a continuous string of characters with the individual fields
separated by a defined separator character (See Separator, below). If the data are from a multi-row
table, there is one record in the file for each row of the table. This export format is suitable for
importing into Microsoft Excel.
Output Encoding
The Output Encoding radio buttons control the character set that is used to encode the data in the
output file. The default is UTF-8. If you select the Other radio button and leave the associated edit
box blank, the encoding will be the default for the local PC. For information regarding values that
may be specified for "Other", see the BIRT documentation.
Separator
The Separator combo box enables you to select the separator character that will be used in the
"csv" file. The choices are:
 Comma (Default) - Decimal 44, Hexadecimal 2C
 Semicolon - Decimal 59, Hexadecimal 3B
 Colon - Decimal 58, Hexadecimal 3A
 Vertical Line - Decimal 124, Hexadecimal 7C
 Tab - Decimal 9, Hexadecimal 9
Contents of the Output File
The output file will contain one record for each row in the SQL table that is defined by the selected
result set. In addition, the first record in the output file will contain a list of the column names
appearing in the file. The column names are placed in the record in the same way as the data, i.e.,
as a continuous string of characters with the individual fields separated by the separator character.
121
Export Column's Data Type

For a description of this check box, see the BIRT documentation.
Export Column as Locale Neutral
For a description of this check box, see the BIRT documentation.
Exporting the Data

After making the desired selections, invoke the export operation by clicking the OK button. The
default name of the export file is the report name with the extension ".csv" appended to the end.
The specific download behavior depends upon which browser you are using. In either case, the
dialogs presented are self-explanatory and should not present a problem to any experienced user.
Exporting a Report
The Export Report function enables you to export an image of the report as it is displayed in the
browser to an external file on your PC. Exporting a report should not be confused with exporting the
report data. (See Exporting Report Data.)
When you select the Export Report button of the Report tool bar, the Export Report dialog is
displayed.
Export Format
The format of the exported report can be compatible with the following:
 Microsoft Word (Default)
 Microsoft PowerPoint
 Microsoft Excel
 PostScript
 Adobe PDF
To select one of the export formats, click the down arrow of the Export Format combo box and
select from the drop-down list.
Pages
You can export some or all of the pages contained in the report. The choices are:
 All pages
 The current page (The page currently displayed in the browser.)
 Individual pages or a range of pages (Examples: 3-6 or 1,3,6)
122
Select your choice by clicking one of the radio buttons and, if necessary, entering the page
numbers of the pages to print.
Size Radio Buttons
The size radio buttons are enabled for export formats PowerPoint, PDF and PostScript. The
choices are:
 Auto
 Actual Size
 Fit to Whole Page
The selection is passed to the individual export target program where the effect is the same as if
you made the selection from within the application program.
After making the desired selections, invoke the export operation by clicking the OK button. A
standard Windows File Download dialog is displayed.
From the File Download dialog, you can:

 Open the file in the selected application
 Save the file to your local PC
 Cancel the export operation
The file name is assigned by RM based on the report type. The file extension is assigned based on
the export format:
 doc - Microsoft Word
 xls - Microsoft Excel
 ppt - Microsoft PowerPoint
 pdf - Adobe Portable Document Format
 ps - PostScript
If you select the Open button on the File Download dialog, the application invoked is the default
Windows application assigned to the "open" operation for the file type. In this case, the file type is
defined by the file extension. This will normally be the same application that is invoked by double-
clicking on a file name in the Windows Explorer.
If you select the Save button on the File Download dialog, a standard Windows Save As dialog is
displayed.
123
On this dialog, you can select the folder where the file will be saved and, if desired, change the file
name. After making any changes, click the Save button to begin the download of the file. While the
file is downloading, a Download Progress dialog is displayed, followed by a Download Complete
dialog.
On this dialog, you can:

 Open the downloaded file (Open button)
 Open the folder in Windows Explorer where the file was saved (Open Folder button)
 Close the dialog (Close button)
If you select the Open button, the same action occurs as for the Open button on the File
Download dialog, as described above.
124
Appendix G - Entering/Updating the RM License Information

The server component of Report Manager is licensed. There are two types of licenses:
 Test Drive Trial License
 Permanent License
A Test Drive Trial License has a fixed expiration date, whereas a Permanent License does not
expire. As the last step of installing the server component of Report Manager, you must enter a
license validation string before you will be able to use the product. If you are taking RM for a "test
drive", you will be provided a license validation string that enables RM for a fixed period of time. If
you have purchased RM, you will be provided a validation string for a Permanent License. The
validation string is sent via e-mail after downloading the installation package from the Rocket Aldon
web site (http://aldon.rocketsoftware.com). Refer to the Report Manager Installation Guide for
details.
Entering License Information for the First Time

As the last step in the installation procedure of the RM server, you will be prompted to enter the
validation string. For this procedure you must be logged on to the RM server computer with a user
name that has administrator rights.
 Upon completion of the installation procedure, The Enter Validation Information dialog is
displayed. If you cannot locate the validation string, click the Cancel button. When you have
the validation string, you can proceed as described below in Updating License Information.
 Enter the validation string exactly as provided by Rocket Aldon. It consists of 3 sets of 4
alphanumeric characters and one set of 2 alphanumeric characters. Alphabetic characters
are always entered in upper case. Click the Next button.
 If you click the Next button without entering the validation string, the following message is
displayed.
 If you do not have the validation string available, click the Close button .
125
 If you click the OK button, the Enter Validation Information dialog is redisplayed.
 If the validation string is invalid or you entered the string incorrectly, the Validation Error 300
error message is displayed.
 Click the OK button. The Enter Validation Information dialog is redisplayed. If you have
entered the validation string correctly and you still get the error, call the telephone number
shown in the message.
 If the entered validation string is valid, the installation procedure completes with no further
messages.
Updating License Information

If you are not certain which type of license you have, either contact your Rocket Aldon Account
Manager or see Report Manager Licensing.
There are three cases where you may need to update the license information:
 You could not locate the validation string at the time you installed the RM server and want to
enter it now
 You have a Test Drive Trial License, the expiration date is nearing or past and you have
obtained an extension of the expiration date from Rocket Aldon
 You have a Test Drive Trial License and you want to change it to a Permanent License
To update the license information, do the following:
 Log on to the Windows server computer that is hosting the RM server component with a
user name that has administrator authority.
 Change the directory to C:\Aldon Report Manager Report Categories.
 Execute the batch file LicenseRM.bat. Note: Depending on the Windows settings for this
computer, you might need to run as Administrator.
 The Enter Validation Information dialog is displayed.
 Enter the validation string exactly as provided by Rocket Aldon. It consists of 3 sets of 4
alphanumeric characters and one set of 2 alphanumeric characters. Alphabetic characters
are always entered in upper case. Click the Next button.
 If you click the Next button without entering the validation string, the following message is
displayed.
126
 If you do not have the validation string available, click the Close button .
 If you click the OK button, the Enter Validation Information dialog is redisplayed.
 If the validation string is invalid or you entered the string incorrectly, the Validation Error 300
error message is displayed.
 Click the OK button. The Enter Validation Information dialog is redisplayed. If you have
entered the validation string correctly and you still get the error, call the telephone number
shown in the message.
 If the entered validation string is valid, the installation procedure completes with no further
messages.
127
Appendix H - Known Issues

In this release of Report Manager, we are aware of the following issues:
Browser Settings
A variety of Web browser settings control how your Web browser behaves during use. Browser
settings associated with tabs and cookies can in turn affect the way RM behaves.
Tabs
When RM opens a new browser window, it will either invoke a new instance of the browser or open
a new tab in the existing browser instance. Because both supported browsers, Mozilla Firefox and
Internet Explorer, support multiple tabs, and because you can indicate in your browser's settings
how you want the browser to behave when opening a new window, the application's behavior
depends on those browser settings. Consult the documentation for the browser you are using to
adjust the settings to your preference.
Cookies
The security settings in Internet Explorer can affect the display of graphics in RM. For IE-8, if you
have the security level set above "High" or for IE-7 if cookies are not allowed, certain graphics will
not display properly in the RM windows. Note that this is an issue with BIRT that is beyond the RM
application's control.
Unpredictable Results Using the Microsoft PowerPoint Output Option

Some RM reports must process very large quantities of data in your LM(e) database. For example,
an LM(e) report that includes all activities in all releases could be very large, depending on your
usage of LM(e) over time. If the data volume is sufficiently large, you might encounter errors like
these:
 A server error, in which your report exceeds the Java processing space available on your
RM server; OR
 A Microsoft PowerPoint error related to the size of the HTML page.
This is particularly true of, but not limited to, use of the PowerPoint output type. You might also
notice that even for smaller reports, PowerPoint will render much more slowly than other output
options. These issues result from factors that are beyond the RM application's control.
Report Title Affects Export to Microsoft Excel

If you specify a custom report title that contains special characters OR that is overly long, then
exporting to Microsoft Excel may fail because BIRT attempts to use the report title text for the Excel
sheet name. If you will export report data to Microsoft Excel, avoid special characters, and keep the
title short. (We suggest 30 characters or fewer.)
128
Appendix I - Licenses
Disclaimer - The information contained in this appendix was compiled from multiple sources. While
it is believed to be accurate at the time of publication, Rocket Software makes no warranty of any
kind with regard to the information shown herein.
Licenses
Report Manager , Lifecycle Manager (Enterprise Edition), and Lifecycle Manager (IBM i Edition) are
used in accordance with the Rocket Software License. RM uses third party products or libraries, in
accordance with their respective licenses. The full text of the Rocket Software License and a
complete list of third party products and their license information appears in the RM install location,
in the following file:
C:\Program Files\Aldon\AldonReportManager\Licenses\license.txt
(This path reflects the default install location. If the install location was changed from the default
value at installation time, substitute your install location for the default path shown above.)
License Agreement
This software and the associated documentation are proprietary and confidential to Rocket
Software, Inc., are furnished under license, and may be used and copied only in accordance with
 Your use of Rocket software, documentation, information and other Rocket content
(collectively, “Content”) is subject to you or your employer entering into a signed license
agreement (“Agreement”) with Rocket governing how the Content may be used by you.
 If you or your employer have not executed such an Agreement with Rocket covering your
use of the Content, please do NOT continue installing or using the Rocket software or other
Content.
 Plug-ins, Plug-in fragments, and other features also constitute Rocket Content and are also
governed by the Agreement, whether or not expressly referenced therein.
 Any conflict between any online or other license agreement between you and Rocket and
the signed Agreement shall be resolved in favor of the signed Agreement.
 Your rights to use the Content may not be assigned or transferred to any other user without
Rocket’s express prior written consent.
 Rocket software and other content is also protected by United States copyright laws and
international treaties. Any unauthorized use of the software and other copyrighted content
can subject you to statutory damages running to US $150,000 per infringement, and
possibly to criminal penalties.
129
Appendix J - Resources
The information in this online help system is also available as a user guide in PDF format from the
Rocket Community (http://www.rocketsoftware.com/support).
RM
For information about installing or upgrading RM and about applying PTFs, refer to your RM
Installation Guide.
LM(e)
If you are an LM(e) user, you can access the LM(e) on-line help. For more information about LM(e),
the following resources are also available in PDF format on the Rocket Community
(http://www.rocketsoftware.com/support):
 LM(e) User Guide: Introduction and Overview
 LM(e) User Guide: How Do I ... ?
 LM(e) User Guide: Setup and Special Topics
LM(i)
For more information about LM(i), the following resources are available for download from the
Rocket Community (http://www.rocketsoftware.com/support).
 LM(i) Features and Capabilities Reference
 LM(i) User's Guide
 LM(i) Daily Operations Reference
 LM(i) Setup and Administration Reference
 LM(i) Object Deployment Reference
 LM(i) Task Tracking Reference
 LM(i) General Topics Reference
 LM(i) Additional Interfaces Reference
In addition to the above documents, if you are an LM(i) user, you can access the LM(i) on-line help.
Accessing Documentation on the Web Site

To access the product documentation provided on the Rocket Community (including the User Guide
form of this help system), you must register to obtain a user name and password.
Adobe PDF
All documentation available for download from the Rocket Community is provided in Adobe Acrobat
Portable Document Format (PDF). To use them, you must be able to view and/or print PDF
documents. One solution is to download the Adobe Reader from the Adobe web site
(www.adobe.com). Any Adobe Reader version 6.0 or later should work.
130
BIRT Documentation
For more information about Eclipse/BIRT, see http://www.eclipse.org/birt/phoenix/intro/. There are
also several BIRT reference books available. The following are two examples:
 BIRT: A Field Guide to Reporting (2nd Edition)(Eclipse Series) by Diana Peh, Nola Hague
and Jane Tatchell
 Practical Data Analysis and Reporting with BIRT by John Ward.
Tomcat Documentation
For more information about Apache Tomcat, see http://tomcat.apache.org/.
131
Appendix K - Customizing the Report Logo

You can replace the logo that appears on generated reports with your own company logo.
To do this, replace the logo file on your RM server in the location described below with your own
logo file. The file you provide must have the following characteristics:
File Name: report_logo.png
Dimensions: 177 pixels x 34 pixels
Resolution: 72 dpi
Location: drive:\Aldon Report Manager Report

Categories\_Aldon Supplied Report
Designs\images
where drive represents the drive letter associated with the drive
or partition where the software is installed. (This value is set
during the install procedure.)
Note: Following these instructions changes the logo that appears on your generated reports, but
does not change the product logo that appears on the RM home page.
132
Report Manager User Guide Glossary
Glossary
A
Activity Type: A code that indicates the type of activity that caused a database record to be
created
Application: A collection of one or more releases
B
BIRT: Acronym for Eclipse Business Information Reporting Tool
C
Client: The computer hosting the web browser used to run Report Manager
E
Environment: A version of an object
Export: Copying either the report image or the report data to an external file
G
Group: A collection of one or more applications
L
License: Report Manager is licensed. There are two types of licenses, Test Drive Trial License
and Permanent License. A Test Drive Trial License has a fixed expiration date while a
Permanent License does not expire.
LM(e): Rocket Aldon Lifecycle Manager (Enterprise Edition)
LM(i): Rocket Aldon Lifecycle Manager (IBM i Edition)
P
PDF: Adobe Portable Document Format
R
Release: A collection of objects that, taken together, constitute a version of an application
Report: Any of the predefined report type and a specific set of report parameters
Report Category: A collection of report folders and reports. RM is shipped with one report
category defined. Users may define up to 19 additional categories.
Report Folder: A container for sub-folders and reports
Report Manager: A web-based application for creating reports using LM(i) and LM(e) data
133
Glossary Report Manager User Guide
Report Parameters: A set of values that serve to select a subset of data from the database as
well as define the output options
Report Type: Any of a set of pre-defined report formats included with Report Manager
Result Set: A subset of the available data fields in a report that will be exported
S
Security Server: Rocket Aldon Security Server provides security services such as user
authentication and user authorization for Rocket Aldon products.
Server: Depending on context, this might refer to the computer hosting the server portion of
LM(i) or LM(e), OR it might refer to the Report Manager server.
T
Task: The description of a unit of work to be performed on the parts or objects in a release
TOMCAT: Web page server for Web-based applications
U
User: A person that is authorized to use LM(i)
V
Validation String: A string of alphanumeric characters used to validate the license for RM. It
consists of 3 sets of 4 alphanumeric characters and 1 set of 2 alphanumeric characters
W
Wildcard: A special character (%) that can represent any number of characters in a match
string
134
Report Manager User Guide Index
Index
About Activity Reports - LM(e), 43 Customizing the report logo, 132

About Activity Reports - LM(i), 80 Databases, Accessing, 119
About LM(e) Report Samples, 32 Deployment Reports, 100, 102
About LM(i) Report Samples, 64 Dialog, New Folder, 29
About Report Storage Maintenance, 30 Dialog, Save, 28
About Rocket Aldon, 1 Documentation, 130
Accessing the LM Databases via Report Exporting Data from Aldon RM, 19
Manager, 119 Exporting from Aldon RM, Appendix F, 120
Activity Reports - LM(e), 43, 45, 47, 49, 52, 54 Fonts, Installing, 8
Activity Reports - LM(i), 80, 82, 84, 85, 87, 89, Help Button, 10
90
Introduction to Report Manager, 1
Aldon Report Manager, Overview, 2
Known Issues, Appendix H, 128
Aldon RM Legend, 9
Launching Report Manager, 7
Aldon RM License Information, Updating
(Appendix G), 125 legal notices, ii
Appendix B - BIRT Overview, 110 Legend, Aldon RM, 9
Appendix C - Report Parameters Permissible Legend, Report Manager, 9
Values, 111 License Information, Updating (Appendix G),
Appendix D - Report Options, 114 125
Appendix F - Exporting from Aldon RM, 120 Licensing, Report Manager, 4
Appendix G - Updating the Aldon RM License LM(e) Activities by Part Report, 43
Information, 125 LM(e) Activities by Release Report, 45
Appendix H - Known Issues, 128 LM(e) Activities by Type Report, 47
Appendix I - Trademarks, Copyrights and LM(e) Activities by User Report, 49
Licenses, 129 LM(e) Activity Summary by Release Report,
Appendix J - Resources, 130 52
Available Reports, 12 LM(e) Activity Summary by User Report, 54
Backing up reports, 31 LM(e) Java Compile Classpath Report, 42
BIRT Overview, Appendix B, 110 LM(e) Promotion Activities for Environment by
Button, Help, 10 Part, 56
Button, Options, 10 LM(e) Promotion Activity for Environment by
Part Report, 56
Button, Run, 10
LM(e) Release Summary Report, 37
Closing Report Manager, 11
LM(e) Task Assemblies Associated with
Concepts, Aldon LM(i) - Appendix A, 109 Release Report, 32
Contact technical support, iii LM(e) Task Summary Report, 33
Conversion during upgrade, 30 LM(i) Active Tasks Associated with Release
Custom Reports Report, 74
About, 19 LM(i) Activities by Object Report, 80
Customizing report content, 2, 19, 20 LM(i) Activities by Release Report, 82
135
Index Report Manager User Guide
LM(i) Activities by Task Report, 84 Report Manager, Introduction, 1

LM(i) Activities by Type Report, 85 Report Manager, Launching, 7
LM(i) Activities by User Report, 87 Report Options - Appendix D, 114
LM(i) Activity Summary by Type Report, 89 Report Parameters, 14
LM(i) Activity Summary by User Report, 90 Report Parameters Valid Values, Appendix C,
LM(i) Concepts - Appendix A, 109 111
LM(i) Deployed Object History by Release Report Storage Location, About, 30
Report, 100 Report Storage Location, Managing, 30
LM(i) Deployment Sets by Release Report, Report, Running, 11
102 Reports, Activity, 43, 45, 47, 49, 52, 54, 56,
LM(i) Permissions by Release Report, 105 80, 82, 84, 85, 87, 89, 90, 92, 94, 96
LM(i) Permissions by User Report, 107 Reports, Available, 12
LM(i) Promotion Activities for Environment by Reports, Deployment, 100, 102
Object Report, 92 Reports, Permission, 105, 107
LM(i) Promotion Activities for Environment by Reports, Release, 37, 75
Task Report, 94
Reports, Saving, 25
LM(i) Promotion and Checkout Activities by
Object, 96 Reports, Supplemental, 42, 43
LM(i) Promotion and Checkout Activities by Reports, Task, 32, 33, 64, 67, 69, 70, 74
Object Report, 96 Run Button, 10
LM(i) Release Summary Report, 75 Running a Report, 11
LM(i) Task Activity Time Log, 67 Save Dialog, 28
LM(i) Task Activity Time Log Report, 67 Saving Reports, 25
LM(i) Task Activity Time Log Summary Servers, reviewing, 4
Report, 64 Storage Location, About, 30
LM(i) Task Objects Report, 69 Storage Location, Managing, 30
LM(i) Task Summary Report, 70 technical support, iii
Logo, customizing, 132 Technology, 2
New Folder Dialog, 29 trademarks, ii
Options Button, 10 Trademarks, Copyrights and Licenses,
Overview of Report Manager, 2 Appendix I, 129
Parameters Dialog, 17 Truncated report titles, PDF, 114
Parameters, Report, 14 What's New in this Version?, 2
Performing Report Storage Maintenance, 30
Permission Reports, 105, 107
Report Categories, 10
Report Folders, 11
Report logo, customizing, 132
Report Manager
Introduction, 1
Launching, 7
Report Manager Home Page Legend, 9
Report Manager Licensing, 4
136

AldonRM UserGuide V18

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AldonRM UserGuide V18

Uploaded by

Copyright:

Available Formats

Rocket Report Manager

Country Toll-free telephone number

Contacting Technical Support

Getting Started with Report Manager........................................................................... 2

Using Rocket Aldon Report Manager ........................................................................ 11

LM(e) Report Samples ................................................................................................ 32

LM(i) Report Samples ................................................................................................. 64

Appendices ................................................................................................................ 108

Glossary .................................................................................................................... 133

Index .......................................................................................................................... 135

Rocket Aldon Report Manager

Introduction to Report Manager

Product Name Short Name

Rocket Aldon Lifecycle Manager LM(e)

Rocket Aldon Report Manager RM

Rocket Aldon Security Server Security Server

About Rocket Aldon

What's New in Version 1.8

Getting Started with Report Manager

Overview of Report Manager

Format Best used for...

HTML Immediate viewing

PDF Immediate viewing and saving

XLS Saving and embedding in documents

Saving, Reusing, and Organizing Report Parameters

Report Manager Licensing

Determining Current License Type

 About Report Manager dialog

About Report Manager Dialog

Note the "Licensed Copy" text on the dialog.

Connection validation information

Expiration of Test Drive Trial License

Launching Report Manager

Installing Report Manager Required Fonts

Follow the instructions on the dialog to

Report Manager Home Page Legend

1 The page heading with the Rocket Aldon logo.

5 A list of reports in a report folder.

7 Buttons for opening the Report Parameters dialog.

8 Links to report descriptions in the help.

9 Links to on-line help topics.

An unopened report category appears as shown below.

To close a report category, click the "minus" button.

Closing Report Manager

Using Rocket Aldon Report Manager

 LM(e) Task Assemblies  LM(i) Task Activity Time Log

 LM(e) Release Summary  LM(i) Active Tasks Associated with

 LM(e) Activities by Release  LM(i) Activities by Object

 LM(i) Deployed Object History by

 LM(e) Authority Change History  LM(i) Permissions by Release

Saving Report Parameter Sets

Creating New Report Designs

Supplying Report Parameters

The text immediately below the dialog

Selection Criteria Parameters

Sort Order and Control Breaks

Output Control Parameters

Opening the Report Parameters Dialog

1. Launch Report Manager (see Launching Report Manager).

2. If necessary, expand the appropriate report storage area.

b. Click a yellow Run button ; OR

Using the Report Parameters Dialog

Tips for entering report