App Builder Enterprise Rebuild

BluePhoenix AppBuilder 2.0.3.
Enterprise Rebuild Guide
BluePhoenix AppBuilder 2.0.3.1

Enterprise Rebuild Guide
September, 2002
Corporate Headquarters
BluePhoenix Solutions
Vlierwerf 7B
4704 SB Roosendaal
The Netherlands
+31 (0) 165 399 401
+31 (0) 165 396 308 fax
www.bluephoenixsolutions.nl
USA Headquarters
BluePhoenix Solutions USA, Inc.
8000 Regency Parkway
Cary, NC 27511
United States
+1 919.380.5100
+1 919.380.5111 fax
www.bluephoenixsolutions.com
1992-2002 BluePhoenix Solutions

All rights reserved.
BluePhoenix is a trademark of BluePhoenix Solutions. All other product and company names
mentioned herein are for identification purposes only and are the property of, and may be trademarks
of, their respective owners.
Portions of this product may be covered by U.S. Patent Numbers 5,495,222 and 5,495,610 and various
other non-U.S. patents.
The software supplied with this document is the property of BluePhoenix Solutions, and is furnished
under a license agreement. Neither the software nor this document may be copied or transferred by any
means, electronic or mechanical, except as provided in the licensing agreement.
BluePhoenix Solutions has made every effort to ensure that the information contained in this document
is accurate; however, there are no representations or warranties regarding this information, including
warranties of merchantability or fitness for a particular purpose. BluePhoenix Solutions assumes no
responsibility for errors or omissions that may occur in this document. The information in this
document is subject to change without prior notice and does not represent a commitment by
BluePhoenix Solutions or its representatives.
TABLE OF
CONTENTS
Table of Contents
AppBuilder 2.0.3.1 Enterprise Rebuild Guide
1 Understanding Rebuild Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Rebuild Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Understanding Rebuild Package Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Rebuild Processing Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Rebuild Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Rebuilding Package Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Preparing OpenCOBOL Rebuilds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Static Linking of Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
2 Rebuilding Applications
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Before You Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Step 1 - Create the Rebuild Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Step 2 - Select Objects for Rebuild Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Creating Relations from the Rebuild Package Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Creating Relations from the Root Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Step 3 - Identify Objects to be Prepared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Reviewing Analyze Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Handling Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Getting an Advice File for the Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Step 4 - Prepare Objects in the Rebuild Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Reviewing Rebuild Prepare Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Step 5 - Install the Application for Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Reviewing the Rebuild Install Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
After You Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
3 Using Rebuild Analyze and Prepare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Rebuild Analyze Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Exception Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Inverse Scope Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Specifying Inverse Scope Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Running RANALYZE with Inverse Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Managing Concurrent Rebuilds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Concurrent Rebuilds with Staging Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Specifying Single Staging Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Updating CICS using the DFHCSDUP Batch Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Specifying DFHCSDUP Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
4 Rebuild Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Rebuild Action Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Add an Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Add Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Add a Relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Add Text to Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Add Text to Relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Analyze Rebuild Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Clean-up Rebuild Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Delete Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Delete Relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Export Rebuild Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Install Objects in the Rebuild Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
List Rebuild Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
List Relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Maintain Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Maintain Relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Prepare Object in Rebuild Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Reset Object Install Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Reset Object Prepare Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Set Rebuild Install Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Super Prepare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
View Results of Rebuild. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
5 Setting Up The Rebuild Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Rebuild Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Migrate Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
A Status Values
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
B Rebuild Processing Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Rebuild Entity and Relationship Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
C File Allocations during Rebuild Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

The Rebuild Analyze Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
File Allocation Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Rebuild Analyzer and Prepare Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
CHAPTER
UNDERSTANDING REBUILD
PROCESSING
Most applications begin with an application design, pass through several development phases, and result
in a product. The development life cycle for AppBuilder development consists of five phases:
application analysis and design
application construction
code preparation
testing and debugging
deployment
Each of the five phases has a detailed set of activities and deliverables. Each activity consists of a set of
tasks, including structured checkpoints that serve as a basis for project monitoring, scheduling, and
resource allocation. Phase deliverables are continuously refined by overlapping phase activities. Each
phase iteratively refines the previous work until a completed application is generated, tested, and
delivered. See the Information Model Reference Guide for more information about application
development phases.
The preparation phase involves moving an application that has completed all the previous phases to a
quality assurance (QA) environment, where it is tested. After testing, you deploy the executable
application to client and server platforms in the production environment.
Once an application has been migrated toor changed inan environment, the Enterprise Rebuild
Facility prepares, installs, links, and binds the host objects in that environment.
Rebuild Processing
The Rebuild process generates executable files by preparing all objects that have been changed on the
host. For example, if you change a fields lengtheither through a migration, or directly in the host
workbenchyou must prepare all executable objects in the target environment that use that field.
The rebuild process automatically analyzes which, if any, of the objects in the package need to be
prepared and the environment in which they need to be prepared. Once all the objects within the rebuild
package that need to be rebuilt have been identified, the rebuild analysis creates another list of all objects
outside the rebuild package that rebuilding affects. Although not in the rebuild package, these objects
will be affected by the rebuild process and are called exceptions.
1-1
Understanding Rebuild Package Components
When preparing the selected objects, the system creates and compiles the execution code and stores it in
staging libraries on the platform for which the objects were prepared. You must install the prepared
objects for testing on the platform for which they were prepared, before moving the application for
distribution.
Note
All objects that need to be prepared on the workstation must be either exported to a group repository and
prepared, or downloaded to a personal repository and prepared.
Understanding Rebuild Package Components

The Rebuild Facility lets you rebuild any preparable object in migration packages (rules, sets,
components, files, windows, and reports).
A migration package is a virtual container that holds repository objects to be copied.
The rebuild package, like the migration package, consists of the rebuild entity, a relationship between the
rebuild entity and each root entity, the root entities themselves, and every object subordinate to a root
entity (determined by the objects you select, see Creating a Prepare Scope).
A function entity is the highest level object in a physical application hierarchy and it defines an
enterprises high-level activities, for example, Leasing, Sales, or Inventory Control. Typically, you define
instances of function entities during the analysis phase of the development life cycle. A function refines
into one or more processes.
A process entity represents a single application (a leaf process) or a set of applications. Each process is
defined to work in one or more execution environmentssuch as CICS on the host environment or PC
on the workstation environment.
Rebuild Processing Terms

An entity type is a generic category of entities, such as a rule, window, or rebuild package entity type.
An exception, also called an affected object, is an object the rebuild will effect even though it is not
included in the rebuild package.
A leaf process represents a single application, and is a child entity of either a function or another process.
An object is an instance of either an entity or relationship type, with attributes and parts.
An object attribute is an element of an object that helps define and identify that object.
An object part is an element of an object. An entity object can have source code, keywords, and text. A
relationship object can have keywords and text.
The prepare scope includes the entity, along with all objects needed to prepare it on the host.
A rebuild package entity is an instance of the rebuild package entity type. Rebuild package entity
attributes provide information about the objects you are rebuilding, and they control rebuild processing.
1-2
Understanding Rebuild Processing
Rebuild Management
A rebuild package is the rebuild package entity and every object with a relationship to it. The rebuild
package entity is a virtual container that holds repository objects to be copied. The rebuild package,
therefore, consists of the rebuild package entity, one relationship between the rebuild package entity and
each root entity, the root entities themselves, and every object subordinate to the root objects.
A relationship type is a kind of relationship, such as the has-access-to or has-root relationship.
A root entity is the first or top entity in any hierarchy that you want to rebuild. A rebuild package entity
has a has-root relationship to one or more root entities.
A seed is a root entity added to a rebuild package entity.
Rebuild Management
Generally, a repository administrator or change management team is responsible for rebuilding
applications. Method security defines who can rebuild in which repositories, versions, and projects. The
function of the repository determines the access rights; therefore, access rights differ from repository to
repository. For example, a QA or production repository is more controlled than a development
repository.
Note
Only one person can rebuild a specific rebuild package at a time.
One or more repository administrators perform the following functions:

Coordinate with the development project leader and quality assurance manager to schedule a
rebuild after a migration or after changes have been made to objects on the host
Perform rebuild processing, correct problems that arise, and repeat action processing until all jobs
complete successfully
Move the executable code of the tested application for distribution
Rebuilding Package Entities

Rebuild processing is divided into five actions performed in a structured sequence (Figure 1-1):
Creating the Rebuild Package
Selecting Objects for Rebuild Processing
Identifying Objects for Preparation
Preparing Objects in the Rebuild Package
Installing the Application
The action sequence is the same whether you are rebuilding entire applications or parts of applications.
1-3
Figure 1-1
Rebuild Steps
Creating the Rebuild Package

Creating the rebuild package entails naming and defining a rebuild package entity. Rebuild processing
centers around this entity, which serves as the following:
An identity cardThe rebuild package object lets you know the name, system ID, and purpose of
the rebuild package.
A containerThe rebuild package object serves as an envelope that contains root entities or root
entity hierarchies during rebuild processing.
A management toolYou can reuse a rebuild package object to organize and manage routine
rebuilds. For example, if you implement an airline reservation management system in the
production environment, you can reuse the rebuild package object to perform subsequent rebuilds
related to that system.
The rebuild package entity has 18 attributes that are divided into three types (Table 1-1)..
Table 1-1
Rebuild Package Attribute Types
Attribute type
Description
Naming
Identifies an instance of an entity. The name and system ID are alternate ways of identifying the
instance of an entity to the enterprise repository. The entity description can describe the
purpose of the rebuild.
State
Identifies the state of the jobs associated with a rebuild package entity. The system generates
the rebuild state value after a batch job is submitted.
Audit
Identifies the date, time, and user ID of the individual who created or modified the entity. The
system generates the values when the object is saved.
For detailed instructions, refer to Step 1 - Create the Rebuild Package on page 2-3.
1-4
Selecting Objects for Rebuild Processing

To select objects for rebuild processing, you must create a relationship between your new rebuild
package entity and any migration entities, functions, or processes you want to rebuild. You create a
separate has-root relationship between a rebuild package entity and each root entity that you want to
rebuild. For example, if you create a relationship between a rebuild package entity and a root function,
the relationship between them is Rebuild Package entity has-root Function (see Figure 1-2). In addition,
the many-to-many relationship type permits one rebuild package to contain a combination of these root
entity types or preparable objects.
Figure 1-2
Rebuild Package Entity has-root Function
The purpose of the rebuild helps determine the number and type of root entities the package contains.
For example, if you are rebuilding a newly-migrated application in the quality assurance environment,
the root entity might be a migration entity. If you are rebuilding because of changes made to an existing
group of applications, the root entities might be several processes and their related hierarchies.
For detailed instructions, refer to Step 2 - Select Objects for Rebuild Processing on page 2-7.
Creating a Prepare Scope
The Rebuild Facility analyzes the rebuild package by creating a prepare scopea list of all the preparable
objects (leaf processes, rules, components, reports, windows, files, and sets)for each leaf process. Then
the system compares the significant date (the date of the last significant change) with the preparation
date (the date that the entity was last prepared). If the significant date is more recent than the
preparation date, the object needs to be prepared.
Note
The Rebuild Facility prepares only those objects with significant changes since the last preparation.
The system places the object in a rebuild package prepare table and then moves on to the next item in the
hierarchy. The Rebuild Facility checks each object in the prepare scope from the top down, then explodes
each object to be prepared from the bottom up to find all of the leaf processes affected by preparing these
objects (Figure 1-3). The leaf processes are listed as exceptions and you can choose whether to add them
to the rebuild package and reanalyze. After you are satisfied with the results of the rebuild analyze, start
preparation of all the selected objects.
For more information on preparing scope, refer to
1-5
Figure 1-3
Analyzing the Rebuild Package
Identifying Objects for Preparation

To rebuild, you must identify the objects that need to be prepared. The analyze rebuild impact
(RANALYZE) action performs an extended where-used search to identify entities in a target
environment that must be prepared after you have imported a migration or made changes to one or
more entities.
Preparing Objects in the Rebuild Package

Preparing objects in the rebuild package automatically generates executable code for all the objects
identified as included in the prepare. Most executable code created during the prepare (DBRMS, objects,
etc.) is written to Rebuild Staging Libraries. The Staging Libraries are used by the Rebuild Install Method
to complete the prepare. The staging file allocations are determined by the Rebuild Analyze and Rebuild
Prepare methods. For more information on allocations, see Appendix C, File Allocations during
Rebuild Processing.
The prepare process starts at the bottom of an application hierarchy, finds the first instance of an object
marked for prepare, and prepares that instance. The process then continues upward in the hierarchy to
the next instance and prepares that instance, until all marked objects are prepared.
Installing the Application

Installing the application for testing is mandatory before moving the executables for distribution. The
Rebuild Facility copies, binds, and installs the selected mainframe executables. You can then download
the workstation executables.
Refer to the Construction Workbench Reference Guide for information on using the Preparation
Workbench to complete the installation. When installation is complete, test the application to make sure
it works properly.
1-6
Preparing OpenCOBOL Rebuilds

The Rebuild facility for OpenCOBOL includes changes to the way that the VIEW, SET RULE
and COMPONENT objects prepare. Only the following RBD methods are supported in this release:
RELINK
BIND
INSTALL
Static Linking of Rules

AppBuilder OpenCOBOL links rules during the prepare phase in contrast to static linking based on the
compiler option. Lower level rules and components must be prepared before the higher level rule and
components.
Note
The VIEW and SET prepares must be completed before a rule or component prepares.
For more information about OpenCOBOL application development, see the Enterprise Applications
Guide and the Rules Language Reference Guide.
1-7
1-8
CHAPTER
REBUILDING APPLICATIONS
When you migrate or change an AppBuilder application in the mainframe environment, you use the
Rebuild facility to prepare and install it. The specific steps required to perform this operation is
described in detail in the following sections:
Before You Rebuild
Step 1 - Create the Rebuild Package
Step 2 - Select Objects for Rebuild Processing
Step 3 - Identify Objects to be Prepared
Step 4 - Prepare Objects in the Rebuild Package
Step 5 - Install the Application for Testing
After You Rebuild
Before You Rebuild

Before you begin the rebuild process, ensure that:
You are authorized to perform rebuild actions in the environment you have chosen. Check with
your repository administrator if you are not sure whether you are authorized to rebuild.
You have adequate time to complete the rebuild.
Your environment has enough space and has been properly prepared. Use the view initialization
files (INIDISP) action to check the values of your rebuild control environment variables.
Note
Your repository administrator may have other criteria you must meet before rebuilding.
When you are ready to rebuild, you must first access the enterprise repository by following these three
steps:
1.
Following your site procedure, log on to the Time Sharing Option (TSO) system.
2.
On the command line of the Interactive System Productivity Facility/Program Development Facility
(ISPF/PDF) Primary Option menu, type the option (H in Figure 2-1) used to access the enterprise
repository and press Enter. The installation team specifies this value during your system
installation.
2-1
Before You Rebuild
Figure 2-1
Note
3.
The ISPF/PDF Primary Option menu shown in Figure 2-1 is a sample and includes site-specific options.
The equivalent panel at your site may look quite different.
The System Options menu is displayed (Figure 2-2). To access the enterprise repository, select
option 1 (AppBuilder Enterprise Repository) from the System Options menu and press Enter.
Figure 2-2
Note
2-2
ISPF/PDF Primary Option menu
System Options menu
The number of options available depends on which options are installed.
Rebuilding Applications
Figure 2-3
Host Workbench panel

Host Workbench
Repository: SUNRISE
Action
________
________
________
________
________
________
________
________
________
________
________
________
________
________
________
________
________
V: 2
Project: DEV
Level: 1
Entity
Migration
Organization
Physical Event
Process
Rebuild Package
Relationship
Report
Rule
Section
Server
Set
State
Symbol
Table
Transition
Value
View
Command ===> _______________________________________________________________
Note
4.
During rebuild processing, you will use actions, which are entered in the Action column, and commands,
which are entered from the command line. Chapter 4, Rebuild Actions provides a complete list of the
rebuild processing actions.
The Host Workbench panel opens (Figure 2-3). Use the Display Entities (ENTITY) action at any
time to display this panel listing entity types in the repository.

The rebuild package entity and its roots comprise the rebuild package, and all actions performed during
rebuild processing center around it. The add an entity (ADDE) action creates an instance of a rebuild
package entity in the enterprise repository.
To add a rebuild package entity:
1.
Navigate to the Host Workbench panel of the repository, version, and project in which you want to
rebuild. To change projects, use the change projects (PROJECTS) action.
2.
To add a rebuild package entity, type ADDE on the Rebuild Package action line (Figure 2-4) and
press Enter.
2-3
Figure 2-4
Creating the rebuild package entity

Host Workbench
Repository: SUNRISE
Action
________
________
________
ADDE____
________
________
________
________
________
________
________
________
________
________
________
________
________
3.
2-4
V: 2
Project: DEV
Level: 1
Entity
Organization
Physical Event
Process
Rebuild Package
Relationship
Report
Rule
Section
Server
Set
State
Symbol
Table
Transition
Value
View
Window
On the blank Add an Entity detail panel, type the name and, optionally, the description of the entity
(Figure 2-5).
Figure 2-5
Naming the rebuild package entity

Add an Entity
Repository: SUNRISE
Rebuild Package
Name . . . .
System Id . .
Description .
V: 2
More:
Project: DEV
Level: 2
Attributes:
. . . . . . . . DMC_VER2_RBD__________________
. . . . . . . :
. . . . . . . . To rebuild migrated DMC App_l
Rebuild Package State . . . :
Audit Attributes:
Date Created .
Time Created .
Created by . .
Date Maintained
Time Maintained
Maintained by .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Export Successful
Export Job Submitted
Export Job Failed
Export Job Executing
Exceptions Seeded
Seeded
Rebuild Analyze Submitted
Rebuild Analyze Failed
RBDA Successful w/Exceptions
Rebuild Analyze Successful
Rebuild Prepare Submitted
Rebuild Prepare Executing
Rebuild Prepare Failed
Rebuild Prepare Successful
15.
16.
17.
18.
19.
20.
21.
22.
Rebuild
Rebuild
Rebuild
N/A
Rebuild
Rebuild
Rebuild
Rebuild
Install Submitted
Install Failed
Install Successful
Install
Prepare
Analyze
Install
Incomplete
Incomplete
Executing
Executing
:
:
:
:
:
:
The description, which can be up to 30 characters of text, explains the purpose of the rebuild to
other Rebuild Facility users. Although a description is optional, we strongly recommend you add
one to make the rebuild package entity more useful to other project members.
4.
When you have finished, tab to the command line and type SAVE. Press Enter.
After you save, the panel title changes from Add an Entity to Maintain an Entity, the system-defined
attributes are filled in, and you see a message that reads:
User modifications to object have been saved.(See Figure 2-6.)
After an entity is saved, you can change the user-defined attributes by overtyping values and then
typing SAVE on the command line again.
2-5
Figure 2-6
Maintaining the rebuild package entity

Maintain an Entity
Repository: SUNRISE
V: 2
Rebuild Package Attributes:

Name . . . . . . . . . .
System Id . . . . . . . .
Description . . . . . . .
Rebuild Package State . .
.
.
.
.
Project: DEV
.
:
.
:
More
Level: 2
DMC_VER2_RBD
AA5ENR
To rebuild migrated DMC_App_l
18
N/A
Audit Attributes:
Date Created . . . . . . . : 95/05/17
Time Created . . . . . . . : 11:02
Created by . . . . . . . . : SS0222
Date Maintained . . . . . . : 95/10/07
Time Maintained . . . . . . : 15:08
Maintained by . . . . . . . : SS0222
Project . . . . . . . . . . : DOC
Change # . . . . . . . . . : 0001
Owner Id . . . . . . . . . : SS0346
Local Maintenance Date . . : 95/10/07
Local Maintenance Time . . : 15:08:38
User modifications to object have been Saved.
Note
5.
If the Autosave option is on, the information you enter is saved as soon as you press F3 to return to the
previous level. However, if you request an action that takes you to a subsequent level, you may lose your
changes when exiting from that level. Manually save your changes in this case to prevent losing them.
Refer to the Enterprise Administration Guide for more information on the Autosave option.
To add text to the entity, type TXE on the command line. The text describes the purpose and scope
of the rebuild package to other Rebuild Facility users. Figure 2-7 shows sample text. Although
optional, this step is recommended.
Figure 2-7
Adding text to the rebuild package entity
--------- SS0222.SS0196.MOD.STK -----------------------------COLUMNS 001 072
TEXT for Rebuild Package
Name . . . . . . . : DMC_VER2_RBD
Version . . . . . : 2
****** ***************************** TOP OF DATA
2-6
6.
Press F3 to save the text and return to the Maintain an Entity panel.
7.
Type K on the command line to add keywords to the entity. Keywords describe the purpose and
scope of the rebuild package to other Rebuild Facility users. Figure 2-8 shows sample keywords. This
step is optional.
Figure 2-8
Adding keywords to the entity
--------- SS0222.SS0196.MOD.STK -----------------------------COLUMNS 001 072
KEYWORDS for Rebuild Package
Name . . . . . . . : DMC_VER2_RBD
Version . . . . . : 2
****** ***************************** TOP OF DATA
******************************
000001 REBUILD
000002 DMC
000003 VER2
000004 VER2
8.
Press F3 to return to the Maintain an Entity panel.
9.
Press F3 to exit the Maintain an Entity panel. You can use the maintain entity (ME) action to display
this panel if you want to check or change the entity attribute values.
10. Record the name of this entity because you will use it throughout source environment processing.
The rebuild package entity is not complete until you add one or more root entities to it. At this stage, you
can only list existing entities with the list entity (LE) action, maintain entities with the maintain entity
(ME) action, or delete entities with the delete entity (DE) action.
To continue with the rebuild process, you must now define the scope of objects to be included in the
rebuild package, which you do by adding relations to the rebuild package. The following section
describes how to define the scope.

You now have to select objects to be included in the rebuild package. The add a relation (ADDR) action
defines the scope of objects to be included in the rebuild package by Creating Relations from the Rebuild
Package Entity and the objects that you want to rebuild.
You can create a relation between a rebuild package entity and root entities (or from the root entity to
other entities) only if the entities are stored in the same version. That is, a rebuild package or root entity
in version 2 can have relations only to entities that are also in version 2.
You usually select objects for rebuild processing by creating relations from the rebuild package entity,
but you can also use the procedure outlined in Creating Relations from the Root Entity.
Creating Relations from the Rebuild Package Entity

1.
Record the name of each root entity that you want to add to the rebuild package.
2.
On the Host Workbench panel, type LE on the Rebuild Package action line (Figure 2-9). Press Enter
to navigate to the List Facility for Entity Rebuild Package panel.
2-7
Figure 2-9
Navigating to the List Facility for Entity Rebuild Package panel

Host Workbench
Repository: SUNRISE
Level: 1
Action
________
________
________
LE______
________
________
________
________
________
________
________
________
3.
Project: DEV
Entity
Organization
Physical Event
Process
Rebuild Package
Relationship
Report
Rule
Section
Server
Set
State
Symbol
Type ADDR on the action line of your rebuild package entity (Figure 2-10) and press Enter.
Figure 2-10
Creating the relation from the rebuild entity

Host List Facility for Entity Rebuild Package
Repository: SUNRISE
Level: 2
Action Name
________ AWT_VER1_RBD
4.
V: 2
V: 2
Project: DEV
System Id
AA46NR
The system generates a blank Add a Relation panel with the Rebuild Package Name field filled in
(Figure 2-11). Type the number of the relation type you want to create in the Relation Type field. In
Figure 2-12, the relation type is Has-Root Function.
Figure 2-11 Adding a relation to the rebuild entity

------------------------- Action Information -----------------------|
More:
- +
|
| Action . . . . . . . . . . . : Add a Relation
|
| Use . . . . . . . . . . . . . . 1
Name
|
| Entity Type . . . . . . . . . : Rebuild Package
|
| Name/System Id . . . . . . . . DMC_VER2_RBD
_________________
|
|
|
| Relation Type . . . . . . . . . 3 1. Has-Root Component
|
|
2. Has-Root File
|
5.
2-8
The Add a Relation panel is displayed (Figure 2-12). In the Has-Root <entity type> Name field, type
the name of the root entity that you want to add to the rebuild package. This should be the
migration entity you exported to this target. The name must be an alphanumeric string up to 30
single-byte or 14 double-byte characters.
Note
You must analyze and import the migration entity before proceeding to rebuild processing.
Figure 2-12
Naming the rebuild package

