MKS Implementer 2006 Administration Guide

Chapter 3: Implementer Administration
122
message legend that guides you to specific actions to resolve the errors
NOTE Although rare, the job log may also include unique problems not detectable
by Implementer.
Environment Repository Report
The Environment Repository Report provides a listing of all source members and objects
currently in the repository. The report is a print snapshot of the environment information
that displays when filtering by environment and viewing detail in Work with Objects.
The report includes general environment information and a list of all objects and object codes
currently in the repository. You can optionally include related objects. You can sort the report
by object name or object code.
When both traditional and IFS objects exist for an environment, the report is divided into two
sections; one for traditional objects and the other for IFS objects. IFS object names include the
full object name and relative path. If the long name and path are longer than 100 characters,
the field truncates at the end.
The values stored in the Chg Date/Time fields are the latter of the date and time of the last
environment build or the last promotion.
The report is available by using Work with Environments option 27=Repository Report.
When selected, it prompts the Repository Report (IPRTREPRPT) command. You can also
issue the command from a command line. This is a host-only feature (not available on remote
systems).
To generate the Environment Repository Report
1 Do either of the following to prompt the Repository Report (IPRTREPRPT) command:
From Work with Environments, type option 27=Repository Report next to the
environment, and press ENTER.
On a command line, type IPRTREPRPT and press F4=Prompt.
2 Complete the parameters as defined next in “Repository Report (IPRTREPRPT)
Command Parameters” and press ENTER. The report generates to the user’s default spool
file based on the command parameters.
NOTE Running the Environment Repository Report for an environment when the
build list has not been run causes an empty report. In Work with Environments,
check the Build List field to verify the environment’s build status.