Add a Relation
Repository: SUNRISE
V: 2
Project: DEV
More: +
Level: 4
Rebuild Package
Name . . . . . . . . . . . . DMC_VER2_RBD__________________
Has-Root Function
Name . . . . . . . . . . . . DMC_VER2_FUNC1________________
Relationship Attributes:
Application Configuration . . PROJECT_DMC___________________
Is a Root Entity
. . . . . . 2
Is a Refined Entity . . . . :
6.
1. No
2. Yes
1. No
If you are using the Host Workbench, type the long name of the application configuration in the
Application Configuration field, as shown in Figure 2-12.
Note
If you want to have two configurations for one entity, you can create two separate relations between the
rebuild package entity and the entity you want configured. Assign one an application configuration and
leave the other one blank.
7.
Tab to the command line, type SAVE, and press Enter.
8.
A value of 2 (YES) is displayed to indicate the added entity is a root entity. (The values in these
three fields are system-generated, so you cannot type values in them.)
RANALYZE needs at least one root entity to perform the explode, for this reason the exit always sets the
"is a root entity" value to YES when you add the relationship for initial processing. For example, if you
establish a relationship between a rebuild package and a Report and select NO for the option "is a
root entity", the exit resets it to YES. When you maintain the relationship, the same attribute can
now be switched from YES to NO. See Handling Exceptions.
After you save the relation, the panel changes from Add a Relation to Maintain a Relation and the system
fills in the values for the audit attributes. Note that the rebuild package state changes from N/A (not
applicable) to seeded, indicating you have added a root entity to the package. A message that reads User
modifications to object have been saved appears in the command area (Figure 2-13).
2-9
Figure 2-13
Saving a relation
Maintain a Relation
Repository: SUNRISE
V: 2
Project: DEV
More:
Level: 3
Rebuild Package
Name . . . . . . . . . . . . DMC_VER2_RBD________________
Has-Root Function
Name . . . . . . . . . . . . DMC_VER2_FUNC1_______________
Application Configuration . . ______________________________
Is a Root Entity . . . . . . 2
Yes
Is a Refined Entity . . . . : 1
No
Has Hierarchy Changed . . . : 1
No
Affected Entity (Not Analyze: 1
No
Audit Attributes:
Date Created . . . . . . . : 95/10/17
Time Created . . . . . . . : 17:18
User modifications to object have been Saved.
After a relation is saved, you can change the user-defined attributes by typing over the values and
then typing SAVE on the command line again.
9.
Type TXR on the action line to add text to the relation. Use the text to describe the purpose of the
relation to other users. This step is recommended, although optional (Figure 2-14).
10. Press F3 to save the text and return to the Maintain a Relation panel.
Figure 2-14 Adding text to the relation
--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072
TEXT for Relations
Name . . . . . . . : DMC_VER2_FUNC1
Version . . . . . : 2
******
000001
000002
000003
******
***************************** TOP OF DATA ******************************

DMC_VER2_RBD HAS ROOT FUNCTION DMC_VER2_FUNC1.
APPLICATION CONFIGURATION IS PROJECT_DMC.
REBUILDING PACKAGE IN VERSION 2 FOR FIRST TIME.
**************************** BOTTOM OF DATA ****************************
11. To add another root entity of the same type to the rebuild package from the active Maintain a
Relation panel, tab to the Has-Root <entity type> Name field, and overtype the first entity name
with the next entity name. Then type SAVE on the command line and press Enter. The system
displays the message, User modifications to object have been saved.
12. To add a root entity of another entity type, press F3 to exit the active panel. Then repeat steps 2
through 9, until you have included all the objects you want to rebuild.
13. Press F3 to exit the Maintain a Relation panel. You can use the maintain relation (MR) action to
display this panel again if you want to check or change the relation attribute values.
Caution
2-10
Once you start the analyze rebuild impact action (RANALYZE), you cannot add more entities to the
rebuild package unless you use the clean-up rebuild information action to set the state back to
seeded. Make sure you have included all the objects you want to rebuild. For information about the
CLEANUP action, see Clean-up Rebuild Information on page 4-12.
Use the list relations (LR) action to make sure you have included all the root entities you want in the
rebuild package. Use the delete relation (DR) action to delete any entities you do not want in the rebuild
package.
Once you determine that the rebuild package is complete, you are ready to analyze it. The section, Step 3
- Identify Objects to be Prepared, describes the analyze rebuild impact (RANALYZE) action in detail.
Creating Relations from the Root Entity

Although it is more common to select objects for the rebuild object is by creating relations from the
rebuild package entity, you can also create relations from the root entity or entities. The relationships
you add should be the same as those from the root entities of the migration entity you exported to this
target environment.
The procedure is almost the same as the one described for creating relations from the rebuild package
entity. The differences between the two procedures are described below.
1.
Record the name of each root entity that you want to add to the rebuild package. Also record the
name of your rebuild entity.
2.
Type ADDR on the action line that corresponds to the object you want to include in the rebuild
package (Figure 2-15). Press Enter.
Figure 2-15
Adding a relation from the root entity

Host List Facility for Entity Function
Repository: SUNRISE
V: 2
Project: DEV
Level: 2
Action
Name
System Id
ADDR____ DMC_VER2_FUNC2
AA4HNR
________ GET_NRV1V2
AA3YNR
________ MIG_FDFAULT
AA12NR
________ MIG_FREPORT
AA13NR
________ MIG_MODIFY_TESTS
AA49NR
________ MIG_TCFLVIEW
AA4WNR
________ WMM_MIG_PHY_EVT
AA2INR
****************************** BOTTOM OF DATA ********************************
3.
Select Is-A-Root-Of Rebuild Package from the list of available relation types on the Action
Information pop-up panel (Figure 2-16). Then press Enter.
2-11
Figure 2-16
Choosing the relation type
-------------------------- Action Information ------------------------|

More:
+
|
| Action . . . . . . . . . . . : Add a Relation
|
| Use . . . . . . . . . . . . . . 1
Name
|
| Entity Type . . . . . . . . . : Function
|
| Name/System Id . . . . . . . . DMC_VER2_FUNC2________________
|
|
|
| Relation Type . . . . . . . . . 10 1. Has Bitmap
|
|
2. Is-Encap'ed-By Config. Unit
|
|
3. Replaces Current System
|
|
4. Intersects-With Entity
|
|
5. Uses Language
|
|
6. Is-Carried-Out-At Location
|
|
7. Is-A-Root-Of Migration
|
|
|
|
9. Refines-Into Process
|
|
10. Is-A-Root-Of Rebuild Package
|
| Version . . . . . . . . . . . : 2
|
| Prompt for Input. . . . . . . . 1
Yes
|
4.
The system generates a blank Add a Relation panel with the Has-Root <entity type> (in the example
it is Function) Name field filled in. Type the name of the rebuild package entity in the Rebuild
Package Name field as shown in Figure 2-17. The name you type must match the name of your
existing rebuild package entity.
Figure 2-17
Naming the root entity

Add a Relation
Repository: SUNRISE
V: 2
Project: DEV
More:
Level: 4
Rebuild Package
Name . . . . . . . . . . . . DMC_VER2_RBD_________________
Has-Root Function
Name . . . . . . . . . . . . DMC_VER2_FUNC2________________
Application Configuration . . ______________________________
Is a Root Entity
5.
. . . . . . 2
1. No
2. Yes
1. No
2. Yes
Has Hierarchy Changed . . . :
1. No
2. Yes
Tab to the command line, type SAVE, and press Enter.

After you save the relation, the panel heading changes from Add a Relation to Maintain a Relation,
and the system fills in the values for the audit attributes.
A value of 2 (YES) displays in the Is a Root Entity field indicating the object is a root entity. (The
values in these three fields are system-generated, so you cannot type values in them.)
A message that reads User modifications to object have been saved appears in the command area
(Figure 2-18).
2-12
Figure 2-18
Saving the relation

Maintain a Relation
Repository: SUNRISE
V: 2
Project: DEV
More:
Level: 3
Rebuild Package
Name . . . . . . . . . . . . DMC_VER2_RBD_________________
Has-Root Function
Name . . . . . . . . . . . . DMC_VER2_FUNC2________________
Application Configuration
Is a Root Entity . . . .
Is A Refined Entity . . .
Has Hierarchy Changed . .
Audit Attributes:
Date Created . . .
Time Created . . .
Created by . . . .
Date Maintained . .
User modifications to
.
.
.
.
.
.
:
:
PROJECT_DMC___________________
2
Yes
1
No
1
No
. . . . : 95/05/17
. . . . : 16:01
. . . . : SS0222
. . . . : 95/10/07
object have been Saved.
6.
To add an instance of another entity type, return to the Host Workbench panel (Figure 2-9) and
repeat steps 2 through 5.
7.
Repeat this procedure until you have included all the root entity you want in the rebuild package.
Use the list relations (LR) action to verify that all the root entities you want are in the rebuild package.
The system displays each relation type, the name of each seed entity, and the date the relation was
created. Use the delete relation (DR) action to delete any entities you do not want in the rebuild package.
Once you determine that the rebuild package is complete, you are ready to analyze it. The next section
describes the analyze rebuild impact (RANALYZE) action in detail.

environment that must be prepared after you have imported a migration, or made changes to one or
more entities.
The analyze rebuild impact (RANALYZE) action submits a batch job that generates an online report.
The reports lists every entity that needs to be prepared and installed by name, system ID, entity type, and
execution environment. See List Rebuild Contents on page 4-16.
This section describes how to identify which objects need to be prepared.
8.
On the Host Workbench panel, type LE on the Rebuild Package action line (Figure 2-19) to
navigate to the List Facility for Entity Rebuild Package panel.
2-13
Figure 2-19
Navigating to the List Facility for Entity Rebuild Package panel

Host Workbench
Repository: SUNRISE
Action
________
________
________
LE______
________
________
________
________
________
________
________
________
________
________
________
________
________
9.
V: 2
Project: DEV
Level: 1
Entity
Organization
Physical Event
Process
Rebuild Package
Relationship
Report
Rule
Section
Server
Set
State
Symbol
Table
Transition
Value
View
Window
Type RANALYZE on the action line of your rebuild package entity (Figure 2-20).
Figure 2-20
Selecting the rebuild package entity to analyze

Repository: SUNRISE
V: 2
Project: DEV
Level: 2
Action
Name
System Id
AA46NR
________ BRS_VER3_RBD
AA5CNR
RANALYZE DMC_VER2_RBD
AA5ENR
***************************** BOTTOM OF DATA ********************************
10. Press Enter to start the rebuild analyze job and return to the List Facility screen.
The system acknowledges the submission of the rebuild analyze job with the message:
Rebuild analyze for <entity name> processed.
11. Monitor the progress of your job by checking the value of the rebuild package state attribute on the
Maintain an Entity panel (Figure 2-21).
Note
2-14
You must press F19 to refresh the values on the screen.
Figure 2-21
Checking the rebuild package state

Maintain an Entity
Repository: SUNRISE
V: 2
Project: DEV
More:
Level: 3

Name . . . . . . . . . .
System Id . . . . . . . .
.
.
.
.
.
:
.
:
DMC_VER2_RBD_________________
AA5ENR
REBUILD MIGRATED DMC_APP_1
21
Rebuild Analyze Executing
Audit Attributes:
Date Created . .
Time Created . .
Created by . . .
Date Maintained .
Time Maintained .
Maintained by . .
Project . . . . .
Change # . . . .
Owner Id . . . .
Local Maintenance
.
.
.
.
.
.
.
.
.
.
:
:
:
:
:
:
:
:
:
:
95/05/17
08:51
SS0222
95/10/07
09:22
SS0222
DEV
0005
SS0222
95/10/07
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
Date
.
.
.
.
.
.
.
.
.
.
12. You cannot go to the next step until the rebuild package state registers a value of Rebuild Analyze
Successful. See Table 4-7 on page 4-22 for a complete list of rebuild package state values.
If the rebuild analyze job fails, review the job results using the System Display and Search Facility
(SDSF), correct the problem, and run the job again.
Caution
If the state of the repository changes before you rerun the analyze job, the results might not be the
same.
Reviewing Analyze Results

The analyze rebuild impact (RANALYZE) submits a TSO job. Once the job has finished, you can review
the results online in three ways:
Refresh the Maintain an Entity panel (press F19) to see the current rebuild package state attribute.
The state reflects the submission, execution, and success or failure of the job.
Record the job number that is displayed after you submit the analyze job. Then use SDSF to get
detailed job status information.
Look at the messages associated with analyze processing. For instructions on accessing, interpreting,
and printing analyze job messages, refer to the Enterprise Administration Guide.
When you determine that the analyze has been successful, you can use the following actions to examine
the rebuild package:
Use the list rebuild contents (LISTRBD) action to view the results of the rebuild impact.
Use the list relation (LR) action to see which objects are part of the rebuild package.
Use the view results of rebuild (RES) action to see the messages that contain the results of the batch
job, including date and time stamps for job start and job end, as well as the final job-state value.
See Chapter 4, Rebuild Actions for more information about these actions.
2-15
Handling Exceptions
Exceptions are objects that, although not part of the rebuild package, will be affected by the rebuild. If
the results of an analyze rebuild impact (RANALYZE) action indicate the presence of exceptions (Figure
2-22), you can either analyze some or all again to include them in your rebuild package.
Figure 2-22
Rebuild status showing exceptions

Maintain an Entity
Repository: SUNRISE
V: 2
Project: DEV
More: +
Level: 3

Name . . . . . . . . . .
System Id . . . . . . . .
.
.
.
.
. DMC_VER2_RBD__________________
: AGWASR
. ______________________________
: 9
RBDA Successful w/Exceptions
Audit Attributes:
Date Created .
Time Created .
Created by . .
Date Maintained
Time Maintained
Maintained by .
Project . . . .
.
.
.
.
.
.
.
:
:
:
:
:
:
:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
95/10/11
18:03
SS0222
95/11/14
14:57
SS0222
DEV
Processing Selected Exceptions

To process some, but not all of the exceptions, you need to update their relations to the rebuild package.
You can list the exceptions by using the list relations (LR) action next to the name of the rebuild package.
Scroll right to see the Affected Entity column, as shown in Figure 2-23.
Note
If you decide to continue the rebuild process without exceptions, you can process the exceptions later.
Figure 2-23
Exceptions listed as affected entities
Repository: SUNRISE
V: 2
Entity Name: DMC_VER2_RBD
Relation Type: Has-Root Rule
Action
________
________
________
________
________
________
________
Name
DVT_RULE_ALL_SET_BATCH_SBCS
DVT_RULE_ALL_SET_CICS_SBCS
DVT_RULE_ALL_SET_IMS_SBCS
DVT_RULE_ALL_SET_MVS_SBCS
DVT_RULE_ALL_SET_PCCICS_SBCS
DVT_RULE_ALL_SET_PCIMS_SBCS
NEW_COMP_TEST
Project: DEV
Level: 3
Affected Entity (Not Analyzed)

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Processing All Exceptions

To reanalyze all exceptions, type RANALYZE on the action line for the rebuild package entity. The
Analyze Options panel is displayed (Figure 2-24).
2-16
Figure 2-24
Selecting exceptions to analyze

Rebuild Package Analyze Options
Name . . . . . . . . : DMC_VER2_RBD
Version . . . . . . : 2
Select the following processing options.
Processing Options
Exceptional Process Option . . . 4 1.
2.
3.
4.
Then press Enter.
Prepare excluding ALL Exceptions

Re-Analyze including ALL Exceptions
Re-Analyze excluding ALL Exceptions
Select Exceptions to Analyze
To analyze somebut not allof the exceptions use the maintain relation (MR) action next to the
exceptions you want to analyze. The Maintain a Relation panel is displayed (Figure 2-25).
Figure 2-25
Listing an exceptions relation to the rebuild package

Maintain a Relation
Repository: SUNRISE
V: 2
Project: DEV
More: +
Level: 4
Rebuild Package
Name . . . . . . . . . . . . DMC_VER2_RBD________________
Has-Root Rule
Name . . . . . . . . . . . . DVT_RULE_ALL_SET_BATCH_SBCS___
Application Configuration . .
Is a Root Entity . . . . . .
Affected Entity (Not Analyze:
______________________________
2
Yes
2
Yes
2
Yes
2
Yes
Overtype the 2 with a 1 in the Is a Root Entity field to specify that the exception is not to be a
root entity (Figure 2-26).
Note
For initial processing, RANALYZE needs at least one root entity to perform the explode, for this reason, the
exit always sets the "is a root entity" value to YES when you initially add a relationship.
Figure 2-26
Updating an exceptions relation to the rebuild package

Maintain a Relation
Repository: SUNRISE
V: 2
Project: DEV
More: +
Level: 4
Rebuild Package
Name . . . . . . . . . . . . DMC_VER2_RBD________________
Has-Root Rule
Name . . . . . . . . . . . . DVT_RULE_ALL_SET_BATCH_SBCS___
Application Configuration . .
Is a Root Entity . . . . . .
Affected Entity (Not Analyze:
______________________________
1
No
2
Yes
2
Yes
2
Yes
2-17
After an analyze, you can switch the exceptions (out-of-scope) from root to non-root to minimize the
explode tree. See Creating Relations from the Rebuild Package Entity for information on switching this
attribute.
After you have updated the relations of the exceptions you are interested in (that is, you have made them
root or non-root entities), you can reanalyze the rebuild package. Once you are satisfied with the results
of the analyze rebuild impact, prepare the package.
Getting an Advice File for the Workstation

The analyze process writes a list of objects that need to prepared on the workstation to an advice file. The
file has the same high-level qualifier(s) as the Results file, which is defined when AppBuilder software is
installed. The low-level qualifier is ADVICE. The value of the RBWB variable in the @USERENVn file,
where n is the repository version number, needs to be set to Y to get an advice file.
An advice file is a file that contains a list of the entities to be prepared. By using an advice file, you can
split up the work of preparing large repositories into more manageable pieces. Because these pieces are
non-overlapping lists of preparable entities, they can be prepared in parallel as well.
In the workstation Migration Workbench, you import the objects the advice file identifies as needing
preparation. You then use the Preparation Workbench to prepare them. See Export Rebuild Package
on page 4-13 for more information about getting the objects listed in the advice file to the workstation.

The rebuild prepare (RPREPARE) action submits a batch driver job that generates and compiles
executable code for the selected objects. The code is placed in staging libraries until installation.
To prepare the rebuild package:
1.
On the Host Workbench panel, type LE on the Rebuild Package action line to navigate to the List
Facility for Entity Rebuild Package panel. Type RPREPARE on the entity action line (Figure 2-27)
and press Enter.
Figure 2-27
Preparing the rebuild package

Repository: SUNRISE
Action
________
________
RPREPARE
2.
2-18
Name
AWT_VER1_RBD
BRS_VER3_RBD
DMC_VER2_RBD
V: 2
Project: DEV
Level: 2
System Id
AA46NR
AA5CNR
AA5ENR
Choose your rebuild prepare options in the Rebuild Package Prepare Options panel (Figure 2-28).
Figure 2-28
Selecting rebuild prepare options

Rebuild Prepare Options for RBDPKG
Name . . . . . . . . : DMS_VER2_RBD
Version . . . . . . : 2
Then press Enter.
Processing Options
Objects to Prepare . . . . . . . . . . 5 1.
2.
3.
4.
5.
Execution Options
. . . . . . . . . . _
_
_
S
_
Sets
Files, Windows, Reports
Components, Rules
Process (Not Needed)
All of the above
Continuous submission
Re-submit incomplete prepares
Re-submit failed prepares
Ignore failed prepares
Defer jobs to run overnight
Number of jobs active in the queue . . 0003
In the Objects to Prepare selection field, type the number that corresponds to the types of objects
you want to prepare. You must prepare the phases in the order listed, unless the rebuild package
does not contain any objects in one of the phases.
Option 4, Process (Not Needed), indicates that you do not need to prepare processes in AppBuilder.
In the Execution Options field, type S to selector a space to deselect an option.
In the Number of Jobs Active in the Queue field, you can keep the default value or type a number
from 1 to 9999.
3.
Press Enter to start the rebuild prepare job and return to the List Facility screen.
The system acknowledges the submission of the rebuild prepare job with the message:
Rebuild prepare for <entity name> processed.
4.
Monitor the progress of your job by checking the value of the rebuild package state attribute on the
Maintain an Entity panel (see Figure 2-29).
Note
You must press F19 to refresh the values on the screen.
2-19
Figure 2-29
Checking the rebuild package state

Maintain an Entity
Repository: SUNRISE
5.
V: 2
Project: DEV
More: +
Level: 3

Name . . . . . . . . . .
System Id . . . . . . . .
.
.
.
.
.
:
.
:
DMC_VER2_RBD_________________
AA5ENR
______________________________
12
Audit Attributes:
Date Created . .
Time Created . .
Created by . . .
Date Maintained .
Time Maintained .
Maintained by . .
Project . . . . .
Change # . . . .
Owner Id . . . .
Local Maintenance
.
.
.
.
.
.
.
.
.
.
:
:
:
:
:
:
:
:
:
:
95/05/17
16:29
SS0222
95/10/10
13:46
SS0222
DEV
0010
SS0222
95/10/10
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
Date
.
.
.
.
.
.
.
.
.
.
You cannot go to the next step until the rebuild package state registers a value of Rebuild Prepare
Successful. See Table 4-7 on page 4-22 for a complete list of rebuild package state values.
If the rebuild prepare job fails, review the job results using SDSF, correct the problem, and resubmit
the job with the Resubmit Failed Jobs option selected.
See Reset Object Prepare Status on page 4-25 for more information about resetting the prepare
status.
Caution
If you reset the prepare status, you must reset the status of all entities in subsequent phases.
Reviewing Rebuild Prepare Results

The rebuild prepare (RPREPARE) action submits one driver job that submits multiple prepare jobs to
fulfill your request. After the jobs are finished, you can review the results online in several ways:
Refresh the Maintain an Entity panel (press F19) to see the current rebuild package state. The state
reflects the submission, execution, incompletion, success, or failure of the job.
Use the list rebuild (LISTRBD) action to monitor each rebuild prepare status.
To get more information for processed prepares, use the view results (RES) action by typing RES on
the action line beside the name of the rebuild package entity you want to view.
The results file for any action processed with the rebuild package is listed. This is particularly useful
to find the reason an object did not prepare successfully.
Be aware that any existing RES file for a preparable entity is overwritten by the last preparation (Prepare, Superprepare, or Rebuild).
2-20
You can browse, print, or delete the results file from the Repository File Browser.
To track the job, record the job number displayed after you submit the rebuild prepare job and then
choose the Spool Display and Search Facility in ISPF to get detailed job status information.
Look at the messages associated with rebuild analyze processing. For instructions on accessing,
interpreting, and printing results messages, refer to The MVS Environment.
If the job fails, correct the problem, and resubmit the job with one of the following options:
Resubmit incomplete prepares (a JCL error prevented the job from completing)
Resubmit failed prepares
Ignore failed prepares
If the preparation failed because of an external condition, such as running out of space, you can reset the
preparation status after correcting the environmental condition that caused the failure. Use the reset
prepare status action (RESETPR) to reset the preparation of some or all of the objects in the rebuild
package. See Reset Object Prepare Status on page 4-25 for more information.
When you determine that the rebuild prepare has been successful, you are ready to install the application
for testing.

After the rebuild prepare (RPREPARE) action creates executable code, you must install the code. The
rebuild install (RINSTALL) action moves executable files into user libraries for testing.
The rebuild install (RINSTALL) action submits a batch driver job that copies the host executable files
from staging data sets to user run-time libraries, and then binds them. This rebuild install is required to
complete processing.
To install the objects in the rebuild package:
1.
On the Host Workbench panel (Figure 2-3), type LE on the Rebuild Package action line to navigate
to the List Facility for Entity Rebuild Package panel. Type RINSTALL on the entity action line
(Figure 2-30).
Figure 2-30
Selecting the rebuild package to install

Host List
Host
Facility
List Facility
for Entity
forRebuild
Entity Package
Rebuild Package
Repository: SUNRISE
Level: 2
Action
Name
Action
________Name
AWT_VER1_RBD
________
BRS_VER3_RBD
RINSTALL DMC_VER2_RBD
2.
V: 2
Project: DEV
Level: 2
System Id
System Id
AA46NR
AA46NRAA5CNR
AA5ENR
Choose your rebuild install options in the Rebuild Package Install Options panel, as Figure 2-31
shows.
2-21
Figure 2-31
Selecting install options for the rebuild package
Rebuild Install Options for RBDPKG Command =======>

___________________________________________________________
Name . . . . . . . . :
TEST01_REBUILD1 Version . . . . . . :
Type 's' to select an option or type a space to deselect.

press ENTER.
Processing Options Install
1. Static Link
4.
2. Copy Executables
5.
3. DB2 Bind Package
6.
Then
Steps to Execute . . . _
DB2 Bind Top Rules
LU2 Install
All of the above
Execution Options . . . . . .
_ Re-submit incomplete installs
_Re-submit failed installs S Ignore failed installs
_ Re-generate Bindcontrol cards
_ Re-generate LU2 control cards
_Defer jobs for overnight execution
DB2 Bind Intermediate Rules . 2 1. Yes 2. No
In the Install Steps to Execute field, type a 1 to static link, a 2 to copy executables, a 3 to bind the
package, a 4 do a top bind, a 5 to do an LU2 install, or a 6 to do all of the above.
In the Execution Options field, type an S to selector a space to deselectan option.
In the DB2 Bind Intermediate Rules field, type a 1 to select Yes or a 2 to select No.
3.
Press Enter to start the rebuild install job and return to the List Facility screen.
The system acknowledges the submission of the rebuild install job with the message:
Rebuild install for <entity name> processed.
4.
Monitor the progress of your job by checking the value of the rebuild package state attribute on the
Maintain an Entity panel.
The rebuild package state registers a value of Rebuild Install Successful when processing is complete.
See Table 4-7 for a complete list of rebuild package state values.
If the rebuild install job fails, review the job results using SDSF, correct the problem, and resubmit
the job with the Resubmit Failed Jobs option selected. See Reset Object Install Status on page 4-24
for more information about resetting the install status.
Caution
If you reset the install status, you reset the status of all entities in subsequent phases.
Updating Preparation Status

The preparation status of repository objects is updated after a successful rebuild install. Note that if two
or more rebuild packages share a preparable object, the shared objects can have only a single status. So if
two or more rebuild packages are processing simultaneously, the job that finishes first updates the status
of any shared objects.
For example, suppose rebuild package ONE and rebuild package TWO both contain rule A. Between the
time rule A is successfully prepared but before it is installed in package ONE, rebuild package TWO runs
the analyze step. Because the status of rule A is not yet Rebuild Install Successful, package TWO analyzes
and prepares rule A again.
2-22
After You Rebuild
Reviewing the Rebuild Install Results

The rebuild install (RINSTALL) action submits one driver job which submits multiple jobs to fulfill your
request. Once the jobs are finished, you can review the results online in several ways:
reflects the submission, execution, and success or failure of the job.
Use the list rebuild (LISTRBD) action to monitor each rebuild install status.
To get more information for processed installs, use the view results (RES) action by typing RES on
the action line beside the rebuild package entity you want to view.
To track the job, record the job number displayed after you submit the rebuild install job, then
choose the System Display and Search Facility in ISPF to get detailed job status information.
Look at the messages associated with rebuild install processing. For instructions on accessing,
interpreting, and printing results messages, refer to The MVS Environment.
If the job fails, correct the problem, and resubmit the job with the Resubmit Failed Objects option
selected.
If the install failed because of an external condition, such as running out of space, you can reset the
install status after correcting the environmental condition that caused the failure. Use the reset install
status action (RESETINS) to reset the install of some or all of the objects in the rebuild package. See
Reset Object Install Status on page 4-24 for more information.
After You Rebuild

When you determine that the rebuild has been successful, you can use the following actions to further
examine the rebuilt migration package:
Use the list rebuild (LISTRBD) action to examine what changes have been made to the repository.
job, including date and timestamps for job start and job end, as well as the final job status value.
Use the report (REP) action to generate hard copy or on-line reports.
When you determine that the rebuild install has been successful, you are ready to test the application.
2-23
After You Rebuild
2-24
CHAPTER
USING REBUILD ANALYZE AND

PREPARE
In the previous section, we discussed the step-by-step procedure to rebuild applications. There are
several specific tools you can use during the analyze and prepare process that will enhance performance
and efficiency.
Rebuild Analyze Utilities

You use the RANALYZE (Rebuild Analyze) action to submit a batch job that identifies every entity in the
rebuild package that needs to be prepared. Once these entities have been marked for prepare, rebuild
analyze checks for entities outside the rebuild package that rebuilding may also effect. It automatically
adds these entities, called exceptions, to the package.
Processing Options
Analyzing exceptions is a time-consuming, labor-intensive process that may not be appropriate for every
rebuild. Repositories that feature a high degree of object reuse may require a great many rebuild-analyze
iterations before all exceptions have been identified. Especially in the dynamic environment of a
development repository, where applications are frequently being modified and reprepared, you may
want to try a less stringent approach called inverse scope processing.
Two approaches offer solutions to these issues:
Exception Scope
Inverse Scope Processing
Note
Inverse scope cannot be used in a mix-and-match mode with Exception scope processing.
Exception Scope
In exception scope processing, rebuild analyze looks at every preparable entity in the rebuild package to
determine whether the date it was last changed is more recent than the date it was last installed. If so, the
entity is marked for prepare. Preparable entities are rules, components, reports, sets, windows, files, and
3-1
Processing Options
bitmaps. Views, component subroutines, forms, physical events, and bitmap implementation names are
not considered preparable entities.
If an entity has not been changed after it was last installed, it still is marked for prepare if one of its
childrenincluding a non-preparable childhas changed: if view1 has changed and if view1 is a child
of rule1, then mark rule1 for prepare. A view need not be an immediate child of rule1; it need only exist
somewhere in rule1s preparation scope.
Once an entity has been marked for prepare, rebuild analyze checks for exceptionswhether preparing
the entity may effect entities outside the rebuild package (Figure 3-3). Suppose you are analyzing
process1, and rule1 is marked for prepare. If rule1 is also used in process2, process2 is marked as an
exception (the change to view1 might effect a parent of rule1 in process2; when you analyze exceptions,
the parent of rule1 will be marked for prepare).
Inverse Scope Processing

In inverse scope processing, rebuild analyze looks at every entity in the rebuild package, whether or not
its parent has changed, to determine whether the date it was last changed is more recent than the date it
was last installed. A changed preparable entity is marked for prepare. An unchanged preparable entity is
marked for prepare if one of its children has changed.
There is no notion of exceptions. A preparable entity outside the rebuild package is marked for prepare if
one of its children inside the rebuild package has changed.
The principal differences between the scopes are:
Inside the rebuild package: Inverse scope processing checks entities for change whether or not their
parents have changed.
Outside the rebuild package: Inverse scope processing has no notion of exceptions.
The following sections :
Comparing Exception and Inverse Scope Processing looks at these differences in practical terms.
Comparing Exception and Inverse Scope Processing

Inverse scope processing checks entities for change whether or not their parents have changed.
Figure 3-1 shows how exception scope processing checks non-preparable child entities for change only
when their parents have not changed.
3-2
Using Rebuild Analyze and Prepare
Processing Options
Figure 3-1
Exception scope: checking children

@ entity changed
+ entity marked for prepare
package
process1
rule1
+
view1
rule2
No change to rule1
so check view1
@+
Rule2 changes so
dont check view2
view2
Figure 3-2 shows how inverse scope processing checks children for change regardless of whether their
parents have changed.
Figure 3-2
Inverse scope: checking children

@ entity changed
package
process1
rule1
view1
rule2
Check view1 and view2

whether or not their parents
have changed
+
@
@+
view2
As the illustrations show, the scopes give the same results. The differing approach to checking children
involves performance reasons: inverse scope processing is more efficient than exception scope processing
in the majority of cases.
Inverse scope processing checks every entity in the rebuild package, whereas exception scope processing
checks non-preparable entities only if their parents have not changed. If every preparable entity in the
package has changed, inverse scope will be slower than exception scope.
In most cases, your package will look much like the one in Figure 3-1 and Figure 3-2, with some
preparable entities that have changed and some that have not.
Each scope processes the unchanged preparable entity in our example in a different way. Inverse scope
processing performs better than exception scope processing because:
When exception scope processing finds that rule1 has not changed, it checks a set of tables that
define the rules relationships. Each child of rule1 is checked for changes. If a child has changed, the
3-3
Processing Options
parent is marked for prepare. In our example, the change to view1 causes rule1 to be marked for
prepare.
When inverse scope processing finds that rule1 has not changed, it does nothing. Inverse scope does
not need to check rule1s relationship tables because it is going to look at every entity in the rebuild
package anyway. When it eventually detects the change to view1, inverse scope identifies the rule as
a parent and marks it for prepare.
In this way, inverse scope processing avoids a major expense; it checks every entity in the rebuild package
whether or not its parent has changed, inverse scope saves the cost of having to check the unchanged
parents relationship tables.
Figure 3-3 shows how exception scope processing handles entities outside the rebuild package.
Figure 3-3
Exception scope: handling entities outside the package

rule1 marked for prepare
so mark process2
as exception
package
rule3
process1
rule1
+
view1
rule2
process2
@+
view2
Change to view1
so mark rule3 for
prepare on 2nd run
@ entity changed
* entity marked as exception
# entity marked for prepare 2nd run
As the example shows, process2 is marked as an exception after rule1 is marked for prepare. When
process2 is added to the rebuild package and the package is analyzed again, rule3 is marked for prepare
because of the change to view1.
Figure 3-4 shows how inverse scope processing handles entities outside the rebuild package.
3-4
Processing Options
Figure 3-4
Inverse scope: handling entities outside the package
process2
package
rule3
process1
rule1
+
Change to view1
so mark rule3 for prepare
view1
rule2
@
@ entity changed
* entity marked as exception
# entity marked for prepare 2nd run
@+
view2
As the example shows, rule3 is marked for prepare because of the change to view1. Once again, inverse
scope mimics the results for exception scope, but now after exception scope has been run a second time,
that is, after the exception has been added to the rebuild package and the package has been analyzed
again.
Figure 3-6 looks at a case in which the scopes give different results.
Figure 3-5
Different Results from Scopes
package
process1
process3
rule1
+
set1
+
@+
Change to set1 so mark

rule4 for prepare
rule4
rule5
rule5 not marked for

prepare despite change
3-5
Processing Options
Figure 3-6
Exception scope: a different result
package
Change to set1 so mark
process3 as exception
process1
*
rule1
+
set1
process3
rule4
@+
Change to set1
so mark rule4 for
prepare on 2nd run
@#
rule5
Change to rule5
so mark rule5 for
prepare on 2nd run
As the example shows, process3 is marked as an exception after set1 is marked for prepare. When
process3 is added to the rebuild package and rebuild analyze is run again, rule4 is marked for prepare
because of the change to set1, while rule5 is marked for prepare because of the change to itself.
Figure 3-6 shows how inverse scope handles the same scenario.
In this case, inverse scope marks rule4 for prepare because of the change to set1, but ignores rule5
because it is not the parent of an entity in the rebuild package
How Inverse Scope Handles Migration Entity Seeds

Inverse scope works the same way for migration entities as application entitiesyou obtain the same
results whether you seed the rebuild package with an application entity or a migration entity seeded with
that application entity.
Specifying Inverse Scope Processing

Before Running Inverse Scope and Running RANALYZE with Inverse Scope describe the steps to run
rebuild analyze with inverse scope.
Before Running Inverse Scope

Before you can run rebuild analyze with inverse scope, you must add views and component subroutines
to an install table that tracks changes to these entities since they were last installed. You do that by
invoking, one time only, the method UPDRSTAT on each repository version.
Note
Non-preparable entities are never actually installed. The product marks these entities as if they had been
installed.
UPDRSTAT first compares the date the non-preparable entity changed with the date its parents were last
installed. (In fact, this is the same comparison that exception scope processing uses to determine
whether a change to a non-preparable entity affects an unchanged parent.)
If the non-preparable entity has changed more recently than its parents were last installed, the entity is
added to the table with an install date less recent than its change date. Thus, if view1 has a change date of
3-6
Processing Options
1/99, and its parents have install dates of 1/97 and 1/98, UPDRSTAT inserts the view in the table with an
install date of 1/99 minus n milliseconds (Figure 3-7).
Figure 3-7
Basic UPDRSTAT processing
installed 1/97
installed 1/98
rule1
rule2
If view1 change date >

rule1 and rule2 install dates,
insert view1 in table with
install date = change date
minus n milliseconds.
view1
changed 1/99
When you run rebuild analyze with inverse scope, RANALYZE consults the table to determine whether
the non-preparable entity has a change date more recent than its install date (in this example, 1/99
versus 1/99 minus n milliseconds). If so, all of the entitys parents are marked for prepare.
In this way, UPDRSTAT averts another costly rebuild-analyze comparison, this time between the date
the non-preparable entity changed and the date each of its parents was installed. The results mimic the
results obtained with exception scope.
UPDRSTAT Reports
UPDRSTAT does not add bitmap implementation names, forms, or physical events to the install table.
For these non-preparable entities, and for views and component subroutines as well, UPDRSTAT
generates a report. The report lists entities that need to be reprepared because of changes to the nonpreparable entities. To view the report, enter the RES command against the management services entity,
as described in Invoking UPDRSTAT.
Conflict Processing
If one parent has an install date less recent than the non-preparable entitys change date, while the other
parents install date is more recent, the process differs (Figure 3-8).
Figure 3-8
UPDRSTAT conflict processing
installed 1/97
installed 1/99
rule1
rule2
view1
If view1 change date

> rule1 install date and
< rule2 install date,
insert view1 in table with

install date = change date.
changed 1/98
First, the non-preparable entity is added to the table with an install date equal to its change date,
meaning that RANALYZE views the entity as not having changed. Second, UPDRSTAT reports that the
parent with the less recent install date (rule1 in our example) needs to be prepared. To view the report,
enter the RES command against the management services entity, as described in Invoking UPDRSTAT.
3-7
Processing Options
Invoking UPDRSTAT
1.
You invoke UPDRSTAT against the management services entity in the entities window for an ADM
project, as shown in Figure 3-9.
Figure 3-9
Running the UPDRSTAT action
Command ===> ______________________________________________________________

Repository: CAPE541
V: 5
Project: ADM
Level: 1
Action
Entity
updrstat
Management Services
________
Migration
________
Project
________
Repository
________
User
******************** BOTTOM OF DATA **********************
2.
When the Rebuild Install update panel is displayed (Figure 3-10), specify the repository version, or
an A for all versions.
3.
At the Commit Count prompt, enter an integer less than 9999 that represents the number of views
you want UPDRSTAT to process before committing the database.
4.
At the Update Rebuild Install Table prompt, specify N if you do not want non-preparable entities to
be added to the tracking table. You will receive a report of UPDRSTAT activity only.
5.
To view the report, enter the RES command against the management services entity.
Figure 3-10
Specifying the entities to update

REBUILD INSTALL -- UPDATE PANEL
Enter processing information and press ENTER.
Version . . . . . . . . . . . .1
Commit Count . . . . . . . . . 200_
Update Rebuild Install Table . Y
Note
You need only run UPDRSTAT once for each repository version. New entities are added to the table as
necessary, without the need to run the utility again.
New PR Flag
When you use the PR command to manually prepare an entity, set the variable UPDENTMT in the
@USRENVn file to Y to update the install date of the entity to the current date, as if rebuild had
prepared and installed the entity. Otherwise, the entity may be prepared again when you do a full
rebuild.
Running RANALYZE with Inverse Scope

Select 1 for inverse scope in the Rebuild Analyze panel, as shown in Figure 3-11. If you plan to use
inverse scope only, set the INVERSE_PREPARE_SCOPE variable in the @RBDENVn file to Y; the option
to specify inverse or exception scope processing will not be displayed on the Rebuild Analyze panel.
3-8
Managing Concurrent Rebuilds
Figure 3-11
Running RANALYZE with inverse scope

Rebuild Analyze for RBDPKG Entity
Name . . . . . APPCFG_CICS_TEST
Version . . . 1
Specify Rebuild Analyze option. Then Press Enter.
Rebuild Analyze option . . . 1 1. Inverse Processing
2. Exception processing
.

Concurrent rebuilds present special problems for repositories with a high degree of object reuse.
Consider the scenario described in Figure 3-12. rule1 is contained in rebuild package1 and rebuild
package2. rebuild package1 is prepared on March 3; its executables are stored in a staging library until
the package can be installed. Meanwhile, rule1 is changed on March 4 and rebuild package2 is prepared.
Because package2s executables are stored in a separate staging library, the change to rule1 is not
reflected in the staging library for package1. If rebuild package1 is installed after rebuild package2, the
change will be lost.
Figure 3-12
Concurrent Rebuilds
prepared 3/3
prepared 3/5
package1
package2
rule1
changed 3/4
library1
Problem: library1 does

not reflect change to rule1
library2
Concurrent Rebuilds with Staging Libraries

The rebuild prepare feature in AppBuilder lets you use a single staging library for concurrent rebuilds in
a repository version, as shown in Figure 3-13. The single staging library reflects the most current state of
the entities in the rebuild packages.
3-9
Figure 3-13
Concurrent rebuilds with a single staging library
prepared 3/3
prepared 3/5
package1
package2
rule1
changed 3/4
Solution: single staging

library reflects change to rule1
library
Keep in mind the following tradeoffs in using single staging libraries for concurrent rebuilds:
If your site is doing many concurrent rebuilds, you may run into resource contention problems as
the rebuilds wait for the single library to become available.
Single staging libraries use more disk space, because they contain information for multiple rebuilds
in a repository version.
Specifying Single Staging Libraries

To specify a single staging library:
1.
Set the variable ONE_STAGING_LIB in the @RBDENVn file to Y to specify that you want to use a
single staging library.
2.
Specify a dataset qualifier for the library in the variable RBD_DSN_QUALIFIER in the @USRENVn
file. The default is RBDPKG. For example, you might have a staging library dataset name of
HPSOUT.FF1.RBDPKG.STATLNK.
The file @SEERENV INI file contains dataset storage information about staging libraries, both single and multiple, in lines of the form:
VFLE_1= 1 CYL PO FB 80 3120 NEWFREE CATALOG N/A STATLNK STATLNK
VFL2_1= 20 10 100
The values for multiple staging libraries are calculated internally. The repository administrator must
set the required values for single staging libraries. On every VFLE_n and VFL2_n line, specify values
for the fields shown in bold in the example:
Type of storage (CYL, for cylinder storage, in line 1 of the example)
Number of primary storage (20, in line 2 of the example)
Number of secondary storage (10, in line 2 of the example)
Number of directory blocks (100, in line 2 of the example)
Make sure to overestimate so that you dont run out of space and do not modify any other settings.
The datasets will not be allocated during a rebuild until they are needed (as determined by rebuild
analyze).
3-10
Updating CICS using the DFHCSDUP Batch Facility

When you prepare a rule in the host environment, AppBuilder automatically updates the platform the
rule executes in. For CICS, the updates are managed in a batch job that simulates a user performing the
updates with an LU2 script file.
This approach works well for ordinary prepares in a development environment, where you are typically
processing one rule at a time. It works much less efficiently in a rebuild, where different script
commands have to be generated and executed for every rule being prepared.
The rebuild install feature in AppBuilder lets you use an IBM batch facility called DFHCSDUP to update
CICS. Instead of generating multiple LU2 script commands, rebuild install simply writes the required
updates to an intermediate file, which the utility then uses to perform the updates in CICS. Note that
you must recycle the CICS region before the changes are activated.
Specifying DFHCSDUP Processing

To specify DFHCSDUP processing:
1.
Set the variable RDODEFN in the CICS INI file for the repository version to Y to specify that you
want to use DFHCSDUP.
2.
In the variable RDOCSDLT in the CICS INI file, specify Y if you want to submit the batch job
automatically, N if you want to save the job stream to a dataset for later execution. The RDOCSDLT
option is useful at sites at which only CICS systems programmers are authorized to execute the
DFHCSDUP utility.
The sequential dataset for the intermediate file has a name of the form:
<QUALIFIERS.PERMQUAL>.<REPOSITORY.REPID>.<RQST.VERSION>.
<PARMS.SYSTEMID>.RINSTALL.HMFCDUP
Sample command language to run the DFHCSDUP batch utility follows:
//XXXXXXXX JOB (DRHA-AZ),'DFHCSDUP',PRTY=15,
//
MSGLEVEL=(1,1),CLASS=1,MSGCLASS=X,
//
NOTIFY=XXXXXX,TIME=10
//*
//STEP01
EXEC PGM=DFHCSDUP,REGION=3M
//*
//STEPLIB DD DSN=CICS.SDFHLOAD,DISP=SHR
//*
//DFHCSD
DD DSN=<CICS.CSDNAME>,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSOUT
DD SYSOUT=*
//SYSIN
DD DSN= <QUALIFIERS.PERMQUAL>.<REPOSITORY.
REPID>.<RQST.VERSION>. <PARMS.SYSTEMID>.
RINSTALL.HMFCDUP, DISP=SHR
3-11
3-12
CHAPTER
REBUILD ACTIONS
The rebuild actions and methods outlined in this section allow you to control the rebuild process by
generating reports, overriding values, automating the rebuild process, maintaining the repository, and
other functions. Topics include:
Rebuild Action Summary
Install Objects in the Rebuild Package
Add an Entity
List Rebuild Contents
Add Keywords
List Relations
Add a Relation
Maintain Entity
Add Text to Entity
Maintain Relation
Add Text to Relation
Prepare Object in Rebuild Package
Analyze Rebuild Impact
Reset Object Install Status
Clean-up Rebuild Information
Reset Object Prepare Status
Delete Entity
Set Rebuild Install Status
Delete Relation
Super Prepare
Export Rebuild Package
View Results of Rebuild

Table 4-1 lists and describes each action in alphabetical order by command and gives a reference so you
can find more detailed information. Your enterprise administrator controls the INI variables.
Note
Table 4-1
Refer to the Enterprise Administration Guide for more information on mainframe actions.
Rebuild Actions
Action
Description
ACTIONS
List entity actions
Displays all actions available to you. The actions available depend on where
you are in the rebuild process. This is a standard repository action.
ADDE
Add an entity
Adds a rebuild package entity. See Add an Entity.
ADDR
Add a relation
Adds a relation between the rebuild package entity and each root entity to be
included in the rebuild package. See Add a Relation.
AUTOSAVE
Update Autosave setting
Turns the autosave feature on or off. This is a standard repository action.
4-1
Table 4-1
4-2
Rebuild Actions (Continued)
Action
Description
BE
Browse entity
Lets you see the entity attributes, but not change them. This is a standard
repository action.
BK
Browse keywords
Lets you see an entitys keywords, but not change them. This is a standard
repository action.
BR
Browse relation
Lets you see the relation attributes, but not change them. This is a standard
repository action.
BTXE
Browse entity text
Lets you see an entitys text, but not change it. This is a standard repository
action.
CLEANUP
Clean-up rebuild information
Deletes rebuild files and rebuild processing information from internal control
tables.
See Clean-up Rebuild Information.
CO
Change ownership of entity
Changes the ownership of an entity from your user ID or project to another user
ID or project. This is a standard repository action.
DE
Delete entity
Deletes an entity from the enterprise repository.

See Delete Entity.
DEBUG
Update debug profile
Customizes your debug profile so you can determine the level of detail you see
on the screen. This is a standard repository action.
DR
Delete relation
Deletes a relation from the enterprise repository.

See Delete Relation.
ENTITY
Display entities
Return to the Host Workbench panel.This is a standard repository action.
EW
Extended where-used report
Generates an online report that shows an entitys parent entities, as well as their
parent entities, and so on to the top of the hierarchy. This is a standard
repository action.
EXPORT
Export rebuild package
Export a rebuild package to download to a Workgroup repository the objects

that need to be prepared on a workstation.
See Export Rebuild Package.
INIDISP
View AppBuilder INI files
Displays the environment control command lists (CLISTs). This is a standard

repository action.
K
Add keywords to entity
Adds keywords to the rebuild package entity so you can define the rebuild
package.
See Add Keywords.
LE
List entities
Displays an entity list of the particular type of entity you choose. This is a
standard repository action.
LISTRBD
List rebuild contents
Lists object counts, objects included in rebuild package and their rebuild status.
See List Rebuild Contents.
LOCK
Lock entity
Locks an entity, which prevents others from making changes to the entity. This is
a standard repository action.
LR
List relations
Lists instances of relationships between two entity types. After analysis, the LR
action will also list items affected by the rebuild process.
See List Relations.
ME
Maintain entity
Displays the detail panel of any listed entity, and lets you modify the entity
attributes.
See Maintain Entity.
MR
Maintain relation
Displays the detail panel of any listed relation, and lets you modify the relation
attributes.
See Maintain Relation.
PROJECTS
Change projects
Lets you change from one project or version within a repository to another. This
is a standard repository action.
Rebuild Actions
Table 4-1
Rebuild Actions (Continued)
Action
Description
RANALYZE
Analyze rebuild impact
Identifies objects in the rebuild package that need to be prepared.

See Analyze Rebuild Impact.
REFRESH
Refresh the screen
Updates the data and state values on any panel. This is a standard repository
action.
RES
View results of rebuild
Lets you browse the results of the rebuild actions.

See View Results of Rebuild.
RESETINS
Reset object install status
Lets you change the install status of an object to what it was before an
attempted install.
See Reset Object Install Status.
RESETPR
Reset object prepare status
Lets you change the prepare status of an object to what it was before an
attempted prepare.
SeeReset Object Prepare Status.
RINSTALL
Install the objects in the rebuild
package
Installs the objects in the rebuild package.

See Install Objects in the Rebuild Package.
RPREPARE
Prepare objects in rebuild
package
Prepares the objects in the rebuild package that were marked for prepare during
analyze processing.
SeePrepare Object in Rebuild Package.
RSTATUS
Set the installation status of
rebuild package object
Sets the installation status of rebuild package objects.

See Set Rebuild Install Status.
SA
Save as
Lets you save an entity as a new entity with the same user-defined attributes.
This is a standard repository action.
SRCH
Search for keywords
Helps you find and reuse existing entities by searching for entities of all types
associated with specified keywords. This is a standard repository action.
SUPERPR
Super prepare
Lets you automatically analyze, prepare, and install all objects in one step.
See Super Prepare.
TXE
Add text to entity
Adds text to the rebuild package entity so you can define the rebuild package.
See Add Text to Entity.
TXR
Add text to relation
Adds text to a relation so you can define the purpose of that relation.
See Add Text to Relation.
UEMTH
Define user entity method
Provides access to user-written software to perform custom processing on any

entity. This is a standard repository action.
UNLOCK
Unlock entity
Unlocks an entity, which allows others to make changes to the entity. This is a
standard repository action.
UPROF
Update user profile
Lets you update any of the attributes that define your user ID. This is a standard
repository action.
URMTH
Define user relation method
Provides access to user-written software to perform custom processing on any

relation. This is a standard repository action.
Add an Entity
The add an entity (ADDE) action is the Create action common to all entity types. The created entity is
called the rebuild entity and all actions performed during rebuild source processing effect it.
In the target environment, use the add an entity (ADDE) action to display a blank Add an Entity panel
and enter the attribute values for a new rebuild entity. All target actions relate to this entity.
4-3
Attributes
An attribute is a single characteristic of an entity or relationship. There are two types of attributes:
User-defined Attributes
System-generated Attributes
User-defined Attributes
Whenever you create a rebuild package in the repository, you must name the rebuild entity. The first
four attributes that appear on the Add an Entity panel identify the object and its status. The name and
description attributes are user-definable. The system automatically generates the other attributes.
Table 4-2 lists and describes the user-defined rebuild entity attributes.
Table 4-2
User-defined rebuild entity attributes
User-defined attribute
Description
Name
Required.
An alphanumeric string up to either 30 single-byte or 14 double-byte characters.
No default.
Description
Optional.
Up to 30 characters of text that explains the purpose of the rebuild to other Rebuild
Facility users.
No default value is generated. Although a description is optional, it is highly
recommended because it makes the rebuild entity much more useful to other project
members.
System-generated Attributes
When you save the rebuild entity, the system generates the rest of the rebuild attributes and the audit
attributes (Figure 4-1).
The following topics describe details related to the system-generated attributes:
Rebuild Attributes
Audit Attributes
Figure 4-1
Rebuild entity attributes

Maintain an Entity
Repository: SUNRISE
4-4
V: 2
Project: DEV
More:
Level: 3

Name . . . . . . . . . . .
System Id . . . . . . . . .
Description . . . . . . . .
Rebuild Package State . . .
. DMC_VER2_RBD__________________
: AA5ENR
. MIGRATED DMC_APP_1 FROM V1 TO V2
: 18
N/A
Audit Attributes:
Date Created . .
Time Created . .
Created by . . .
Date Maintained .
Time Maintained .
Maintained by . .
Project . . . . .
Change # . . . .
Owner Id . . . .
Local Maintenance
:
:
:
:
:
:
:
:
:
:
Rebuild Actions
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
Date
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
95/05/17
18:53
SS0222
95/10/09
18:53
SS0222
DEV
0003
SS0222
95/10/09
Rebuild Attributes
Rebuild attributes identify both the object and its status. The system does not generate values for
description or name. The system ID, rebuild state, and audit attributes are generated automatically.
Table 4-3 lists and describes the system-generated rebuild attributes.
Table 4-3
System-generated rebuild entity attributes
System-generated attribute
Description
System ID
A default ID that consists of six single-byte characters. The first four characters are
random alphanumeric characters. The starting string of characters is set at
installation time and the string is incremented with each new creation. The last two
characters are the alphanumeric repository identifier that is also defined at
installation.
Rebuild State
The state of the entity in the following rebuild jobs: analyze, rebuild, prepare, install.
Not Applicable - the entity has not yet been seeded with one or more root entities.
Submitted - the job has been submitted and it is in the queue, but it has not been
processed.
Executing - the job has been submitted, and it is being processed.
Incomplete - a JCL error has prevented the job from finishing.
Successful - the batch job ran successfully.
Failed - the job was submitted and the system processed it, but the job failed
from a system or a job-related error. Exit the Rebuild Facility and browse the job
results in the system utilities.
Seeded - you have added one or more root entities to the rebuild entity.
Exceptions seeded - objects that may impact the objects you explicitly added to a
rebuild entity have also been added.
Audit Attributes
Audit attributes include 14 fields that indicate who created or modified the object, as well as the time
and date it was created or last modified (Figure 4-1). The system automatically generates the values
when you save the entity and you cannot directly edit them. Table 4-4 describes the audit attributes.
Table 4-4
Audit attributes
Audit attribute
Description
Date Created
The date (year/month/day) the rebuild object was created.
Time Created
The time, based on a 24-hour clock, when the rebuild object was created.
Created by
The user ID of the individual who created the rebuild object.
Date Maintained
The date (year/month/day) the rebuild object was last modified.
Time Maintained
The time, based on a 24-hour clock, when the rebuild object was last modified.
Maintained by
The user ID of the individual who last modified the rebuild object.
Project
The name of the project in which the rebuild object was created.
Change #
The number of times that the rebuild object has been updated. A value of 0001
indicates that the object has not been changed since it was created and 0002
indicates it has been changed and saved once since it was created.
NOTE: The change number increases by one each time an object is saved, even if
the object data do not change, or if only objects parts change.
Owner ID
The user ID of the individual who created the rebuild object.
Local Maintenance
The user ID of the individual who created the rebuild object on the host.
Local Date
The date (year/month/day) the rebuild object was last modified on the host.
4-5
Table 4-4
Audit attributes (Continued)
Audit attribute
Description
Local Time
The time, based on a 24-hour clock, when the rebuild object was last modified on the
host.
Local Project
The name of the project on the host in which the rebuild object was created.
Local User
The user ID of the individual who last modified the rebuild object on the host.
Version
The repository version in which the rebuild object was created.
Input
User input from the Add an Entity panel.
Output
None.
Result
The rebuild entity is not complete until you add one or more root entities to it. At this stage, you can
only list existing entities with the list entity (LE) action, maintain entities with the maintain entity (ME)
action, or delete entities with the delete entity (DE) action.
Add Keywords
To reuse entities, developers must be able to find entities they can use in their applications. The keyword
(K) action associates entity instances of different types with a particular subject. Defining consistent
keywords lets you systematically search the repository for rebuild entities that you can reuse, as well as
other reusable objects. See Figure 2-8 for an example of adding keywords.
Keyword Attributes
Keywords have no specific attributes. However, note that each word separated by a space is treated as an
individual keyword, and that the total number of characters used for all of an entitys keywords can not
exceed 240.
Input
User input from the Keywords for Migration panel.
Output
Keywords are added to the E_KEYWRD table.
Result
You can display or modify the keywords for a given entity by using the add keywords (K) action again.
You can also search for keywords by using the search for keywords (SRCH) action.
4-6
Rebuild Actions
Add a Relation
The add a relation (ADDR) action lets you include entities in the rebuild package by creating relations
between the rebuild entity and the objects that you want to rebuild. When you add a relation between
the rebuild entity and a root entity, you have seeded the rebuild entity.
See Step 2 - Select Objects for Rebuild Processing on page 2-7 for detailed instructions on adding a
relation. You can add to the rebuild entity (one at a time) any of the relations below:
Has-Root Component
Has-Root File
Has-Root Function
Profiles Group
Has-Root Migration
Has-Root Process
Has-Root Report
Has-Root Rule
Has-Root Set
Has-Root Window
Add a Relation Attributes

The following attributes can be defined for the Add a Relation entity:
User-defined Relation Attributes
System-generated Relation Attributes
User-defined Relation Attributes
Whenever you add relations to the rebuild entity, you must assign values for several attributes. On the
Action Information pop-up panel, choose the relation type you want. The rest of the information on the
panel is for your information; you cannot change it.
On the Add a Relation panel, you need to specify either the rebuild entity name or root entity name,
depending on which entity you are adding the relation from. You also need to choose the rebuild scope.
The system generates the audit information when you save the relation. Table 4-5 lists and describes each
user-defined relation attribute.
Table 4-5
User-defined relation attributes
User-defined Attribute
Description
Rebuild Name
Required.
An alphanumeric string up to 30 single-byte or 14 double-byte characters. Must match
the name of an existing rebuild entity.
NOTE: The system populates this field if you are adding a relation from the rebuild entity.
Has-Root-Entity Name
Required.
An alphanumeric string up to 30 single-byte or 14 double-byte characters. Must match
the name of an existing entity of the same type.
NOTE: The system populates this field if you are adding a relation from the root entity.
4-7
System-generated Relation Attributes

The system automatically populates the Rebuild Name or Has-Root-Entity Name fields, depending on
which entity you are adding the relation from. As soon as you save the relation, the system also generates
the audit attributes. Audit attributes include twelve fields that indicate who created or modified the
object, as well as the time and date it was created or last modified. You cannot edit these field values
directly. See Table 4-6 for detailed descriptions of system-generated attributes
.
Table 4-6
System-generated relation attributes
System-generated attribute
Description
Rebuild Name
The system populates this field only if you are adding a relation from the rebuild
entity.
Has-Root-Entity Name
The system populates this field only if you are adding a relation from the root entity.
Date Created
The date (year/month/day) the relation was created.
Time Created
The time, based on a 24-hour clock, when the relation was created.
Created by
The user ID of the individual who created the relation.
Date Maintained
The date (year/month/day) the relation was last modified.
Time Maintained
The time, based on a 24-hour clock, when the relation was last modified.
Maintained by
The user ID of the individual who last modified the relation.
Change #
The number of times that the relation has been updated. A value of 0001 indicates
that the relation has not been changed since it was created and 0002 indicates it
has been changed and saved once since it was created.
NOTE: The change number increases by one each time an object is saved, even if
the object data does not change, or if only its parts change.
Local Maintenance Date
The date (year/month/day) the relation was last modified on the host.
Local Maintenance Time
The time, based on a 24-hour clock, the relation was last modified on the host.
Local Maintenance Project
The name of the project on the host in which the relation was created.
Local Maintenance User
The user ID of the individual who last modified the relation on the host.
Version
The project version in which the relation was created.
Input
User input from the Add a Relation panel.
Output
None.
Result
At this stage, you can list the root, or seed, entities that are included in the rebuild package with the list
relation (LR) action, maintain the relation with the maintain relation (MR) action, or delete the relation
with the delete relation (DR) action.
Add Text to Entity

Add text to your rebuild entity to describe the purpose and scope of the rebuild package to other Rebuild
Facility users. Include a brief description of the entitys purpose and the type of information it contains.
4-8
Rebuild Actions
For example, if you are rebuilding a fix into production, explain that in the text. See Figure 2-5 on
page 2-5 for an example of adding text to a rebuild entity.
Attributes
Text has no specific attributes.
Input
User input from the Text for Migration panel.
Output
Text is added to the E_TEXT table.
Result
You can display or modify the text for a given entity by using the add text to entity (TXE) action again.
Add Text to Relation

Add text to the relations between your rebuild entity and objects in the rebuild package. Use the text to
describe the purpose and scope of the rebuild package to other Rebuild Facility users. Include a brief
description of the relations purpose. For example, if you have attached the hierarchy of a new
application that you are rebuilding for the first time, explain that in the text. See Step 2 - Select Objects
for Rebuild Processing on page 2-7 for more information.
Attributes
Text has no specific attributes.
Input
User input from the Text panel.
Output
Text is stored in the E_TEXT table.
Result
You can display or modify the text for a given entity by using the add text to relation (TXR) action again.
4-9
Analyze Rebuild Impact

environment that must be prepared after you have imported a migration, or made changes to one or
more entities.
The analyze rebuild impact (RANALYZE) action submits a batch job that generates an online report.
The report lists every entity that needs to be prepared and installed by name, system ID, entity type, and
execution environment.
The analyze process also writes a list of objects that need to prepared on the workstation to an advice file
if the value of the RBWB variable in the @USRENVn file, where n is the repository version number, is
set to Y for Yes.
After you export the rebuild entity, you read in the advice file on the workstation and then prepare the
objects. The file has the same high-level qualifiers as the Results file, which is defined when AppBuilder
software is installed. The low-level qualifier is ADVICE. See Export Rebuild Package.
Figure 4-2 shows part of an example advice file.
Figure 4-2
Sample advice file
RBDCNTL)
REPNAME=SUNRISE
PCCODEPG=437
MFCODEPG=037
MIGREL=MHPS531
HPSREL=
TIME=11:11
DATE=95/11/22
V=1
RBDID=AGWASR
OBJECT PREPARE)
COMPONENT Prepare)
XVT_COMPONENT_WKS_PCCMPU:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
COMPONENT Prepare)
XVT_COMPONENT_WKS_PCCMPS:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
COMPONENT Prepare)
XVT_COMPONENT_WKS_C:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
COMPONENT Prepare)
XVT_COMPONENT_WKS_C_DB2:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
REPORT Prepare)
XVT_REPORT_WKS:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
RULE Prepare)
XVT_RULE_WKS_DRIVER:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
RULE Prepare)
XVT_RULE_PCCICS3270_DRIVER:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
RULE Prepare)
XVT_RULE_PCCICS_COOP_DRIVER:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
RULE Prepare)
XVT_RULE_PCCICS_DRIVER:MACHINE=Local,DBTYPE=DB2/2,TARGETENV=OS/2
RULE Prepare)
If the rebuild analyze job fails, review the job results using the Spool Display and Search Facility (SDSF),
correct the problem, and run the job again.
4-10
Rebuild Actions
Processing Options
The processing options let you select which parts (text, keywords, source) you want to include in rebuild
analysis. Type a space in the selection field to exclude an option from processing.
Note
See your repository administrator to override the default processing options.
Commits and Rollbacks

The COMMIT_LEVEL variable in the @RBDENVn.INI file, where n is the repository version number,
controls how analyze processing handles commits and rollbacks if an analyze job fails. If the variable has
a value of 0, any error incurred during analyze processing will result in the rollback of the entire rebuild
package. Once you determine what caused the failure and have corrected that condition, you can reload
or restart analyze processing.
If the COMMIT_LEVEL variable has a numerical value greater than 0, then commits and rollbacks are
performed at the object level. Any error incurred during analyze processing will result in the rollback of
the last n number of objects, where n is the value of the COMMIT_LEVEL variable. The rollback
includes the specified number of objects and all of their parts: keywords, relations, source code, and text.
Once you determine what caused the failure and have corrected that condition, you can reload or restart
analyze processing.
You can restart or reload the RANALYZE action. Restart continues rebuild processing from the last
phase that completed successfully. Select the Restart option to start the job from the internal step that
failed. Reload starts rebuild over again from the beginning. Select the Reload Rebuild Files option to
resubmit the analyze job from the beginning.
Input
None.
Output
User results displayed by entering RES.
Result
RANALYZE submits a TSO job. Once the job has finished, you can review the results online in three
ways:
Refresh the Maintain an Entity panel (press F19) to see the current Rebuild State attribute. The state
reflects the submission, execution, incompletion, success, or failure of the job.
Record the job number that is displayed after you submit the analyze job; then use SDSF to get
detailed job status information.
Look at the messages associated with analyze processing.
4-11
When you determine that the analyze has been successful, you can use the following actions to examine
the rebuild package:
Use the list rebuild contents (LISTRBD) action to view the rebuild impact.
Use the list relation (LR) action to see which objects need to be prepared as a result of the rebuild.
The resulting list has a rebuild will prepare message by each object to be prepared.
Clean-up Rebuild Information

The clean-up rebuild information (CLEANUP) action deletes rebuild files and rebuild processing
information from internal control tables, and then sets the status of the rebuild package entity to seeded.
The clean-up rebuild information action is useful when you have started processing a rebuild package
but want to change its contents and begin processing again.
To clean-up the Rebuild process:
1.
Navigate to the List Facility for the rebuild package entity, type CLEANUP on the action line by the
entity for which you want to delete rebuild information, and press Enter. A confirmation pop-up
panel is displayed, as in Figure 4-3.
Figure 4-3
Cleanup confirmation pop-up panel
------------------- Confirm Request -------------------|

|
|
Rebuild Package is in progress. Should continue
|
|
with Clean-Up?
|
|
|
|
|
|
|
|
_ 1. Yes
|
|
2. No
|
The system displays the message:

Clean-up Rebuild Information for <entity> Processed
2.
After the CLEANUP action completes, type ME by the rebuild package entity and note that the
rebuild package state has been reset to seeded.
Note
You must use the clean-up rebuild information action before deleting a rebuild package entity, unless you
delete before analyzing or after successfully installing the entity.
Options
The clean-up rebuild information action has no options.
Input
None.
Output
The RES command will display if the Cleanup was successful.
4-12
Rebuild Actions
Result
Rebuild files and rebuild processing information from internal control tables are deleted.
Delete Entity
The delete entity (DE) action deletes a rebuild package entity. You must use the clean-up rebuild
information (CLEANUP) action before deleting a rebuild package entity, unless you delete before
analyzing or after successfully installing the entity.
Delete Relation
The delete relation (DR) action deletes a relation from a rebuild entity. Use the delete relation action to
delete any entities you do not want in the rebuild package. First use the list relation (LR) action next to
the rebuild package entity from which you want to delete a relation. Then use the delete relation (DR)
action next to the relation you want to delete.
You must use the clean-up rebuild information (CLEANUP) action before deleting a relation from the
rebuild package entity, unless you delete the relation before analyzing or after successfully installing the
entity.
Export Rebuild Package

Use the export rebuild package (EXPORT) action to get the files you need to download for the objects
that are to be prepared on the workstation. Make sure that the RBWB variable in the USERENVn file is
set to YES so that the analyze process creates an advice file listing all the objects that need preparation on
the workstation.
To export a rebuild package:
1.
Type EXPORT in the action line next to the rebuild package entity that you have already analyzed.
The panel in Figure 4-4 asks you to specify the data set prefix for the migration files. These
migration files contain the objects that the advice file identifies as needing preparation on the
workstation.
Figure 4-4
Exporting a rebuild package

Migration Export Options
Name . . . . . . . . : DMC_VER2_RBD
Version . . . . . . : 1
Type 's' to select an option or type a space to deselect. Then press ENTER.
Processing Options
Object Parts to Process
. . . . . . . S Text
S Source
S Keywords
Data Set Prefix for Migration Files
. SS0222.ADV.SRCE
4-13
2.
After the export job has finished, look at the contents of the export by typing LISTMIG next to the
rebuild entity you exported. Figure 4-5 shows a sample that lists the counts of the entities and
relations exported.
Figure 4-5
Command
Listing the exported contents of the rebuild entity

List Contents of Migration DMC_VER2_RBD Version 2
=======> __________________________________________________________
Type FILTER ON/OFF/MODIFY on command line for filter processing.
Display Parts Y
Migration
Status
_ All
_ Exported
Total
Count
2097
2097
Entity
Count
915
915
Relation
Count
1182
1182
******************************* BOTTOM OF DATA ******************************
3.
You can view the list of these files with ISPF Primary Option 3.4, Data Set List Utility. Type the same
data set prefix you specified for the migration file in Figure 4-4 in the DNAME LEVEL field on the
Data Set List Utility panel.
4.
Press Enter. The list of data sets beginning with that prefix is displayed, as Figure 4-6 shows.
Figure 4-6
Listing the migration data sets
DSLIST - DATA SETS BEGINNING WITH SS0222.ADV.SRCE --------------- ROW 1 OF 13

COMMAND ===>
SCROLL ===> PAGE
COMMAND
NAME
MESSAGE
VOLUME
------------------------------------------------------------------------------SS0222.ADV.SRCE.MIG.ELOGKEY
NAAD24
SS0222.ADV.SRCE.MIG.EMIG
NAAD24
SS0222.ADV.SRCE.MIG.ENTITY
MDAA04
SS0222.ADV.SRCE.MIG.INMIG
MDAA04
SS0222.ADV.SRCE.MIG.KEYWORD
MDAA04
SS0222.ADV.SRCE.MIG.MIGCNTL
NAAD01
SS0222.ADV.SRCE.MIG.MIGXX
MDAA01
SS0222.ADV.SRCE.MIG.RELATE
MDAA01
SS0222.ADV.SRCE.MIG.RLOGKEY
MDAA01
SS0222.ADV.SRCE.MIG.SOURCE
NAVA02
SS0222.ADV.SRCE.MIG.SRCBDAT
MDAA01
SS0222.ADV.SRCE.MIG.SRCBHDR
NAVA02
SS0222.ADV.SRCE.MIG.TEXT
NAAD24
***************************** END OF DATA SET LIST ****************************
5.
When you are ready to import these files and the advice file on the workstation, go to ISPF Primary
Option 6. On the workstation you will specify the migration data set prefix in a script to download
these files and the advice file. You use the migration facility to import them into a repository and
use the Construction Workbench to prepare the objects.
Refer to Enterprise Migration Guide for information about the download script and the Migration
Workbench. Refer to the Developing Applications Guide for information about preparing the objects
listed in the advice file and using Construction Workbench.
Install Objects in the Rebuild Package

After the rebuild prepare (RPREPARE) action creates executable code, you must install the code. The
rebuild install (RINSTALL) action moves executable files into user libraries for testing. The RINSTALL
action submits a batch driver job that submits multiple jobs that copy the host executable files from
staging data sets to user run-time libraries, and then binds them.
4-14
Rebuild Actions
Figure 4-7 shows the results of the list rebuild contents (LISTRBD) action after the install rebuild
package (RINSTALL) action.
Figure 4-7
List rebuild contents after installing the rebuild package

List Rebuild Contents for RBDPKG DMV_VER2_RBD Version 1
Rebuild
Entity
Status
Count
_ All
206
_ Prepare Successful
62
_ Prepare Needed
23
_ Install Copy Successful
60
_ Install Top Bind Failed
13
_ Install LU2 Failed
39
_ Install Intermediate Bind Needed
9
******************************* BOTTOM OF DATA *******************************
Figure 4-8 shows the Repository Browser panel that is displayed after you type RES (view results action)
next to a rebuild package entity.
Figure 4-8
Repository File Browser panel from a LISTRBD action

Repository File Browser
Name . . . . . . . : DMV_VER2_RBD
Version . . . . . : 2
Select one or more of the following.
S=Browse P=Print D=Delete
Then press ENTER.
Action Method
Results File
_
ANALYZE
Analyze Job Stats / Messages
_
PREPARE
Prepare Job Stats / Messages
_
INSTALL
Install Job Stats / Messages
_
INSTALL
Install Static Link Messages
_
INSTALL
Install Copy PDS Messages
S
INSTALL
Install Copy VSAM Messages
_
INSTALL
Install Package Bind Messages
_
INSTALL
Install Top Bind Messages
_
INSTALL
Install Interm Bind Messages
_
INSTALL
Install LU2 Messages
******************************* BOTTOM OF DATA ********************************
You can type an S next to the results file you want to view. Figure 4-9 shows the Repository File Browser
panel that lists the Install Copy VSAM messages.
Figure 4-9
Viewing the results of installing VSAM files
--------- SEEROUT.SR1.AGG9SR.RINSTALL.RESVSAM ------ LINE 00000000 COL 001 080

Name . . . . . . . : DMV_VER2_RBD
Version . . . . . : 1
********************************* TOP OF DATA **********************************
GR0107I *********************************************************
GR0109E - Results for COPY VSAM records phase for Rebuild Package: DMV_VER2_RBD
GR9047E - Changing status of Install Action Copy Relation record(s) for Batch to
GR9047E - Changing status of Install Action Copy Rule Source record(s) for Batch
GR9047E - Changing status of Install Action Copy VIEWDEF record(s) for Batch to
GR9047E - Changing status of Install Action Copy Relation record(s) for CICS to
GR9047E - Changing status of Install Action Copy Rule Source record(s) for CICS
GR9047E - Changing status of Install Action Copy VIEWDEF record(s) for CICS to S
GR9047E - Changing status of Install Action Copy VIDTEXT record(s) to Successful
GR0113I - All Non-IMS VSAM records have been copied successfully.
******************************** BOTTOM OF DATA ********************************
4-15
Results
The rebuild install (RINSTALL) action submits one driver job which submits multiple jobs to fulfill your
request. Once the jobs are finished, you can review the results online in several ways:
reflects the submission, execution, and success or failure of the job.
Use the list rebuild (LISTRBD) action to monitor each rebuild install status.
To get more information for processed installs, use the view results (RES) action by typing RES on
the action line beside the rebuild package entity you want to view.
To track the job, record the job number displayed after you submit the rebuild install job and then
choose the SDSF in ISPF to get detailed job status information.
Look at the messages associated with rebuild install processing. For instructions on accessing,
interpreting, and printing results messages, refer to the Enterprise Administration Guide.
If the job fails, correct the problem and resubmit the job with the Resubmit Failed Objects option
selected.
If the install failed because of an external condition, such as running out of space, you can reset the
install status after correcting the environmental condition that caused the failure.
List Rebuild Contents

Use the list rebuild contents (LISTRBD) action to see the exact contents of the rebuild package, as well as
to select processing options on an object-by-object basis. The list rebuild contents action lists all objects
in the rebuild package, so you can see exactly what was updated or created in the repository.
You filter the report to include or exclude entities and relations from the rebuild contents list that the
system generates. A filter summary provides a count of total objects, filtered objects, filtered entities, and
filtered relations. The entity and relation filters allow you to select which types of entities and relations to
include in your rebuild contents list. Using the filters to get a report that lists only the objects of interest
speeds processing.
Using Filters to List Rebuild Contents

To apply filters to your list of rebuild contents:
4-16
1.
Type LISTRBD on the action line beside the name of the rebuild entity.
2.
On the command line, type FILTER MODIFY to change the filter options (Figure 4-10). Press
Enter.
Rebuild Actions
Figure 4-10
Modifying filter settings

List Contents of Rebuild Package DMC_VER2_RBD Version 2
Rebuild
Entity
Status
Count
_ All
205
_ Prepare Needed
84
_ Install Copy Needed
60
_ Install Top Bind Needed
13
_ Install LU2 Needed
39
9
******************************* BOTTOM OF DATA *******************************
3.
A pop-up panel displays a list of entities to select for filtering on the left and a summary of the
current filter settings on the right, as shown in Figure 4-11.
Figure 4-11
Selecting platforms for filtering
---------------------------------------------------------------------------|
|
|----------------------------------------------------------------------------|
|------------ Platform Filter ------------------- Filter Summary -------|
|
| |
|
|
| |
|
| Press ENTER to apply selection.
| | Counts:
|
| RIGHT/LEFT will toggle to the next filter. | | Total......... 205
|
|
| | Filtered...... 195
|
|
All
| |
|
|
MNFR
| | Filters:
|
| S PC
| | Entity ....... Filtered
|
|*************** BOTTOM OF DATA **************| | Phase ........ All
|
|
| | Platform ..... All
|
|
| | Project ...... All
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
----------------------------------------------------------------------------
4.
Select a filter. Type an S next to the filter you want to use: All, MNFR (mainframe), or PC
(workstation). Press Enter to apply the filter.
5.
Press F11 to display a pop-up panel and select the phases for filtering, as shown in Figure 4-12.
4-17
Figure 4-12
Selecting phases for filtering
---------------------------------------------------------------------------|
|
|----------------------------------------------------------------------------|
|--------------- Phase Filter -------------------- Filter Summary -------|
|
| |
|
|
| |
|
| | Counts:
|
|
|
| | Filtered...... 70
|
| _ All
| |
|
| _ Install Copy
| | Filters:
|
| _ Install Inter Bind
|
| _ Install LU2
| | Phase ........ All
|
| _ Install Top Bind
| | Platform ..... Filtered
|
| S Prepare
|
|************** BOTTOM OF DATA ***************| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
----------------------------------------------------------------------------
6.
Press F11 again to display a pop-up panel on which you can apply filtering to projects,as Figure 4-13
shows.
Figure 4-13
Selecting projects for filtering
----------------------------------------------------------------------------- |
|
|-----------------------------------------------------------------------------|
|--------------- Project Filter ------------------ Filter Summary --------|
|
| |
|
|
| |
|
| | Counts:
|
|
|
| | Filtered...... 20
|
| _ All
| |
|
| S DEV
| | Filters:
|
|************** BOTTOM OF DATA ***************| | Entity ....... Filtered
|
|
| | Phase ........ All
|
|
|
|
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
-----------------------------------------------------------------------------
7.
4-18
Press F11 again to display a pop-up panel (Figure 4-14) on which you can select entities for filtering.
Rebuild Actions
Figure 4-14
Selecting entities for filtering
---------------------------------------------------------------------------|
|
|----------------------------------------------------------------------------|
|--------------- Entity Filter ------------------- Filter Summary -------|
|
| |
|
|
| |
|
| | Counts:
|
|
|
| | Filtered...... 12
|
|
| |
|
| _ All
| | Filters:
|
| _ Component
|
| _ File
| | Phase ........ All
|
| _ Report
|
| S Rule
|
| _ Set
| |
|
| _ Window
| |
|
|*************** BOTTOM OF DATA **************| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
----------------------------------------------------------------------------
8.
Then type FILTER ON or FILTER OFF to use or not use the filter in generating the list (Figure
4-15), and press Enter.
Figure 4-15
Turning on the filter selections

Rebuild
Entity
Status
Count
_ All
205
_ Prepare Needed
84
60
_ Install Top Bind Needed
13
39
9
******************************* BOTTOM OF DATA *******************************
9.
Press F3 to display a panel that shows that the filter is on and the number of filtered entities and
relations found, as in Figure 4-16. Type an S next to the rebuild status you want to display and press
Enter.
Figure 4-16
Filtered entity counts and Rebuild status

List Rebuild Contents for RBDPKG DMC_VER2_RBD Version 2
Filter On
Rebuild
Entity
Status
Count
S All
12
_ Prepare Needed
12
******************************* BOTTOM OF DATA *******************************
10. You can now view the results, as Figure 4-17 shows.
4-19
Figure 4-17
Filtered List of Rebuild Contents

Type RES next to the desired object. Then press ENTER.
Filter On
________ Prepare Needed for Rule SXT_RULE_CICS_COOP_DRIVER
Platform:PC
Project: DEV
________ Prepare Needed for Rule SXT_RULE_IMS_COOP_DRIVER
Platform:PC
Project: DEV
________ Prepare Needed for Rule SXT_RULE_MVS_COOP_DRIVER
Platform:PC
Project: DEV
________ Prepare Needed for Rule SXT_RULE_PCCICS_DRIVER
Platform:PC
Project: DEV
________ Prepare Needed for Rule SXT_RULE_PCCICS_COOP_DRIVER
Platform:PC
Project: DEV
Input
None.
Output
The system generates an online list of the rebuild contents based on your processing options.
List Relations
The list relations action lists the relations in the rebuild package. You can view one, several, or all types.
1.
On the List Facility for Entity Rebuild panel (Figure 4-18), type LR on the action line next to the
entity whose relationships you want to view. Press Enter.
Figure 4-18
List Facility for rebuild entities

HPS List Facility for Entity Rebuild
Repository: SUNRISE
Action
LR______
________
________
________
________
________
________
________
________
________
________
________
________
2.
4-20
V: 2
Name
DMC_VER2_RBD
GVK
GVK_BK_CRAIG
GVK_BK_PAULA
GVK_CRAIG_GE
GVK_DRAW
GVK_GRE
GVK_MIG_DRAWINGS
GVK_POUGH
GVK_P2
GVK_Q26
GVK_Q26B
KEST_MIGRATION2
Project: DEV
Level: 2
System Id
AA5ENR
AFJBNR
AAAHNR
AAAINR
AFTXNR
AFTUNR
AESDNR
ADZANR
AFTPNR
AFTQNR
AFKXNR
AFMHNR
ABDTNR
On the Relation Options pop-up panel (Figure 4-19), type S in the selection field next to the
relationship types you want to view. If you want to view all the relation types, type ALL on the
command line. Press Enter.
Rebuild Actions
Figure 4-19
Relation Options panel
---------------- Relation Options -----------------|

|
|
|
|
|
|
|
|
|
|
|
|
Entity . . . . : Rebuild
|
Name . . . . . : DMC_VER2_RBD
|
|
Select
Relation Type
|
_
Has-Root Function
|
S
Has-Root Rule
|
****************** BOTTOM OF DATA **************** |
Select one or more.
3.
Then press Eenter.
The system generates a Relation List panel for relation types you selected (Figure 4-20).
Figure 4-20
Listing a rebuild packages relations
Repository: SUNRISE
V: 2
Entity Name: DMC_VER2_RBD
Relation Type: Has-Root Rule
Project: DEV
Level: 3
Action
Name
________ DVT_RULE_ALL_SET_BATCH_SBCS
________ DVT_RULE_ALL_SET_CICS_SBCS
________ DVT_RULE_ALL_SET_IMS_SBCS
________ DVT_RULE_ALL_SET_MVS_SBCS
________ DVT_RULE_ALL_SET_PCCICS_SBCS
________ DVT_RULE_ALL_SET_PCIMS_SBCS
________ NEW_COMP_TEST
******************************* BOTTOM OF DATA ********************************
4.
Use the Scroll Right function key to see additional columns of information:
Is a Root Entity (Yes or No)
Is a Refined Entity (Yes or No)
Has Hierarchy Changed (Yes or No)
Affected Entity (Not Analyzed) (Yes or No)
Date Created
Time Created
Created by (user ID)
Date Maintained
Time Maintained
Maintained by (user ID)
5.
You can use the view results action by typing RES in the Action line next to the relation you want to
view.
6.
Press F3 to exit the Relation List panel.
Input
User input for types of entities in the relationship.
Result
The system generates an online list of the relations in the rebuild package.
4-21
Maintain Entity
Use this action to display any entitys Maintain an Entity panel on which you can edit the entitys
attributes. Type ME on the action line of the rebuild entity you want to update. The detail panel of the
entity is displayed on which you can modify the entity attributes.
Rebuild Status Values

One of the system-generated attributes of a rebuild entity is its package state, which is another name for
its rebuild status value. When you create a rebuild entity, its rebuild package state is not applicable (N/A)
until you add a relation to a root entity, which changes the rebuild status value to seeded. The Maintain
an Entity panel displays the rebuild package state (Figure 2-21). When you analyze, prepare, or install
the rebuild entity, its status value reflects the change of its state. A rebuild entity can have one of the
rebuild status values listed in Table 4-7.
Table 4-7
Rebuild status values
Status value
Description
Exceptions Seeded
Objects that may impact objects in the rebuild package have been added to it.
N/A
Not applicable, which means the rebuild package has not been seeded with a
root entity.
Seeded
The rebuild entity has one or more root entities.
Rebuild Analyze Submitted
The rebuild package has been submitted for analysis.
Rebuild Analyzed Failed
The analysis has failed on the rebuild package.
RBDA Successful with Exceptions
The rebuild analysis completed successfully with implicitly related objects

included.
Rebuild Analyze Successful
The rebuild package was successfully analyzed.
Rebuild Prepare Submitted
The rebuild package has been submitted for preparation.
Preparation of the rebuild package is executing.
Rebuild Prepare Failed
At least one of the objects in the rebuild package failed to prepare.
Rebuild Prepare Successful
The rebuild package was successful prepared.
Rebuild Install submitted
The rebuild package has been submitted for installation.
Rebuild Install Executing
Installation of the rebuild package is executing.
Rebuild Install Failed
At least one of the objects in the rebuild package failed to install.
Rebuild Install Successful
The rebuild package was successful installed.
In addition to these values, any of the steps could also be incomplete, which indicates a command
language error prevented the job from finishing.
Maintain Relation
Use this action to display any entitys Maintain a Relation panel on which you can edit the entitys
attributes. Type MR on the action line of the rebuild entity you want to update. The detail panel of the
relation is displayed on which you can modify the relation attributes.
Use the maintain relation action to process exceptions. See Handling Exceptions on page 2-16 for
more information.
4-22
Rebuild Actions
Prepare Object in Rebuild Package

The prepare (RPREPARE) action prepares the objects in the rebuild package that are marked for prepare
during rebuild analyze. From the Maintain a Relation panel, type RPREPARE on the action line of the
rebuild entity you want to prepare.
Results for preparing individual entities in the rebuild package overwrite any previous preparation
results. The results files reflect the last preparation, regardless of the method used to prepare it.
Figure 4-21 shows the results of the list rebuild contents (LISTRBD) action after preparing the rebuild
package.
Figure 4-21
List rebuild contents after preparing the rebuild package

Rebuild
Entity
Status
Count
S All
6
S Prepare Successful
2
2
2
******************************* BOTTOM OF DATA *******************************
Figure 4-22 shows the results of typing S next to ALL on the panel in Figure 4-21. You can type RES next
to an entity to see the results file for it.
Figure 4-22
View results after listing rebuild contents after preparing the rebuild package
RES_____ Prepare Successful for Rule R_CCS_36546

Platform:MNFR
Project: QA
________ Prepare Successful for Rule R_CCS_DUMMY

Platform:MNFR
Project: QA
Results
The prepare action submits one driver job TSO job that submits multiple jobs. You can monitor the
rebuild package state by refreshing the Maintain an Entity panel (press F19) to see the current rebuild
package state attribute. The state reflects the submission, execution, and success or failure of the job.
After the prepare job is finished, you can use the following actions to examine the results of preparing
the rebuild package.
Use the list rebuild contents (LISTRBD) to view a detailed list of the results of the preparation.
If preparation failed, type an S next to that rebuild status to view a list of entities whose preparation
failed. The list will show the platform and project for each entity.
job, including date and time stamps for job start and job end, as well as the final job state value.
The RES action on the rebuild package entity displays the methods (such as analyze, prepare, install,
and cleanup) that have been processed for the rebuild package.
4-23
Be aware that any existing RES file for a preparable entity is overwritten by the last preparation (Prepare, Superprepare, or Rebuild).
Type an S next to the PREPARE method to see a list of:
Prepare jobs submitted
Progress of jobs currently executing
Prepare jobs status (successful, failed, or incomplete)
The preparation status of repository objects is updated after a successful rebuild install. Note that if two
or more rebuild packages share a preparable object, the shared objects can have only a single status. So if
two or more rebuild packages are processing simultaneously, the job that finishes first updates the status
of any shared objects.
For example, suppose rebuild package ONE and rebuild package TWO both contain rule A. Between the
time rule A is successfully prepared but before it is installed in package ONE, rebuild package TWO runs
the analyze step. Because the status of rule A is not yet Rebuild Install Successful, package TWO analyzes
and prepares rule A again.
Reset Object Install Status

The reset object install status (RESETINS) action lets you change the install status of an object to what it
was before an attempted install.
To reset an object install status:
1.
On the List Facility for the rebuild entity, type RESETINS on the action line of the object for which
you want to reset the install status. Press Enter. The Reset Rebuild Install Status panel is displayed, as
shown in Figure 4-23.
Figure 4-23
Reset install options

Reset Rebuild Install Status for RBDPKG
Name . . . . . . . . : DMC_VER2_RBD
Version . . . . . . : 2
Select one of the following.
Then press Enter.
Processing Options
Reset Options . . . . . . . . . . . . 1 1.
2.
3.
4.
5.
6.
7.
Caution
All Install Actions

Static Link
Copy Executables
DB2 Bind Package
DB2 Bind Top Rules
LU2 Install
DB2 Bind Intermediate Rules
Resetting the installation status of an object resets the status of all entities in any subsequent phases.
If you reset all install actions, the entire results file is deleted. However, if you reset the install status
of only one phase, the results of the next install action are appended to the existing results file.
Remember to skip the first set of messages of the results file to view the most recent results.
2.
4-24
After you choose the reset install options, the Message Handler displays the result of the reset install
status, as shown in Figure 4-24.
Rebuild Actions
Figure 4-24
Reset install status results
----------------------------- 10/30/95
GR9086I
GR9068I
GR9063I
GR9067I
GR9064I
GR9067I
GR9098I
GR9068I
GR9065I
GR9068I
GR9066I
14:07:58
----------------------------
Resetting install status of actions in 'Static Link' step.

NO installs were found to be reset.
Resetting install status of actions in 'Copy Executables' step.
Installs were reset successfully.
Resetting install status of actions in 'DB2 Bind Top Rules' step.
Installs were reset successfully.
Resetting install status of actions in 'DB2 Package Bind' step.
Resetting install status of actions in 'LU2 Install' step.
Resetting install status of actions in 'DB2 Bind
Intermediate Rules' step.
GR9067I - Installs were reset successfully.
GR9061I - Rebuild Install Status Reset has finished successfully.
Press
ENTER
key to continue
The RESETINS action is useful if you need to correct some external condition and then start the install
process again.
Reset Object Prepare Status

The reset object prepare status (RESETPR) action lets you change the prepare status of an object to what
it was before an attempted prepare.
To reset the object prepare status:
1.
Type RESETPR on the action line of the object for which you want to reset the prepare status. Press
Enter. The Reset Rebuild Prepare Options panel is displayed as shown in Figure 4-25.
Figure 4-25
Reset prepare options

Reset Rebuild Prepare Status for RBDPKG
Name . . . . . . . . : DMC_VER2_RBD
Version . . . . . . : 2
Processing Options
Reset Options . . . . . . . . . . .
Caution
2.
Then press Enter.
1 1. All entities
2. Sets, Files, Windows, Reports,
Components, Rules
3. Files, Windows, Reports,
Components, Rules
4. Components, Rules
5. Process (Set-up)
Resetting the preparation status of an object resets the status of all entities in subsequent phases.
Select a reset option and press Enter. The Message Handler displays the results of the reset prepare
status, as shown in Figure 4-26.
4-25
Figure 4-26
Results of resetting the prepare status
---------------------------- 10/30/95
16:01:26
----------------------------
GR9028I - Resetting prepare status of object in phase 1, (Set).

GR9029I - Prepares were reset successfully.
GR9028I - Resetting prepare status of object in phase 2, (File,
Window, Report).
GR9028I - Resetting prepare status of object in phase 3, (Component, Rule).
GR9028I - Resetting prepare status of object in phase 4, (Process).
GR9030I - NO prepares were found to be reset.
GR9035I - Rebuild Prepare Status Reset has finished successfully.
HM0150I - Reset Prepare for SVK_ROBIN V: 1 processed
If you reset all prepare actions, the entire results file is deleted. However, if you reset the prepare status of only one phase, the results of the next prepare action are appended to the existing results file.
Remember to skip the first set of messages of the results file to view the most recent results.
The RESETPR action is useful if you need to correct some external condition, such as needing to
create some DB2 tables, and then start the preparation process again.
Set Rebuild Install Status

The rebuild install status (RSTATUS) action lets you set the status of a preparable object that has
completed all the rebuild install steps except:
LU2
HPIVSAM (IMS)
PC object prepares
Normally, the rebuild package objects are marked as installed after the LU2 step, or if needed, the
HPIVSAM step. To prevent the objects from being unnecessarily reprepared as part of other rebuild
package jobs, use the RSTATUS action to mark the objects as installed before you complete these steps.
The RSTATUS action panel lets you choose the action for Mainframe and/or PC objects. You cannot use
the RSTATUS action until all copy actions on mainframe objects for the rebuild install are completed.
You can use the RSTATUS action to set the status of PC objects, typically after you have written them to
an advice file, downloaded them, and prepared them on the workstation. Then you can mark them as
installed on the mainframe so they will not be marked as needing preparation, and thus will not be
written to future advice files. This also prevents the PC objects from being listed in the rebuild reports.
Super Prepare
The super prepare (SUPERPR) action lets you automatically analyze, prepare, and install all objects in
one step. Type SUPERPR on the action line of the object you want to super prepare.
The super prepare action uses the default settings from the RBDENVn.INI file, where n is the repository
version. See Chapter 5, Setting Up The Rebuild Environment for information about the default values
for the INI variables.
4-26
Rebuild Actions
Remember that the results for preparing individual entities in the rebuild package overwrite any
previous preparation results. The results files reflect the last preparation, regardless of the method used
to prepare it.
Results
The super prepare action submits one driver TSO job that submits multiple jobs. You can monitor the
rebuild package entity by refreshing the Maintain an Entity panel (press F19) to see the current rebuild
package state attribute. The state reflects the submission, execution, and success or failure of the job.
After the super prepare job is finished, you can use the following actions to examine the results of super
preparing the rebuild package.
Use the list rebuild contents (LISTRBD) to view a detailed list of the results of the analyze,
preparation, and installation.
If analyze, preparation, or installation failed, type an S next to that rebuild status to view a list of
entities whose analyze, preparation, or installation failed. The list will show the platform and
project for each entity.
job, including date and time stamps for job start and job end, as well as the final job state value.
The RES action displays the methods (such as analyze, prepare, install, and cleanup) that have been
processed for the rebuild package.
Type an S next to a method to see a list of:
Jobs submitted
Progress of jobs currently executing
Prepare jobs status (successful, failed, or incomplete)
View Results of Rebuild

Use the view results (RES) action to see the messages that contain the results of a batch job. The system
generates user messages that display the date and timestamps for job start and job end, as well as the
final job status value. Use these message types to check the number and kind of objects in a rebuild
package, track and resolve problems, and check audit information.
To view the results of the jobs run on a rebuild package entity:
1.
Type RES in its action line. Press Enter. The view results panel displays a Repository File Browser
panel that lists the methods processed on the rebuild entity, as Figure 4-27 shows.
4-27
Figure 4-27
View results action displays the Repository File Browser

Name . . . . . . . : DMC_VER2_RBD
Version . . . . . : 2
Select one or more of the following.
S=Browse P=Print D=Delete
Then press ENTER.
Action Method
Results File
_
ANALYZE
Analyze Job Stats / Messages
_
PREPARE
Prepare Job Stats / Messages
RES
_
INSTALL
Install Job Stats / Messages
_
INSTALL
Install Static Link Messages
_
INSTALL
Install Copy VSAM Messages
_
INSTALL
Install Package Bind Messages
_
INSTALL
Install Top Bind Messages
_
INSTALL
Install Interm Bind Messages
_
CLEANUP
Clean-up Job Stats / Messages
_
INSTALL
Install LU2 Messages
******************************* BOTTOM OF DATA******************************
2.
You can browse the job statistics and messages by typing S in the action line of the job you want to
view.
3.
You can also print the messages or delete the results file by typing P or D respectively.
Input
User selection of Job Result files.
Output
Result files that are viewable by selecting them.
Result
The view results action lists the jobs for the methods you have run on a rebuild entity. The results file for
each job lists the following data:
Start date and time for each job and routine in the program
End date and time for each job and routine in the program
Review of values that you selected for the rebuild attributes
Warning and error messages
4-28
Rebuild Actions
CHAPTER
SETTING UP THE REBUILD

ENVIRONMENT
The rebuild environment-control variables control various aspects of rebuild processing. A thorough
understanding of these variables and their effect on rebuild processing allows you to customize the
Rebuild Facility to suit your environment. Because the values you select change how you process
rebuilds, be sure you let all Rebuild Facility users know which values you selected for the variables.
The variables described in this section are:
Rebuild Variables
Migrate Variables
Note
All of these environment-control variables effect an entire repository.
Although the installation team selects values for each variable during initial software installation, you
can change them later. All values are stored in the @RBDENVn INI file (where n is the repository
version) that is generated during the initial installation. (migration environment-control variables are
stored in the @MIGENVn INI file.) You can use the AppBuilder Installation Workbench to change the
value of each variable.
Rebuild Variables
Table 5-1 lists the rebuild environment-control variables in alphabetical order. Please note that this is
not the order in which they appear in the @RBDENVn INI file. All of the rebuild environment-control
variables effect an entire repository.
Table 5-1
Rebuild environment-control variables
Name
Description
Values
COMMIT_LEVEL
Specify whether analyze should be

committed by number of objects or by
rebuild.
Any number greater than 0.

0 (zero)The rollback of any analyze
failure will be performed at the rebuild
level. Any error encountered during the
processing will result in the rollback of
all objects processed and the
termination of the rebuild.
Default is 99.
MINIMUM_SUBMIT
Specify the minimum number of jobs to

submit for each prepare.
Default = 1
5--1
Rebuild Variables
Table 5-1
5--2
Rebuild environment-control variables (Continued)
Name
Description
Values
VSAM_COMMIT
Specify the commit level for vsam

copies during rebuild install.
Default = 100
RUN_REPORT
Specify if the rebuild report should be

executed automatically at the
completion of a successful prepare.
This information produced is a detail of
the processing which has completed.
Invalid data: will create problems
during AppBuilder internal processing.
DEFAULT = Y
ALLOC_DISP
Default temporary file allocation

disposition.
DELETE (default)
CATLG
KEEP
CONT_SUBMIT
Submit jobs continuously.
Default is N (No).
DISPLAY_PREV_FAILED
Display selection of Ignore failed

prepares in previous phases.
Default is N (No).
EXCEPTION_RPRT
Initiate prepares when rebuild analyze

for SUPERPR ends successfully with
exceptional processes.
Default is Y (Yes).
IGNORE_FAILED_PREPARES
Initiate install when prepares failed or

are incomplete.
Default is N (No).
IGNORE_PREV_FAILED
Ignore failed prepares in previous

phases.
Default is N (No).
INTERMEDIATE_BIND
Intermediate bind.
Default is N (No).
NIGHTRUN
Defer jobs to run overnight.
Default is N (No).
PHASE_2
Controls whether users can prepare

files.
When the value is FILE WINDOW

REPORT (the default), users can
prepare files.
When the value is WINDOW REPORT,
users are restricted to preparing
windows and reports.
PROCESS52
When set to Y (Yes), marks version 5.2

processes for preparation.
Default is Y (Yes).
RESUBMIT_FAILED
Resubmit failed jobs.
Default is N (No).
RESUBMIT_INCOMPLETE
Resubmit failed prepares.
Default is N (No).
REGEN_LU2
Specify if the user wants to regenerate LU2 install control cards

during Rebuild Install. The option allow
user to make corrections to INI
variables and regenerate LU2 control
cards during rebuild install.
Default = N
REGEN_BIND
Specify if the user wants to change

DB2 owner id and/or qualifier in INI
files and regenerate DB2 Bind control
cards during rebuild Install.
Default = N
RUN_REPORT
Specify if the rebuild report should be

executed automatically at the
completion of a successful prepare
validation. The information produced is
a detail of the processing which has
completed.
Invalid data: will create problems
during AppBuilder internal processing.
Default = Y
Setting Up The Rebuild Environment
Migrate Variables
Table 5-1
Rebuild environment-control variables (Continued)
Name
Description
Values
SKIP_SEER1
Skip processing preparable entities

with project of SEER1. Setting this
variable to Y skips entities in the
default repository.
Default is Y (Yes).
SKIP_SEER2
Skip processing preparable entities

with project of SEER2. Setting this
variable to Y skips entities in the
default repository.
Default is Y (Yes).
STATIC_LINK_DEFAULT
Specify the default for static link

analysis.
Default = N
STATIC_LINK_COMPONENT
Specify the default for comp link

processing.
Default = N
STORAGE_INCREMENT
Storage allocation increment
Default is 100.
Migrate Variables
You use the @MIGENVn .INI variables described in Table 5-2 to customize the automate migration
(MIGRATE) action to your environment. The automate migration (MIGRATE) action automates all of
(or any segment of) migration and rebuild processing. All of the migration environment-control
variables effect an entire repository.
Table 5-2
MIGRATE variables
Name
Description
Valid values
RUNIMP
Specify the default value to be

used for the import migration
option.
Y Import the migration package during automated

migration processing.
N Do not import the migration package during automated
Default is N.
RUNRBDA

used for the analyze rebuild
package option.
Y Analyze the rebuild package during automated

N Do not analyze the rebuild package during automated
Default is N.
RUNRBDPR

used for the prepare rebuild
package option.
Y Prepare the rebuild package during automated

N Do not prepare the rebuild package during automated
Default is Y.
RUNRBDIN

used for the install rebuild
package option.
Y Install the rebuild package during automated migration

processing.
N Do not install the rebuild package during automated
Default is Y.
RUNRBDEX

used for the export rebuild
package option.
Y Export the rebuild package during automated

N Do not export the rebuild package during automated
Default is Y.
OVIMP
Specify whether the user can

override the default value for the
import migration option.
Y The user can override the option.

N The user cannot override the option.
Default is N.
5--3
Migrate Variables
Table 5-2
5--4
MIGRATE variables (Continued)
Name
Description
Valid values
OVRBDA

analyze rebuild package option.

Default is Y.
OVRBDPR

prepare rebuild package option.

Default is Y.
OVRBDIN

install rebuild package option.

Default is Y.
Setting Up The Rebuild Environment
APPENDIX
STATUS VALUES
This appendix lists the migration status values used by the Migration Facility and the Rebuild Facility.
Table A-1 lists the migration status-value internal codes and descriptions, and Table A-2 lists the rebuild
status-value internal codes and descriptions.
Table A-1
Migration status values
Internal Code
Description
11
Packaged
12
Exported
13
Loaded
14
Not Packaged
15
Not Exported
16
Not Loaded
101
Unchanged
102
Import will Update
103
Import will Create
104
Import will Delete
160
Collision
201
Explicit Skip Unchanged
202
Explicit Skip Update
203
Explicit Skip Create
204
Explicit Skip Delete
260
Explicit Skip Collision
301
Implicit Skip Unchanged
302
Implicit Skip Update
303
Implicit Skip Create
304
Implicit Skip Delete
360
Implicit Skip Collision
401
Unchanged, Not Imported
402
Update, Not Imported
403
Create, Not Imported
404
Delete, Not Imported
501
Successful Unchanged
502
Successful Update
A-1
Table A-1
Migration status values (Continued)
Internal Code
Description
503
Successful Create
504
Successful Delete
601
Partial Unchanged of
602
Partial Update of
603
Partial Create of
604
Successful Selective Delete
701
Failed Unchanged
702
Failed Update
703
Failed Create
704
Failed Delete
801
Rolled Back Unchanged
802
Rolled Back Update
803
Rolled Back Create
804
Rolled Back Delete
Table A-2 lists the rebuild status-value internal codes and descriptions.
Table A-2
A-2
Rebuild status values
Internal Code
Description
6400
Prepare Successful
6404
Prepare Incomplete
6408
Prepare Failed
6410
Prepare Executing
6412
Prepare Submitted
6413
Prepare Selected
6414
Prepare Needed
6500
Install Successful
6504
Install Incomplete
6508
Install Failed
6510
Install Executing
6512
Install Submitted
6513
Install Selected
6514
Install Needed
6600
Install Static Link Successful
6604
Install Static Link Incomplete
6608
Install Static Link Failed
6610
Install Static Link Executing
6612
Install Static Link Submitted
6613
Install Static Link Selected
6614
Install Static Link Needed
6700
Install Copy Successful
6704
Install Copy Incomplete
Status Values
Table A-2
Rebuild status values (Continued)
Internal Code
Description
6708
Install Copy Failed
6710
Install Copy Executing
6712
Install Copy Submitted
6713
Install Copy Selected
6714
Install Copy Needed
6800
Install Top Bind Successful
6804
Install Top Bind Incomplete
6808
Install Top Bind Failed
6810
Install Top Bind Executing
6812
Install Top Bind Submitted
6813
Install Top Bind Selected
6814
Install Top Bind Needed
6900
Install LU2 Successful
6904
Install LU2 Incomplete
6908
Install LU2 Failed
6910
Install LU2 Executing
6912
Install LU2 Submitted
6913
Install LU2 Selected
6914
Install LU2 Needed
7000
Install Intermediate Bind

Successful
7004

Incomplete
7008
Install Intermediate Bind Failed
7010

Executing
7012

Submitted
7013

Selected
7014

Needed
A-3
A-4
Status Values
APPENDIX
REBUILD PROCESSING ATTRIBUTES
For rebuild purposes, entity and relationship attributes are logically split into two types: significant and
insignificant attributes. Changes in value between the source values and target values of significant
attributes result in target repository updates. Changes in value between source values and target values
of insignificant attributes do not result in target repository updates.
Rebuild Entity and Relationship Attribute

Table B-1 defines the headings used in the entity and relationship attribute Table B-2.:
Table B-1
Heading Descriptions
Heading
Description
Object type
This value is either ENTITY or RELATE (relationship).
System name
The system name of an entity or relationship type. For example, APPCFG

is the system name for the application configuration entity type.
Attribute name
The attribute name used on the user interface panels.
Significant?
If this value is Y, the attribute is significant. If the value is N, the attribute is

insignificant.
Table B-2
Entity and Relationship Attributes
Object Type
System Name
Attribute Name
Significant?
ENTITY
APPCFG
System Id
ENTITY
APPCFG
Name
ENTITY
APPCFG
Date Created
ENTITY
APPCFG
Time Created
ENTITY
APPCFG
Created by
ENTITY
APPCFG
Date Maintained
ENTITY
APPCFG
Time Maintained
ENTITY
APPCFG
Maintained by
ENTITY
APPCFG
Project
ENTITY
APPCFG
Lock Type
ENTITY
APPCFG
Lock Id
ENTITY
APPCFG
Change #
ENTITY
APPCFG
Owner Id
B-1
Table B-2
B-2
Entity and Relationship Attributes (Continued)
Object Type
System Name
Attribute Name
Significant?
ENTITY
APPCFG
QA Status
ENTITY
APPCFG
ENTITY
APPCFG
ENTITY
APPCFG
ENTITY
APPCFG
ENTITY
APPCFG
Version
ENTITY
ASSUMP
System Id
ENTITY
ASSUMP
Name
ENTITY
ASSUMP
Assumption Type
ENTITY
ASSUMP
Priority
ENTITY
ASSUMP
Act Start
ENTITY
ASSUMP
Plnd Start
ENTITY
ASSUMP
Conf Level
ENTITY
ASSUMP
Risk
ENTITY
ASSUMP
Date Created
ENTITY
ASSUMP
Time Created
ENTITY
ASSUMP
Created by
ENTITY
ASSUMP
Date Maintained
ENTITY
ASSUMP
Time Maintained
ENTITY
ASSUMP
Maintained by
ENTITY
ASSUMP
Project
ENTITY
ASSUMP
Lock Type
ENTITY
ASSUMP
Lock Id
ENTITY
ASSUMP
Change #
ENTITY
ASSUMP
Owner Id
ENTITY
ASSUMP
QA Status
ENTITY
ASSUMP
ENTITY
ASSUMP
ENTITY
ASSUMP
ENTITY
ASSUMP
ENTITY
ASSUMP
Version
ENTITY
ATTRIB
System Id
ENTITY
ATTRIB
Name
ENTITY
ATTRIB
Derived
ENTITY
ATTRIB
Date Created
ENTITY
ATTRIB
Time Created
ENTITY
ATTRIB
Created by
ENTITY
ATTRIB
Date Maintained
ENTITY
ATTRIB
Time Maintained
Rebuild Processing Attributes
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
ATTRIB
Maintained by
ENTITY
ATTRIB
Project
ENTITY
ATTRIB
Lock Type
ENTITY
ATTRIB
Lock Id
ENTITY
ATTRIB
Change #
ENTITY
ATTRIB
Owner Id
ENTITY
ATTRIB
QA Status
ENTITY
ATTRIB
ENTITY
ATTRIB
ENTITY
ATTRIB
ENTITY
ATTRIB
ENTITY
ATTRIB
Version
ENTITY
BITMAP
System Id
ENTITY
BITMAP
Name
ENTITY
BITMAP
Type
ENTITY
BITMAP
Implementation Name
ENTITY
BITMAP
Description
ENTITY
BITMAP
Date Created
ENTITY
BITMAP
Time Created
ENTITY
BITMAP
Created by
ENTITY
BITMAP
Date Maintained
ENTITY
BITMAP
Time Maintained
ENTITY
BITMAP
Maintained by
ENTITY
BITMAP
Project
ENTITY
BITMAP
Lock Type
ENTITY
BITMAP
Lock Id
ENTITY
BITMAP
Change #
ENTITY
BITMAP
Owner Id
ENTITY
BITMAP
QA Status
ENTITY
BITMAP
ENTITY
BITMAP
ENTITY
BITMAP
ENTITY
BITMAP
ENTITY
BITMAP
Version
ENTITY
BMPIMP
System Id
ENTITY
BMPIMP
Name
ENTITY
BMPIMP
Country Language
ENTITY
BMPIMP
X Resolution
ENTITY
BMPIMP
Y Resolution
B-3
Table B-2
B-4
Object Type
System Name
Attribute Name
Significant?
ENTITY
BMPIMP
Format Type
ENTITY
BMPIMP
Date Created
ENTITY
BMPIMP
Time Created
ENTITY
BMPIMP
Created by
ENTITY
BMPIMP
Date Maintained
ENTITY
BMPIMP
Time Maintained
ENTITY
BMPIMP
Maintained by
ENTITY
BMPIMP
Project
ENTITY
BMPIMP
Lock Type
ENTITY
BMPIMP
Lock Id
ENTITY
BMPIMP
Change #
ENTITY
BMPIMP
Owner Id
ENTITY
BMPIMP
QA Status
ENTITY
BMPIMP
ENTITY
BMPIMP
ENTITY
BMPIMP
ENTITY
BMPIMP
ENTITY
BMPIMP
Version
ENTITY
BUSOBJ
System Id
ENTITY
BUSOBJ
Name
ENTITY
BUSOBJ
Description
ENTITY
BUSOBJ
Type
ENTITY
BUSOBJ
Date Created
ENTITY
BUSOBJ
Time Created
ENTITY
BUSOBJ
Created by
ENTITY
BUSOBJ
Date Maintained
ENTITY
BUSOBJ
Time Maintained
ENTITY
BUSOBJ
Maintained by
ENTITY
BUSOBJ
Project
ENTITY
BUSOBJ
Lock Type
ENTITY
BUSOBJ
Lock Id
ENTITY
BUSOBJ
Change #
ENTITY
BUSOBJ
Owner Id
ENTITY
BUSOBJ
QA Status
ENTITY
BUSOBJ
ENTITY
BUSOBJ
ENTITY
BUSOBJ
ENTITY
BUSOBJ
ENTITY
BUSOBJ
Version
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
CAPLST
System Id
ENTITY
CAPLST
Customer Group Id
ENTITY
CAPLST
Customer Group Name
ENTITY
CAPLST
Date Created
ENTITY
CAPLST
Time Created
ENTITY
CAPLST
Created by
ENTITY
CAPLST
Date Maintained
ENTITY
CAPLST
Time Maintained
ENTITY
CAPLST
Maintained by
ENTITY
CAPLST
Project
ENTITY
CAPLST
Lock Type
ENTITY
CAPLST
Lock Id
ENTITY
CAPLST
Change #
ENTITY
CAPLST
Owner Id
ENTITY
CAPLST
QA Status
ENTITY
CAPLST
ENTITY
CAPLST
ENTITY
CAPLST
ENTITY
CAPLST
ENTITY
CAPLST
Version
ENTITY
CELL
System Id
ENTITY
CELL
Name
ENTITY
CELL
Protocol
ENTITY
CELL
Date Created
ENTITY
CELL
Time Created
ENTITY
CELL
Created by
ENTITY
CELL
Date Maintained
ENTITY
CELL
Time Maintained
ENTITY
CELL
Maintained by
ENTITY
CELL
Project
ENTITY
CELL
Lock Type
ENTITY
CELL
Lock Id
ENTITY
CELL
Change #
ENTITY
CELL
Owner Id
ENTITY
CELL
QA Status
ENTITY
CELL
ENTITY
CELL
ENTITY
CELL
ENTITY
CELL
ENTITY
CELL
Version
B-5
Table B-2
B-6
Object Type
System Name
Attribute Name
Significant?
ENTITY
CFGUNIT
System Id
ENTITY
CFGUNIT
Name
ENTITY
CFGUNIT
Type
ENTITY
CFGUNIT
Implementation Name
ENTITY
CFGUNIT
Protocol
ENTITY
CFGUNIT
Server Link Type
ENTITY
CFGUNIT
Server Start Type
ENTITY
CFGUNIT
Server Cell Rank
ENTITY
CFGUNIT
Owner
ENTITY
CFGUNIT
Qualifier
ENTITY
CFGUNIT
Plan Name
ENTITY
CFGUNIT
Collection Id
ENTITY
CFGUNIT
Isolation Mode
ENTITY
CFGUNIT
Minimum Transaction Id
ENTITY
CFGUNIT
Maximum Transaction Id
ENTITY
CFGUNIT
Unit Of Work
ENTITY
CFGUNIT
Date Created
ENTITY
CFGUNIT
Time Created
ENTITY
CFGUNIT
Created by
ENTITY
CFGUNIT
Date Maintained
ENTITY
CFGUNIT
Time Maintained
ENTITY
CFGUNIT
Maintained by
ENTITY
CFGUNIT
Project
ENTITY
CFGUNIT
Lock Type
ENTITY
CFGUNIT
Lock Id
ENTITY
CFGUNIT
Change #
ENTITY
CFGUNIT
Owner Id
ENTITY
CFGUNIT
QA Status
ENTITY
CFGUNIT
ENTITY
CFGUNIT
ENTITY
CFGUNIT
ENTITY
CFGUNIT
ENTITY
CFGUNIT
Version
ENTITY
COLLECT
System Id
ENTITY
COLLECT
Name
ENTITY
COLLECT
Type
ENTITY
COLLECT
Nature
ENTITY
COLLECT
Number Of Elements
ENTITY
COLLECT
Number Of Groups
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
COLLECT
Date Created
ENTITY
COLLECT
Time Created
ENTITY
COLLECT
Created by
ENTITY
COLLECT
Date Maintained
ENTITY
COLLECT
Time Maintained
ENTITY
COLLECT
Maintained by
ENTITY
COLLECT
Project
ENTITY
COLLECT
Lock Type
ENTITY
COLLECT
Lock Id
ENTITY
COLLECT
Change #
ENTITY
COLLECT
Owner Id
ENTITY
COLLECT
QA Status
ENTITY
COLLECT
ENTITY
COLLECT
ENTITY
COLLECT
ENTITY
COLLECT
ENTITY
COLLECT
Version
ENTITY
COLUMN
System Id
ENTITY
COLUMN
Name
ENTITY
COLUMN
Implementation Name
ENTITY
COLUMN
Column Format
ENTITY
COLUMN
Column Length
ENTITY
COLUMN
Column Fraction
ENTITY
COLUMN
Average Length
ENTITY
COLUMN
Date Created
ENTITY
COLUMN
Time Created
ENTITY
COLUMN
Created by
ENTITY
COLUMN
Date Maintained
ENTITY
COLUMN
Time Maintained
ENTITY
COLUMN
Maintained by
ENTITY
COLUMN
Project
ENTITY
COLUMN
Lock Type
ENTITY
COLUMN
Lock Id
ENTITY
COLUMN
Change #
ENTITY
COLUMN
Owner Id
ENTITY
COLUMN
QA Status
ENTITY
COLUMN
ENTITY
COLUMN
ENTITY
COLUMN
ENTITY
COLUMN
B-7
Table B-2
B-8
Object Type
System Name
Attribute Name
Significant?
ENTITY
COLUMN
Version
ENTITY
COMP
System Id
ENTITY
COMP
Name
ENTITY
COMP
Execution Environment
ENTITY
COMP
Info Src
ENTITY
COMP
Language
ENTITY
COMP
Subroutine
ENTITY
COMP
DBMS Usage
ENTITY
COMP
Description
ENTITY
COMP
Implementation Name
ENTITY
COMP
Date Created
ENTITY
COMP
Time Created
ENTITY
COMP
Created by
ENTITY
COMP
Date Maintained
ENTITY
COMP
Time Maintained
ENTITY
COMP
Maintained by
ENTITY
COMP
Project
ENTITY
COMP
Lock Type
ENTITY
COMP
Lock Id
ENTITY
COMP
Change #
ENTITY
COMP
Owner Id
ENTITY
COMP
QA Status
ENTITY
COMP
ENTITY
COMP
ENTITY
COMP
ENTITY
COMP
ENTITY
COMP
Version
ENTITY
CSTGRP
System Id
ENTITY
CSTGRP
Customer Group Id
ENTITY
CSTGRP
Customer Group Name
ENTITY
CSTGRP
Date Created
ENTITY
CSTGRP
Time Created
ENTITY
CSTGRP
Created by
ENTITY
CSTGRP
Date Maintained
ENTITY
CSTGRP
Time Maintained
ENTITY
CSTGRP
Maintained by
ENTITY
CSTGRP
Project
ENTITY
CSTGRP
Lock Type
ENTITY
CSTGRP
Lock Id
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
CSTGRP
Change #
ENTITY
CSTGRP
Owner Id
ENTITY
CSTGRP
QA Status
ENTITY
CSTGRP
ENTITY
CSTGRP
ENTITY
CSTGRP
ENTITY
CSTGRP
ENTITY
CSTGRP
Version
ENTITY
CURSYS
System Id
ENTITY
CURSYS
Name
ENTITY
CURSYS
Description
ENTITY
CURSYS
Date Created
ENTITY
CURSYS
Time Created
ENTITY
CURSYS
Created by
ENTITY
CURSYS
Date Maintained
ENTITY
CURSYS
Time Maintained
ENTITY
CURSYS
Maintained by
ENTITY
CURSYS
Project
ENTITY
CURSYS
Lock Type
ENTITY
CURSYS
Lock Id
ENTITY
CURSYS
Change #
ENTITY
CURSYS
Owner Id
ENTITY
CURSYS
QA Status
ENTITY
CURSYS
ENTITY
CURSYS
ENTITY
CURSYS
ENTITY
CURSYS
ENTITY
CURSYS
Version
ENTITY
CUST
System Id
ENTITY
CUST
Customer Id
ENTITY
CUST
Customer Name
ENTITY
CUST
Customer Title
ENTITY
CUST
Customer Code
ENTITY
CUST
Business Telephone Number
ENTITY
CUST
Business Telephone
Extension
ENTITY
CUST
Home Telephone Number
ENTITY
CUST
Profile Filename
ENTITY
CUST
Date Created
B-9
Table B-2
B-10
Object Type
System Name
Attribute Name
Significant?
ENTITY
CUST
Time Created
ENTITY
CUST
Created by
ENTITY
CUST
Date Maintained
ENTITY
CUST
Time Maintained
ENTITY
CUST
Maintained by
ENTITY
CUST
Project
ENTITY
CUST
Lock Type
ENTITY
CUST
Lock Id
ENTITY
CUST
Change #
ENTITY
CUST
Owner Id
ENTITY
CUST
QA Status
ENTITY
CUST
ENTITY
CUST
ENTITY
CUST
ENTITY
CUST
ENTITY
CUST
Version
ENTITY
DATA
System Id
ENTITY
DATA
Name
ENTITY
DATA
Data Format
ENTITY
DATA
Data Length
ENTITY
DATA
Data Fraction
ENTITY
DATA
Date Created
ENTITY
DATA
Time Created
ENTITY
DATA
Created by
ENTITY
DATA
Date Maintained
ENTITY
DATA
Time Maintained
ENTITY
DATA
Maintained by
ENTITY
DATA
Project
ENTITY
DATA
Lock Type
ENTITY
DATA
Lock Id
ENTITY
DATA
Change #
ENTITY
DATA
Owner Id
ENTITY
DATA
QA Status
ENTITY
DATA
ENTITY
DATA
ENTITY
DATA
ENTITY
DATA
ENTITY
DATA
Version
ENTITY
DATABAS
System Id
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
DATABAS
Name
ENTITY
DATABAS
Implementation Name
ENTITY
DATABAS
Type
ENTITY
DATABAS
Machine Name
ENTITY
DATABAS
Database Directory Path
ENTITY
DATABAS
Date Created
ENTITY
DATABAS
Time Created
ENTITY
DATABAS
Created by
ENTITY
DATABAS
Date Maintained
ENTITY
DATABAS
Time Maintained
ENTITY
DATABAS
Maintained by
ENTITY
DATABAS
Project
ENTITY
DATABAS
Lock Type
ENTITY
DATABAS
Lock Id
ENTITY
DATABAS
Change #
ENTITY
DATABAS
Owner Id
ENTITY
DATABAS
QA Status
ENTITY
DATABAS
ENTITY
DATABAS
ENTITY
DATABAS
ENTITY
DATABAS
ENTITY
DATABAS
Version
ENTITY
DRAWNG
System Id
ENTITY
DRAWNG
Name
ENTITY
DRAWNG
Drawing Type
ENTITY
DRAWNG
Date Created
ENTITY
DRAWNG
Time Created
ENTITY
DRAWNG
Created by
ENTITY
DRAWNG
Date Maintained
ENTITY
DRAWNG
Time Maintained
ENTITY
DRAWNG
Maintained by
ENTITY
DRAWNG
Project
ENTITY
DRAWNG
Lock Type
ENTITY
DRAWNG
Lock Id
ENTITY
DRAWNG
Change #
ENTITY
DRAWNG
Owner Id
ENTITY
DRAWNG
QA Status
ENTITY
DRAWNG
ENTITY
DRAWNG
ENTITY
DRAWNG
B-11
Table B-2
B-12
Object Type
System Name
Attribute Name
Significant?
ENTITY
DRAWNG
ENTITY
DRAWNG
Version
ENTITY
ENT
System Id
ENTITY
ENT
Name
ENTITY
ENT
Entity Type
ENTITY
ENT
Expected Minimum Rows
ENTITY
ENT
Expected Maximum Rows
ENTITY
ENT
Activity Period
ENTITY
ENT
Average Inserts for Period
ENTITY
ENT
Average Deletes for Period
ENTITY
ENT
Average Updates for Period
ENTITY
ENT
Expected Rows
ENTITY
ENT
Date Created
ENTITY
ENT
Time Created
ENTITY
ENT
Created by
ENTITY
ENT
Date Maintained
ENTITY
ENT
Time Maintained
ENTITY
ENT
Maintained by
ENTITY
ENT
Project
ENTITY
ENT
Lock Type
ENTITY
ENT
Lock Id
ENTITY
ENT
Change #
ENTITY
ENT
Owner Id
ENTITY
ENT
QA Status
ENTITY
ENT
ENTITY
ENT
ENTITY
ENT
ENTITY
ENT
ENTITY
ENT
Version
ENTITY
ENTITY
Entity Type
ENTITY
ENTITY
Name
ENTITY
ENTITY
Screen Description
ENTITY
ENTITY
Entity Code
ENTITY
ENTITY
Implementation Name
ENTITY
ENTITY
Migration File Name
ENTITY
ENTITY
Implementation Storage
ENTITY
ENTITY
Exit Routine
ENTITY
ENTITY
Date Created
ENTITY
ENTITY
Time Created
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
ENTITY
Created by
ENTITY
ENTITY
Date Maintained
ENTITY
ENTITY
Time Maintained
ENTITY
ENTITY
Maintained by
ENTITY
ENTITY
Project
ENTITY
ENTITY
Lock Type
ENTITY
ENTITY
Lock Id
ENTITY
ENTITY
Change #
ENTITY
ENTITY
Owner Id
ENTITY
ENTITY
QA Status
ENTITY
ENTITY
ENTITY
ENTITY
ENTITY
ENTITY
ENTITY
ENTITY
ENTITY
ENTITY
Version
ENTITY
EVENT
System Id
ENTITY
EVENT
Name
ENTITY
EVENT
Description
ENTITY
EVENT
Event Type
ENTITY
EVENT
Event Class
ENTITY
EVENT
Date Created
ENTITY
EVENT
Time Created
ENTITY
EVENT
Created by
ENTITY
EVENT
Date Maintained
ENTITY
EVENT
Time Maintained
ENTITY
EVENT
Maintained by
ENTITY
EVENT
Project
ENTITY
EVENT
Lock Type
ENTITY
EVENT
Lock Id
ENTITY
EVENT
Change #
ENTITY
EVENT
Owner Id
ENTITY
EVENT
QA Status
ENTITY
EVENT
ENTITY
EVENT
ENTITY
EVENT
ENTITY
EVENT
ENTITY
EVENT
Version
ENTITY
FILE
System Id
ENTITY
FILE
Name
B-13
Table B-2
B-14
Object Type
System Name
Attribute Name
Significant?
ENTITY
FILE
File Type
ENTITY
FILE
Implementation Name
ENTITY
FILE
Date Created
ENTITY
FILE
Time Created
ENTITY
FILE
Created by
ENTITY
FILE
Date Maintained
ENTITY
FILE
Time Maintained
ENTITY
FILE
Maintained by
ENTITY
FILE
Project
ENTITY
FILE
Lock Type
ENTITY
FILE
Lock Id
ENTITY
FILE
Change #
ENTITY
FILE
Owner Id
ENTITY
FILE
QA Status
ENTITY
FILE
ENTITY
FILE
ENTITY
FILE
ENTITY
FILE
ENTITY
FILE
Version
ENTITY
FLD
System Id
ENTITY
FLD
Name
ENTITY
FLD
Field Picture - Storage
ENTITY
FLD
Field Picture - Display
ENTITY
FLD
Screen Literal - Long
ENTITY
FLD
Field Format
ENTITY
FLD
Field Length
ENTITY
FLD
Field Fraction
ENTITY
FLD
Range - Minimum Value
ENTITY
FLD
Range - Maximum Value
ENTITY
FLD
Reference Table Name
ENTITY
FLD
Screen Literal - Short
ENTITY
FLD
Implementation Name
ENTITY
FLD
Date Created
ENTITY
FLD
Time Created
ENTITY
FLD
Created by
ENTITY
FLD
Date Maintained
ENTITY
FLD
Time Maintained
ENTITY
FLD
Maintained by
ENTITY
FLD
Project
ENTITY
FLD
Lock Type
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
FLD
Lock Id
ENTITY
FLD
Change #
ENTITY
FLD
Owner Id
ENTITY
FLD
QA Status
ENTITY
FLD
ENTITY
FLD
ENTITY
FLD
ENTITY
FLD
ENTITY
FLD
Version
ENTITY
FORM
System Id
ENTITY
FORM
Name
ENTITY
FORM
Form Environment
ENTITY
FORM
Base
ENTITY
FORM
Country Language
ENTITY
FORM
Date Created
ENTITY
FORM
Time Created
ENTITY
FORM
Created by
ENTITY
FORM
Date Maintained
ENTITY
FORM
Time Maintained
ENTITY
FORM
Maintained by
ENTITY
FORM
Project
ENTITY
FORM
Lock Type
ENTITY
FORM
Lock Id
ENTITY
FORM
Change #
ENTITY
FORM
Owner Id
ENTITY
FORM
QA Status
ENTITY
FORM
ENTITY
FORM
ENTITY
FORM
ENTITY
FORM
ENTITY
FORM
Version
ENTITY
FSCHEME
System Id
ENTITY
FSCHEME
Name
ENTITY
FSCHEME
Description
ENTITY
FSCHEME
Mutually Exclusive
ENTITY
FSCHEME
Date Created
ENTITY
FSCHEME
Time Created
ENTITY
FSCHEME
Created by
ENTITY
FSCHEME
Date Maintained
B-15
Table B-2
B-16
Object Type
System Name
Attribute Name
Significant?
ENTITY
FSCHEME
Time Maintained
ENTITY
FSCHEME
Maintained by
ENTITY
FSCHEME
Project
ENTITY
FSCHEME
Lock Type
ENTITY
FSCHEME
Lock Id
ENTITY
FSCHEME
Change #
ENTITY
FSCHEME
Owner Id
ENTITY
FSCHEME
QA Status
ENTITY
FSCHEME
ENTITY
FSCHEME
ENTITY
FSCHEME
ENTITY
FSCHEME
ENTITY
FSCHEME
Version
ENTITY
FUNC
System Id
ENTITY
FUNC
Name
ENTITY
FUNC
Business System Id
ENTITY
FUNC
Menu Description
ENTITY
FUNC
Sub-Process Menu Type
ENTITY
FUNC
Application Id
ENTITY
FUNC
Date Created
ENTITY
FUNC
Time Created
ENTITY
FUNC
Created by
ENTITY
FUNC
Date Maintained
ENTITY
FUNC
Time Maintained
ENTITY
FUNC
Maintained by
ENTITY
FUNC
Project
ENTITY
FUNC
Lock Type
ENTITY
FUNC
Lock Id
ENTITY
FUNC
Change #
ENTITY
FUNC
Owner Id
ENTITY
FUNC
QA Status
ENTITY
FUNC
ENTITY
FUNC
ENTITY
FUNC
ENTITY
FUNC
ENTITY
FUNC
Version
ENTITY
FVALUE
System Id
ENTITY
FVALUE
Name
ENTITY
FVALUE
Description
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
FVALUE
Date Created
ENTITY
FVALUE
Time Created
ENTITY
FVALUE
Created by
ENTITY
FVALUE
Date Maintained
ENTITY
FVALUE
Time Maintained
ENTITY
FVALUE
Maintained by
ENTITY
FVALUE
Project
ENTITY
FVALUE
Lock Type
ENTITY
FVALUE
Lock Id
ENTITY
FVALUE
Change #
ENTITY
FVALUE
Owner Id
ENTITY
FVALUE
QA Status
ENTITY
FVALUE
ENTITY
FVALUE
ENTITY
FVALUE
ENTITY
FVALUE
ENTITY
FVALUE
Version
ENTITY
GROUP
System Id
ENTITY
GROUP
Name
ENTITY
GROUP
Description
ENTITY
GROUP
Date Created
ENTITY
GROUP
Time Created
ENTITY
GROUP
Created by
ENTITY
GROUP
Date Maintained
ENTITY
GROUP
Time Maintained
ENTITY
GROUP
Maintained by
ENTITY
GROUP
Project
ENTITY
GROUP
Lock Type
ENTITY
GROUP
Lock Id
ENTITY
GROUP
Change #
ENTITY
GROUP
Owner Id
ENTITY
GROUP
QA Status
ENTITY
GROUP
ENTITY
GROUP
ENTITY
GROUP
ENTITY
GROUP
ENTITY
GROUP
Version
ENTITY
HELP
System Id
ENTITY
HELP
Name
B-17
Table B-2
B-18
Object Type
System Name
Attribute Name
Significant?
ENTITY
HELP
Format
ENTITY
HELP
Description
ENTITY
HELP
Country Language
ENTITY
HELP
Date Created
ENTITY
HELP
Time Created
ENTITY
HELP
Created by
ENTITY
HELP
Date Maintained
ENTITY
HELP
Time Maintained
ENTITY
HELP
Maintained by
ENTITY
HELP
Project
ENTITY
HELP
Lock Type
ENTITY
HELP
Lock Id
ENTITY
HELP
Change #
ENTITY
HELP
Owner Id
ENTITY
HELP
QA Status
ENTITY
HELP
ENTITY
HELP
ENTITY
HELP
ENTITY
HELP
ENTITY
HELP
Version
ENTITY
HLPTXT
System Id
ENTITY
HLPTXT
Name
ENTITY
HLPTXT
Country Language
ENTITY
HLPTXT
Date Created
ENTITY
HLPTXT
Time Created
ENTITY
HLPTXT
Created by
ENTITY
HLPTXT
Date Maintained
ENTITY
HLPTXT
Time Maintained
ENTITY
HLPTXT
Maintained by
ENTITY
HLPTXT
Project
ENTITY
HLPTXT
Lock Type
ENTITY
HLPTXT
Lock Id
ENTITY
HLPTXT
Change #
ENTITY
HLPTXT
Owner Id
ENTITY
HLPTXT
QA Status
ENTITY
HLPTXT
ENTITY
HLPTXT
ENTITY
HLPTXT
ENTITY
HLPTXT
ENTITY
HLPTXT
Version
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
IDENT
System Id
ENTITY
IDENT
Name
ENTITY
IDENT
Type
ENTITY
IDENT
Date Created
ENTITY
IDENT
Time Created
ENTITY
IDENT
Created by
ENTITY
IDENT
Date Maintained
ENTITY
IDENT
Time Maintained
ENTITY
IDENT
Maintained by
ENTITY
IDENT
Project
ENTITY
IDENT
Lock Type
ENTITY
IDENT
Lock Id
ENTITY
IDENT
Change #
ENTITY
IDENT
Owner Id
ENTITY
IDENT
QA Status
ENTITY
IDENT
ENTITY
IDENT
ENTITY
IDENT
ENTITY
IDENT
ENTITY
IDENT
Version
ENTITY
KEY
System Id
ENTITY
KEY
Name
ENTITY
KEY
Implementation Name
ENTITY
KEY
Type
ENTITY
KEY
Unique Flag
ENTITY
KEY
Delete Method
ENTITY
KEY
Update Method
ENTITY
KEY
Date Created
ENTITY
KEY
Time Created
ENTITY
KEY
Created by
ENTITY
KEY
Date Maintained
ENTITY
KEY
Time Maintained
ENTITY
KEY
Maintained by
ENTITY
KEY
Project
ENTITY
KEY
Lock Type
ENTITY
KEY
Lock Id
ENTITY
KEY
Change #
ENTITY
KEY
Owner Id
ENTITY
KEY
QA Status
B-19
Table B-2
B-20
Object Type
System Name
Attribute Name
Significant?
ENTITY
KEY
ENTITY
KEY
ENTITY
KEY
ENTITY
KEY
ENTITY
KEY
Version
ENTITY
LANG
System Id
ENTITY
LANG
Name
ENTITY
LANG
Language Abbreviation
ENTITY
LANG
Date Created
ENTITY
LANG
Time Created
ENTITY
LANG
Created by
ENTITY
LANG
Date Maintained
ENTITY
LANG
Time Maintained
ENTITY
LANG
Maintained by
ENTITY
LANG
Project
ENTITY
LANG
Lock Type
ENTITY
LANG
Lock Id
ENTITY
LANG
Change #
ENTITY
LANG
Owner Id
ENTITY
LANG
QA Status
ENTITY
LANG
ENTITY
LANG
ENTITY
LANG
ENTITY
LANG
ENTITY
LANG
Version
ENTITY
LOC
System Id
ENTITY
LOC
Name
ENTITY
LOC
Description
ENTITY
LOC
Date Created
ENTITY
LOC
Time Created
ENTITY
LOC
Created by
ENTITY
LOC
Date Maintained
ENTITY
LOC
Time Maintained
ENTITY
LOC
Maintained by
ENTITY
LOC
Project
ENTITY
LOC
Lock Type
ENTITY
LOC
Lock Id
ENTITY
LOC
Change #
ENTITY
LOC
Owner Id
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
LOC
QA Status
ENTITY
LOC
ENTITY
LOC
ENTITY
LOC
ENTITY
LOC
ENTITY
LOC
Version
ENTITY
LOGPRO
System Id
ENTITY
LOGPRO
Name
ENTITY
LOGPRO
Description
ENTITY
LOGPRO
Type
ENTITY
LOGPRO
Mode
ENTITY
LOGPRO
Date Created
ENTITY
LOGPRO
Time Created
ENTITY
LOGPRO
Created by
ENTITY
LOGPRO
Date Maintained
ENTITY
LOGPRO
Time Maintained
ENTITY
LOGPRO
Maintained by
ENTITY
LOGPRO
Project
ENTITY
LOGPRO
Lock Type
ENTITY
LOGPRO
Lock Id
ENTITY
LOGPRO
Change #
ENTITY
LOGPRO
Owner Id
ENTITY
LOGPRO
QA Status
ENTITY
LOGPRO
ENTITY
LOGPRO
ENTITY
LOGPRO
ENTITY
LOGPRO
ENTITY
LOGPRO
Version
ENTITY
MACHINE
System Id
ENTITY
MACHINE
Name
ENTITY
MACHINE
Implementation Name
ENTITY
MACHINE
Operating System
ENTITY
MACHINE
OS Release
ENTITY
MACHINE
Machine Group
ENTITY
MACHINE
Date Created
ENTITY
MACHINE
Time Created
ENTITY
MACHINE
Created by
ENTITY
MACHINE
Date Maintained
ENTITY
MACHINE
Time Maintained
B-21
Table B-2
B-22
Object Type
System Name
Attribute Name
Significant?
ENTITY
MACHINE
Maintained by
ENTITY
MACHINE
Project
ENTITY
MACHINE
Lock Type
ENTITY
MACHINE
Lock Id
ENTITY
MACHINE
Change #
ENTITY
MACHINE
Owner Id
ENTITY
MACHINE
QA Status
ENTITY
MACHINE
ENTITY
MACHINE
ENTITY
MACHINE
ENTITY
MACHINE
ENTITY
MACHINE
Version
ENTITY
MCGRP
System Id
ENTITY
MCGRP
Name
ENTITY
MCGRP
Date Created
ENTITY
MCGRP
Time Created
ENTITY
MCGRP
Created by
ENTITY
MCGRP
Date Maintained
ENTITY
MCGRP
Time Maintained
ENTITY
MCGRP
Maintained by
ENTITY
MCGRP
Project
ENTITY
MCGRP
Lock Type
ENTITY
MCGRP
Lock Id
ENTITY
MCGRP
Change #
ENTITY
MCGRP
Owner Id
ENTITY
MCGRP
QA Status
ENTITY
MCGRP
ENTITY
MCGRP
ENTITY
MCGRP
ENTITY
MCGRP
ENTITY
MCGRP
Version
ENTITY
MIGRTN
System Id
ENTITY
MIGRTN
Name
ENTITY
MIGRTN
Description
ENTITY
MIGRTN
Data Set Prefix
ENTITY
MIGRTN
Migration State
ENTITY
MIGRTN
Return Code
ENTITY
MIGRTN
Processing Version
ENTITY
MIGRTN
Date Created
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
MIGRTN
Time Created
ENTITY
MIGRTN
Created by
ENTITY
MIGRTN
Date Maintained
ENTITY
MIGRTN
Time Maintained
ENTITY
MIGRTN
Maintained by
ENTITY
MIGRTN
Project
ENTITY
MIGRTN
Lock Type
ENTITY
MIGRTN
Lock Id
ENTITY
MIGRTN
Change #
ENTITY
MIGRTN
Owner Id
ENTITY
MIGRTN
QA Status
ENTITY
MIGRTN
ENTITY
MIGRTN
ENTITY
MIGRTN
ENTITY
MIGRTN
ENTITY
MIGRTN
Version
ENTITY
ORG
System Id
ENTITY
ORG
Name
ENTITY
ORG
Date Created
ENTITY
ORG
Time Created
ENTITY
ORG
Created by
ENTITY
ORG
Date Maintained
ENTITY
ORG
Time Maintained
ENTITY
ORG
Maintained by
ENTITY
ORG
Project
ENTITY
ORG
Lock Type
ENTITY
ORG
Lock Id
ENTITY
ORG
Change #
ENTITY
ORG
Owner Id
ENTITY
ORG
QA Status
ENTITY
ORG
ENTITY
ORG
ENTITY
ORG
ENTITY
ORG
ENTITY
ORG
Version
ENTITY
PANEL
System Id
ENTITY
PANEL
Name
ENTITY
PANEL
Coordinate System
ENTITY
PANEL
X-Resolution
B-23
Table B-2
B-24
Object Type
System Name
Attribute Name
Significant?
ENTITY
PANEL
Y-Resolution
ENTITY
PANEL
Description
ENTITY
PANEL
Country Language
ENTITY
PANEL
Base
ENTITY
PANEL
GUI
ENTITY
PANEL
Date Created
ENTITY
PANEL
Time Created
ENTITY
PANEL
Created by
ENTITY
PANEL
Date Maintained
ENTITY
PANEL
Time Maintained
ENTITY
PANEL
Maintained by
ENTITY
PANEL
Project
ENTITY
PANEL
Lock Type
ENTITY
PANEL
Lock Id
ENTITY
PANEL
Change #
ENTITY
PANEL
Owner Id
ENTITY
PANEL
QA Status
ENTITY
PANEL
ENTITY
PANEL
ENTITY
PANEL
ENTITY
PANEL
ENTITY
PANEL
Version
ENTITY
PHYEVT
System Id
ENTITY
PHYEVT
Name
ENTITY
PHYEVT
Event Description
ENTITY
PHYEVT
Event Type
ENTITY
PHYEVT
Event Class
ENTITY
PHYEVT
Event Scope
ENTITY
PHYEVT
Date Created
ENTITY
PHYEVT
Time Created
ENTITY
PHYEVT
Created by
ENTITY
PHYEVT
Date Maintained
ENTITY
PHYEVT
Time Maintained
ENTITY
PHYEVT
Maintained by
ENTITY
PHYEVT
Project
ENTITY
PHYEVT
Lock Type
ENTITY
PHYEVT
Lock Id
ENTITY
PHYEVT
Change #
ENTITY
PHYEVT
Owner Id
ENTITY
PHYEVT
QA Status
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
PHYEVT
ENTITY
PHYEVT
ENTITY
PHYEVT
ENTITY
PHYEVT
ENTITY
PHYEVT
Version
ENTITY
PROCES
System Id
ENTITY
PROCES
Name
ENTITY
PROCES
Description
ENTITY
PROCES
Menu Description
ENTITY
PROCES
Work Station Group Id
ENTITY
PROCES
Sub-Process Menu Type
ENTITY
PROCES
ENTITY
PROCES
Date Created
ENTITY
PROCES
Time Created
ENTITY
PROCES
Created by
ENTITY
PROCES
Date Maintained
ENTITY
PROCES
Time Maintained
ENTITY
PROCES
Maintained by
ENTITY
PROCES
Project
ENTITY
PROCES
Lock Type
ENTITY
PROCES
Lock Id
ENTITY
PROCES
Change #
ENTITY
PROCES
Owner Id
ENTITY
PROCES
QA Status
ENTITY
PROCES
ENTITY
PROCES
ENTITY
PROCES
ENTITY
PROCES
ENTITY
PROCES
Version
ENTITY
PROJCT
System Id
ENTITY
PROJCT
Project Name
ENTITY
PROJCT
Project Id
ENTITY
PROJCT
Type
ENTITY
PROJCT
Description
ENTITY
PROJCT
Date Created
ENTITY
PROJCT
Time Created
ENTITY
PROJCT
Created by
ENTITY
PROJCT
Date Maintained
ENTITY
PROJCT
Time Maintained
B-25
Table B-2
B-26
Object Type
System Name
Attribute Name
Significant?
ENTITY
PROJCT
Maintained by
ENTITY
PROJCT
Project
ENTITY
PROJCT
Lock Type
ENTITY
PROJCT
Lock Id
ENTITY
PROJCT
Change #
ENTITY
PROJCT
Owner Id
ENTITY
PROJCT
QA Status
ENTITY
PROJCT
ENTITY
PROJCT
ENTITY
PROJCT
ENTITY
PROJCT
ENTITY
PROJCT
Version
ENTITY
RBDPKG
System Id
ENTITY
RBDPKG
Name
ENTITY
RBDPKG
Description
ENTITY
RBDPKG
Rebuild Package State
ENTITY
RBDPKG
Return Code
ENTITY
RBDPKG
Date Created
ENTITY
RBDPKG
Time Created
ENTITY
RBDPKG
Created by
ENTITY
RBDPKG
Date Maintained
ENTITY
RBDPKG
Time Maintained
ENTITY
RBDPKG
Maintained by
ENTITY
RBDPKG
Project
ENTITY
RBDPKG
Lock Type
ENTITY
RBDPKG
Lock Id
ENTITY
RBDPKG
Change #
ENTITY
RBDPKG
Owner Id
ENTITY
RBDPKG
QA Status
ENTITY
RBDPKG
ENTITY
RBDPKG
ENTITY
RBDPKG
ENTITY
RBDPKG
ENTITY
RBDPKG
Version
ENTITY
REL
Relationship Type
ENTITY
REL
Name
ENTITY
REL
Relationship Code
ENTITY
REL
Y Description
ENTITY
REL
X Description
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
REL
Implementation Name
ENTITY
REL
Migration File Name
ENTITY
REL
Exit Routine
ENTITY
REL
Date Created
ENTITY
REL
Time Created
ENTITY
REL
Created by
ENTITY
REL
Date Maintained
ENTITY
REL
Time Maintained
ENTITY
REL
Maintained by
ENTITY
REL
Project
ENTITY
REL
Lock Type
ENTITY
REL
Lock Id
ENTITY
REL
Change #
ENTITY
REL
Owner Id
ENTITY
REL
QA Status
ENTITY
REL
ENTITY
REL
ENTITY
REL
ENTITY
REL
ENTITY
REL
Version
ENTITY
REPORT
Report Id
ENTITY
REPORT
Name
ENTITY
REPORT
ENTITY
REPORT
Page Size
ENTITY
REPORT
Line Size
ENTITY
REPORT
Left Margin
ENTITY
REPORT
Top Margin
ENTITY
REPORT
Printer Type
ENTITY
REPORT
Orientation
ENTITY
REPORT
Implementation Name
ENTITY
REPORT
Date Created
ENTITY
REPORT
Time Created
ENTITY
REPORT
Created by
ENTITY
REPORT
Date Maintained
ENTITY
REPORT
Time Maintained
ENTITY
REPORT
Maintained by
ENTITY
REPORT
Project
ENTITY
REPORT
Lock Type
ENTITY
REPORT
Lock Id
ENTITY
REPORT
Change #
B-27
Table B-2
B-28
Object Type
System Name
Attribute Name
Significant?
ENTITY
REPORT
Owner Id
ENTITY
REPORT
QA Status
ENTITY
REPORT
ENTITY
REPORT
ENTITY
REPORT
ENTITY
REPORT
ENTITY
REPORT
Version
ENTITY
REPOSIT
System Id
ENTITY
REPOSIT
Name
ENTITY
REPOSIT
Description
ENTITY
REPOSIT
Type
ENTITY
REPOSIT
Implementation Name
ENTITY
REPOSIT
Date Created
ENTITY
REPOSIT
Time Created
ENTITY
REPOSIT
Created by
ENTITY
REPOSIT
Date Maintained
ENTITY
REPOSIT
Time Maintained
ENTITY
REPOSIT
Maintained by
ENTITY
REPOSIT
Project
ENTITY
REPOSIT
Lock Type
ENTITY
REPOSIT
Lock Id
ENTITY
REPOSIT
Change #
ENTITY
REPOSIT
Owner Id
ENTITY
REPOSIT
QA Status
ENTITY
REPOSIT
ENTITY
REPOSIT
ENTITY
REPOSIT
ENTITY
REPOSIT
ENTITY
REPOSIT
Version
ENTITY
RLN
System Id
ENTITY
RLN
Name
ENTITY
RLN
Complex
ENTITY
RLN
ENTITY
RLN
ENTITY
RLN
Activity Period
ENTITY
RLN
Average Inserts for Period
ENTITY
RLN
Average Deletes for Period
ENTITY
RLN
Average Updates for Period
ENTITY
RLN
Expected Rows
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
RLN
Date Created
ENTITY
RLN
Time Created
ENTITY
RLN
Created by
ENTITY
RLN
Date Maintained
ENTITY
RLN
Time Maintained
ENTITY
RLN
Maintained by
ENTITY
RLN
Project
ENTITY
RLN
Lock Type
ENTITY
RLN
Lock Id
ENTITY
RLN
Change #
ENTITY
RLN
Owner Id
ENTITY
RLN
QA Status
ENTITY
RLN
ENTITY
RLN
ENTITY
RLN
ENTITY
RLN
ENTITY
RLN
Version
ENTITY
RULE
System Id
ENTITY
RULE
Name
ENTITY
RULE
ENTITY
RULE
DB2 Plan Name
ENTITY
RULE
DBMS Usage
ENTITY
RULE
Description
ENTITY
RULE
Execution Mode
ENTITY
RULE
CICS / IMS Transaction Id
ENTITY
RULE
Implementation Name
ENTITY
RULE
Package
ENTITY
RULE
Isolation Mode
ENTITY
RULE
Date Created
ENTITY
RULE
Time Created
ENTITY
RULE
Created by
ENTITY
RULE
Date Maintained
ENTITY
RULE
Time Maintained
ENTITY
RULE
Maintained by
ENTITY
RULE
Project
ENTITY
RULE
Lock Type
ENTITY
RULE
Lock Id
ENTITY
RULE
Change #
ENTITY
RULE
Owner Id
ENTITY
RULE
QA Status
B-29
Table B-2
B-30
Object Type
System Name
Attribute Name
Significant?
ENTITY
RULE
ENTITY
RULE
ENTITY
RULE
ENTITY
RULE
ENTITY
RULE
Version
ENTITY
SDSAPK
System Id
ENTITY
SDSAPK
Name
ENTITY
SDSAPK
Release Name
ENTITY
SDSAPK
Date Created
ENTITY
SDSAPK
Time Created
ENTITY
SDSAPK
Created by
ENTITY
SDSAPK
Date Maintained
ENTITY
SDSAPK
Time Maintained
ENTITY
SDSAPK
Maintained by
ENTITY
SDSAPK
Project
ENTITY
SDSAPK
Lock Type
ENTITY
SDSAPK
Lock Id
ENTITY
SDSAPK
Change #
ENTITY
SDSAPK
Owner Id
ENTITY
SDSAPK
QA Status
ENTITY
SDSAPK
ENTITY
SDSAPK
ENTITY
SDSAPK
ENTITY
SDSAPK
ENTITY
SDSAPK
Version
ENTITY
SDSPAK
System Id
ENTITY
SDSPAK
Name
ENTITY
SDSPAK
Total Orders Licensed
ENTITY
SDSPAK
Orders Remaining
ENTITY
SDSPAK
Date Created
ENTITY
SDSPAK
Time Created
ENTITY
SDSPAK
Created by
ENTITY
SDSPAK
Date Maintained
ENTITY
SDSPAK
Time Maintained
ENTITY
SDSPAK
Maintained by
ENTITY
SDSPAK
Project
ENTITY
SDSPAK
Lock Type
ENTITY
SDSPAK
Lock Id
ENTITY
SDSPAK
Change #
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
SDSPAK
Owner Id
ENTITY
SDSPAK
QA Status
ENTITY
SDSPAK
ENTITY
SDSPAK
ENTITY
SDSPAK
ENTITY
SDSPAK
ENTITY
SDSPAK
Version
ENTITY
SDSPCD
System Id
ENTITY
SDSPCD
Name
ENTITY
SDSPCD
Date Created
ENTITY
SDSPCD
Time Created
ENTITY
SDSPCD
Created by
ENTITY
SDSPCD
Date Maintained
ENTITY
SDSPCD
Time Maintained
ENTITY
SDSPCD
Maintained by
ENTITY
SDSPCD
Project
ENTITY
SDSPCD
Lock Type
ENTITY
SDSPCD
Lock Id
ENTITY
SDSPCD
Change #
ENTITY
SDSPCD
Owner Id
ENTITY
SDSPCD
QA Status
ENTITY
SDSPCD
ENTITY
SDSPCD
ENTITY
SDSPCD
ENTITY
SDSPCD
ENTITY
SDSPCD
Version
ENTITY
SDSPSC
System Id
ENTITY
SDSPSC
Name
ENTITY
SDSPSC
Extract to File Name
ENTITY
SDSPSC
Date Created
ENTITY
SDSPSC
Time Created
ENTITY
SDSPSC
Created by
ENTITY
SDSPSC
Date Maintained
ENTITY
SDSPSC
Time Maintained
ENTITY
SDSPSC
Maintained by
ENTITY
SDSPSC
Project
ENTITY
SDSPSC
Lock Type
ENTITY
SDSPSC
Lock Id
ENTITY
SDSPSC
Change #
B-31
Table B-2
B-32
Object Type
System Name
Attribute Name
Significant?
ENTITY
SDSPSC
Owner Id
ENTITY
SDSPSC
QA Status
ENTITY
SDSPSC
ENTITY
SDSPSC
ENTITY
SDSPSC
ENTITY
SDSPSC
ENTITY
SDSPSC
Version
ENTITY
SECENV
System Id
ENTITY
SECENV
Customer Group Id
ENTITY
SECENV
Customer Group Name
ENTITY
SECENV
Date Created
ENTITY
SECENV
Time Created
ENTITY
SECENV
Created by
ENTITY
SECENV
Date Maintained
ENTITY
SECENV
Time Maintained
ENTITY
SECENV
Maintained by
ENTITY
SECENV
Project
ENTITY
SECENV
Lock Type
ENTITY
SECENV
Lock Id
ENTITY
SECENV
Change #
ENTITY
SECENV
Owner Id
ENTITY
SECENV
QA Status
ENTITY
SECENV
ENTITY
SECENV
ENTITY
SECENV
ENTITY
SECENV
ENTITY
SECENV
Version
ENTITY
SECTN
System Id
ENTITY
SECTN
Name
ENTITY
SECTN
Implementation Name
ENTITY
SECTN
Date Created
ENTITY
SECTN
Time Created
ENTITY
SECTN
Created by
ENTITY
SECTN
Date Maintained
ENTITY
SECTN
Time Maintained
ENTITY
SECTN
Maintained by
ENTITY
SECTN
Project
ENTITY
SECTN
Lock Type
ENTITY
SECTN
Lock Id
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
SECTN
Change #
ENTITY
SECTN
Owner Id
ENTITY
SECTN
QA Status
ENTITY
SECTN
ENTITY
SECTN
ENTITY
SECTN
ENTITY
SECTN
ENTITY
SECTN
Version
ENTITY
SERVER
System Id
ENTITY
SERVER
Name
ENTITY
SERVER
Implementation Name
ENTITY
SERVER
Date Created
ENTITY
SERVER
Time Created
ENTITY
SERVER
Created by
ENTITY
SERVER
Date Maintained
ENTITY
SERVER
Time Maintained
ENTITY
SERVER
Maintained by
ENTITY
SERVER
Project
ENTITY
SERVER
Lock Type
ENTITY
SERVER
Lock Id
ENTITY
SERVER
Change #
ENTITY
SERVER
Owner Id
ENTITY
SERVER
QA Status
ENTITY
SERVER
ENTITY
SERVER
ENTITY
SERVER
ENTITY
SERVER
ENTITY
SERVER
Version
ENTITY
SET
System Id
ENTITY
SET
Name
ENTITY
SET
Field Picture - Storage
ENTITY
SET
Set Format
ENTITY
SET
Set Length
ENTITY
SET
Set Fraction
ENTITY
SET
Implementation Name
ENTITY
SET
Style
ENTITY
SET
Representation Length
ENTITY
SET
Date Created
ENTITY
SET
Time Created
B-33
Table B-2
B-34
Object Type
System Name
Attribute Name
Significant?
ENTITY
SET
Created by
ENTITY
SET
Date Maintained
ENTITY
SET
Time Maintained
ENTITY
SET
Maintained by
ENTITY
SET
Project
ENTITY
SET
Lock Type
ENTITY
SET
Lock Id
ENTITY
SET
Change #
ENTITY
SET
Owner Id
ENTITY
SET
QA Status
ENTITY
SET
ENTITY
SET
ENTITY
SET
ENTITY
SET
ENTITY
SET
Version
ENTITY
SOURCEB
System Id
ENTITY
SOURCEB
Name
ENTITY
SOURCEB
Description
ENTITY
SOURCEB
Implementation Name
ENTITY
SOURCEB
Implementation Storage
ENTITY
SOURCEB
Migration File Name
ENTITY
SOURCEB
Date Created
ENTITY
SOURCEB
Time Created
ENTITY
SOURCEB
Created by
ENTITY
SOURCEB
Date Maintained
ENTITY
SOURCEB
Time Maintained
ENTITY
SOURCEB
Maintained by
ENTITY
SOURCEB
Project
ENTITY
SOURCEB
Lock Type
ENTITY
SOURCEB
Lock Id
ENTITY
SOURCEB
Change #
ENTITY
SOURCEB
Owner Id
ENTITY
SOURCEB
QA Status
ENTITY
SOURCEB
ENTITY
SOURCEB
ENTITY
SOURCEB
ENTITY
SOURCEB
ENTITY
SOURCEB
Version
ENTITY
STATE
System Id
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
STATE
Name
ENTITY
STATE
Description
ENTITY
STATE
Type
ENTITY
STATE
Date Created
ENTITY
STATE
Time Created
ENTITY
STATE
Created by
ENTITY
STATE
Date Maintained
ENTITY
STATE
Time Maintained
ENTITY
STATE
Maintained by
ENTITY
STATE
Project
ENTITY
STATE
Lock Type
ENTITY
STATE
Lock Id
ENTITY
STATE
Change #
ENTITY
STATE
Owner Id
ENTITY
STATE
QA Status
ENTITY
STATE
ENTITY
STATE
ENTITY
STATE
ENTITY
STATE
ENTITY
STATE
Version
ENTITY
STORE
System Id
ENTITY
STORE
Name
ENTITY
STORE
Description
ENTITY
STORE
Date Created
ENTITY
STORE
Time Created
ENTITY
STORE
Created by
ENTITY
STORE
Date Maintained
ENTITY
STORE
Time Maintained
ENTITY
STORE
Maintained by
ENTITY
STORE
Project
ENTITY
STORE
Lock Type
ENTITY
STORE
Lock Id
ENTITY
STORE
Change #
ENTITY
STORE
Owner Id
ENTITY
STORE
QA Status
ENTITY
STORE
ENTITY
STORE
ENTITY
STORE
ENTITY
STORE
ENTITY
STORE
Version
B-35
Table B-2
B-36
Object Type
System Name
Attribute Name
Significant?
ENTITY
SYMBOL
System Id
ENTITY
SYMBOL
Name
ENTITY
SYMBOL
Define
ENTITY
SYMBOL
Encoding
ENTITY
SYMBOL
Display
ENTITY
SYMBOL
Date Created
ENTITY
SYMBOL
Time Created
ENTITY
SYMBOL
Created by
ENTITY
SYMBOL
Date Maintained
ENTITY
SYMBOL
Time Maintained
ENTITY
SYMBOL
Maintained by
ENTITY
SYMBOL
Project
ENTITY
SYMBOL
Lock Type
ENTITY
SYMBOL
Lock Id
ENTITY
SYMBOL
Change #
ENTITY
SYMBOL
Owner Id
ENTITY
SYMBOL
QA Status
ENTITY
SYMBOL
ENTITY
SYMBOL
ENTITY
SYMBOL
ENTITY
SYMBOL
ENTITY
SYMBOL
Version
ENTITY
TABLE
System Id
ENTITY
TABLE
Name
ENTITY
TABLE
Table Or View
ENTITY
TABLE
Table Creator
ENTITY
TABLE
Implementation Name
ENTITY
TABLE
ENTITY
TABLE
ENTITY
TABLE
Activity Period
ENTITY
TABLE
Average Inserts For Period
ENTITY
TABLE
Average Deletes For Period
ENTITY
TABLE
Average Updates For Period
ENTITY
TABLE
Date Created
ENTITY
TABLE
Time Created
ENTITY
TABLE
Created by
ENTITY
TABLE
Date Maintained
ENTITY
TABLE
Time Maintained
ENTITY
TABLE
Maintained by
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
TABLE
Project
ENTITY
TABLE
Lock Type
ENTITY
TABLE
Lock Id
ENTITY
TABLE
Change #
ENTITY
TABLE
Owner Id
ENTITY
TABLE
QA Status
ENTITY
TABLE
ENTITY
TABLE
ENTITY
TABLE
ENTITY
TABLE
ENTITY
TABLE
Version
ENTITY
TRANS
System Id
ENTITY
TRANS
Name
ENTITY
TRANS
Date Created
ENTITY
TRANS
Time Created
ENTITY
TRANS
Created by
ENTITY
TRANS
Date Maintained
ENTITY
TRANS
Time Maintained
ENTITY
TRANS
Maintained by
ENTITY
TRANS
Project
ENTITY
TRANS
Lock Type
ENTITY
TRANS
Lock Id
ENTITY
TRANS
Change #
ENTITY
TRANS
Owner Id
ENTITY
TRANS
QA Status
ENTITY
TRANS
ENTITY
TRANS
ENTITY
TRANS
ENTITY
TRANS
ENTITY
TRANS
Version
ENTITY
TXT
System Id
ENTITY
TXT
ENTITY
TXT
ENTITY
TXT
ENTITY
TXT
ENTITY
TXT
Version
ENTITY
USER
System Id
ENTITY
USER
Name
B-37
Table B-2
B-38
Object Type
System Name
Attribute Name
Significant?
ENTITY
USER
User Name
ENTITY
USER
User Id
ENTITY
USER
JOB Accounting Information
ENTITY
USER
User Location
ENTITY
USER
JOB Name
ENTITY
USER
JOB Options
ENTITY
USER
Date Created
ENTITY
USER
Time Created
ENTITY
USER
Created by
ENTITY
USER
Date Maintained
ENTITY
USER
Time Maintained
ENTITY
USER
Maintained by
ENTITY
USER
Project
ENTITY
USER
Lock Type
ENTITY
USER
Lock Id
ENTITY
USER
Change #
ENTITY
USER
Owner Id
ENTITY
USER
QA Status
ENTITY
USER
ENTITY
USER
ENTITY
USER
ENTITY
USER
ENTITY
USER
Version
ENTITY
VALUES
System Id
ENTITY
VALUES
Name
ENTITY
VALUES
Value
ENTITY
VALUES
Date Created
ENTITY
VALUES
Time Created
ENTITY
VALUES
Created by
ENTITY
VALUES
Date Maintained
ENTITY
VALUES
Time Maintained
ENTITY
VALUES
Maintained by
ENTITY
VALUES
Project
ENTITY
VALUES
Lock Type
ENTITY
VALUES
Lock Id
ENTITY
VALUES
Change #
ENTITY
VALUES
Owner Id
ENTITY
VALUES
QA Status
ENTITY
VALUES
ENTITY
VALUES
Table B-2
Object Type
System Name
Attribute Name
Significant?
ENTITY
VALUES
ENTITY
VALUES
ENTITY
VALUES
Version
ENTITY
VIEW
System Id
ENTITY
VIEW
Name
ENTITY
VIEW
Description
ENTITY
VIEW
Implementation Name
ENTITY
VIEW
Date Created
ENTITY
VIEW
Time Created
ENTITY
VIEW
Created by
ENTITY
VIEW
Date Maintained
ENTITY
VIEW
Time Maintained
ENTITY
VIEW
Maintained by
ENTITY
VIEW
Project
ENTITY
VIEW
Lock Type
ENTITY
VIEW
Lock Id
ENTITY
VIEW
Change #
ENTITY
VIEW
Owner Id
ENTITY
VIEW
QA Status
ENTITY
VIEW
ENTITY
VIEW
ENTITY
VIEW
ENTITY
VIEW
ENTITY
VIEW
Version
ENTITY
WINCON
System Id
ENTITY
WINCON
Name
ENTITY
WINCON
GUI
ENTITY
WINCON
Date Created
ENTITY
WINCON
Time Created
ENTITY
WINCON
Created by
ENTITY
WINCON
Date Maintained
ENTITY
WINCON
Time Maintained
ENTITY
WINCON
Maintained by
ENTITY
WINCON
Project
ENTITY
WINCON
Lock Type
ENTITY
WINCON
Lock Id
ENTITY
WINCON
Change #
ENTITY
WINCON
Owner Id
ENTITY
WINCON
QA Status
B-39
Table B-2
B-40
Object Type
System Name
Attribute Name
Significant?
ENTITY
WINCON
ENTITY
WINCON
ENTITY
WINCON
ENTITY
WINCON
ENTITY
WINCON
Version
ENTITY
WINDOW
System Id
ENTITY
WINDOW
Name
ENTITY
WINDOW
Description
ENTITY
WINDOW
Implementation Name
ENTITY
WINDOW
Date Created
ENTITY
WINDOW
Time Created
ENTITY
WINDOW
Created by
ENTITY
WINDOW
Date Maintained
ENTITY
WINDOW
Time Maintained
ENTITY
WINDOW
Maintained by
ENTITY
WINDOW
Project
ENTITY
WINDOW
Lock Type
ENTITY
WINDOW
Lock Id
ENTITY
WINDOW
Change #
ENTITY
WINDOW
Owner Id
ENTITY
WINDOW
QA Status
ENTITY
WINDOW
ENTITY
WINDOW
ENTITY
WINDOW
ENTITY
WINDOW
ENTITY
WINDOW
Version
RELATE
ACHACU
Parent Type
RELATE
ACHACU
Application Config. Long

Name
RELATE
ACHACU
Sequence Number
RELATE
ACHACU
Child Type
RELATE
ACHACU
Configuration Unit Long

Name
RELATE
ACHACU
Separator Id
RELATE
ACHACU
Date Created
RELATE
ACHACU
Time Created
RELATE
ACHACU
Created by
RELATE
ACHACU
Date Maintained
RELATE
ACHACU
Time Maintained
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
ACHACU
Maintained by
RELATE
ACHACU
Change #
RELATE
ACHACU
QA Status
RELATE
ACHACU
RELATE
ACHACU
RELATE
ACHACU
RELATE
ACHACU
RELATE
ACHACU
Version
RELATE
ADPPAP
Parent Type
RELATE
ADPPAP
Parent Id
RELATE
ADPPAP
Sequence Number
RELATE
ADPPAP
Child Type
RELATE
ADPPAP
Child Id
RELATE
ADPPAP
Separator Id
RELATE
ADPPAP
Date Created
RELATE
ADPPAP
Time Created
RELATE
ADPPAP
Created by
RELATE
ADPPAP
Date Maintained
RELATE
ADPPAP
Time Maintained
RELATE
ADPPAP
Maintained by
RELATE
ADPPAP
Change #
RELATE
ADPPAP
QA Status
RELATE
ADPPAP
RELATE
ADPPAP
RELATE
ADPPAP
RELATE
ADPPAP
RELATE
ADPPAP
Version
RELATE
ATTATT
Parent Type
RELATE
ATTATT
Business Attribute Name
RELATE
ATTATT
Sequence Number
RELATE
ATTATT
Child Type
RELATE
ATTATT
RELATE
ATTATT
Separator Id
RELATE
ATTATT
Occurs
RELATE
ATTATT
Date Created
RELATE
ATTATT
Time Created
RELATE
ATTATT
Created by
RELATE
ATTATT
Date Maintained
RELATE
ATTATT
Time Maintained
B-41
Table B-2
B-42
Object Type
System Name
Attribute Name
Significant?
RELATE
ATTATT
Maintained by
RELATE
ATTATT
Change #
RELATE
ATTATT
QA Status
RELATE
ATTATT
RELATE
ATTATT
RELATE
ATTATT
RELATE
ATTATT
RELATE
ATTATT
Version
RELATE
ATTDAT
Parent Type
RELATE
ATTDAT
RELATE
ATTDAT
Sequence Number
RELATE
ATTDAT
Child Type
RELATE
ATTDAT
Data Type Name
RELATE
ATTDAT
Separator Id
RELATE
ATTDAT
Date Created
RELATE
ATTDAT
Time Created
RELATE
ATTDAT
Created by
RELATE
ATTDAT
Date Maintained
RELATE
ATTDAT
Time Maintained
RELATE
ATTDAT
Maintained by
RELATE
ATTDAT
Change #
RELATE
ATTDAT
QA Status
RELATE
ATTDAT
RELATE
ATTDAT
RELATE
ATTDAT
RELATE
ATTDAT
RELATE
ATTDAT
Version
RELATE
BMHABI
Parent Type
RELATE
BMHABI
Parent Long Name
RELATE
BMHABI
Sequence Number
RELATE
BMHABI
Child Type
RELATE
BMHABI
Child Long Name
RELATE
BMHABI
Separator Id
RELATE
BMHABI
Date Created
RELATE
BMHABI
Time Created
RELATE
BMHABI
Created by
RELATE
BMHABI
Date Maintained
RELATE
BMHABI
Time Maintained
RELATE
BMHABI
Maintained by
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
BMHABI
Change #
RELATE
BMHABI
QA Status
RELATE
BMHABI
RELATE
BMHABI
RELATE
BMHABI
RELATE
BMHABI
RELATE
BMHABI
Version
RELATE
BOBRBO
Parent Type
RELATE
BOBRBO
Business Object Long Name
RELATE
BOBRBO
Sequence Number
RELATE
BOBRBO
Child Type
RELATE
BOBRBO
Business Object Long Name
RELATE
BOBRBO
Separator Id
RELATE
BOBRBO
Date Created
RELATE
BOBRBO
Time Created
RELATE
BOBRBO
Created by
RELATE
BOBRBO
Date Maintained
RELATE
BOBRBO
Time Maintained
RELATE
BOBRBO
Maintained by
RELATE
BOBRBO
Change #
RELATE
BOBRBO
QA Status
RELATE
BOBRBO
RELATE
BOBRBO
RELATE
BOBRBO
RELATE
BOBRBO
RELATE
BOBRBO
Version
RELATE
BOOWXX
Parent Type
RELATE
BOOWXX
Business Object Name
RELATE
BOOWXX
Sequence Number
RELATE
BOOWXX
Child Type
RELATE
BOOWXX
Name
RELATE
BOOWXX
Separator Id
RELATE
BOOWXX
Date Created
RELATE
BOOWXX
Time Created
RELATE
BOOWXX
Created by
RELATE
BOOWXX
Date Maintained
RELATE
BOOWXX
Time Maintained
RELATE
BOOWXX
Maintained by
RELATE
BOOWXX
Change #
B-43
Table B-2
B-44
Object Type
System Name
Attribute Name
Significant?
RELATE
BOOWXX
QA Status
RELATE
BOOWXX
RELATE
BOOWXX
RELATE
BOOWXX
RELATE
BOOWXX
RELATE
BOOWXX
Version
RELATE
CECOXX
Parent Type
RELATE
CECOXX
Cell Long Name
RELATE
CECOXX
Sequence Number
RELATE
CECOXX
Child Type
RELATE
CECOXX
Child Long Name
RELATE
CECOXX
Separator Id
RELATE
CECOXX
Machine Implementation
Name
RELATE
CECOXX
Cell Manager
RELATE
CECOXX
Communication Gateway
RELATE
CECOXX
Application Server
RELATE
CECOXX
Network Id
RELATE
CECOXX
Date Created
RELATE
CECOXX
Time Created
RELATE
CECOXX
Created by
RELATE
CECOXX
Date Maintained
RELATE
CECOXX
Time Maintained
RELATE
CECOXX
Maintained by
RELATE
CECOXX
Change #
RELATE
CECOXX
QA Status
RELATE
CECOXX
RELATE
CECOXX
RELATE
CECOXX
RELATE
CECOXX
RELATE
CECOXX
Version
RELATE
COMCOM
Parent Type
RELATE
COMCOM
Component Long Name
RELATE
COMCOM
Sequence Number
RELATE
COMCOM
Child Type
RELATE
COMCOM
Sub-Component Long Name
RELATE
COMCOM
Separator Id
RELATE
COMCOM
Date Created
RELATE
COMCOM
Time Created
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
COMCOM
Created by
RELATE
COMCOM
Date Maintained
RELATE
COMCOM
Time Maintained
RELATE
COMCOM
Maintained by
RELATE
COMCOM
Change #
RELATE
COMCOM
QA Status
RELATE
COMCOM
RELATE
COMCOM
RELATE
COMCOM
RELATE
COMCOM
RELATE
COMCOM
Version
RELATE
CSGCPL
Parent Type
RELATE
CSGCPL
Parent Id
RELATE
CSGCPL
Sequence Number
RELATE
CSGCPL
Child Type
RELATE
CSGCPL
Child Id
RELATE
CSGCPL
Separator Id
RELATE
CSGCPL
Date Created
RELATE
CSGCPL
Time Created
RELATE
CSGCPL
Created by
RELATE
CSGCPL
Date Maintained
RELATE
CSGCPL
Time Maintained
RELATE
CSGCPL
Maintained by
RELATE
CSGCPL
Change #
RELATE
CSGCPL
QA Status
RELATE
CSGCPL
RELATE
CSGCPL
RELATE
CSGCPL
RELATE
CSGCPL
RELATE
CSGCPL
Version
RELATE
CSGCSG
Parent Type
RELATE
CSGCSG
Parent Id
RELATE
CSGCSG
Sequence Number
RELATE
CSGCSG
Child Type
RELATE
CSGCSG
Child Id
RELATE
CSGCSG
Separator Id
RELATE
CSGCSG
Date Created
RELATE
CSGCSG
Time Created
RELATE
CSGCSG
Created by
B-45
Table B-2
B-46
Object Type
System Name
Attribute Name
Significant?
RELATE
CSGCSG
Date Maintained
RELATE
CSGCSG
Time Maintained
RELATE
CSGCSG
Maintained by
RELATE
CSGCSG
Change #
RELATE
CSGCSG
QA Status
RELATE
CSGCSG
RELATE
CSGCSG
RELATE
CSGCSG
RELATE
CSGCSG
RELATE
CSGCSG
Version
RELATE
CSGCST
Parent Type
RELATE
CSGCST
Parent Id
RELATE
CSGCST
Sequence Number
RELATE
CSGCST
Child Type
RELATE
CSGCST
Child Id
RELATE
CSGCST
Separator Id
RELATE
CSGCST
Date Created
RELATE
CSGCST
Time Created
RELATE
CSGCST
Created by
RELATE
CSGCST
Date Maintained
RELATE
CSGCST
Time Maintained
RELATE
CSGCST
Maintained by
RELATE
CSGCST
Change #
RELATE
CSGCST
QA Status
RELATE
CSGCST
RELATE
CSGCST
RELATE
CSGCST
RELATE
CSGCST
RELATE
CSGCST
Version
RELATE
CSGCXX
Parent Type
RELATE
CSGCXX
Parent Id
RELATE
CSGCXX
Sequence Number
RELATE
CSGCXX
Child Type
RELATE
CSGCXX
Child Id
RELATE
CSGCXX
Separator Id
RELATE
CSGCXX
Date Created
RELATE
CSGCXX
Time Created
RELATE
CSGCXX
Created by
RELATE
CSGCXX
Date Maintained
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
CSGCXX
Time Maintained
RELATE
CSGCXX
Maintained by
RELATE
CSGCXX
Change #
RELATE
CSGCXX
QA Status
RELATE
CSGCXX
RELATE
CSGCXX
RELATE
CSGCXX
RELATE
CSGCXX
RELATE
CSGCXX
Version
RELATE
CSTENV
Parent Type
RELATE
CSTENV
Parent Id
RELATE
CSTENV
QA Status
RELATE
CSTENV
Sequence Number
RELATE
CSTENV
Child Type
RELATE
CSTENV
Child Id
RELATE
CSTENV
Separator Id
RELATE
CSTENV
Login ID
RELATE
CSTENV
Date Created
RELATE
CSTENV
Time Created
RELATE
CSTENV
Created by
RELATE
CSTENV
Date Maintained
RELATE
CSTENV
Time Maintained
RELATE
CSTENV
Maintained by
RELATE
CSTENV
Change #
RELATE
CSTENV
RELATE
CSTENV
RELATE
CSTENV
RELATE
CSTENV
RELATE
CSTENV
Version
RELATE
CUECXX
Parent Type
RELATE
CUECXX
Configuration Unit Long

Name
RELATE
CUECXX
Sequence Number
RELATE
CUECXX
Child Type
RELATE
CUECXX
Child Long Name
RELATE
CUECXX
Separator Id
RELATE
CUECXX
Preparation Time
RELATE
CUECXX
Implementation Name
RELATE
CUECXX
Service Name
B-47
Table B-2
B-48
Object Type
System Name
Attribute Name
Significant?
RELATE
CUECXX
Significant Time
RELATE
CUECXX
Link Type
RELATE
CUECXX
Owner Id
RELATE
CUECXX
Qualifier
RELATE
CUECXX
Plan Name
RELATE
CUECXX
Collection Id
RELATE
CUECXX
Version Id
RELATE
CUECXX
Isolation Mode
RELATE
CUECXX
Date Created
RELATE
CUECXX
Time Created
RELATE
CUECXX
Created by
RELATE
CUECXX
Date Maintained
RELATE
CUECXX
Time Maintained
RELATE
CUECXX
Maintained by
RELATE
CUECXX
Change #
RELATE
CUECXX
QA Status
RELATE
CUECXX
RELATE
CUECXX
RELATE
CUECXX
RELATE
CUECXX
RELATE
CUECXX
Version
RELATE
DATDAT
Parent Type
RELATE
DATDAT
Data Type Name
RELATE
DATDAT
Sequence Number
RELATE
DATDAT
Child Type
RELATE
DATDAT
Data Type Name
RELATE
DATDAT
Separator Id
RELATE
DATDAT
Occurs
RELATE
DATDAT
Date Created
RELATE
DATDAT
Time Created
RELATE
DATDAT
Created by
RELATE
DATDAT
Date Maintained
RELATE
DATDAT
Time Maintained
RELATE
DATDAT
Maintained by
RELATE
DATDAT
Change #
RELATE
DATDAT
QA Status
RELATE
DATDAT
RELATE
DATDAT
RELATE
DATDAT
RELATE
DATDAT
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
DATDAT
Version
RELATE
DATSET
Parent Type
RELATE
DATSET
Data Type Name
RELATE
DATSET
Sequence Number
RELATE
DATSET
Child Type
RELATE
DATSET
Set Name
RELATE
DATSET
Separator Id
RELATE
DATSET
Date Created
RELATE
DATSET
Time Created
RELATE
DATSET
Created by
RELATE
DATSET
Date Maintained
RELATE
DATSET
Time Maintained
RELATE
DATSET
Maintained by
RELATE
DATSET
Change #
RELATE
DATSET
QA Status
RELATE
DATSET
RELATE
DATSET
RELATE
DATSET
RELATE
DATSET
RELATE
DATSET
Version
RELATE
DBHATB
Parent Type
RELATE
DBHATB
Database Long Name
RELATE
DBHATB
Sequence Number
RELATE
DBHATB
Child Type
RELATE
DBHATB
Table Long Name
RELATE
DBHATB
Separator Id
RELATE
DBHATB
RELATE
DBHATB
RELATE
DBHATB
Activity Period
RELATE
DBHATB
Average Inserts
RELATE
DBHATB
Average Deletes
RELATE
DBHATB
Average Updates
RELATE
DBHATB
Done
RELATE
DBHATB
To Do
RELATE
DBHATB
Date Created
RELATE
DBHATB
Time Created
RELATE
DBHATB
Created by
RELATE
DBHATB
Date Maintained
RELATE
DBHATB
Time Maintained
B-49
Table B-2
B-50
Object Type
System Name
Attribute Name
Significant?
RELATE
DBHATB
Maintained by
RELATE
DBHATB
Change #
RELATE
DBHATB
QA Status
RELATE
DBHATB
RELATE
DBHATB
RELATE
DBHATB
RELATE
DBHATB
RELATE
DBHATB
Version
RELATE
ENTATT
Parent Type
RELATE
ENTATT
Business Entity Name
RELATE
ENTATT
Sequence Number
RELATE
ENTATT
Child Type
RELATE
ENTATT
RELATE
ENTATT
Separator Id
RELATE
ENTATT
Optional
RELATE
ENTATT
Date Created
RELATE
ENTATT
Time Created
RELATE
ENTATT
Created by
RELATE
ENTATT
Date Maintained
RELATE
ENTATT
Time Maintained
RELATE
ENTATT
Maintained by
RELATE
ENTATT
Change #
RELATE
ENTATT
QA Status
RELATE
ENTATT
RELATE
ENTATT
RELATE
ENTATT
RELATE
ENTATT
RELATE
ENTATT
Version
RELATE
ENTIDE
Parent Type
RELATE
ENTIDE
RELATE
ENTIDE
Sequence Number
RELATE
ENTIDE
Child Type
RELATE
ENTIDE
Identifier Name
RELATE
ENTIDE
Separator Id
RELATE
ENTIDE
Date Created
RELATE
ENTIDE
Time Created
RELATE
ENTIDE
Created by
RELATE
ENTIDE
Date Maintained
RELATE
ENTIDE
Time Maintained
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
ENTIDE
Maintained by
RELATE
ENTIDE
Change #
RELATE
ENTIDE
QA Status
RELATE
ENTIDE
RELATE
ENTIDE
RELATE
ENTIDE
RELATE
ENTIDE
RELATE
ENTIDE
Version
RELATE
ENTLO1
Parent Type
RELATE
ENTLO1
Parent Id
RELATE
ENTLO1
Sequence Number
RELATE
ENTLO1
Child Type
RELATE
ENTLO1
Child Id
RELATE
ENTLO1
Separator Id
RELATE
ENTLO1
Create Flag
RELATE
ENTLO1
Read Flag
RELATE
ENTLO1
Update Flag
RELATE
ENTLO1
Delete Flag
RELATE
ENTLO1
Comments
RELATE
ENTLO1
Date Created
RELATE
ENTLO1
Time Created
RELATE
ENTLO1
Created by
RELATE
ENTLO1
Date Maintained
RELATE
ENTLO1
Time Maintained
RELATE
ENTLO1
Maintained by
RELATE
ENTLO1
Change #
RELATE
ENTLO1
QA Status
RELATE
ENTLO1
RELATE
ENTLO1
RELATE
ENTLO1
RELATE
ENTLO1
RELATE
ENTLO1
Version
RELATE
ENTLO2
Parent Type
RELATE
ENTLO2
Parent Id
RELATE
ENTLO2
Sequence Number
RELATE
ENTLO2
Child Type
RELATE
ENTLO2
Child Id
RELATE
ENTLO2
Separator Id
RELATE
ENTLO2
Master Indicator
B-51
Table B-2
B-52
Object Type
System Name
Attribute Name
Significant?
RELATE
ENTLO2
Variant Indicator
RELATE
ENTLO2
Partitioned Indicator
RELATE
ENTLO2
Replicated Indicator
RELATE
ENTLO2
Subset Data
RELATE
ENTLO2
Reorganized Data
RELATE
ENTLO2
Teleprocessing (Remode
Data)
RELATE
ENTLO2
Comments
RELATE
ENTLO2
Date Created
RELATE
ENTLO2
Time Created
RELATE
ENTLO2
Created by
RELATE
ENTLO2
Date Maintained
RELATE
ENTLO2
Time Maintained
RELATE
ENTLO2
Maintained by
RELATE
ENTLO2
Change #
RELATE
ENTLO2
QA Status
RELATE
ENTLO2
RELATE
ENTLO2
RELATE
ENTLO2
RELATE
ENTLO2
RELATE
ENTLO2
Version
RELATE
ENTRLN
Parent Type
RELATE
ENTRLN
RELATE
ENTRLN
Sequence Number
RELATE
ENTRLN
Child Type
RELATE
ENTRLN
Business Relation Name
RELATE
ENTRLN
Separator Id
RELATE
ENTRLN
Chief Executive
RELATE
ENTRLN
Cardinality
RELATE
ENTRLN
Optionality
RELATE
ENTRLN
Dependant
RELATE
ENTRLN
Abstract
RELATE
ENTRLN
Role
RELATE
ENTRLN
Minimun Cardinality
RELATE
ENTRLN
Maximum Cardinality
RELATE
ENTRLN
Date Created
RELATE
ENTRLN
Time Created
RELATE
ENTRLN
Created by
RELATE
ENTRLN
Date Maintained
RELATE
ENTRLN
Time Maintained
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
ENTRLN
Maintained by
RELATE
ENTRLN
Change #
RELATE
ENTRLN
QA Status
RELATE
ENTRLN
RELATE
ENTRLN
RELATE
ENTRLN
RELATE
ENTRLN
RELATE
ENTRLN
Version
RELATE
EVCAXX
Parent Type
RELATE
EVCAXX
Event Name
RELATE
EVCAXX
Sequence Number
RELATE
EVCAXX
Child Type
RELATE
EVCAXX
Name
RELATE
EVCAXX
Separator Id
RELATE
EVCAXX
Description
RELATE
EVCAXX
Date Created
RELATE
EVCAXX
Time Created
RELATE
EVCAXX
Created by
RELATE
EVCAXX
Date Maintained
RELATE
EVCAXX
Time Maintained
RELATE
EVCAXX
Maintained by
RELATE
EVCAXX
Change #
RELATE
EVCAXX
QA Status
RELATE
EVCAXX
RELATE
EVCAXX
RELATE
EVCAXX
RELATE
EVCAXX
RELATE
EVCAXX
Version
RELATE
EVHARU
Parent Type
RELATE
EVHARU
Rule Long Name
RELATE
EVHARU
Sequence Number
RELATE
EVHARU
Child Type
RELATE
EVHARU
Event Long Name
RELATE
EVHARU
Separator Id
RELATE
EVHARU
Action Type
RELATE
EVHARU
Action Host
RELATE
EVHARU
View Mapping
RELATE
EVHARU
Date Created
RELATE
EVHARU
Time Created
B-53
Table B-2
B-54
Object Type
System Name
Attribute Name
Significant?
RELATE
EVHARU
Created by
RELATE
EVHARU
Date Maintained
RELATE
EVHARU
Time Maintained
RELATE
EVHARU
Maintained by
RELATE
EVHARU
Change #
RELATE
EVHARU
QA Status
RELATE
EVHARU
RELATE
EVHARU
RELATE
EVHARU
RELATE
EVHARU
RELATE
EVHARU
Version
RELATE
EVILBO
Parent Type
RELATE
EVILBO
Event Name
RELATE
EVILBO
Sequence Number
RELATE
EVILBO
Child Type
RELATE
EVILBO
Business Object Name
RELATE
EVILBO
Separator Id
RELATE
EVILBO
Description
RELATE
EVILBO
Date Created
RELATE
EVILBO
Time Created
RELATE
EVILBO
Created by
RELATE
EVILBO
Date Maintained
RELATE
EVILBO
Time Maintained
RELATE
EVILBO
Maintained by
RELATE
EVILBO
Change #
RELATE
EVILBO
QA Status
RELATE
EVILBO
RELATE
EVILBO
RELATE
EVILBO
RELATE
EVILBO
RELATE
EVILBO
Version
RELATE
FILECM
Type
RELATE
FILECM
Long Name
RELATE
FILECM
Sequence Number
RELATE
FILECM
Child Type
RELATE
FILECM
Child Id
RELATE
FILECM
Separator Id
RELATE
FILECM
Component Usage
RELATE
FILECM
Date Created
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
FILECM
Time Created
RELATE
FILECM
Created by
RELATE
FILECM
Date Maintained
RELATE
FILECM
Time Maintained
RELATE
FILECM
Maintained by
RELATE
FILECM
Change #
RELATE
FILECM
QA Status
RELATE
FILECM
RELATE
FILECM
RELATE
FILECM
RELATE
FILECM
RELATE
FILECM
Version
RELATE
FORWRD
Parent Type
RELATE
FORWRD
Parent Id
RELATE
FORWRD
Sequence Number
RELATE
FORWRD
Child Type
RELATE
FORWRD
Child Id
RELATE
FORWRD
Separator Id
RELATE
FORWRD
Store and Forward Update

Rule
RELATE
FORWRD
Store and Forward Delete

Rule
RELATE
FORWRD
Store and Forward Insert Rule
RELATE
FORWRD
Date Created
RELATE
FORWRD
Time Created
RELATE
FORWRD
Created by
RELATE
FORWRD
Date Maintained
RELATE
FORWRD
Time Maintained
RELATE
FORWRD
Maintained by
RELATE
FORWRD
Change #
RELATE
FORWRD
QA Status
RELATE
FORWRD
RELATE
FORWRD
RELATE
FORWRD
RELATE
FORWRD
RELATE
FORWRD
Version
RELATE
FSHAFV
Parent Type
RELATE
FSHAFV
FSDM Scheme Long Name
RELATE
FSHAFV
Sequence Number
B-55
Table B-2
B-56
Object Type
System Name
Attribute Name
Significant?
RELATE
FSHAFV
Child Type
RELATE
FSHAFV
FSDM Value Long Name
RELATE
FSHAFV
Separator Id
RELATE
FSHAFV
Date Created
RELATE
FSHAFV
Time Created
RELATE
FSHAFV
Created by
RELATE
FSHAFV
Date Maintained
RELATE
FSHAFV
Time Maintained
RELATE
FSHAFV
Maintained by
RELATE
FSHAFV
Change #
RELATE
FSHAFV
QA Status
RELATE
FSHAFV
RELATE
FSHAFV
RELATE
FSHAFV
RELATE
FSHAFV
RELATE
FSHAFV
Version
RELATE
FUNCPR
Parent Type
RELATE
FUNCPR
Business Function Long

Name
RELATE
FUNCPR
Sequence Number
RELATE
FUNCPR
Child Type
RELATE
FUNCPR
Business Process Long

Name
RELATE
FUNCPR
Separator Id
RELATE
FUNCPR
Date Created
RELATE
FUNCPR
Time Created
RELATE
FUNCPR
Created by
RELATE
FUNCPR
Date Maintained
RELATE
FUNCPR
Time Maintained
RELATE
FUNCPR
Maintained by
RELATE
FUNCPR
Change #
RELATE
FUNCPR
QA Status
RELATE
FUNCPR
RELATE
FUNCPR
RELATE
FUNCPR
RELATE
FUNCPR
RELATE
FUNCPR
Version
RELATE
FUNENT
Parent Type
RELATE
FUNENT

Name
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
FUNENT
Sequence Number
RELATE
FUNENT
Child Type
RELATE
FUNENT
Entity Long Name
RELATE
FUNENT
Separator Id
RELATE
FUNENT
Create Flag
RELATE
FUNENT
Read Flag
RELATE
FUNENT
Update Flag
RELATE
FUNENT
Delete Flag
RELATE
FUNENT
Comments
RELATE
FUNENT
Date Created
RELATE
FUNENT
Time Created
RELATE
FUNENT
Created by
RELATE
FUNENT
Date Maintained
RELATE
FUNENT
Time Maintained
RELATE
FUNENT
Maintained by
RELATE
FUNENT
Change #
RELATE
FUNENT
QA Status
RELATE
FUNENT
RELATE
FUNENT
RELATE
FUNENT
RELATE
FUNENT
RELATE
FUNENT
Version
RELATE
FUNLOC
Parent Type
RELATE
FUNLOC

Name
RELATE
FUNLOC
Sequence Number
RELATE
FUNLOC
Child Type
RELATE
FUNLOC
Location Long Name
RELATE
FUNLOC
Separator Id
RELATE
FUNLOC
Major Involvement in
Function
RELATE
FUNLOC
Minor Involvement in
Function
RELATE
FUNLOC
Comments
RELATE
FUNLOC
Date Created
RELATE
FUNLOC
Time Created
RELATE
FUNLOC
Created by
RELATE
FUNLOC
Date Maintained
RELATE
FUNLOC
Time Maintained
RELATE
FUNLOC
Maintained by
RELATE
FUNLOC
Change #
B-57
Table B-2
B-58
Object Type
System Name
Attribute Name
Significant?
RELATE
FUNLOC
QA Status
RELATE
FUNLOC
RELATE
FUNLOC
RELATE
FUNLOC
RELATE
FUNLOC
RELATE
FUNLOC
Version
RELATE
FVCLFS
Parent Type
RELATE
FVCLFS
FSDM Value Long Name
RELATE
FVCLFS
Sequence Number
RELATE
FVCLFS
Child Type
RELATE
FVCLFS
FSDM Scheme Long Name
RELATE
FVCLFS
Separator Id
RELATE
FVCLFS
Date Created
RELATE
FVCLFS
Time Created
RELATE
FVCLFS
Created by
RELATE
FVCLFS
Date Maintained
RELATE
FVCLFS
Time Maintained
RELATE
FVCLFS
Maintained by
RELATE
FVCLFS
Change #
RELATE
FVCLFS
QA Status
RELATE
FVCLFS
RELATE
FVCLFS
RELATE
FVCLFS
RELATE
FVCLFS
RELATE
FVCLFS
Version
RELATE
GRPGRP
Parent Type
RELATE
GRPGRP
Parent Long Name
RELATE
GRPGRP
Sequence Number
RELATE
GRPGRP
Child Type
RELATE
GRPGRP
Child Long Name
RELATE
GRPGRP
Separator Id
RELATE
GRPGRP
Date Created
RELATE
GRPGRP
Time Created
RELATE
GRPGRP
Created by
RELATE
GRPGRP
Date Maintained
RELATE
GRPGRP
Time Maintained
RELATE
GRPGRP
Maintained by
RELATE
GRPGRP
Change #
RELATE
GRPGRP
QA Status
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
GRPGRP
RELATE
GRPGRP
RELATE
GRPGRP
RELATE
GRPGRP
RELATE
GRPGRP
Version
RELATE
GRPPRJ
Parent Type
RELATE
GRPPRJ
Parent Long Name
RELATE
GRPPRJ
Sequence Number
RELATE
GRPPRJ
Child Type
RELATE
GRPPRJ
Child Long Name
RELATE
GRPPRJ
Separator Id
RELATE
GRPPRJ
Method Name
RELATE
GRPPRJ
Scope
RELATE
GRPPRJ
Scope Mode
RELATE
GRPPRJ
Date Created
RELATE
GRPPRJ
Time Created
RELATE
GRPPRJ
Created by
RELATE
GRPPRJ
Date Maintained
RELATE
GRPPRJ
Time Maintained
RELATE
GRPPRJ
Maintained by
RELATE
GRPPRJ
Change #
RELATE
GRPPRJ
QA Status
RELATE
GRPPRJ
RELATE
GRPPRJ
RELATE
GRPPRJ
RELATE
GRPPRJ
RELATE
GRPPRJ
Version
RELATE
GRPUSR
Parent Type
RELATE
GRPUSR
Parent Id
RELATE
GRPUSR
Sequence Number
RELATE
GRPUSR
Child Type
RELATE
GRPUSR
Child Id
RELATE
GRPUSR
Separator Id
RELATE
GRPUSR
User Authority level
RELATE
GRPUSR
Field Authority level
RELATE
GRPUSR
Date Created
RELATE
GRPUSR
Time Created
RELATE
GRPUSR
Created by
RELATE
GRPUSR
Date Maintained
B-59
Table B-2
B-60
Object Type
System Name
Attribute Name
Significant?
RELATE
GRPUSR
Time Maintained
RELATE
GRPUSR
Maintained by
RELATE
GRPUSR
Change #
RELATE
GRPUSR
QA Status
RELATE
GRPUSR
RELATE
GRPUSR
RELATE
GRPUSR
RELATE
GRPUSR
RELATE
GRPUSR
Version
RELATE
IDEATT
Parent Type
RELATE
IDEATT
Identifier Name
RELATE
IDEATT
Sequence Number
RELATE
IDEATT
Child Type
RELATE
IDEATT
RELATE
IDEATT
Separator Id
RELATE
IDEATT
Date Created
RELATE
IDEATT
Time Created
RELATE
IDEATT
Created by
RELATE
IDEATT
Date Maintained
RELATE
IDEATT
Time Maintained
RELATE
IDEATT
Maintained by
RELATE
IDEATT
Change #
RELATE
IDEATT
QA Status
RELATE
IDEATT
RELATE
IDEATT
RELATE
IDEATT
RELATE
IDEATT
RELATE
IDEATT
Version
RELATE
KEYDBY
Parent Type
RELATE
KEYDBY
Parent Id
RELATE
KEYDBY
Sequence Number
RELATE
KEYDBY
Child Type
RELATE
KEYDBY
Child Id
RELATE
KEYDBY
Separator Id
RELATE
KEYDBY
File Key type
RELATE
KEYDBY
Date Created
RELATE
KEYDBY
Time Created
RELATE
KEYDBY
Created by
RELATE
KEYDBY
Date Maintained
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
KEYDBY
Time Maintained
RELATE
KEYDBY
Maintained by
RELATE
KEYDBY
Change #
RELATE
KEYDBY
QA Status
RELATE
KEYDBY
RELATE
KEYDBY
RELATE
KEYDBY
RELATE
KEYDBY
RELATE
KEYDBY
Version
RELATE
KYHACO
Parent Type
RELATE
KYHACO
Key Long Name
RELATE
KYHACO
Sequence Number
RELATE
KYHACO
Child Type
RELATE
KYHACO
Column Long Name
RELATE
KYHACO
Separator Id
RELATE
KYHACO
Date Created
RELATE
KYHACO
Time Created
RELATE
KYHACO
Created by
RELATE
KYHACO
Date Maintained
RELATE
KYHACO
Time Maintained
RELATE
KYHACO
Maintained by
RELATE
KYHACO
Change #
RELATE
KYHACO
QA Status
RELATE
KYHACO
RELATE
KYHACO
RELATE
KYHACO
RELATE
KYHACO
RELATE
KYHACO
Version
RELATE
LOIBRL
Parent Type
RELATE
LOIBRL
Logical Long Name
RELATE
LOIBRL
Sequence Number
RELATE
LOIBRL
Child Type
RELATE
LOIBRL
Physical Long Name
RELATE
LOIBRL
Separator Id
RELATE
LOIBRL
Date Created
RELATE
LOIBRL
Time Created
RELATE
LOIBRL
Created by
RELATE
LOIBRL
Date Maintained
RELATE
LOIBRL
Time Maintained
B-61
Table B-2
B-62
Object Type
System Name
Attribute Name
Significant?
RELATE
LOIBRL
Maintained by
RELATE
LOIBRL
Change #
RELATE
LOIBRL
QA Status
RELATE
LOIBRL
RELATE
LOIBRL
RELATE
LOIBRL
RELATE
LOIBRL
RELATE
LOIBRL
Version
RELATE
LPAFXX
Parent Type
RELATE
LPAFXX
Logical Process Name
RELATE
LPAFXX
Sequence Number
RELATE
LPAFXX
Child Type
RELATE
LPAFXX
Name
RELATE
LPAFXX
Separator Id
RELATE
LPAFXX
Create
RELATE
LPAFXX
Read
RELATE
LPAFXX
Update
RELATE
LPAFXX
Delete
RELATE
LPAFXX
Comments
RELATE
LPAFXX
Date Created
RELATE
LPAFXX
Time Created
RELATE
LPAFXX
Created by
RELATE
LPAFXX
Date Maintained
RELATE
LPAFXX
Time Maintained
RELATE
LPAFXX
Maintained by
RELATE
LPAFXX
Change #
RELATE
LPAFXX
QA Status
RELATE
LPAFXX
RELATE
LPAFXX
RELATE
LPAFXX
RELATE
LPAFXX
RELATE
LPAFXX
Version
RELATE
LPIBRU
Parent Type
RELATE
LPIBRU
Logical Process Long Name
RELATE
LPIBRU
Sequence Number
RELATE
LPIBRU
Child Type
RELATE
LPIBRU
Rule Long Name
RELATE
LPIBRU
Separator Id
RELATE
LPIBRU
Date Created
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
LPIBRU
Time Created
RELATE
LPIBRU
Created by
RELATE
LPIBRU
Date Maintained
RELATE
LPIBRU
Time Maintained
RELATE
LPIBRU
Maintained by
RELATE
LPIBRU
Change #
RELATE
LPIBRU
QA Status
RELATE
LPIBRU
RELATE
LPIBRU
RELATE
LPIBRU
RELATE
LPIBRU
RELATE
LPIBRU
Version
RELATE
MCCAMC
Parent Type
RELATE
MCCAMC
Parent Machine Name
RELATE
MCCAMC
Sequence Number
RELATE
MCCAMC
Child Type
RELATE
MCCAMC
Name
RELATE
MCCAMC
Separator Id
RELATE
MCCAMC
Date Created
RELATE
MCCAMC
Time Created
RELATE
MCCAMC
Created by
RELATE
MCCAMC
Date Maintained
RELATE
MCCAMC
Time Maintained
RELATE
MCCAMC
Maintained by
RELATE
MCCAMC
Change #
RELATE
MCCAMC
QA Status
RELATE
MCCAMC
RELATE
MCCAMC
RELATE
MCCAMC
RELATE
MCCAMC
RELATE
MCCAMC
Version
RELATE
MCHENV
Parent Type
RELATE
MCHENV
Parent Id
RELATE
MCHENV
Sequence Number
RELATE
MCHENV
Child Type
RELATE
MCHENV
Child Id
RELATE
MCHENV
Separator Id
RELATE
MCHENV
Security Type
RELATE
MCHENV
Date Created
B-63
Table B-2
B-64
Object Type
System Name
Attribute Name
Significant?
RELATE
MCHENV
Time Created
RELATE
MCHENV
Created by
RELATE
MCHENV
Date Maintained
RELATE
MCHENV
Time Maintained
RELATE
MCHENV
Maintained by
RELATE
MCHENV
Change #
RELATE
MCHENV
QA Status
RELATE
MCHENV
RELATE
MCHENV
RELATE
MCHENV
RELATE
MCHENV
RELATE
MCHENV
Version
RELATE
MCINMG
Parent Type
RELATE
MCINMG
Parent Id
RELATE
MCINMG
Sequence Number
RELATE
MCINMG
Child Type
RELATE
MCINMG
Child Id
RELATE
MCINMG
Separator Id
RELATE
MCINMG
Date Created
RELATE
MCINMG
Time Created
RELATE
MCINMG
Created by
RELATE
MCINMG
Date Maintained
RELATE
MCINMG
Time Maintained
RELATE
MCINMG
Maintained by
RELATE
MCINMG
Change #
RELATE
MCINMG
QA Status
RELATE
MCINMG
RELATE
MCINMG
RELATE
MCINMG
RELATE
MCINMG
RELATE
MCINMG
Version
RELATE
MGPRXX
Parent Type
RELATE
MGPRXX
Migration Id
RELATE
MGPRXX
Sequence Number
RELATE
MGPRXX
Child Type
RELATE
MGPRXX
Child Id
RELATE
MGPRXX
Separator Id
RELATE
MGPRXX
Child Name
RELATE
MGPRXX
Located In
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
MGPRXX
Date Created
RELATE
MGPRXX
Time Created
RELATE
MGPRXX
Created by
RELATE
MGPRXX
Date Maintained
RELATE
MGPRXX
Time Maintained
RELATE
MGPRXX
Maintained by
RELATE
MGPRXX
Change #
RELATE
MGPRXX
QA Status
RELATE
MGPRXX
RELATE
MGPRXX
RELATE
MGPRXX
RELATE
MGPRXX
RELATE
MGPRXX
Version
RELATE
MIGXX
Parent Type
RELATE
MIGXX
Parent Id
RELATE
MIGXX
Sequence Number
RELATE
MIGXX
Child Type
RELATE
MIGXX
Child Id
RELATE
MIGXX
Migration Status
RELATE
MIGXX
Scope type
RELATE
MIGXX
Seed Status
RELATE
MIGXX
Has Reuse
RELATE
MIGXX
Date Created
RELATE
MIGXX
Time Created
RELATE
MIGXX
Created by
RELATE
MIGXX
Date Maintained
RELATE
MIGXX
Time Maintained
RELATE
MIGXX
Maintained by
RELATE
MIGXX
Change #
RELATE
MIGXX
QA Status
RELATE
MIGXX
RELATE
MIGXX
RELATE
MIGXX
RELATE
MIGXX
RELATE
MIGXX
Version
RELATE
ORGENT
Parent Type
RELATE
ORGENT
Organization Long Name
RELATE
ORGENT
Sequence Number
RELATE
ORGENT
Child Type
B-65
Table B-2
B-66
Object Type
System Name
Attribute Name
Significant?
RELATE
ORGENT
Entity Long Name
RELATE
ORGENT
Separator Id
RELATE
ORGENT
Create Flag
RELATE
ORGENT
Read Flag
RELATE
ORGENT
Update Flag
RELATE
ORGENT
Delete Flag
RELATE
ORGENT
Comments
RELATE
ORGENT
Date Created
RELATE
ORGENT
Time Created
RELATE
ORGENT
Created by
RELATE
ORGENT
Date Maintained
RELATE
ORGENT
Time Maintained
RELATE
ORGENT
Maintained by
RELATE
ORGENT
Change #
RELATE
ORGENT
QA Status
RELATE
ORGENT
RELATE
ORGENT
RELATE
ORGENT
RELATE
ORGENT
RELATE
ORGENT
Version
RELATE
ORGFUN
Parent Type
RELATE
ORGFUN
RELATE
ORGFUN
Sequence Number
RELATE
ORGFUN
Child Type
RELATE
ORGFUN

Name
RELATE
ORGFUN
Separator Id
RELATE
ORGFUN
Responsible for Function
RELATE
ORGFUN
Function
RELATE
ORGFUN
Function
RELATE
ORGFUN
Comments
RELATE
ORGFUN
Date Created
RELATE
ORGFUN
Time Created
RELATE
ORGFUN
Created by
RELATE
ORGFUN
Date Maintained
RELATE
ORGFUN
Time Maintained
RELATE
ORGFUN
Maintained by
RELATE
ORGFUN
Change #
RELATE
ORGFUN
QA Status
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
ORGFUN
RELATE
ORGFUN
RELATE
ORGFUN
RELATE
ORGFUN
RELATE
ORGFUN
Version
RELATE
ORGPRO
Parent Type
RELATE
ORGPRO
RELATE
ORGPRO
Sequence Number
RELATE
ORGPRO
Child Type
RELATE
ORGPRO

Name
RELATE
ORGPRO
Separator Id
RELATE
ORGPRO
Responsible for Function
RELATE
ORGPRO
Function
RELATE
ORGPRO
Function
RELATE
ORGPRO
Comments
RELATE
ORGPRO
Date Created
RELATE
ORGPRO
Time Created
RELATE
ORGPRO
Created by
RELATE
ORGPRO
Date Maintained
RELATE
ORGPRO
Time Maintained
RELATE
ORGPRO
Maintained by
RELATE
ORGPRO
Change #
RELATE
ORGPRO
QA Status
RELATE
ORGPRO
RELATE
ORGPRO
RELATE
ORGPRO
RELATE
ORGPRO
RELATE
ORGPRO
Version
RELATE
OWNSET
Type
RELATE
OWNSET
Long Name
RELATE
OWNSET
Sequence Number
RELATE
OWNSET
Child Type
RELATE
OWNSET
Set Long Name
RELATE
OWNSET
Separator Id
RELATE
OWNSET
Date Created
RELATE
OWNSET
Time Created
RELATE
OWNSET
Created by
B-67
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
OWNSET
Date Maintained
RELATE
OWNSET
Time Maintained
RELATE
OWNSET
Maintained by
RELATE
OWNSET
Change #
RELATE
OWNSET
QA Status
RELATE
OWNSET
RELATE
OWNSET
RELATE
OWNSET
RELATE
OWNSET
RELATE
OWNSET
Version
RELATE
PAHAPS
Parent Type
RELATE
PAHAPS
Parent Id
RELATE
PAHAPS
Sequence Number
RELATE
PAHAPS
Child Type
RELATE
PAHAPS
Child Id
RELATE
PAHAPS
Separator Id
RELATE
PAHAPS
Date Created
RELATE
PAHAPS
Time Created
RELATE
PAHAPS
Created by
RELATE
PAHAPS
Date Maintained
RELATE
PAHAPS
Time Maintained
RELATE
PAHAPS
Maintained by
RELATE
PAHAPS
Change #
RELATE
PAHAPS
QA Status
RELATE
PAHAPS
RELATE
PAHAPS
RELATE
PAHAPS
RELATE
PAHAPS
RELATE
PAHAPS
Version
RELATE
PRODEP
Parent Type
RELATE
PRODEP
Parent Id
RELATE
PRODEP
Sequence Number
RELATE
PRODEP
Child Type
RELATE
PRODEP
Child Id
RELATE
PRODEP
Separator Id
RELATE
PRODEP
Description
RELATE
PRODEP
Inclusive Flag
PRODEP
Exclusive/Or Sequence
number
RELATE
B-68
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
PRODEP
Date Created
RELATE
PRODEP
Time Created
RELATE
PRODEP
Created by
RELATE
PRODEP
Date Maintained
RELATE
PRODEP
Time Maintained
RELATE
PRODEP
Maintained by
RELATE
PRODEP
Change #
RELATE
PRODEP
QA Status
RELATE
PRODEP
RELATE
PRODEP
RELATE
PRODEP
RELATE
PRODEP
RELATE
PRODEP
Version
RELATE
PROENT
Parent Type
RELATE
PROENT

Name
RELATE
PROENT
Sequence Number
RELATE
PROENT
Child Type
RELATE
PROENT
Entity Long Name
RELATE
PROENT
Separator Id
RELATE
PROENT
Create Flag
RELATE
PROENT
Read Flag
RELATE
PROENT
Update Flag
RELATE
PROENT
Delete Flag
RELATE
PROENT
Comments
RELATE
PROENT
Date Created
RELATE
PROENT
Time Created
RELATE
PROENT
Created by
RELATE
PROENT
Date Maintained
RELATE
PROENT
Time Maintained
RELATE
PROENT
Maintained by
RELATE
PROENT
Change #
RELATE
PROENT
QA Status
RELATE
PROENT
RELATE
PROENT
RELATE
PROENT
RELATE
PROENT
RELATE
PROENT
Version
RELATE
PROLOC
Parent Type
B-69
Table B-2
B-70
Object Type
System Name
Attribute Name
Significant?
RELATE
PROLOC

Name
RELATE
PROLOC
Sequence Number
RELATE
PROLOC
Child Type
RELATE
PROLOC
Location Long Name
RELATE
PROLOC
Separator Id
RELATE
PROLOC
Function
RELATE
PROLOC
Function
RELATE
PROLOC
Comments
RELATE
PROLOC
Date Created
RELATE
PROLOC
Time Created
RELATE
PROLOC
Created by
RELATE
PROLOC
Date Maintained
RELATE
PROLOC
Time Maintained
RELATE
PROLOC
Maintained by
RELATE
PROLOC
Change #
RELATE
PROLOC
QA Status
RELATE
PROLOC
RELATE
PROLOC
RELATE
PROLOC
RELATE
PROLOC
RELATE
PROLOC
Version
RELATE
PROPRO
Parent Type
RELATE
PROPRO

Name
RELATE
PROPRO
Sequence Number
RELATE
PROPRO
Child Type
RELATE
PROPRO
Sub-Business Process Long

Name
RELATE
PROPRO
Separator Id
RELATE
PROPRO
Conditional Flag
RELATE
PROPRO
Date Created
RELATE
PROPRO
Time Created
RELATE
PROPRO
Created by
RELATE
PROPRO
Date Maintained
RELATE
PROPRO
Time Maintained
RELATE
PROPRO
Maintained by
RELATE
PROPRO
Change #
RELATE
PROPRO
QA Status
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
PROPRO
RELATE
PROPRO
RELATE
PROPRO
RELATE
PROPRO
RELATE
PROPRO
Version
RELATE
PRORUL
Parent Type
PRORUL

Name
RELATE
RELATE
PRORUL
Sequence Number
RELATE
PRORUL
Child Type
RELATE
PRORUL
Rule Long Name
RELATE
PRORUL
Separator Id
RELATE
PRORUL
Date Created
RELATE
PRORUL
Time Created
RELATE
PRORUL
Created by
RELATE
PRORUL
Date Maintained
RELATE
PRORUL
Time Maintained
RELATE
PRORUL
Maintained by
RELATE
PRORUL
Change #
RELATE
PRORUL
QA Status
RELATE
PRORUL
RELATE
PRORUL
RELATE
PRORUL
RELATE
PRORUL
RELATE
PRORUL
Version
RELATE
REPREP
Parent Type
RELATE
REPREP
Parent Long Name
RELATE
REPREP
Sequence Number
RELATE
REPREP
Child Type
RELATE
REPREP
Child Long Name
RELATE
REPREP
Separator Id
RELATE
REPREP
Source Version
RELATE
REPREP
Target Version
RELATE
REPREP
Direction
RELATE
REPREP
Logical Key
RELATE
REPREP
Date Created
RELATE
REPREP
Time Created
RELATE
REPREP
Created by
RELATE
REPREP
Date Maintained
B-71
Table B-2
B-72
Object Type
System Name
Attribute Name
Significant?
RELATE
REPREP
Time Maintained
RELATE
REPREP
Maintained by
RELATE
REPREP
Change #
RELATE
REPREP
QA Status
RELATE
REPREP
RELATE
REPREP
RELATE
REPREP
RELATE
REPREP
RELATE
REPREP
Version
RELATE
REPSEC
Parent Type
RELATE
REPSEC
Report Long Name
RELATE
REPSEC
Sequence Number
RELATE
REPSEC
Child Type
RELATE
REPSEC
Section Long Name
RELATE
REPSEC
Separator Id
RELATE
REPSEC
Type
RELATE
REPSEC
Break Sequence Number
RELATE
REPSEC
Page Placement
RELATE
REPSEC
Break Field
RELATE
REPSEC
Break Qualifier
RELATE
REPSEC
Left Margin
RELATE
REPSEC
Print Option
RELATE
REPSEC
Date Created
RELATE
REPSEC
Time Created
RELATE
REPSEC
Created by
RELATE
REPSEC
Date Maintained
RELATE
REPSEC
Time Maintained
RELATE
REPSEC
Maintained by
RELATE
REPSEC
Change #
RELATE
REPSEC
QA Status
RELATE
REPSEC
RELATE
REPSEC
RELATE
REPSEC
RELATE
REPSEC
RELATE
REPSEC
Version
RELATE
RLNRLN
Parent Type
RELATE
RLNRLN
RELATE
RLNRLN
Sequence Number
RELATE
RLNRLN
Child Type
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
RLNRLN
RELATE
RLNRLN
Separator Id
RELATE
RLNRLN
Chief Executive
RELATE
RLNRLN
Cardinality
RELATE
RLNRLN
Optionality
RELATE
RLNRLN
Dependant
RELATE
RLNRLN
Abstract
RELATE
RLNRLN
Role
RELATE
RLNRLN
Date Created
RELATE
RLNRLN
Time Created
RELATE
RLNRLN
Created by
RELATE
RLNRLN
Date Maintained
RELATE
RLNRLN
Time Maintained
RELATE
RLNRLN
Maintained by
RELATE
RLNRLN
Change #
RELATE
RLNRLN
QA Status
RELATE
RLNRLN
RELATE
RLNRLN
RELATE
RLNRLN
RELATE
RLNRLN
RELATE
RLNRLN
Version
RELATE
RPHAFM
Parent Type
RELATE
RPHAFM
Parent Long Name
RELATE
RPHAFM
Sequence Number
RELATE
RPHAFM
Child Type
RELATE
RPHAFM
Child Long Name
RELATE
RPHAFM
Separator Id
RELATE
RPHAFM
Date Created
RELATE
RPHAFM
Time Created
RELATE
RPHAFM
Created by
RELATE
RPHAFM
Date Maintained
RELATE
RPHAFM
Time Maintained
RELATE
RPHAFM
Maintained by
RELATE
RPHAFM
Change #
RELATE
RPHAFM
QA Status
RELATE
RPHAFM
RELATE
RPHAFM
RELATE
RPHAFM
RELATE
RPHAFM
RELATE
RPHAFM
Version
B-73
Table B-2
B-74
Object Type
System Name
Attribute Name
Significant?
RELATE
RPINXX
Parent Type
RELATE
RPINXX
Parent Id
RELATE
RPINXX
Sequence Number
RELATE
RPINXX
Child Type
RELATE
RPINXX
Child Id
RELATE
RPINXX
Migration Status
RELATE
RPINXX
Install Action
RELATE
RPINXX
Install Status
RELATE
RPINXX
Install for Platform
RELATE
RPINXX
Operating System
RELATE
RPINXX
Data Base Type
RELATE
RPINXX
Configuration Unit
RELATE
RPINXX
Row Selected
RELATE
RPINXX
Install Start Time Stamp
RELATE
RPINXX
install Stop Time Stamp
RELATE
RPINXX
Return Code
RELATE
RPINXX
Date Created
RELATE
RPINXX
Time Created
RELATE
RPINXX
Created by
RELATE
RPINXX
Date Maintained
RELATE
RPINXX
Time Maintained
RELATE
RPINXX
Maintained by
RELATE
RPINXX
Change #
RELATE
RPINXX
QA Status
RELATE
RPINXX
RELATE
RPINXX
RELATE
RPINXX
RELATE
RPINXX
RELATE
RPINXX
Version
RELATE
RPXX
Parent Type
RELATE
RPXX
Parent Id
RELATE
RPXX
Sequence Number
RELATE
RPXX
Child Type
RELATE
RPXX
Child Id
RELATE
RPXX
Migration Status
RELATE
RPXX
RELATE
RPXX
Scope type
RELATE
RPXX
Seed status
RELATE
RPXX
Has Reuse
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
RPXX
Is a Root Entity
RELATE
RPXX
Is a Refined Entity
RELATE
RPXX
Has Hierarchy Changed
RELATE
RPXX
Affected Entity (Not Analyzed)
RELATE
RPXX
Date Created
RELATE
RPXX
Time Created
RELATE
RPXX
Created by
RELATE
RPXX
Date Maintained
RELATE
RPXX
Time Maintained
RELATE
RPXX
Maintained by
RELATE
RPXX
Change #
RELATE
RPXX
QA Status
RELATE
RPXX
RELATE
RPXX
RELATE
RPXX
RELATE
RPXX
RELATE
RPXX
Version
RELATE
RULCOM
Parent Type
RELATE
RULCOM
Rule Long Name
RELATE
RULCOM
Sequence Number
RELATE
RULCOM
Child Type
RELATE
RULCOM
Component Long Name
RELATE
RULCOM
Separator Id
RELATE
RULCOM
Date Created
RELATE
RULCOM
Time Created
RELATE
RULCOM
Created by
RELATE
RULCOM
Date Maintained
RELATE
RULCOM
Time Maintained
RELATE
RULCOM
Maintained by
RELATE
RULCOM
Change #
RELATE
RULCOM
QA Status
RELATE
RULCOM
RELATE
RULCOM
RELATE
RULCOM
RELATE
RULCOM
RELATE
RULCOM
Version
RELATE
RULDEP
Parent Type
RELATE
RULDEP
Parent Id
RELATE
RULDEP
Sequence Number
B-75
Table B-2
B-76
Object Type
System Name
Attribute Name
Significant?
RELATE
RULDEP
Child Type
RELATE
RULDEP
Child Id
RELATE
RULDEP
Separator Id
RELATE
RULDEP
Description
RELATE
RULDEP
Inclusive Flag
RELATE
RULDEP
number
RELATE
RULDEP
Date Created
RELATE
RULDEP
Time Created
RELATE
RULDEP
Created by
RELATE
RULDEP
Date Maintained
RELATE
RULDEP
Time Maintained
RELATE
RULDEP
Maintained by
RELATE
RULDEP
Change #
RELATE
RULDEP
QA Status
RELATE
RULDEP
RELATE
RULDEP
RELATE
RULDEP
RELATE
RULDEP
RELATE
RULDEP
Version
RELATE
RULREP
Parent Type
RELATE
RULREP
Rule Long Name
RELATE
RULREP
Sequence Number
RELATE
RULREP
Child Type
RELATE
RULREP
Report Long Name
RELATE
RULREP
Separator Id
RELATE
RULREP
Date Created
RELATE
RULREP
Time Created
RELATE
RULREP
Created by
RELATE
RULREP
Date Maintained
RELATE
RULREP
Time Maintained
RELATE
RULREP
Maintained by
RELATE
RULREP
Change #
RELATE
RULREP
QA Status
RELATE
RULREP
RELATE
RULREP
RELATE
RULREP
RELATE
RULREP
RELATE
RULREP
Version
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
RULRUL
Parent Type
RELATE
RULRUL
Rule Long Name
RELATE
RULRUL
Sequence Number
RELATE
RULRUL
Child Type
RELATE
RULRUL
Sub-Rule Long Name
RELATE
RULRUL
Separator Id
RELATE
RULRUL
Date Created
RELATE
RULRUL
Time Created
RELATE
RULRUL
Created by
RELATE
RULRUL
Date Maintained
RELATE
RULRUL
Time Maintained
RELATE
RULRUL
Maintained by
RELATE
RULRUL
Change #
RELATE
RULRUL
QA Status
RELATE
RULRUL
RELATE
RULRUL
RELATE
RULRUL
RELATE
RULRUL
RELATE
RULRUL
Version
RELATE
RULWND
Parent Type
RELATE
RULWND
Rule Long Name
RELATE
RULWND
Sequence Number
RELATE
RULWND
Child Type
RELATE
RULWND
Window Long Name
RELATE
RULWND
Separator Id
RELATE
RULWND
Date Created
RELATE
RULWND
Time Created
RELATE
RULWND
Created by
RELATE
RULWND
Date Maintained
RELATE
RULWND
Time Maintained
RELATE
RULWND
Maintained by
RELATE
RULWND
Change #
RELATE
RULWND
QA Status
RELATE
RULWND
RELATE
RULWND
RELATE
RULWND
RELATE
RULWND
RELATE
RULWND
Version
RELATE
RUTREV
Parent Type
B-77
Table B-2
B-78
Object Type
System Name
Attribute Name
Significant?
RELATE
RUTREV
Rule Long Name
RELATE
RUTREV
Sequence Number
RELATE
RUTREV
Child Type
RELATE
RUTREV
Event Long Name
RELATE
RUTREV
Separator Id
RELATE
RUTREV
Rule Trigger Type
RELATE
RUTREV
Trigger Condition
RELATE
RUTREV
View Mapping
RELATE
RUTREV
Date Created
RELATE
RUTREV
Time Created
RELATE
RUTREV
Created by
RELATE
RUTREV
Date Maintained
RELATE
RUTREV
Time Maintained
RELATE
RUTREV
Maintained by
RELATE
RUTREV
Change #
RELATE
RUTREV
QA Status
RELATE
RUTREV
RELATE
RUTREV
RELATE
RUTREV
RELATE
RUTREV
RELATE
RUTREV
Version
RELATE
SAHASP
Parent Type
RELATE
SAHASP
Parent Id
RELATE
SAHASP
Sequence Number
RELATE
SAHASP
Child Type
RELATE
SAHASP
Child Id
RELATE
SAHASP
Separator Id
RELATE
SAHASP
Date Created
RELATE
SAHASP
Time Created
RELATE
SAHASP
Created by
RELATE
SAHASP
Date Maintained
RELATE
SAHASP
Time Maintained
RELATE
SAHASP
Maintained by
RELATE
SAHASP
Change #
RELATE
SAHASP
QA Status
RELATE
SAHASP
RELATE
SAHASP
RELATE
SAHASP
RELATE
SAHASP
RELATE
SAHASP
Version
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
SDSORD
Parent Type
RELATE
SDSORD
Parent Id
RELATE
SDSORD
Sequence Number
RELATE
SDSORD
Child Type
RELATE
SDSORD
Child Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Separator Id
RELATE
SDSORD
Date Created
RELATE
SDSORD
Time Created
RELATE
SDSORD
Created by
RELATE
SDSORD
Date Maintained
RELATE
SDSORD
Time Maintained
RELATE
SDSORD
Maintained by
RELATE
SDSORD
Change #
RELATE
SDSORD
QA Status
RELATE
SDSORD
RELATE
SDSORD
RELATE
SDSORD
RELATE
SDSORD
RELATE
SDSORD
Version
RELATE
SDSPCM
Parent Type
RELATE
SDSPCM
Parent Id
RELATE
SDSPCM
Sequence Number
RELATE
SDSPCM
Child Type
RELATE
SDSPCM
Child Id
RELATE
SDSPCM
Separator Id
RELATE
SDSPCM
Command to Invoke
B-79
Table B-2
B-80
Object Type
System Name
Attribute Name
Significant?
RELATE
SDSPCM
Date Created
RELATE
SDSPCM
Time Created
RELATE
SDSPCM
Created by
RELATE
SDSPCM
Date Maintained
RELATE
SDSPCM
Time Maintained
RELATE
SDSPCM
Maintained by
RELATE
SDSPCM
Change #
RELATE
SDSPCM
QA Status
RELATE
SDSPCM
RELATE
SDSPCM
RELATE
SDSPCM
RELATE
SDSPCM
RELATE
SDSPCM
Version
RELATE
SETVAL
Parent Type
RELATE
SETVAL
Set Long Name
RELATE
SETVAL
Sequence Number
RELATE
SETVAL
Child Type
RELATE
SETVAL
Value Long Name
RELATE
SETVAL
Separator Id
RELATE
SETVAL
Symbol
RELATE
SETVAL
Date Created
RELATE
SETVAL
Time Created
RELATE
SETVAL
Created by
RELATE
SETVAL
Date Maintained
RELATE
SETVAL
Time Maintained
RELATE
SETVAL
Maintained by
RELATE
SETVAL
Change #
RELATE
SETVAL
QA Status
RELATE
SETVAL
RELATE
SETVAL
RELATE
SETVAL
RELATE
SETVAL
RELATE
SETVAL
Version
RELATE
SPRQSP
Parent Type
RELATE
SPRQSP
Parent Id
RELATE
SPRQSP
Sequence Number
RELATE
SPRQSP
Child Type
RELATE
SPRQSP
Child Id
RELATE
SPRQSP
Separator Id
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
SPRQSP
Date Created
RELATE
SPRQSP
Time Created
RELATE
SPRQSP
Created by
RELATE
SPRQSP
Date Maintained
RELATE
SPRQSP
Time Maintained
RELATE
SPRQSP
Maintained by
RELATE
SPRQSP
Change #
RELATE
SPRQSP
QA Status
RELATE
SPRQSP
RELATE
SPRQSP
RELATE
SPRQSP
RELATE
SPRQSP
RELATE
SPRQSP
Version
RELATE
SRVRUL
Parent Type
RELATE
SRVRUL
Server Long Name
RELATE
SRVRUL
Sequence Number
RELATE
SRVRUL
Child Type
RELATE
SRVRUL
Rule Long Name
RELATE
SRVRUL
Separator Id
RELATE
SRVRUL
Entry Type
RELATE
SRVRUL
Object Name
RELATE
SRVRUL
Service Name
RELATE
SRVRUL
Date Created
RELATE
SRVRUL
Time Created
RELATE
SRVRUL
Created by
RELATE
SRVRUL
Date Maintained
RELATE
SRVRUL
Time Maintained
RELATE
SRVRUL
Maintained by
RELATE
SRVRUL
Change #
RELATE
SRVRUL
QA Status
RELATE
SRVRUL
RELATE
SRVRUL
RELATE
SRVRUL
RELATE
SRVRUL
RELATE
SRVRUL
Version
RELATE
STOENT
Parent Type
RELATE
STOENT
Data Store Long Name
RELATE
STOENT
Sequence Number
RELATE
STOENT
Child Type
B-81
Table B-2
B-82
Object Type
System Name
Attribute Name
Significant?
RELATE
STOENT
Entity Long Name
RELATE
STOENT
Separator Id
RELATE
STOENT
Comments
RELATE
STOENT
Date Created
RELATE
STOENT
Time Created
RELATE
STOENT
Created by
RELATE
STOENT
Date Maintained
RELATE
STOENT
Time Maintained
RELATE
STOENT
Maintained by
RELATE
STOENT
Change #
RELATE
STOENT
QA Status
RELATE
STOENT
RELATE
STOENT
RELATE
STOENT
RELATE
STOENT
RELATE
STOENT
Version
RELATE
SVDESV
Parent Type
RELATE
SVDESV
Table Long Name
RELATE
SVDESV
Sequence Number
RELATE
SVDESV
Child Type
RELATE
SVDESV
Table Long Name
RELATE
SVDESV
Separator Id
RELATE
SVDESV
Date Created
RELATE
SVDESV
Time Created
RELATE
SVDESV
Created by
RELATE
SVDESV
Date Maintained
RELATE
SVDESV
Time Maintained
RELATE
SVDESV
Maintained by
RELATE
SVDESV
Change #
RELATE
SVDESV
QA Status
RELATE
SVDESV
RELATE
SVDESV
RELATE
SVDESV
RELATE
SVDESV
RELATE
SVDESV
Version
RELATE
SYSFUN
Parent Type
RELATE
SYSFUN
Current System Long Name
RELATE
SYSFUN
Sequence Number
RELATE
SYSFUN
Child Type
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
SYSFUN

Name
RELATE
SYSFUN
Separator Id
RELATE
SYSFUN
Currently Supported
RELATE
SYSFUN
Planned Support
RELATE
SYSFUN
Comments
RELATE
SYSFUN
Date Created
RELATE
SYSFUN
Time Created
RELATE
SYSFUN
Created by
RELATE
SYSFUN
Date Maintained
RELATE
SYSFUN
Time Maintained
RELATE
SYSFUN
Maintained by
RELATE
SYSFUN
Change #
RELATE
SYSFUN
QA Status
RELATE
SYSFUN
RELATE
SYSFUN
RELATE
SYSFUN
RELATE
SYSFUN
RELATE
SYSFUN
Version
RELATE
SYSPRO
Parent Type
RELATE
SYSPRO
RELATE
SYSPRO
Sequence Number
RELATE
SYSPRO
Child Type
RELATE
SYSPRO

Name
RELATE
SYSPRO
Separator Id
RELATE
SYSPRO
Currently Supported
RELATE
SYSPRO
Planned Support
RELATE
SYSPRO
Comments
RELATE
SYSPRO
Date Created
RELATE
SYSPRO
Time Created
RELATE
SYSPRO
Created by
RELATE
SYSPRO
Date Maintained
RELATE
SYSPRO
Time Maintained
RELATE
SYSPRO
Maintained by
RELATE
SYSPRO
Change #
RELATE
SYSPRO
QA Status
RELATE
SYSPRO
RELATE
SYSPRO
RELATE
SYSPRO
B-83
Table B-2
B-84
Object Type
System Name
Attribute Name
Significant?
RELATE
SYSPRO
RELATE
SYSPRO
Version
RELATE
SYSSTO
Parent Type
RELATE
SYSSTO
RELATE
SYSSTO
Sequence Number
RELATE
SYSSTO
Child Type
RELATE
SYSSTO
Data Store Long Name
RELATE
SYSSTO
Separator Id
RELATE
SYSSTO
Create Flag
RELATE
SYSSTO
Read Flag
RELATE
SYSSTO
Update Flag
RELATE
SYSSTO
Delete Flag
RELATE
SYSSTO
Comments
RELATE
SYSSTO
Date Created
RELATE
SYSSTO
Time Created
RELATE
SYSSTO
Created by
RELATE
SYSSTO
Date Maintained
RELATE
SYSSTO
Time Maintained
RELATE
SYSSTO
Maintained by
RELATE
SYSSTO
Change #
RELATE
SYSSTO
QA Status
RELATE
SYSSTO
RELATE
SYSSTO
RELATE
SYSSTO
RELATE
SYSSTO
RELATE
SYSSTO
Version
RELATE
TBBOTB
Parent Type
RELATE
TBBOTB
Table Long Name
RELATE
TBBOTB
Sequence Number
RELATE
TBBOTB
Child Type
RELATE
TBBOTB
Table Long Name
RELATE
TBBOTB
Separator Id
RELATE
TBBOTB
Date Created
RELATE
TBBOTB
Time Created
RELATE
TBBOTB
Created by
RELATE
TBBOTB
Date Maintained
RELATE
TBBOTB
Time Maintained
RELATE
TBBOTB
Maintained by
RELATE
TBBOTB
Change #
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
TBBOTB
QA Status
RELATE
TBBOTB
RELATE
TBBOTB
RELATE
TBBOTB
RELATE
TBBOTB
RELATE
TBBOTB
Version
RELATE
TBHACO
Parent Type
RELATE
TBHACO
Table Long Name
RELATE
TBHACO
Sequence Number
RELATE
TBHACO
Child Type
RELATE
TBHACO
Column Long Name
RELATE
TBHACO
Separator Id
RELATE
TBHACO
Null
RELATE
TBHACO
Distinct
RELATE
TBHACO
Distinct Type
RELATE
TBHACO
Update Percentage
RELATE
TBHACO
Date Created
RELATE
TBHACO
Time Created
RELATE
TBHACO
Created by
RELATE
TBHACO
Date Maintained
RELATE
TBHACO
Time Maintained
RELATE
TBHACO
Maintained by
RELATE
TBHACO
Change #
RELATE
TBHACO
QA Status
RELATE
TBHACO
RELATE
TBHACO
RELATE
TBHACO
RELATE
TBHACO
RELATE
TBHACO
Version
RELATE
TBHAKY
Parent Type
RELATE
TBHAKY
Table Long Name
RELATE
TBHAKY
Sequence Number
RELATE
TBHAKY
Child Type
RELATE
TBHAKY
Key Long Name
RELATE
TBHAKY
Separator Id
RELATE
TBHAKY
Date Created
RELATE
TBHAKY
Time Created
RELATE
TBHAKY
Created by
RELATE
TBHAKY
Date Maintained
B-85
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
TBHAKY
Time Maintained
RELATE
TBHAKY
Maintained by
RELATE
TBHAKY
Change #
RELATE
TBHAKY
QA Status
RELATE
TBHAKY
RELATE
TBHAKY
RELATE
TBHAKY
RELATE
TBHAKY
RELATE
TBHAKY
Version
RELATE
TBRBKY
Parent Type
RELATE
TBRBKY
Table Long Name
RELATE
TBRBKY
Sequence Number
RELATE
TBRBKY
Child Type
RELATE
TBRBKY
Key Long Name
RELATE
TBRBKY
Separator Id
RELATE
TBRBKY
Referential Integrity
RELATE
TBRBKY
Date Created
RELATE
TBRBKY
Time Created
RELATE
TBRBKY
Created by
RELATE
TBRBKY
Date Maintained
RELATE
TBRBKY
Time Maintained
RELATE
TBRBKY
Maintained by
RELATE
TBRBKY
Change #
RELATE
TBRBKY
QA Status
RELATE
TBRBKY
RELATE
TBRBKY
RELATE
TBRBKY
RELATE
TBRBKY
RELATE
TBRBKY
Version
RELATE
TRIGGR
Parent Type
RELATE
TRIGGR
Parent Id
RELATE
TRIGGR
Sequence Number
RELATE
TRIGGR
Child Type
RELATE
TRIGGR
Child Id
RELATE
TRIGGR
Separator Id
RELATE
TRIGGR
Description
RELATE
TRIGGR
Inclusive Flag
TRIGGR
number
RELATE
B-86
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
TRIGGR
Date Created
RELATE
TRIGGR
Time Created
RELATE
TRIGGR
Created by
RELATE
TRIGGR
Date Maintained
RELATE
TRIGGR
Time Maintained
RELATE
TRIGGR
Maintained by
RELATE
TRIGGR
Change #
RELATE
TRIGGR
QA Status
RELATE
TRIGGR
RELATE
TRIGGR
RELATE
TRIGGR
RELATE
TRIGGR
RELATE
TRIGGR
Version
RELATE
USESVW
Type
RELATE
USESVW
Long Name
RELATE
USESVW
Sequence Number
RELATE
USESVW
Child Type
RELATE
USESVW
Child Id
RELATE
USESVW
Separator Id
RELATE
USESVW
Usage
RELATE
USESVW
Date Created
RELATE
USESVW
Time Created
RELATE
USESVW
Created by
RELATE
USESVW
Date Maintained
RELATE
USESVW
Time Maintained
RELATE
USESVW
Maintained by
RELATE
USESVW
Change #
RELATE
USESVW
QA Status
RELATE
USESVW
RELATE
USESVW
RELATE
USESVW
RELATE
USESVW
RELATE
USESVW
Version
RELATE
VUOWNS
Parent Type
RELATE
VUOWNS
View Long Name
RELATE
VUOWNS
Sequence Number
RELATE
VUOWNS
Type
RELATE
VUOWNS
Long Name
RELATE
VUOWNS
Separator Id
B-87
Table B-2
B-88
Object Type
System Name
Attribute Name
Significant?
RELATE
VUOWNS
Occurs Number of Times
RELATE
VUOWNS
Null Indicator for DB2
RELATE
VUOWNS
Date Created
RELATE
VUOWNS
Time Created
RELATE
VUOWNS
Created by
RELATE
VUOWNS
Date Maintained
RELATE
VUOWNS
Time Maintained
RELATE
VUOWNS
Maintained by
RELATE
VUOWNS
Change #
RELATE
VUOWNS
QA Status
RELATE
VUOWNS
RELATE
VUOWNS
RELATE
VUOWNS
RELATE
VUOWNS
RELATE
VUOWNS
Version
RELATE
WNCHLP
Parent Type
RELATE
WNCHLP
Instance
RELATE
WNCHLP
Sequence Number
RELATE
WNCHLP
Child Type
RELATE
WNCHLP
Instance
RELATE
WNCHLP
Separator Id
RELATE
WNCHLP
Date Created
RELATE
WNCHLP
Time Created
RELATE
WNCHLP
Created by
RELATE
WNCHLP
Date Maintained
RELATE
WNCHLP
Time Maintained
RELATE
WNCHLP
Maintained by
RELATE
WNCHLP
Change #
RELATE
WNCHLP
QA Status
RELATE
WNCHLP
RELATE
WNCHLP
RELATE
WNCHLP
RELATE
WNCHLP
RELATE
WNCHLP
Version
RELATE
WNCPNL
Parent Type
RELATE
WNCPNL
Instance
RELATE
WNCPNL
Sequence Number
RELATE
WNCPNL
Child Type
RELATE
WNCPNL
Instance
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
WNCPNL
Separator Id
RELATE
WNCPNL
Date Created
RELATE
WNCPNL
Time Created
RELATE
WNCPNL
Created by
RELATE
WNCPNL
Date Maintained
RELATE
WNCPNL
Time Maintained
RELATE
WNCPNL
Maintained by
RELATE
WNCPNL
Change #
RELATE
WNCPNL
QA Status
RELATE
WNCPNL
RELATE
WNCPNL
RELATE
WNCPNL
RELATE
WNCPNL
RELATE
WNCPNL
Version
RELATE
WNDWNC
Parent Type
RELATE
WNDWNC
Instance
RELATE
WNDWNC
Sequence Number
RELATE
WNDWNC
Child Type
RELATE
WNDWNC
Instance
RELATE
WNDWNC
Separator Id
RELATE
WNDWNC
Date Created
RELATE
WNDWNC
Time Created
RELATE
WNDWNC
Created by
RELATE
WNDWNC
Date Maintained
RELATE
WNDWNC
Time Maintained
RELATE
WNDWNC
Maintained by
RELATE
WNDWNC
Change #
RELATE
WNDWNC
QA Status
RELATE
WNDWNC
RELATE
WNDWNC
RELATE
WNDWNC
RELATE
WNDWNC
RELATE
WNDWNC
Version
RELATE
XXCMEV
Parent Type
RELATE
XXCMEV
Name
RELATE
XXCMEV
Sequence Number
RELATE
XXCMEV
Child Type
RELATE
XXCMEV
Event Name
RELATE
XXCMEV
Separator Id
B-89
Table B-2
B-90
Object Type
System Name
Attribute Name
Significant?
RELATE
XXCMEV
Date Created
RELATE
XXCMEV
Time Created
RELATE
XXCMEV
Created by
RELATE
XXCMEV
Date Maintained
RELATE
XXCMEV
Time Maintained
RELATE
XXCMEV
Maintained by
RELATE
XXCMEV
Change #
RELATE
XXCMEV
QA Status
RELATE
XXCMEV
RELATE
XXCMEV
RELATE
XXCMEV
RELATE
XXCMEV
RELATE
XXCMEV
Version
RELATE
XXCMLP
Parent Type
RELATE
XXCMLP
Name
RELATE
XXCMLP
Sequence Number
RELATE
XXCMLP
Child Type
RELATE
XXCMLP
RELATE
XXCMLP
Separator Id
RELATE
XXCMLP
Date Created
RELATE
XXCMLP
Time Created
RELATE
XXCMLP
Created by
RELATE
XXCMLP
Date Maintained
RELATE
XXCMLP
Time Maintained
RELATE
XXCMLP
Maintained by
RELATE
XXCMLP
Change #
RELATE
XXCMLP
QA Status
RELATE
XXCMLP
RELATE
XXCMLP
RELATE
XXCMLP
RELATE
XXCMLP
RELATE
XXCMLP
Version
RELATE
XXCTSY
Parent Type
RELATE
XXCTSY
Parent Long Name
RELATE
XXCTSY
Sequence Number
RELATE
XXCTSY
Child Type
RELATE
XXCTSY
Child Long Name
RELATE
XXCTSY
Separator Id
RELATE
XXCTSY
Date Created
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
XXCTSY
Time Created
RELATE
XXCTSY
Created by
RELATE
XXCTSY
Date Maintained
RELATE
XXCTSY
Time Maintained
RELATE
XXCTSY
Maintained by
RELATE
XXCTSY
Change #
RELATE
XXCTSY
QA Status
RELATE
XXCTSY
RELATE
XXCTSY
RELATE
XXCTSY
RELATE
XXCTSY
RELATE
XXCTSY
Version
RELATE
XXCTXX
Parent Type
RELATE
XXCTXX
Parent Long Name
RELATE
XXCTXX
Sequence Number
RELATE
XXCTXX
Child Type
RELATE
XXCTXX
Child Long Name
RELATE
XXCTXX
Separator Id
RELATE
XXCTXX
Date Created
RELATE
XXCTXX
Time Created
RELATE
XXCTXX
Created by
RELATE
XXCTXX
Date Maintained
RELATE
XXCTXX
Time Maintained
RELATE
XXCTXX
Maintained by
RELATE
XXCTXX
Change #
RELATE
XXCTXX
QA Status
RELATE
XXCTXX
RELATE
XXCTXX
RELATE
XXCTXX
RELATE
XXCTXX
RELATE
XXCTXX
Version
RELATE
XXDPLP
Parent Type
RELATE
XXDPLP
Name
RELATE
XXDPLP
Sequence Number
RELATE
XXDPLP
Child Type
RELATE
XXDPLP
RELATE
XXDPLP
Separator Id
RELATE
XXDPLP
Description
RELATE
XXDPLP
Date Created
B-91
Table B-2
B-92
Object Type
System Name
Attribute Name
Significant?
RELATE
XXDPLP
Time Created
RELATE
XXDPLP
Created by
RELATE
XXDPLP
Date Maintained
RELATE
XXDPLP
Time Maintained
RELATE
XXDPLP
Maintained by
RELATE
XXDPLP
Change #
RELATE
XXDPLP
QA Status
RELATE
XXDPLP
RELATE
XXDPLP
RELATE
XXDPLP
RELATE
XXDPLP
RELATE
XXDPLP
Version
RELATE
XXHABM
Parent Type
RELATE
XXHABM
Parent Long Name
RELATE
XXHABM
Sequence Number
RELATE
XXHABM
Child Type
RELATE
XXHABM
Child Long Name
RELATE
XXHABM
Separator Id
RELATE
XXHABM
Date Created
RELATE
XXHABM
Time Created
RELATE
XXHABM
Created by
RELATE
XXHABM
Date Maintained
RELATE
XXHABM
Time Maintained
RELATE
XXHABM
Maintained by
RELATE
XXHABM
Change #
RELATE
XXHABM
QA Status
RELATE
XXHABM
RELATE
XXHABM
RELATE
XXHABM
RELATE
XXHABM
RELATE
XXHABM
Version
RELATE
XXHAHT
Parent Type
RELATE
XXHAHT
Parent Long Name
RELATE
XXHAHT
Sequence Number
RELATE
XXHAHT
Child Type
RELATE
XXHAHT
Child Long Name
RELATE
XXHAHT
Separator Id
RELATE
XXHAHT
Date Created
RELATE
XXHAHT
Time Created
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
XXHAHT
Created by
RELATE
XXHAHT
Date Maintained
RELATE
XXHAHT
Time Maintained
RELATE
XXHAHT
Maintained by
RELATE
XXHAHT
Change #
RELATE
XXHAHT
QA Status
RELATE
XXHAHT
RELATE
XXHAHT
RELATE
XXHAHT
RELATE
XXHAHT
RELATE
XXHAHT
Version
RELATE
XXHSST
Parent Type
RELATE
XXHSST
Name
RELATE
XXHSST
Sequence Number
RELATE
XXHSST
Child Type
RELATE
XXHSST
State Name
RELATE
XXHSST
Separator Id
RELATE
XXHSST
Date Created
RELATE
XXHSST
Time Created
RELATE
XXHSST
Created by
RELATE
XXHSST
Date Maintained
RELATE
XXHSST
Time Maintained
RELATE
XXHSST
Maintained by
RELATE
XXHSST
Change #
RELATE
XXHSST
QA Status
RELATE
XXHSST
RELATE
XXHSST
RELATE
XXHSST
RELATE
XXHSST
RELATE
XXHSST
Version
RELATE
XXITEV
Parent Type
RELATE
XXITEV
Name
RELATE
XXITEV
Sequence Number
RELATE
XXITEV
Child Type
RELATE
XXITEV
Event Name
RELATE
XXITEV
Separator Id
RELATE
XXITEV
Description
RELATE
XXITEV
Date Created
RELATE
XXITEV
Time Created
B-93
Table B-2
B-94
Object Type
System Name
Attribute Name
Significant?
RELATE
XXITEV
Created by
RELATE
XXITEV
Date Maintained
RELATE
XXITEV
Time Maintained
RELATE
XXITEV
Maintained by
RELATE
XXITEV
Change #
RELATE
XXITEV
QA Status
RELATE
XXITEV
RELATE
XXITEV
RELATE
XXITEV
RELATE
XXITEV
RELATE
XXITEV
Version
RELATE
XXPCST
Parent Type
RELATE
XXPCST
Name
RELATE
XXPCST
Sequence Number
RELATE
XXPCST
Child Type
RELATE
XXPCST
State Name
RELATE
XXPCST
Separator Id
RELATE
XXPCST
Description
RELATE
XXPCST
Date Created
RELATE
XXPCST
Time Created
RELATE
XXPCST
Created by
RELATE
XXPCST
Date Maintained
RELATE
XXPCST
Time Maintained
RELATE
XXPCST
Maintained by
RELATE
XXPCST
Change #
RELATE
XXPCST
QA Status
RELATE
XXPCST
RELATE
XXPCST
RELATE
XXPCST
RELATE
XXPCST
RELATE
XXPCST
Version
RELATE
XXPRGP
Parent Type
RELATE
XXPRGP
Rule Long Name
RELATE
XXPRGP
Sequence Number
RELATE
XXPRGP
Child Type
RELATE
XXPRGP
Sub-Rule Long Name
RELATE
XXPRGP
Separator Id
RELATE
XXPRGP
Profile Type
RELATE
XXPRGP
Date Created
Table B-2
Object Type
System Name
Attribute Name
Significant?
RELATE
XXPRGP
Time Created
RELATE
XXPRGP
Created by
RELATE
XXPRGP
Date Maintained
RELATE
XXPRGP
Time Maintained
RELATE
XXPRGP
Maintained by
RELATE
XXPRGP
Change #
RELATE
XXPRGP
QA Status
RELATE
XXPRGP
RELATE
XXPRGP
RELATE
XXPRGP
RELATE
XXPRGP
RELATE
XXPRGP
Version
RELATE
XXRIST
Parent Type
RELATE
XXRIST
Event Context Long Name
RELATE
XXRIST
Sequence Number
RELATE
XXRIST
Child Type
RELATE
XXRIST
State Long Name
RELATE
XXRIST
Separator Id
RELATE
XXRIST
Description
RELATE
XXRIST
Date Created
RELATE
XXRIST
Time Created
RELATE
XXRIST
Created by
RELATE
XXRIST
Date Maintained
RELATE
XXRIST
Time Maintained
RELATE
XXRIST
Maintained by
RELATE
XXRIST
Change #
RELATE
XXRIST
QA Status
RELATE
XXRIST
RELATE
XXRIST
RELATE
XXRIST
RELATE
XXRIST
RELATE
XXRIST
Version
RELATE
XXTRLP
Parent Type
RELATE
XXTRLP
Name
RELATE
XXTRLP
Sequence Number
RELATE
XXTRLP
Child Type
RELATE
XXTRLP
RELATE
XXTRLP
Separator Id
RELATE
XXTRLP
Description
B-95
Table B-2
B-96
Object Type
System Name
Attribute Name
Significant?
RELATE
XXTRLP
Date Created
RELATE
XXTRLP
Time Created
RELATE
XXTRLP
Created by
RELATE
XXTRLP
Date Maintained
RELATE
XXTRLP
Time Maintained
RELATE
XXTRLP
Maintained by
RELATE
XXTRLP
Change #
RELATE
XXTRLP
QA Status
RELATE
XXTRLP
RELATE
XXTRLP
RELATE
XXTRLP
RELATE
XXTRLP
RELATE
XXTRLP
Version
RELATE
XXUSLA
Parent Type
RELATE
XXUSLA
Parent Long Name
RELATE
XXUSLA
Sequence Number
RELATE
XXUSLA
Child Entity Type
RELATE
XXUSLA
Child Long Name
RELATE
XXUSLA
Separator Id
RELATE
XXUSLA
Short Value
RELATE
XXUSLA
Long Value
RELATE
XXUSLA
Date Created
RELATE
XXUSLA
Time Created
RELATE
XXUSLA
Created by
RELATE
XXUSLA
Date Maintained
RELATE
XXUSLA
Time Maintained
RELATE
XXUSLA
Maintained by
RELATE
XXUSLA
Change #
RELATE
XXUSLA
QA Status
RELATE
XXUSLA
RELATE
XXUSLA
RELATE
XXUSLA
RELATE
XXUSLA
RELATE
XXUSLA
Version
CHAPTER
FILE ALLOCATIONS DURING

REBUILD PROCESSING
This appendix contains information on file allocation activities that occur during the Rebuild Analyze
and Rebuild Prepare phases of a mainframe rebuild.
The Rebuild Analyze Method

The Rebuild Analyze Method creates a file (ddname=INSTFILE) that contains information on the data
sets required by the Rebuild prepare and install methods. The rows in the INSTFILE contain default file
allocation information to be used during the file(s) allocation. For example, a row from the INSTFILE
for the CICS LOAD library reads:
LOADCI HPSOUT.FF1.AAN6FF.LOADCI +
15 5 TRK PO U 0 23200 NEWFREE 4 CATALOG
The following sections describe file allocation conditions and parameters:
File Allocation Conditions
Rebuild Analyzer and Prepare Allocation Parameters
File Allocation Conditions

Conditions causing a particular file to allocate are listed in Table 3-1.
The information used for each file allocation controlled by the INSTFILE is obtained from the
algorithm below in conjunction with the @HPSENV INI file.
@HPSENV INI file - Contains default information used during each files allocation. An example
row containing default information for the CICS LOAD library is shown below:
FILE_6= 1 TRK PO U
0 23200 NEWFREE CATALOG HPSRT LOADCI LOADCI
The primary and secondary space allocations and directory block values are calculated by the
following algorithm:
/* calculate file size */
avg_size = atoi(avg_char);
prim_size = avg_size*count*4/5+1;
C-1
scnd_size = avg_size*count/4+1;
drct_blks = count/6+1;
avg_size = Number after @SEERENV INI file, (INSTALL) section FILE_xx= variable
ie., if FILE_6=1..... then AVG_SIZE=1.
count = Total Install ACTION count for dataset resulting from Rebuild Action for most datasets.
Total ENTITY Count for the Rebuild for the following ddnames (SVLNCDSN, SVLNBDSN,
SVLNIDSN, HMFNCTLB). The total entity count is derived by using the condition column of the
matrix in Table 3-1:
Table 3-1
Allocation Matrix
Conditions Causing Allocate

Unconitionally allocated
DBRM pds
Unconditionally allocated
Loadbs
Unconditionally Allocated
NCALBS
PREPARE.SVRULESRC = Y
PREPARE.SVRULDSN - Generated RULE source
PREPARE.SVCOBSRC = Y
PREPARE.SVCOBDSN - Generated COBOL source
PRODUCT.ENDEVOR = y
PREPARE.SVCPTDSN - Saved copybook control

information
Bind Plan
PREPARE.SVBNDDSN- Saved DB2 Bind control cards
Grant for Plan Bind
PREPARE.SVGRTDSN - Saved DB2 Grant control cards
Plan Bind - PRODUCT.ENDEVOR=y
PREPARE.SVBNTDSN - Saved DB2 Bind control cards in

textual format
Package Bind
PREPARE.SVBPKDSN - Saved DB2 Bind Package control

cards
Package Bind
PREPARE.SVGPKDSN - Saved DB2 Grant Package

control cards
If >=1 Rule, components, windows, sets, and reports
PREPARE.SVLNCDSN - Saved CICS Link Control cards
PREPARE.SVLNBDSN - Saved BATCH Link Control cards

and PRODUCT.IMS = y
PREPARE.SVLNIDSN - Saved IMS Link Control cards
HMFNCTLB - Saved NCAL Link edit control cards

and PREPARE.SVLNKLST=Y
SVLKTDSN - Saved link control cards list
If IMS entities were marked for

Install as part of the REBUILD.
SVLU2DSN - Saved LU2 control cards

LOADIM - IMS Load library
If CICS entities were marked for Install as part of the

REBUILD. MRO is supported , A dataset will be
created for each region.
C-2
Dataset Allocated
SVLU2DSN - Saved CICS LU2 control cards
If CICS entities were marked for Install as part of the

REBUILD. MRO is supported , A dataset will be
created for each region.
LOADCI - CICS Load library
If Rebuild contains Components and the

PREPARE.SVCMPSRC=Y
SVCMPDSN - - Saved extracted component source
If Rebuild contains Components and the

PREPARE.SVCMVSRC=Y
SVCMVDSN - Saved extracted component view source
If Rebuild contains SETS and the

PREPARE.SVSETSRC=Y
SVSETDSN - Saved generated set source
File Allocations during Rebuild Processing
Table 3-1
Allocation Matrix (Continued)
Dataset Allocated
If Rebuild contains Sets and the

PREPARE.SVSTBSRC=Y for COBOL copybooks
SVSTBDSN - Saved extracted set cobol copylib

PREPARE.SVSTCSRC=Y for C copybooks
SVSTCDSN - Saved extracted set C copylib

PREPARE.SVSTPSRC=Y for PL/I copybooks
SVSTPDSN - Saved extracted set PL/l copylib

PREPARE.SVSTRCPY=Y for Set Reference
members
SVSTRDSN - Saved extracted set reference file

PREPARE.SVSTECPY=Y for Set error files
SVERRDSN Saved the generated set errors
If Rebuild contains Window source and the

PREPARE.SVWNDSRC=Y
SVWNDDSN - Saved window source
If Rebuild contains HELP source for windows and

the PREPARE.SVHLPSRC=Y
SVHLPDSN - Saved window help source
If Rebuild contains FILE and the

PREPARE.SVFLEPL1=Y for PLI files
SVFLPDSN - Saved extracted file prepare for PL1

PREPARE.SVFLECOB=Y for COBOL files
SVFLBDSN - Saved extracted file prepare for COBOL

PREPARE.SVFLEC=Y
for C files
SVFLCDSN - Saved extracted file prepare for C
If >=1 Rule, components and reports and If Rebuild

contains component generated BIND File and the
PREPARE.SVBNDX=Y
SVBNXDSN - Saved generated bind file in PDS
If >=1 Rule and components and If Rebuild contains

component generated COBOL VIEW and the
PREPARE.SVVBSRC=Y
SVVCBDSN - Saved extracted view prepare for cobol

component generated COBOL VIEW aligned and
the PREPARE.SVVBASRC=Y
SVVCADSN - Saved extracted view prepare for cobol

aligned

component generated PL/I VIEW and the
PREPARE.SVVPSRC=Y
SVVPLDSN - Saved extracted view prepare for PL/I

component generated PL/I VIEW aligned and the
PREPARE.SVVPASRC=Y
SVVPADSN - Saved extracted view prepare for PL/I

aligned

component generated ASM VIEW and the
PREPARE.SVVASRC=Y
SVVASDSN - Saved extracted view prepare for ASM

component generated ASM VIEW aligned and the
PREPARE.SVVAASRC=Y
SVVAADSN - Saved extracted view prepare for ASM

aligned

component generated C VIEW and the
PREPARE.SVVCSRC=Y
SVVCDSN - Saved extracted view prepare for C

component generated C VIEW aligned and the
PREPARE.SVVCASRC=Y
SVVCADSN - Saved extracted view prepare for C aligned
C-3
Table 3-1
Allocation Matrix (Continued)
Dataset Allocated
If Rebuild contains Sets for COBOL
STCOBDSN - Set library for Cobol
If Rebuild contains Sets for Reference files
STREFDSN - Set library for reference files
If Rebuild contains Sets for PL/I
STPL1DSN - Set library for PL1
If Rebuild contains Sets for C
STCDSN - Set library for C
The E_HPSFILE DB2 table is not used for the allocation of any of the data sets in matrix 1.
Rebuild Analyzer and Prepare Allocation Parameters

The data sets in Matrix 2 are allocated using parameters supplied by the DB2 table E_HPSFILE in the
Rebuild analyzer and prepare methods. These files are allocated by using SVC99 calls.
Table 3-2
C-4
Matrix 2
DDNAME of File
Contents
RBDPRES
Rebuild Prepare Results File
RBDIPARM
Rebuild Install Parms File
RBDIRES
RBD Install Driver Res File
RBDPPARM
Rebuild Prepare Parms File
RBDISRES
RBD Install Stat Link Res File
RBDIPRES
RBD Install Copy PDS Res File
RBDIVRES
RBD Install Copy VSAM Res File
RBDITRES
RBD Install Top Bind Res File
RBDILRES
RBD Install LU2 Res File
RBDIIRES
RBD Install Intr Bind Res File
RBDIGRES
RBD Install Pkg Bind Res File
RBDICLU2
RBD Install CICS LU2 Error
RBDIILU2
RBD Install IMS LU2 Error
RBDIILUR
RBD Install IMS LU2 Retcode
RBDICLUR
RBD Install CICS LU2 Retcode
RBDPDTL
Rebuild Prepare Detail File
RBDPCNT
Rebuild Prepare Count Detail File
RBDICNT
Rebuild Install Count Report
RBDIDTL
Rebuild Install Detail Report
File Allocations during Rebuild Processing
Index
INDEX
A
actions
add
entity 2-3 to 2-6, 4-1, 4-3, 4-6
keywords to entity 2-6, 4-2, 4-6
relation 2-7, 2-11 to 2-12, 4-1, 4-8
text
to entity 2-6, 4-3, 4-8
to relation 2-10, 4-3, 4-9
analyze rebuild impact 1-6, 2-13 to 2-18, 4-3, 4-10 to
4-12
autosave 4-1
browse entity 4-2
browse entity text 4-2
browse keywords 4-2
browse relation 4-2
change
project 4-2
change owner of entity 4-2
clean-up rebuild info 4-2, 4-12
define user
entity method 4-3
relation method 4-3
delete
entity 2-7
relation 2-11, 2-13, 4-2
delete entity 4-2
delete relation 4-13
display entities 4-2
export rebuild package 4-13 to 4-14
extended where-used report 4-2
install rebuild package 4-3, 4-14
list
entities 2-7, 4-2
entity actions 4-1
rebuild contents 2-15, 2-20, 2-23, 4-2, 4-16,
4-16 to 4-20, 4-23, 4-27
relations 2-11, 2-13, 2-15, 4-2, 4-20 to 4-21
lock entity 4-2
maintain
entity 2-7, 4-2, 4-22
relation 2-10, 4-2, 4-22

prepare rebuild object 4-3, 4-23
rebuild
install 2-21 to 2-23, 4-14 to 4-16
prepare 2-18 to 2-21
report 2-23
refresh screen 4-3
reset object
install status 4-3, 4-24
prepare status 4-3, 4-25
save as 4-3
search keywords 4-3, 4-6
set rebuild install status 4-26
super prepare 4-3, 4-26
unlock entity 4-3
update
user profile 4-3
update debug profile 4-2
view results 2-15, 2-20, 2-23, 4-3, 4-16, 4-23, 4-27,
4-27 to 4-28
ACTIONS (list entity actions) action 4-1
ADDE (add entity) action 2-3 to 2-6, 4-1, 4-3, 4-6
ADDR (add relation) action 2-7, 2-11 to 2-12, 4-1, 4-8
advice file 2-18, 4-10, 4-14
analyze rebuild impact
advice file 4-10
attributes
audit 1-4
naming 1-4
rebuild package state 1-4, 2-15
system-generated
audit 4-5
rebuild state 4-5
user-defined attributes
name 4-4
AUTOSAVE action 4-1
B
BE (browse entity) action 4-2
BK (browse keywords) action 4-2
BR (browse relation) action 4-2
BTXE (browse entity text) action 4-2
C
CLEANUP (rebuild info) action 4-2, 4-12
CO (change owner) action 4-2
filtering ?? to 4-20
relations 4-20 to 4-21
LISTRBD (list rebuild contents) action 2-15, 2-20, 2-23,
4-2, 4-16, 4-23, 4-27
using filters ?? to 4-20
LOCK (entity) action 4-2
LR (list relations) action 2-11, 2-13, 2-15, 4-2
D
DE (delete entity) action 2-7, 4-2
DEBUG (update profile) action 4-2
description attribute 4-4
DR (delete relation) action 2-11, 2-13, 4-2, 4-13
ME (maintain entity) action 2-7, 4-2, 4-22

MR (maintain relation) action 2-10, 4-2, 4-22
naming attributes 4-4
enterprise repository, accessing 2-1

entity
rebuilding packages 1-3
ENTITY (display) action 4-2
entity type
definition 1-2
environment control variables 5-1
EW (extended where-used) action 4-2
exception
definition 1-2
exception processing 1-1
EXPORT (rebuild package) action 4-13 to 4-14
advice file 4-14
F
filters for rebuild contents ?? to 4-20
H
has-root relationship 1-5
I
ISPF Primary Options menu 2-1
K
K (keywords) action 2-6, 4-2, 4-6
L
LE (list entities) action 2-7, 4-2
leaf process
definition 1-2
list
entity actions 4-1
rebuild contents 4-16 to 4-20
ii
O
object
definition 1-2
object attribute
definition 1-2
object part
definition 1-2
P
prepare process
sequence 1-6
prepare scope
definition 1-2
in object analysis for rebuild 1-5
PROJECTS (change) action 4-2
R
RANALYZE (analyze rebuild impact) action 1-6, 2-13 to
2-18, 4-3, 4-10 to 4-12
advice file 2-18
options 4-11
rebuild
analyze options 4-11
entity
attributes
description 4-4
user-defined values 4-4
relation attributes 4-7
audit 4-8
Has-Root-Entity Name 4-7
rebuild name 4-7
system-generated 4-8
entity attributes
audit 4-5
job status 4-8
rebuild state 4-5

relation 4-8
system ID 4-5
system-generated 4-4
user-defined values 4-7
package
state attribute 2-15
state values 4-22
package entity attributes 1-4
packaged entity functions 1-4
staging libraries in prepare 1-6
state attribute 4-5
status values 4-22
steps 1-3
Rebuild Analyze C-1
rebuild package
definition 1-3
rebuild package entity
definition 1-2
rebuild processing
definition 1-1
REFRESH (screen) action 4-3
relationship type
definition 1-3
REP (rebuild report) action 2-23
RES (view results) action 2-15, 2-20, 2-23, 4-3, 4-16,
4-23, 4-27, 4-27 to 4-28
RESETINS (reset object install status) action 4-3, 4-24
RESETPR (reset object prepare status) action 4-3, 4-25
RINSTALL (install rebuild package) action 2-21 to 2-23,
4-3, 4-14 to 4-16
root entity
definition 1-3
RPREPARE (prepare rebuild object) action 2-18 to 2-21,
4-3, 4-23
RSTATUS action 4-26
TXE (add entity text) action 2-6, 4-3

TXE (add text) action 4-8
TXR (add relation text) action 2-10, 4-3, 4-9
U
UEMTH (define user entity method) action 4-3
UNLOCK (entity) action 4-3
UPROF (update user profile) action 4-3
URMTH (define user relation method) action 4-3
V
view results action 4-3, 4-27 to 4-28
S
SA (save as) action 4-3
seed
definition 1-3
select objects for rebuild 2-7
SRCH (search keywords) action 4-3, 4-6
status values 4-22
SUPERPR (super prepare) action 4-3, 4-26
system-generated attributes 4-5
rebuild state 4-5
relation 4-8
T
testing
requirements 1-6
Index
iii

App Builder Enterprise Rebuild

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

App Builder Enterprise Rebuild

Uploaded by

Copyright:

Available Formats

BluePhoenix AppBuilder 2.0.3.

Enterprise Rebuild Guide

BluePhoenix AppBuilder 2.0.3.1

1992-2002 BluePhoenix Solutions

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

1 Understanding Rebuild Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Before You Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3 Using Rebuild Analyze and Prepare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Managing Concurrent Rebuilds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

4 Rebuild Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

5 Setting Up The Rebuild Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

B Rebuild Processing Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

C File Allocations during Rebuild Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Understanding Rebuild Package Components

Understanding Rebuild Package Components

Rebuild Processing Terms

Understanding Rebuild Processing

Only one person can rebuild a specific rebuild package at a time.

One or more repository administrators perform the following functions:

Rebuilding Package Entities

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Rebuilding Package Entities

Creating the Rebuild Package

Rebuild Package Attribute Types

Understanding Rebuild Processing

Rebuilding Package Entities

Selecting Objects for Rebuild Processing

Rebuild Package Entity has-root Function

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Rebuilding Package Entities

Analyzing the Rebuild Package

Identifying Objects for Preparation

Preparing Objects in the Rebuild Package

Installing the Application

Understanding Rebuild Processing

Preparing OpenCOBOL Rebuilds

Preparing OpenCOBOL Rebuilds

Static Linking of Rules

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Preparing OpenCOBOL Rebuilds

Understanding Rebuild Processing

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Before You Rebuild

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Before You Rebuild

ISPF/PDF Primary Option menu

System Options menu

The number of options available depends on which options are installed.

Step 1 - Create the Rebuild Package

Host Workbench panel

Command ===> _______________________________________________________________

Step 1 - Create the Rebuild Package

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Step 1 - Create the Rebuild Package

Creating the rebuild package entity

Step 1 - Create the Rebuild Package

Naming the rebuild package entity

Rebuild Package State . . . :

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Step 1 - Create the Rebuild Package

* TOP OF DATA **