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 Description 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. 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. 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. Attribute type Naming
State Audit
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. 2. Following your site procedure, log on to the Time Sharing Option (TSO) system. 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
ISPF/PDF Primary Option menu
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.
System Options menu
Figure 2-2
Note
The number of options available depends on which options are installed.
2-2
Rebuilding Applications
Step 1 - Create the Rebuild Package
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
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.
4.
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. 2. 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. 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 V: 2 Project: DEV Level: 1
Repository: SUNRISE Action ________ ________ ________ ADDE____ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
Entity Organization Physical Event Process Rebuild Package Relationship Report Rule Section Server Set State Symbol Table Transition Value View Window
3.
On the blank Add an Entity detail panel, type the name and, optionally, the description of the entity (Figure 2-5).
2-4
Figure 2-5
Naming the rebuild package entity Add an Entity V: 2 Project: DEV
More:
Repository: SUNRISE Rebuild Package Name . . . . System Id . . Description .
Level: 2
Attributes: . . . . . . . . DMC_VER2_RBD__________________ . . . . . . . : . . . . . . . . To rebuild migrated DMC App_l 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 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 Rebuild Rebuild Rebuild N/A Rebuild Rebuild Rebuild Rebuild Install Submitted Install Failed Install Successful Install Prepare Analyze Install Incomplete Incomplete Executing Executing
Rebuild Package State . . . :
Audit Attributes: Date Created . Time Created . Created by . . Date Maintained Time Maintained Maintained by .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
: : : : : :
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 More +
Repository: SUNRISE
V: 2
Project: DEV
Level: 2
Rebuild Package Attributes: Name . . . . . . . . . . System Id . . . . . . . . Description . . . . . . . Rebuild Package State . .
. . . .
. : . :
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
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.
5.
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
6. 7.
Press F3 to save the text and return to the Maintain an Entity panel. 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.
2-6
Step 2 - Select Objects for Rebuild Processing
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. 9.
Press F3 to return to the Maintain an Entity panel. 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. 2. Record the name of each root entity that you want to add to the rebuild package. 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 V: 2 Project: DEV
Repository: SUNRISE Level: 1 Action ________ ________ ________ LE______ ________ ________ ________ ________ ________ ________ ________ ________
Entity Organization Physical Event Process Rebuild Package Relationship Report Rule Section Server Set State Symbol
3.
Type ADDR on the action line of your rebuild package entity (Figure 2-10) and press Enter.
Creating the relation from the rebuild entity Host List Facility for Entity Rebuild Package V: 2 Project: DEV
Figure 2-10
Repository: SUNRISE Level: 2
Action Name ________ AWT_VER1_RBD
System Id AA46NR
4.
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.
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
2-8
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. Naming the rebuild package Add a Relation Repository: SUNRISE V: 2 Project: DEV More: + Level: 4
Figure 2-12
Rebuild Package Name . . . . . . . . . . . . DMC_VER2_RBD__________________ Has-Root Function Name . . . . . . . . . . . . DMC_VER2_FUNC1________________ Relationship Attributes: Application Configuration . . PROJECT_DMC___________________ Is a Root Entity . . . . . . 2 1. No 2. Yes 1. No
Is a Refined Entity . . . . :
6.
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.
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.
Note
7. 8.
Tab to the command line, type SAVE, and press Enter. 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 More: Level: 3 +
Repository: SUNRISE
V: 2
Project: DEV
Rebuild Package Name . . . . . . . . . . . . DMC_VER2_RBD________________ Has-Root Function Name . . . . . . . . . . . . DMC_VER2_FUNC1_______________ Relationship Attributes: 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
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.
2-10
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. 2. Record the name of each root entity that you want to add to the rebuild package. Also record the name of your rebuild entity. Type ADDR on the action line that corresponds to the object you want to include in the rebuild package (Figure 2-15). Press Enter.
Adding a relation from the root entity Host List Facility for Entity Function V: 2 Project: DEV Level: 2
Figure 2-15
Repository: SUNRISE
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.
Naming the root entity Add a Relation Repository: SUNRISE V: 2 Project: DEV More: +
Figure 2-17
Level: 4
Rebuild Package Name . . . . . . . . . . . . DMC_VER2_RBD_________________ Has-Root Function Name . . . . . . . . . . . . DMC_VER2_FUNC2________________ Relationship Attributes: Application Configuration . . ______________________________ Is a Root Entity . . . . . . 2 1. No 2. Yes 1. No 2. Yes 1. No 2. Yes
Is a Refined Entity . . . . :
Has Hierarchy Changed . . . :
5.
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
Step 3 - Identify Objects to be Prepared
Figure 2-18
Saving the relation Maintain a Relation More: +
Repository: SUNRISE
V: 2
Project: DEV
Level: 3
Rebuild Package Name . . . . . . . . . . . . DMC_VER2_RBD_________________ Has-Root Function Name . . . . . . . . . . . . DMC_VER2_FUNC2________________ Relationship Attributes: 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. 7.
To add an instance of another entity type, return to the Host Workbench panel (Figure 2-9) and repeat steps 2 through 5. 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.

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. 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 V: 2 Project: DEV Level: 1
Repository: SUNRISE Action ________ ________ ________ LE______ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
Entity Organization Physical Event Process Rebuild Package Relationship Report Rule Section Server Set State Symbol Table Transition Value View Window
9.
Type RANALYZE on the action line of your rebuild package entity (Figure 2-20).
Selecting the rebuild package entity to analyze Host List Facility for Entity Rebuild Package V: 2 Project: DEV Level: 2
Figure 2-20
Repository: SUNRISE
Action Name System Id ________ AWT_VER1_RBD 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
You must press F19 to refresh the values on the screen.
2-14
Figure 2-21
Checking the rebuild package state Maintain an Entity V: 2 Project: DEV
More: Level: 3
Repository: SUNRISE
Rebuild Package Attributes: Name . . . . . . . . . . System Id . . . . . . . . Description . . . . . . . Rebuild Package State . . Audit Attributes: Date Created . . Time Created . . Created by . . . Date Maintained . Time Maintained . Maintained by . . Project . . . . . Change # . . . . Owner Id . . . . Local Maintenance
. . . .
. : . :
DMC_VER2_RBD_________________ AA5ENR REBUILD MIGRATED DMC_APP_1 21 Rebuild Analyze Executing
. . . . . . . . . . . . . . . . . . . . . . . . . . . Date
. . . . . . . . . .
. . . . . . . . . .
: : : : : : : : : :
95/05/17 08:51 SS0222 95/10/07 09:22 SS0222 DEV 0005 SS0222 95/10/07
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 V: 2 Project: DEV More: + Level: 3
Repository: SUNRISE
Rebuild Package Attributes: Name . . . . . . . . . . System Id . . . . . . . . Description . . . . . . . Rebuild Package State . . Audit Attributes: Date Created . Time Created . Created by . . Date Maintained Time Maintained Maintained by . Project . . . .
. . . .
. DMC_VER2_RBD__________________ : AGWASR . ______________________________ : 9 RBDA Successful w/Exceptions
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
: : : : : : :
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. Exceptions listed as affected entities Project: DEV Level: 3
Figure 2-23
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
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 V: 2 Project: DEV More: + Level: 4
Repository: SUNRISE
Rebuild Package Name . . . . . . . . . . . . DMC_VER2_RBD________________ Has-Root Rule Name . . . . . . . . . . . . DVT_RULE_ALL_SET_BATCH_SBCS___ Relationship Attributes: Application Configuration . . Is a Root Entity . . . . . . Is a Refined Entity . . . . : Has Hierarchy Changed . . . : 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. Updating an exceptions relation to the rebuild package Maintain a Relation V: 2 Project: DEV
Figure 2-26
More: + Level: 4
Repository: SUNRISE
Rebuild Package Name . . . . . . . . . . . . DMC_VER2_RBD________________ Has-Root Rule Name . . . . . . . . . . . . DVT_RULE_ALL_SET_BATCH_SBCS___ Relationship Attributes: Application Configuration . . Is a Root Entity . . . . . . Is a Refined Entity . . . . : Has Hierarchy Changed . . . : Affected Entity (Not Analyze:
______________________________ 1 No 2 Yes 2 Yes 2 Yes
2-17
Step 4 - Prepare Objects in the Rebuild Package
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.
Preparing the rebuild package Host List Facility for Entity Rebuild Package Repository: SUNRISE V: 2 Project: DEV Level: 2
Figure 2-27
Action ________ ________ RPREPARE
Name AWT_VER1_RBD BRS_VER3_RBD DMC_VER2_RBD
System Id AA46NR AA5CNR AA5ENR
2.
Choose your rebuild prepare options in the Rebuild Package Prepare Options panel (Figure 2-28).
2-18
Figure 2-28
Selecting rebuild prepare options Rebuild Prepare Options for RBDPKG
Name . . . . . . . . : DMS_VER2_RBD Version . . . . . . : 2 Select the following processing options. 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).
You must press F19 to refresh the values on the screen.
Note
2-19
Figure 2-29
Checking the rebuild package state Host List Facility for Entity Rebuild Package Maintain an Entity
More: + Level: 3
Repository: SUNRISE
V: 2
Project: DEV
Rebuild Package Attributes: Name . . . . . . . . . . System Id . . . . . . . . Description . . . . . . . Rebuild Package State . . Audit Attributes: Date Created . . Time Created . . Created by . . . Date Maintained . Time Maintained . Maintained by . . Project . . . . . Change # . . . . Owner Id . . . . Local Maintenance
. . . .
. : . :
DMC_VER2_RBD_________________ AA5ENR ______________________________ 12 Rebuild Prepare Executing
. . . . . . . . . . . . . . . . . . . . . . . . . . . Date
. . . . . . . . . .
. . . . . . . . . .
: : : : : : : : : :
95/05/17 16:29 SS0222 95/10/10 13:46 SS0222 DEV 0010 SS0222 95/10/10
5.
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
Step 5 - Install the Application for Testing
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).
Selecting the rebuild package to install Host List Host Facility List Facility for Entity for Rebuild Entity Package Rebuild Package V: 2 Project: DEV Level: 2
Figure 2-30
Repository: SUNRISE Level: 2
Action Name Action ________Name AWT_VER1_RBD ________ ________ AWT_VER1_RBD BRS_VER3_RBD RINSTALL DMC_VER2_RBD
System Id System Id AA46NR AA46NRAA5CNR AA5ENR
2.
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 . . . . . . : Then L
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. 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: Refresh the Maintain an Entity panel (press F19) to see the current rebuild package state. The state 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. Use the view results of rebuild (RES) action to see the messages that contain the results of the batch 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
No change to rule1 so check view1
rule2
@+
view2
Rule2 changes so dont check 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 + entity marked for prepare
package process1
rule1
+
view1
Check view1 and view2 whether or not their parents have changed
rule2
@+
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 process1
* #
rule1 rule3
process2
+
view1
Change to view1 so mark rule3 for prepare on 2nd run
rule2
@+
view2
@ entity changed + entity marked for prepare * 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
package process1
process2
+
rule1
rule3
+
Change to view1 so mark rule3 for prepare
view1
@
@ entity changed + entity marked for prepare * entity marked as exception # entity marked for prepare 2nd run
rule2
@+
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
+ @+
rule4
rule5
Change to set1 so mark rule4 for prepare
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
process3
+
set1
# @+
rule4
@#
rule5
Change to set1 so mark rule4 for prepare on 2nd run
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
rule1
installed 1/98
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
rule1
installed 1/99
rule2
If view1 change date > rule1 install date and < rule2 install date,
view1
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.
Running the UPDRSTAT action
Figure 3-9
Command ===> ______________________________________________________________ Repository: CAPE541 V: 5 Project: ADM Level: 1
Action Entity updrstat Management Services ________ Migration ________ Project ________ Repository ________ User ******************** BOTTOM OF DATA **********************
2. 3. 4. 5.
When the Rebuild Install update panel is displayed (Figure 3-10), specify the repository version, or an A for all versions. 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. 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. To view the report, enter the RES command against the management services entity.
Specifying the entities to update
REBUILD INSTALL -- UPDATE PANEL
Figure 3-10
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
package1 rule1
prepared 3/5
package2
changed 3/4
Problem: library1 does not reflect change to rule1
library1
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
package1 rule1
prepared 3/5
package2
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. 2. Set the variable ONE_STAGING_LIB in the @RBDENVn file to Y to specify that you want to use a single staging library. 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. 2. Set the variable RDODEFN in the CICS INI file for the repository version to Y to specify that you want to use DFHCSDUP. 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 Add an Entity Add Keywords Add a Relation Add Text to Entity Add Text to Relation Analyze Rebuild Impact Clean-up Rebuild Information Delete Entity Delete Relation Export Rebuild Package Install Objects in the Rebuild Package List Rebuild Contents List Relations Maintain Entity Maintain Relation Prepare Object in Rebuild Package Reset Object Install Status Reset Object Prepare Status Set Rebuild Install Status Super Prepare View Results of Rebuild
Rebuild Action Summary

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 Action ACTIONS List entity actions ADDE Add an entity ADDR Add a relation AUTOSAVE Update Autosave setting Refer to the Enterprise Administration Guide for more information on mainframe actions. Rebuild Actions Description Displays all actions available to you. The actions available depend on where you are in the rebuild process. This is a standard repository action. Adds a rebuild package entity. See Add an Entity. Adds a relation between the rebuild package entity and each root entity to be included in the rebuild package. See Add a Relation. Turns the autosave feature on or off. This is a standard repository action.
4-1
Table 4-1 Action
Rebuild Actions (Continued) Description Lets you see the entity attributes, but not change them. This is a standard repository action. Lets you see an entitys keywords, but not change them. This is a standard repository action. Lets you see the relation attributes, but not change them. This is a standard repository action. Lets you see an entitys text, but not change it. This is a standard repository action. Deletes rebuild files and rebuild processing information from internal control tables. See Clean-up Rebuild Information. Changes the ownership of an entity from your user ID or project to another user ID or project. This is a standard repository action. Deletes an entity from the enterprise repository. See Delete Entity. Customizes your debug profile so you can determine the level of detail you see on the screen. This is a standard repository action. Deletes a relation from the enterprise repository. See Delete Relation. Return to the Host Workbench panel.This is a standard repository action. 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 a rebuild package to download to a Workgroup repository the objects that need to be prepared on a workstation. See Export Rebuild Package. Displays the environment control command lists (CLISTs). This is a standard repository action. Adds keywords to the rebuild package entity so you can define the rebuild package. See Add Keywords. Displays an entity list of the particular type of entity you choose. This is a standard repository action. Lists object counts, objects included in rebuild package and their rebuild status. See List Rebuild Contents. Locks an entity, which prevents others from making changes to the entity. This is a standard repository action. 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. Displays the detail panel of any listed entity, and lets you modify the entity attributes. See Maintain Entity. Displays the detail panel of any listed relation, and lets you modify the relation attributes. See Maintain Relation. Lets you change from one project or version within a repository to another. This is a standard repository action.
BE Browse entity BK Browse keywords BR Browse relation BTXE Browse entity text CLEANUP Clean-up rebuild information CO Change ownership of entity DE Delete entity DEBUG Update debug profile DR Delete relation ENTITY Display entities EW Extended where-used report EXPORT Export rebuild package INIDISP View AppBuilder INI files K Add keywords to entity LE List entities LISTRBD List rebuild contents LOCK Lock entity LR List relations ME Maintain entity MR Maintain relation PROJECTS Change projects
4-2
Rebuild Actions
Table 4-1 Action
Rebuild Actions (Continued) Description Identifies objects in the rebuild package that need to be prepared. See Analyze Rebuild Impact. Updates the data and state values on any panel. This is a standard repository action. Lets you browse the results of the rebuild actions. See View Results of Rebuild. Lets you change the install status of an object to what it was before an attempted install. See Reset Object Install Status. Lets you change the prepare status of an object to what it was before an attempted prepare. SeeReset Object Prepare Status. Installs the objects in the rebuild package. See Install Objects in the Rebuild Package. Prepares the objects in the rebuild package that were marked for prepare during analyze processing. SeePrepare Object in Rebuild Package. Sets the installation status of rebuild package objects. See Set Rebuild Install Status. Lets you save an entity as a new entity with the same user-defined attributes. This is a standard repository action. Helps you find and reuse existing entities by searching for entities of all types associated with specified keywords. This is a standard repository action. Lets you automatically analyze, prepare, and install all objects in one step. See Super Prepare. Adds text to the rebuild package entity so you can define the rebuild package. See Add Text to Entity. Adds text to a relation so you can define the purpose of that relation. See Add Text to Relation. Provides access to user-written software to perform custom processing on any entity. This is a standard repository action. Unlocks an entity, which allows others to make changes to the entity. This is a standard repository action. Lets you update any of the attributes that define your user ID. This is a standard repository action. Provides access to user-written software to perform custom processing on any relation. This is a standard repository action.
RANALYZE Analyze rebuild impact REFRESH Refresh the screen RES View results of rebuild RESETINS Reset object install status RESETPR Reset object prepare status RINSTALL Install the objects in the rebuild package RPREPARE Prepare objects in rebuild package RSTATUS Set the installation status of rebuild package object SA Save as SRCH Search for keywords SUPERPR Super prepare TXE Add text to entity TXR Add text to relation UEMTH Define user entity method UNLOCK Unlock entity UPROF Update user profile URMTH Define user relation method
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 Description Required. An alphanumeric string up to either 30 single-byte or 14 double-byte characters. No default. 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.
User-defined attribute Name
Description
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 V: 2 Project: DEV More: Level: 3 +
Rebuild Package Attributes: Name . . . . . . . . . . . System Id . . . . . . . . . Description . . . . . . . . Rebuild Package State . . . Audit Attributes: Date Created . . Time Created . . Created by . . . Date Maintained . Time Maintained . Maintained by . . Project . . . . . Change # . . . . Owner Id . . . . Local Maintenance
. DMC_VER2_RBD__________________ : AA5ENR . MIGRATED DMC_APP_1 FROM V1 TO V2 : 18 N/A
. . . . . . . . . . . . . . . . . . . . . . . . . . . Date
. . . . . . . . . .
. . . . . . . . . .
: : : : : : : : : :
95/05/17 18:53 SS0222 95/10/09 18:53 SS0222 DEV 0003 SS0222 95/10/09
4-4
Rebuild Actions
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 Description 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. 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.
System-generated attribute
System ID
Rebuild State
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 Description The date (year/month/day) the rebuild object was created. The time, based on a 24-hour clock, when the rebuild object was created. The user ID of the individual who created the rebuild object. The date (year/month/day) the rebuild object was last modified. The time, based on a 24-hour clock, when the rebuild object was last modified. The user ID of the individual who last modified the rebuild object. The name of the project in which the rebuild object was created. 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. The user ID of the individual who created the rebuild object. The user ID of the individual who created the rebuild object on the host. The date (year/month/day) the rebuild object was last modified on the host. Audit attribute Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project
Change #
Owner ID Local Maintenance Local Date
4-5
Table 4-4
Audit attributes (Continued) Description The time, based on a 24-hour clock, when the rebuild object was last modified on the host. The name of the project on the host in which the rebuild object was created. The user ID of the individual who last modified the rebuild object on the host. The repository version in which the rebuild object was created.
Audit attribute Local Time Local Project Local User Version
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 Description 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. 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. User-defined Attribute
Rebuild Name
Has-Root-Entity Name
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 Description The system populates this field only if you are adding a relation from the rebuild entity. The system populates this field only if you are adding a relation from the root entity. The date (year/month/day) the relation was created. The time, based on a 24-hour clock, when the relation was created. The user ID of the individual who created the relation. The date (year/month/day) the relation was last modified. The time, based on a 24-hour clock, when the relation was last modified. The user ID of the individual who last modified the relation. 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. The date (year/month/day) the relation was last modified on the host. The time, based on a 24-hour clock, the relation was last modified on the host. The name of the project on the host in which the relation was created. The user ID of the individual who last modified the relation on the host. The project version in which the relation was created.
System-generated attribute Rebuild Name Has-Root-Entity Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by
Change #
Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
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

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. 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.
Cleanup confirmation pop-up panel
Figure 4-3
------------------- 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.
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.
Note
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.
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
Figure 4-4
. . . . . . . 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.
Listing the exported contents of the rebuild entity
List Contents of Migration DMC_VER2_RBD Version 2 =======> __________________________________________________________
Figure 4-5
Command
Type 's' to select an option or type a space to deselect. Then press ENTER. 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. Press Enter. The list of data sets beginning with that prefix is displayed, as Figure 4-6 shows.
Listing the migration data sets
4.
Figure 4-6
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 Type 's' to select an option or type a space to deselect. Then press ENTER. Type FILTER ON/OFF/MODIFY on command line for filter processing.
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 Repository File Browser 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: Refresh the Maintain an Entity panel (press F19) to see the current rebuild package state. The state 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: 1. 2. Type LISTRBD on the action line beside the name of the rebuild entity. On the command line, type FILTER MODIFY to change the filter options (Figure 4-10). Press Enter.
4-16
Rebuild Actions
Figure 4-10
Modifying filter settings

List Contents of Rebuild Package DMC_VER2_RBD Version 2
Type 's' to select an option or type a space to deselect. Then press ENTER. Type FILTER ON/OFF/MODIFY on command line for filter processing.
Rebuild Entity Status Count _ All 205 _ Prepare Needed 84 _ Install Copy Needed 60 _ Install Top Bind Needed 13 _ Install LU2 Needed 39 _ Install Intermediate Bind Needed 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.
Selecting platforms for filtering
Figure 4-11
---------------------------------------------------------------------------| List Contents of Rebuild Package DMC_VER2_RBD Version 2 | |----------------------------------------------------------------------------| |------------ 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. 5.
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. 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
---------------------------------------------------------------------------| List Contents of Rebuild Package DMC_VER2_RBD Version 2 | |----------------------------------------------------------------------------| |--------------- Phase Filter -------------------- Filter Summary -------| | | | | | | | | | Press ENTER to apply selection. | | Counts: | | RIGHT/LEFT will toggle to the next filter. | | Total......... 205 | | | | Filtered...... 70 | | _ All | | | | _ Install Copy | | Filters: | | _ Install Inter Bind | | Entity ....... Filtered | | _ Install LU2 | | Phase ........ All | | _ Install Top Bind | | Platform ..... Filtered | | S Prepare | | Project ...... All | |************** 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.
Selecting projects for filtering
Figure 4-13
----------------------------------------------------------------------------- | List Contents of Rebuild Package DMC_VER2_RBD Version 2 | |-----------------------------------------------------------------------------| |--------------- Project Filter ------------------ Filter Summary --------| | | | | | | | | | Press ENTER to apply selection. | | Counts: | | RIGHT/LEFT will toggle to the next filter. | | Total......... 205 | | | | Filtered...... 20 | | _ All | | | | S DEV | | Filters: | |************** BOTTOM OF DATA ***************| | Entity ....... Filtered | | | | Phase ........ All | | | | Platform ..... Filtered | | | | Project ...... All | | | | | | | | | | | | | | | | | | | | | | | | | -----------------------------------------------------------------------------
7.
Press F11 again to display a pop-up panel (Figure 4-14) on which you can select entities for filtering.
4-18
Rebuild Actions
Figure 4-14
Selecting entities for filtering
---------------------------------------------------------------------------| List Contents of Rebuild Package DMC_VER2_RBD Version 2 | |----------------------------------------------------------------------------| |--------------- Entity Filter ------------------- Filter Summary -------| | | | | | | | | | Press ENTER to apply selection. | | Counts: | | RIGHT/LEFT will toggle to the next filter. | | Total......... 205 | | | | Filtered...... 12 | | | | | | _ All | | Filters: | | _ Component | | Entity ....... Filtered | | _ File | | Phase ........ All | | _ Report | | Platform ..... Filtered | | S Rule | | Project ...... All | | _ 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.
Turning on the filter selections
List Contents of Rebuild Package DMC_VER2_RBD Version 2
Figure 4-15
Type 's' to select an option or type a space to deselect. Then press ENTER. Type FILTER ON/OFF/MODIFY on command line for filter processing.
Rebuild Entity Status Count _ All 205 _ Prepare Needed 84 _ Install Copy Needed 60 _ Install Top Bind Needed 13 _ Install LU2 Needed 39 _ Install Intermediate Bind Needed 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.
Filtered entity counts and Rebuild status
List Rebuild Contents for RBDPKG DMC_VER2_RBD Version 2
Figure 4-16
Type 's' to select an option or type a space to deselect. Then press ENTER. Type FILTER ON/OFF/MODIFY on command line for filter processing. 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
List Rebuild Contents for RBDPKG DMC_VER2_RBD Version 2 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.
List Facility for rebuild entities
HPS List Facility for Entity Rebuild Repository: SUNRISE V: 2 Project: DEV Level: 2
Figure 4-18
Action LR______ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
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
System Id AA5ENR AFJBNR AAAHNR AAAINR AFTXNR AFTUNR AESDNR ADZANR AFTPNR AFTQNR AFKXNR AFMHNR ABDTNR
2.
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.
4-20
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. Then press Eenter.
3.
The system generates a Relation List panel for relation types you selected (Figure 4-20).
Listing a rebuild packages relations
Project: DEV Level: 3 Repository: SUNRISE V: 2 Entity Name: DMC_VER2_RBD Relation Type: Has-Root Rule
Figure 4-20
Action Name Application Configuration ________ 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. 6.
You can use the view results action by typing RES in the Action line next to the relation you want to view. 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 Description Objects that may impact objects in the rebuild package have been added to it. Not applicable, which means the rebuild package has not been seeded with a root entity. The rebuild entity has one or more root entities. The rebuild package has been submitted for analysis. The analysis has failed on the rebuild package. The rebuild analysis completed successfully with implicitly related objects included. The rebuild package was successfully analyzed. The rebuild package has been submitted for preparation. Preparation of the rebuild package is executing. At least one of the objects in the rebuild package failed to prepare. The rebuild package was successful prepared. The rebuild package has been submitted for installation. Installation of the rebuild package is executing. At least one of the objects in the rebuild package failed to install. The rebuild package was successful installed. Status value Exceptions Seeded N/A Seeded Rebuild Analyze Submitted Rebuild Analyzed Failed RBDA Successful with Exceptions Rebuild Analyze Successful Rebuild Prepare Submitted Rebuild Prepare Executing Rebuild Prepare Failed Rebuild Prepare Successful Rebuild Install submitted Rebuild Install Executing Rebuild Install Failed Rebuild Install Successful
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
List Rebuild Contents for RBDPKG DMC_VER2_RBD Version 1 Type 's' to select an option or type a space to deselect. Then press ENTER. Type FILTER ON/OFF/MODIFY on command line for filter processing.
Rebuild Entity Status Count S All 6 S Prepare Successful 2 _ Install Copy Needed 2 _ Install LU2 Needed 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
List Rebuild Contents for RBDPKG DMC_VER2_RBD Version 1
RES_____ Prepare Successful for Rule R_CCS_36546 Platform:MNFR ________ Prepare Successful for Rule R_CCS_DUMMY Platform:MNFR
Project: QA
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. 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. 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.
Reset install options
Reset Rebuild Install Status for RBDPKG Name . . . . . . . . : DMC_VER2_RBD Version . . . . . . : 2 Select one of the following. Then press Enter.
Figure 4-23
Processing Options Reset Options . . . . . . . . . . . . 1 1. 2. 3. 4. 5. 6. 7.
All Install Actions Static Link Copy Executables DB2 Bind Package DB2 Bind Top Rules LU2 Install DB2 Bind Intermediate Rules
Caution
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. After you choose the reset install options, the Message Handler displays the result of the reset install status, as shown in Figure 4-24.
4-24
Rebuild Actions
Figure 4-24
Reset install status results

14:07:58 ----------------------------
----------------------------- 10/30/95
GR9086I GR9068I GR9063I GR9067I GR9064I GR9067I GR9098I GR9068I GR9065I GR9068I GR9066I
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. NO installs were found to be reset. Resetting install status of actions in 'LU2 Install' step. NO installs were found to be reset. 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.
Reset prepare options
Reset Rebuild Prepare Status for RBDPKG Name . . . . . . . . : DMC_VER2_RBD Version . . . . . . : 2 Select the following processing options. Processing Options Reset Options . . . . . . . . . . . Then press Enter.
Figure 4-25
1 1. All entities 2. Sets, Files, Windows, Reports, Components, Rules 3. Files, Windows, Reports, Components, Rules 4. Components, Rules 5. Process (Set-up)
Caution 2.
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

16:01:26 ----------------------------
---------------------------- 10/30/95
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). GR9029I - Prepares were reset successfully. GR9028I - Resetting prepare status of object in phase 3, (Component, Rule). GR9029I - Prepares were reset successfully. 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. 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. 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

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. 3.
You can browse the job statistics and messages by typing S in the action line of the job you want to view. 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 Name Rebuild environment-control variables Description Values 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. Default = 1
COMMIT_LEVEL
Specify whether analyze should be committed by number of objects or by rebuild.
MINIMUM_SUBMIT
Specify the minimum number of jobs to submit for each prepare.
5--1
Rebuild Variables
Table 5-1 Name
Rebuild environment-control variables (Continued) Description Specify the commit level for vsam copies during rebuild install. 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 temporary file allocation disposition. Submit jobs continuously. Display selection of Ignore failed prepares in previous phases. Initiate prepares when rebuild analyze for SUPERPR ends successfully with exceptional processes. Initiate install when prepares failed or are incomplete. Ignore failed prepares in previous phases. Intermediate bind. Defer jobs to run overnight. Values Default = 100
VSAM_COMMIT
RUN_REPORT
DEFAULT = Y
ALLOC_DISP CONT_SUBMIT DISPLAY_PREV_FAILED
DELETE (default) CATLG KEEP Default is N (No). Default is N (No).
EXCEPTION_RPRT
Default is Y (Yes).
IGNORE_FAILED_PREPARES IGNORE_PREV_FAILED INTERMEDIATE_BIND NIGHTRUN
Default is N (No). Default is N (No). Default is N (No). Default is N (No). 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. Default is Y (Yes). Default is N (No). Default is N (No).
PHASE_2
Controls whether users can prepare files.
PROCESS52 RESUBMIT_FAILED RESUBMIT_INCOMPLETE
When set to Y (Yes), marks version 5.2 processes for preparation. Resubmit failed jobs. Resubmit failed prepares. 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. 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. 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.
REGEN_LU2
Default = N
REGEN_BIND
Default = N
RUN_REPORT
Default = Y
5--2
Setting Up The Rebuild Environment
Migrate Variables
Table 5-1 Name
Rebuild environment-control variables (Continued) Description Skip processing preparable entities with project of SEER1. Setting this variable to Y skips entities in the default repository. Skip processing preparable entities with project of SEER2. Setting this variable to Y skips entities in the default repository. Specify the default for static link analysis. Specify the default for comp link processing. Storage allocation increment Values
SKIP_SEER1
Default is Y (Yes).
SKIP_SEER2
Default is Y (Yes).
STATIC_LINK_DEFAULT STATIC_LINK_COMPONENT STORAGE_INCREMENT
Default = N Default = N 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 Name MIGRATE variables Description Specify the default value to be used for the import migration option. Valid values Y Import the migration package during automated migration processing. N Do not import the migration package during automated migration processing. Default is N. Y Analyze the rebuild package during automated migration processing. N Do not analyze the rebuild package during automated migration processing. Default is N. Y Prepare the rebuild package during automated migration processing. N Do not prepare the rebuild package during automated migration processing. Default is Y. Y Install the rebuild package during automated migration processing. N Do not install the rebuild package during automated migration processing. Default is Y. Y Export the rebuild package during automated migration processing. N Do not export the rebuild package during automated migration processing. Default is Y. Y The user can override the option. N The user cannot override the option. Default is N.
RUNIMP
RUNRBDA
Specify the default value to be used for the analyze rebuild package option.
RUNRBDPR
Specify the default value to be used for the prepare rebuild package option.
RUNRBDIN
Specify the default value to be used for the install rebuild package option.
RUNRBDEX
Specify the default value to be used for the export rebuild package option. Specify whether the user can override the default value for the import migration option.
OVIMP
5--3
Migrate Variables
Table 5-2 Name OVRBDA
MIGRATE variables (Continued) Description Specify whether the user can override the default value for the analyze rebuild package option. Specify whether the user can override the default value for the prepare rebuild package option. Specify whether the user can override the default value for the install rebuild package option. Valid values Y The user can override the option. N The user cannot override the option. Default is Y. Y The user can override the option. N The user cannot override the option. Default is Y. Y The user can override the option. N The user cannot override the option. Default is Y.
OVRBDPR
OVRBDIN
5--4
Setting Up The Rebuild Environment
APPENDIX
A
Table A-1 11 12 13 14 15 16 101 102 103 104 160 201 202 203 204 260 301 302 303 304 360 401 402 403 404 501 502
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.
Migration status values Description Packaged Exported Loaded Not Packaged Not Exported Not Loaded Unchanged Import will Update Import will Create Import will Delete Collision Explicit Skip Unchanged Explicit Skip Update Explicit Skip Create Explicit Skip Delete Explicit Skip Collision Implicit Skip Unchanged Implicit Skip Update Implicit Skip Create Implicit Skip Delete Implicit Skip Collision Unchanged, Not Imported Update, Not Imported Create, Not Imported Delete, Not Imported Successful Unchanged Successful Update Internal Code
A-1
Table A-1
Migration status values (Continued) Description Successful Create Successful Delete Partial Unchanged of Partial Update of Partial Create of Successful Selective Delete Failed Unchanged Failed Update Failed Create Failed Delete Rolled Back Unchanged Rolled Back Update Rolled Back Create Rolled Back Delete
Internal Code 503 504 601 602 603 604 701 702 703 704 801 802 803 804
Table A-2 lists the rebuild status-value internal codes and descriptions.
Table A-2 Rebuild status values Description Prepare Successful Prepare Incomplete Prepare Failed Prepare Executing Prepare Submitted Prepare Selected Prepare Needed Install Successful Install Incomplete Install Failed Install Executing Install Submitted Install Selected Install Needed Install Static Link Successful Install Static Link Incomplete Install Static Link Failed Install Static Link Executing Install Static Link Submitted Install Static Link Selected Install Static Link Needed Install Copy Successful Install Copy Incomplete Internal Code 6400 6404 6408 6410 6412 6413 6414 6500 6504 6508 6510 6512 6513 6514 6600 6604 6608 6610 6612 6613 6614 6700 6704
A-2
Status Values
Table A-2
Rebuild status values (Continued) Description Install Copy Failed Install Copy Executing Install Copy Submitted Install Copy Selected Install Copy Needed Install Top Bind Successful Install Top Bind Incomplete Install Top Bind Failed Install Top Bind Executing Install Top Bind Submitted Install Top Bind Selected Install Top Bind Needed Install LU2 Successful Install LU2 Incomplete Install LU2 Failed Install LU2 Executing Install LU2 Submitted Install LU2 Selected Install LU2 Needed Install Intermediate Bind Successful Install Intermediate Bind Incomplete Install Intermediate Bind Failed Install Intermediate Bind Executing Install Intermediate Bind Submitted Install Intermediate Bind Selected Install Intermediate Bind Needed
Internal Code 6708 6710 6712 6713 6714 6800 6804 6808 6810 6812 6813 6814 6900 6904 6908 6910 6912 6913 6914 7000 7004 7008 7010 7012 7013 7014
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 Object type System name Attribute name Significant? Table B-2 Heading Descriptions Description This value is either ENTITY or RELATE (relationship). The system name of an entity or relationship type. For example, APPCFG is the system name for the application configuration entity type. The attribute name used on the user interface panels. If this value is Y, the attribute is significant. If the value is N, the attribute is insignificant.
Entity and Relationship Attributes System Name APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG Attribute Name System Id Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id Significant? Y Y Y Y Y Y Y Y Y N N N Y
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
B-1
Table B-2
Entity and Relationship Attributes (Continued) System Name APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG Attribute Name QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP
System Id Name Assumption Type Priority Act Start Plnd Start Conf Level Risk Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB
System Id Name Derived Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y
B-2
Rebuild Processing Attributes
Table B-2
Entity and Relationship Attributes (Continued) System Name ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB Attribute Name Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP
System Id Name Type Implementation Name Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y N N Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY
BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP
System Id Name Country Language X Resolution Y Resolution
Y Y Y Y Y
B-3
Table B-2
Entity and Relationship Attributes (Continued) System Name BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP Attribute Name Format Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ
System Id Name Description Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
B-4
Table B-2
Entity and Relationship Attributes (Continued) System Name CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST Attribute Name System Id Customer Group Id Customer Group Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL
System Id Name Protocol Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
B-5
Table B-2
Entity and Relationship Attributes (Continued) System Name Attribute Name Significant?
Object Type
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT
System Id Name Type Implementation Name Protocol Server Link Type Server Start Type Server Cell Rank Owner Qualifier Plan Name Collection Id Isolation Mode Minimum Transaction Id Maximum Transaction Id Unit Of Work Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT
System Id Name Type Nature Number Of Elements Number Of Groups
Y Y Y Y Y Y
B-6
Table B-2
Entity and Relationship Attributes (Continued) System Name COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN
System Id Name Implementation Name Column Format Column Length Column Fraction Average Length Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N
B-7
Table B-2
Entity and Relationship Attributes (Continued) System Name COLUMN Attribute Name Version Significant? N
Object Type ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP
System Id Name Execution Environment Info Src Language Subroutine DBMS Usage Description Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP
System Id Customer Group Id Customer Group Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id
Y Y Y Y Y Y Y Y Y Y N N
B-8
Table B-2
Entity and Relationship Attributes (Continued) System Name CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP Attribute Name Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS
System Id Name Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST
System Id Customer Id Customer Name Customer Title Customer Code Business Telephone Number Business Telephone Extension Home Telephone Number Profile Filename Date Created
Y Y Y Y Y Y Y Y Y Y
B-9
Table B-2
Entity and Relationship Attributes (Continued) System Name CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA
System Id Name Data Format Data Length Data Fraction Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY
DATABAS
System Id
B-10
Table B-2
Entity and Relationship Attributes (Continued) System Name DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS Attribute Name Name Implementation Name Type Machine Name Database Directory Path Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG
System Id Name Drawing Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project
Y Y Y Y Y Y Y Y Y Y N N N Y N N N N
B-11
Table B-2
Entity and Relationship Attributes (Continued) System Name DRAWNG DRAWNG Attribute Name Local Maintenance User Version Significant? N N
Object Type ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT
System Id Name Entity Type Expected Minimum Rows Expected Maximum Rows Activity Period Average Inserts for Period Average Deletes for Period Average Updates for Period Expected Rows Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Entity Type Name Screen Description Entity Code Implementation Name Migration File Name Implementation Storage Exit Routine Date Created Time Created
Y Y Y Y Y Y Y Y Y Y
B-12
Table B-2
Entity and Relationship Attributes (Continued) System Name ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY Attribute Name Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT
System Id Name Description Event Type Event Class Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY
FILE FILE
System Id Name
Y Y
B-13
Table B-2
Entity and Relationship Attributes (Continued) System Name FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE Attribute Name File Type Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD
System Id Name Field Picture - Storage Field Picture - Display Screen Literal - Long Field Format Field Length Field Fraction Range - Minimum Value Range - Maximum Value Reference Table Name Screen Literal - Short Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N
B-14
Table B-2
Entity and Relationship Attributes (Continued) System Name FLD FLD FLD FLD FLD FLD FLD FLD FLD Attribute Name Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM
System Id Name Form Environment Base Country Language Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME
System Id Name Description Mutually Exclusive Date Created Time Created Created by Date Maintained
Y Y Y Y Y Y Y Y
B-15
Table B-2
Entity and Relationship Attributes (Continued) System Name FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME Attribute Name Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC
System Id Name Business System Id Menu Description Sub-Process Menu Type Application Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY
FVALUE FVALUE FVALUE
System Id Name Description
Y Y Y
B-16
Table B-2
Entity and Relationship Attributes (Continued) System Name FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y N N N Y N N N N N N
GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP
ENTITY ENTITY
HELP HELP
System Id Name
Y Y
B-17
Table B-2
Entity and Relationship Attributes (Continued) System Name HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP Attribute Name Format Description Country Language Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT
System Id Name Country Language Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
B-18
Table B-2
Object Type
IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT
System Id Name Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY
System Id Name Implementation Name Type Unique Flag Delete Method Update Method Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N
B-19
Table B-2
Entity and Relationship Attributes (Continued) System Name KEY KEY KEY KEY KEY Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY
LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG
System Id Name Language Abbreviation Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC
System Id Name Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id
Y Y Y Y Y Y Y Y Y Y N N N Y
B-20
Table B-2
Entity and Relationship Attributes (Continued) System Name LOC LOC LOC LOC LOC LOC Attribute Name QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO
System Id Name Description Type Mode Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE
System Id Name Implementation Name Operating System OS Release Machine Group Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y Y Y Y
B-21
Table B-2
Entity and Relationship Attributes (Continued) System Name MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE Attribute Name Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N Y N N N N N N
MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP
System Id Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
N N N N N N N N N N N N N N N N N N N
MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN
System Id Name Description Data Set Prefix Migration State Return Code Processing Version Date Created
N N N N N N N Y
B-22
Table B-2
Entity and Relationship Attributes (Continued) System Name MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG
Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY
PANEL PANEL PANEL PANEL
System Id Name Coordinate System X-Resolution
Y Y Y Y
B-23
Table B-2
Entity and Relationship Attributes (Continued) System Name PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL Attribute Name Y-Resolution Description Country Language Base GUI Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT
System Id Name Event Description Event Type Event Class Event Scope Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N
B-24
Table B-2
Entity and Relationship Attributes (Continued) System Name PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES
System Id Name Description Menu Description Work Station Group Id Sub-Process Menu Type Execution Environment Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT
System Id Project Name Project Id Type Description Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y Y Y
B-25
Table B-2
Entity and Relationship Attributes (Continued) System Name PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT Attribute Name Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N Y N N N N N N
RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG
System Id Name Description Rebuild Package State Return Code Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY
REL REL REL REL REL
Relationship Type Name Relationship Code Y Description X Description
Y Y Y Y Y
B-26
Table B-2
Entity and Relationship Attributes (Continued) System Name REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL Attribute Name Implementation Name Migration File Name Exit Routine Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT
Report Id Name Execution Environment Page Size Line Size Left Margin Top Margin Printer Type Orientation Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change #
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N
B-27
Table B-2
Entity and Relationship Attributes (Continued) System Name REPORT REPORT REPORT REPORT REPORT REPORT REPORT Attribute Name Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT
System Id Name Description Type Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN
System Id Name Complex Expected Minimum Rows Expected Maximum Rows Activity Period Average Inserts for Period Average Deletes for Period Average Updates for Period Expected Rows
Y Y Y Y Y Y Y Y Y Y
B-28
Table B-2
Entity and Relationship Attributes (Continued) System Name RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y N N N Y N N N N N N
RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE
System Id Name Execution Environment DB2 Plan Name DBMS Usage Description Execution Mode CICS / IMS Transaction Id Implementation Name Package Isolation Mode Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status
Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y Y N N N Y N
B-29
Table B-2
Entity and Relationship Attributes (Continued) System Name RULE RULE RULE RULE RULE Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK
System Id Name Release Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
N N N N N N N N N N N N N N N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK
System Id Name Total Orders Licensed Orders Remaining Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change #
N N N N N N N N N N N N N N
B-30
Table B-2
Entity and Relationship Attributes (Continued) System Name SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK Attribute Name Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N N
SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD
N N N N N N N N N N N N N N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC
System Id Name Extract to File Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change #
N N N N N N N N N N N N N
B-31
Table B-2
Entity and Relationship Attributes (Continued) System Name SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC Attribute Name Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N N
SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV
System Id Customer Group Id Customer Group Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN
System Id Name Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id
Y Y Y Y Y Y Y Y Y Y N N
B-32
Table B-2
Entity and Relationship Attributes (Continued) System Name SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN Attribute Name Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER
System Id Name Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SET SET SET SET SET SET SET SET SET SET SET
System Id Name Field Picture - Storage Set Format Set Length Set Fraction Implementation Name Style Representation Length Date Created Time Created
B-33
Table B-2
Entity and Relationship Attributes (Continued) System Name SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET Attribute Name Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB
System Id Name Description Implementation Name Implementation Storage Migration File Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY
STATE
System Id
B-34
Table B-2
Entity and Relationship Attributes (Continued) System Name STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE Attribute Name Name Description Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE
B-35
Table B-2
Object Type
SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL
System Id Name Define Encoding Display Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE
System Id Name Table Or View Table Creator Implementation Name Expected Minimum Rows Expected Maximum Rows Activity Period Average Inserts For Period Average Deletes For Period Average Updates For Period Date Created Time Created Created by Date Maintained Time Maintained Maintained by
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
B-36
Table B-2
Entity and Relationship Attributes (Continued) System Name TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE Attribute Name Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS
Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
TXT TXT TXT TXT TXT TXT
System Id Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y N N N N N
ENTITY ENTITY
USER USER
System Id Name
Y Y
B-37
Table B-2
Entity and Relationship Attributes (Continued) System Name USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER Attribute Name User Name User Id JOB Accounting Information User Location JOB Name JOB Options Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES
System Id Name Value Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time
Y Y Y Y Y Y Y Y Y Y N N N Y N N N
B-38
Table B-2
Entity and Relationship Attributes (Continued) System Name VALUES VALUES VALUES Attribute Name Local Maintenance Project Local Maintenance User Version Significant? N N N
Object Type ENTITY ENTITY ENTITY
VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW
System Id Name Description Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON
System Id Name GUI Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status
Y Y Y Y Y Y Y Y Y Y N N N Y N
B-39
Table B-2
Entity and Relationship Attributes (Continued) System Name WINCON WINCON WINCON WINCON WINCON Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW
System Id Name Description Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU
Parent Type Application Config. Long Name Sequence Number Child Type Configuration Unit Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained
B-40
Table B-2
Entity and Relationship Attributes (Continued) System Name ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT
Parent Type Business Attribute Name Sequence Number Child Type Business Attribute Name Separator Id Occurs Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y Y Y Y Y
B-41
Table B-2
Entity and Relationship Attributes (Continued) System Name ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT
Parent Type Business Attribute Name Sequence Number Child Type Data Type Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by
B-42
Table B-2
Entity and Relationship Attributes (Continued) System Name BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI Attribute Name Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE
BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO
Parent Type Business Object Long Name Sequence Number Child Type Business Object Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX
Parent Type Business Object Name Sequence Number Child Type Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change #
Y Y Y Y Y Y Y Y Y Y Y Y N
B-43
Table B-2
Entity and Relationship Attributes (Continued) System Name BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX Attribute Name QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX
Parent Type Cell Long Name Sequence Number Child Type Child Long Name Separator Id Machine Implementation Name Cell Manager Communication Gateway Application Server Network Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM
Parent Type Component Long Name Sequence Number Child Type Sub-Component Long Name Separator Id Date Created Time Created
Y Y Y Y Y Y Y Y
B-44
Table B-2
Entity and Relationship Attributes (Continued) System Name COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM Attribute Name Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Date Created Time Created Created by
Y Y Y Y Y Y Y Y Y
B-45
Table B-2
Entity and Relationship Attributes (Continued) System Name CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG Attribute Name Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Date Created Time Created Created by Date Maintained
Y Y Y Y Y Y Y Y Y Y
B-46
Table B-2
Entity and Relationship Attributes (Continued) System Name CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX Attribute Name Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV
Parent Type Parent Id QA Status Sequence Number Child Type Child Id Separator Id Login ID Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y N Y Y Y Y Y Y Y Y Y Y Y N N N N N N
CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX
Parent Type Configuration Unit Long Name Sequence Number Child Type Child Long Name Separator Id Preparation Time Implementation Name Service Name
Y Y Y Y Y Y Y Y Y
B-47
Table B-2
Entity and Relationship Attributes (Continued) System Name CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX Attribute Name Significant Time Link Type Owner Id Qualifier Plan Name Collection Id Version Id Isolation Mode Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT
Parent Type Data Type Name Sequence Number Child Type Data Type Name Separator Id Occurs Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N
B-48
Table B-2
Entity and Relationship Attributes (Continued) System Name DATDAT Attribute Name Version Significant? N
Object Type RELATE
DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET
Parent Type Data Type Name Sequence Number Child Type Set Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB
Parent Type Database Long Name Sequence Number Child Type Table Long Name Separator Id Expected Minimum Rows Expected Maximum Rows Activity Period Average Inserts Average Deletes Average Updates Done To Do Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
B-49
Table B-2
Entity and Relationship Attributes (Continued) System Name DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT
Parent Type Business Entity Name Sequence Number Child Type Business Attribute Name Separator Id Optional Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE
Parent Type Business Entity Name Sequence Number Child Type Identifier Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained
B-50
Table B-2
Entity and Relationship Attributes (Continued) System Name ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Master Indicator
Y Y Y Y Y Y Y
B-51
Table B-2
Entity and Relationship Attributes (Continued) System Name ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 Attribute Name Variant Indicator Partitioned Indicator Replicated Indicator Subset Data Reorganized Data Teleprocessing (Remode Data) Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN
Parent Type Business Entity Name Sequence Number Child Type Business Relation Name Separator Id Chief Executive Cardinality Optionality Dependant Abstract Role Minimun Cardinality Maximum Cardinality Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
B-52
Table B-2
Entity and Relationship Attributes (Continued) System Name ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX
Parent Type Event Name Sequence Number Child Type Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU
Parent Type Rule Long Name Sequence Number Child Type Event Long Name Separator Id Action Type Action Host View Mapping Date Created Time Created
B-53
Table B-2
Entity and Relationship Attributes (Continued) System Name EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU Attribute Name Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y N N N N N N N
EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO
Parent Type Event Name Sequence Number Child Type Business Object Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM
Type Long Name Sequence Number Child Type Child Id Separator Id Component Usage Date Created
Y Y Y Y Y Y Y Y
B-54
Table B-2
Entity and Relationship Attributes (Continued) System Name FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Store and Forward Update Rule Store and Forward Delete Rule Store and Forward Insert Rule Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE RELATE
FSHAFV FSHAFV FSHAFV
Parent Type FSDM Scheme Long Name Sequence Number
Y Y Y
B-55
Table B-2
Entity and Relationship Attributes (Continued) System Name FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV Attribute Name Child Type FSDM Value Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR
Parent Type Business Function Long Name Sequence Number Child Type Business Process Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE
FUNENT FUNENT
Parent Type Business Function Long Name
Y Y
B-56
Table B-2
Entity and Relationship Attributes (Continued) System Name FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT Attribute Name Sequence Number Child Type Entity Long Name Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC
Parent Type Business Function Long Name Sequence Number Child Type Location Long Name Separator Id Major Involvement in Function Minor Involvement in Function Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change #
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N
B-57
Table B-2
Entity and Relationship Attributes (Continued) System Name FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC Attribute Name QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N
FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS
Parent Type FSDM Value Long Name Sequence Number Child Type FSDM Scheme Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status
Y Y Y Y Y Y Y Y Y Y Y Y N N
B-58
Table B-2
Entity and Relationship Attributes (Continued) System Name GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE
GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Method Name Scope Scope Mode Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id User Authority level Field Authority level Date Created Time Created Created by Date Maintained
B-59
Table B-2
Entity and Relationship Attributes (Continued) System Name GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR Attribute Name Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N N N N N
IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT
Parent Type Identifier Name Sequence Number Child Type Business Attribute Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id File Key type Date Created Time Created Created by Date Maintained
B-60
Table B-2
Entity and Relationship Attributes (Continued) System Name KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY Attribute Name Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N N N N N
KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO
Parent Type Key Long Name Sequence Number Child Type Column Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL
Parent Type Logical Long Name Sequence Number Child Type Physical Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained
B-61
Table B-2
Entity and Relationship Attributes (Continued) System Name LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX
Parent Type Logical Process Name Sequence Number Child Type Name Separator Id Create Read Update Delete Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU
Parent Type Logical Process Long Name Sequence Number Child Type Rule Long Name Separator Id Date Created
Y Y Y Y Y Y Y
B-62
Table B-2
Entity and Relationship Attributes (Continued) System Name LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N N N N N
MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC
Parent Type Parent Machine Name Sequence Number Child Type Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Security Type Date Created
Y Y Y Y Y Y Y Y
B-63
Table B-2
Entity and Relationship Attributes (Continued) System Name MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N N N N N
MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG
MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX
Parent Type Migration Id Sequence Number Child Type Child Id Separator Id Child Name Located In
Y Y Y Y Y Y Y Y
B-64
Table B-2
Entity and Relationship Attributes (Continued) System Name MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX
Parent Type Parent Id Sequence Number Child Type Child Id Migration Status Scope type Seed Status Has Reuse Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE
ORGENT ORGENT ORGENT ORGENT
Parent Type Organization Long Name Sequence Number Child Type
Y Y Y Y
B-65
Table B-2
Entity and Relationship Attributes (Continued) System Name ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT Attribute Name Entity Long Name Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN
Parent Type Organization Long Name Sequence Number Child Type Business Function Long Name Separator Id Responsible for Function Major Involvement in Function Minor Involvement in Function Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N
B-66
Table B-2
Entity and Relationship Attributes (Continued) System Name ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO
Parent Type Organization Long Name Sequence Number Child Type Business Process Long Name Separator Id Responsible for Function Major Involvement in Function Minor Involvement in Function Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET
Type Long Name Sequence Number Child Type Set Long Name Separator Id Date Created Time Created Created by
Y Y Y Y Y Y Y Y Y
B-67
Table B-2
Entity and Relationship Attributes (Continued) System Name OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET Attribute Name Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS
PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Description Inclusive Flag Exclusive/Or Sequence number
Y Y Y Y Y Y Y Y Y
B-68
Table B-2
Entity and Relationship Attributes (Continued) System Name PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N N N N N
PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT
Parent Type Business Process Long Name Sequence Number Child Type Entity Long Name Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE
PROLOC
Parent Type
B-69
Table B-2
Entity and Relationship Attributes (Continued) System Name PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC Attribute Name Business Process Long Name Sequence Number Child Type Location Long Name Separator Id Major Involvement in Function Minor Involvement in Function Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO
Parent Type Business Process Long Name Sequence Number Child Type Sub-Business Process Long Name Separator Id Conditional Flag Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status
Y Y Y Y Y Y Y Y Y Y Y Y Y N N
B-70
Table B-2
Entity and Relationship Attributes (Continued) System Name PROPRO PROPRO PROPRO PROPRO PROPRO Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL
Parent Type Business Process Long Name Sequence Number Child Type Rule Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Source Version Target Version Direction Logical Key Date Created Time Created Created by Date Maintained
Y Y Y Y Y Y Y Y Y Y Y Y Y Y
B-71
Table B-2
Entity and Relationship Attributes (Continued) System Name REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP Attribute Name Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC
Parent Type Report Long Name Sequence Number Child Type Section Long Name Separator Id Type Break Sequence Number Page Placement Break Field Break Qualifier Left Margin Print Option Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RLNRLN RLNRLN RLNRLN RLNRLN
Parent Type Business Relation Name Sequence Number Child Type
Y Y Y Y
B-72
Table B-2
Entity and Relationship Attributes (Continued) System Name RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN Attribute Name Business Relation Name Separator Id Chief Executive Cardinality Optionality Dependant Abstract Role Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
B-73
Table B-2
Object Type
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX
Parent Type Parent Id Sequence Number Child Type Child Id Migration Status Install Action Install Status Install for Platform Operating System Data Base Type Configuration Unit Row Selected Install Start Time Stamp install Stop Time Stamp Return Code Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX
Parent Type Parent Id Sequence Number Child Type Child Id Migration Status Application Configuration Scope type Seed status Has Reuse
Y Y Y Y Y Y Y Y Y Y
B-74
Table B-2
Entity and Relationship Attributes (Continued) System Name RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX Attribute Name Is a Root Entity Is a Refined Entity Has Hierarchy Changed Affected Entity (Not Analyzed) Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM
Parent Type Rule Long Name Sequence Number Child Type Component Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE
RULDEP RULDEP RULDEP
Parent Type Parent Id Sequence Number
Y Y Y
B-75
Table B-2
Entity and Relationship Attributes (Continued) System Name RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP Attribute Name Child Type Child Id Separator Id Description Inclusive Flag Exclusive/Or Sequence number Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP
Parent Type Rule Long Name Sequence Number Child Type Report Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
B-76
Table B-2
Entity and Relationship Attributes (Continued) System Name RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL Attribute Name Parent Type Rule Long Name Sequence Number Child Type Sub-Rule Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND
Parent Type Rule Long Name Sequence Number Child Type Window Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE
RUTREV
Parent Type
B-77
Table B-2
Entity and Relationship Attributes (Continued) System Name RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV Attribute Name Rule Long Name Sequence Number Child Type Event Long Name Separator Id Rule Trigger Type Trigger Condition View Mapping Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP
B-78
Table B-2
Object Type
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Command to Invoke
Y Y Y Y Y Y Y
B-79
Table B-2
Entity and Relationship Attributes (Continued) System Name SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N N N N N
SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL
Parent Type Set Long Name Sequence Number Child Type Value Long Name Separator Id Symbol Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE
SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id
Y Y Y Y Y Y
B-80
Table B-2
Entity and Relationship Attributes (Continued) System Name SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N N N N N
SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL
Parent Type Server Long Name Sequence Number Child Type Rule Long Name Separator Id Entry Type Object Name Service Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
STOENT STOENT STOENT STOENT
Parent Type Data Store Long Name Sequence Number Child Type
Y Y Y Y
B-81
Table B-2
Entity and Relationship Attributes (Continued) System Name STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT Attribute Name Entity Long Name Separator Id Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV
Parent Type Table Long Name Sequence Number Child Type Table Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
SYSFUN SYSFUN SYSFUN SYSFUN
Parent Type Current System Long Name Sequence Number Child Type
Y Y Y Y
B-82
Table B-2
Entity and Relationship Attributes (Continued) System Name SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN Attribute Name Business Function Long Name Separator Id Currently Supported Planned Support Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO
Parent Type Current System Long Name Sequence Number Child Type Business Process Long Name Separator Id Currently Supported Planned Support Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N
B-83
Table B-2
Entity and Relationship Attributes (Continued) System Name SYSPRO SYSPRO Attribute Name Local Maintenance User Version Significant? N N
Object Type RELATE RELATE
SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO
Parent Type Current System Long Name Sequence Number Child Type Data Store Long Name Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB
Parent Type Table Long Name Sequence Number Child Type Table Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change #
Y Y Y Y Y Y Y Y Y Y Y Y N
B-84
Table B-2
Entity and Relationship Attributes (Continued) System Name TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB Attribute Name QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO
Parent Type Table Long Name Sequence Number Child Type Column Long Name Separator Id Null Distinct Distinct Type Update Percentage Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY
Parent Type Table Long Name Sequence Number Child Type Key Long Name Separator Id Date Created Time Created Created by Date Maintained
Y Y Y Y Y Y Y Y Y Y
B-85
Table B-2
Entity and Relationship Attributes (Continued) System Name TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY Attribute Name Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N N N N N
TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY
Parent Type Table Long Name Sequence Number Child Type Key Long Name Separator Id Referential Integrity Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Description Inclusive Flag Exclusive/Or Sequence number
Y Y Y Y Y Y Y Y Y
B-86
Table B-2
Entity and Relationship Attributes (Continued) System Name TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N N N N N
USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW
Type Long Name Sequence Number Child Type Child Id Separator Id Usage Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS
Parent Type View Long Name Sequence Number Type Long Name Separator Id
Y Y Y Y Y Y
B-87
Table B-2
Entity and Relationship Attributes (Continued) System Name VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS Attribute Name Occurs Number of Times Null Indicator for DB2 Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP
Parent Type Instance Sequence Number Child Type Instance Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE
WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL
Parent Type Instance Sequence Number Child Type Instance
Y Y Y Y Y
B-88
Table B-2
Entity and Relationship Attributes (Continued) System Name WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL Attribute Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC
Parent Type Instance Sequence Number Child Type Instance Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV
Parent Type Name Sequence Number Child Type Event Name Separator Id
Y Y Y Y Y Y
B-89
Table B-2
Entity and Relationship Attributes (Continued) System Name XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N N N N N
XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP
Parent Type Name Sequence Number Child Type Logical Process Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created
Y Y Y Y Y Y Y
B-90
Table B-2
Entity and Relationship Attributes (Continued) System Name XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N N N N N
XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX
XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP
Parent Type Name Sequence Number Child Type Logical Process Name Separator Id Description Date Created
Y Y Y Y Y Y Y Y
B-91
Table B-2
Entity and Relationship Attributes (Continued) System Name XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N N N N N
XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM
XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created
Y Y Y Y Y Y Y Y
B-92
Table B-2
Entity and Relationship Attributes (Continued) System Name XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT Attribute Name Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y N N N N N N N
XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST
Parent Type Name Sequence Number Child Type State Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV
Parent Type Name Sequence Number Child Type Event Name Separator Id Description Date Created Time Created
Y Y Y Y Y Y Y Y Y
B-93
Table B-2
Entity and Relationship Attributes (Continued) System Name XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV Attribute Name Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y N N N N N N N
XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST
Parent Type Name Sequence Number Child Type State Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP
Parent Type Rule Long Name Sequence Number Child Type Sub-Rule Long Name Separator Id Profile Type Date Created
Y Y Y Y Y Y Y Y
B-94
Table B-2
Entity and Relationship Attributes (Continued) System Name XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N N N N N
XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST
Parent Type Event Context Long Name Sequence Number Child Type State Long Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP
Parent Type Name Sequence Number Child Type Logical Process Name Separator Id Description
Y Y Y Y Y Y Y
B-95
Table B-2
Entity and Relationship Attributes (Continued) System Name XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP Attribute Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA
Parent Type Parent Long Name Sequence Number Child Entity Type Child Long Name Separator Id Short Value Long Value Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
B-96
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 Dataset Allocated DBRM pds Loadbs NCALBS PREPARE.SVRULDSN - Generated RULE source PREPARE.SVCOBDSN - Generated COBOL source PREPARE.SVCPTDSN - Saved copybook control information PREPARE.SVBNDDSN- Saved DB2 Bind control cards PREPARE.SVGRTDSN - Saved DB2 Grant control cards PREPARE.SVBNTDSN - Saved DB2 Bind control cards in textual format PREPARE.SVBPKDSN - Saved DB2 Bind Package control cards PREPARE.SVGPKDSN - Saved DB2 Grant Package control cards PREPARE.SVLNCDSN - Saved CICS Link Control cards PREPARE.SVLNBDSN - Saved BATCH Link Control cards PREPARE.SVLNIDSN - Saved IMS Link Control cards HMFNCTLB - Saved NCAL Link edit control cards SVLKTDSN - Saved link control cards list SVLU2DSN - Saved LU2 control cards LOADIM - IMS Load library SVLU2DSN - Saved CICS LU2 control cards Conditions Causing Allocate Unconitionally allocated Unconditionally allocated Unconditionally Allocated PREPARE.SVRULESRC = Y PREPARE.SVCOBSRC = Y PRODUCT.ENDEVOR = y Bind Plan Grant for Plan Bind Plan Bind - PRODUCT.ENDEVOR=y Package Bind Package Bind If >=1 Rule, components, windows, sets, and reports If >=1 Rule, components, windows, sets, and reports If >=1 Rule, components, windows, sets, and reports and PRODUCT.IMS = y If >=1 Rule, components, windows, sets, and reports If >=1 Rule, components, windows, sets, and reports and PREPARE.SVLNKLST=Y If IMS entities were marked for Install as part of the REBUILD. If CICS entities were marked for Install as part of the REBUILD. MRO is supported , A dataset will be created for each region. If CICS entities were marked for Install as part of the REBUILD. MRO is supported , A dataset will be created for each region. If Rebuild contains Components and the PREPARE.SVCMPSRC=Y If Rebuild contains Components and the PREPARE.SVCMVSRC=Y If Rebuild contains SETS and the PREPARE.SVSETSRC=Y
LOADCI - CICS Load library
SVCMPDSN - - Saved extracted component source SVCMVDSN - Saved extracted component view source SVSETDSN - Saved generated set source
C-2
File Allocations during Rebuild Processing
Table 3-1
Allocation Matrix (Continued) Dataset Allocated SVSTBDSN - Saved extracted set cobol copylib SVSTCDSN - Saved extracted set C copylib SVSTPDSN - Saved extracted set PL/l copylib
Conditions Causing Allocate If Rebuild contains Sets and the PREPARE.SVSTBSRC=Y for COBOL copybooks If Rebuild contains Sets and the PREPARE.SVSTCSRC=Y for C copybooks If Rebuild contains Sets and the PREPARE.SVSTPSRC=Y for PL/I copybooks If Rebuild contains Sets and the PREPARE.SVSTRCPY=Y for Set Reference members If Rebuild contains Sets and the PREPARE.SVSTECPY=Y for Set error files If Rebuild contains Window source and the PREPARE.SVWNDSRC=Y If Rebuild contains HELP source for windows and the PREPARE.SVHLPSRC=Y If Rebuild contains FILE and the PREPARE.SVFLEPL1=Y for PLI files If Rebuild contains FILE and the PREPARE.SVFLECOB=Y for COBOL files If Rebuild contains FILE and the PREPARE.SVFLEC=Y for C files If >=1 Rule, components and reports and If Rebuild contains component generated BIND File and the PREPARE.SVBNDX=Y If >=1 Rule and components and If Rebuild contains component generated COBOL VIEW and the PREPARE.SVVBSRC=Y If >=1 Rule and components and If Rebuild contains component generated COBOL VIEW aligned and the PREPARE.SVVBASRC=Y If >=1 Rule and components and If Rebuild contains component generated PL/I VIEW and the PREPARE.SVVPSRC=Y If >=1 Rule and components and If Rebuild contains component generated PL/I VIEW aligned and the PREPARE.SVVPASRC=Y If >=1 Rule and components and If Rebuild contains component generated ASM VIEW and the PREPARE.SVVASRC=Y If >=1 Rule and components and If Rebuild contains component generated ASM VIEW aligned and the PREPARE.SVVAASRC=Y If >=1 Rule and components and If Rebuild contains component generated C VIEW and the PREPARE.SVVCSRC=Y If >=1 Rule and components and If Rebuild contains component generated C VIEW aligned and the PREPARE.SVVCASRC=Y
SVSTRDSN - Saved extracted set reference file
SVERRDSN Saved the generated set errors SVWNDDSN - Saved window source SVHLPDSN - Saved window help source SVFLPDSN - Saved extracted file prepare for PL1 SVFLBDSN - Saved extracted file prepare for COBOL
SVFLCDSN - Saved extracted file prepare for C
SVBNXDSN - Saved generated bind file in PDS
SVVCBDSN - Saved extracted view prepare for cobol
SVVCADSN - Saved extracted view prepare for cobol aligned
SVVPLDSN - Saved extracted view prepare for PL/I
SVVPADSN - Saved extracted view prepare for PL/I aligned
SVVASDSN - Saved extracted view prepare for ASM
SVVAADSN - Saved extracted view prepare for ASM aligned
SVVCDSN - Saved extracted view prepare for C
SVVCADSN - Saved extracted view prepare for C aligned
C-3
Table 3-1
Allocation Matrix (Continued) Dataset Allocated STCOBDSN - Set library for Cobol STREFDSN - Set library for reference files STPL1DSN - Set library for PL1 STCDSN - Set library for C
Conditions Causing Allocate If Rebuild contains Sets for COBOL If Rebuild contains Sets for Reference files If Rebuild contains Sets for PL/I If Rebuild contains Sets 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 Matrix 2 Contents Rebuild Prepare Results File Rebuild Install Parms File RBD Install Driver Res File Rebuild Prepare Parms File RBD Install Stat Link Res File RBD Install Copy PDS Res File RBD Install Copy VSAM Res File RBD Install Top Bind Res File RBD Install LU2 Res File RBD Install Intr Bind Res File RBD Install Pkg Bind Res File RBD Install CICS LU2 Error RBD Install IMS LU2 Error RBD Install IMS LU2 Retcode RBD Install CICS LU2 Retcode Rebuild Prepare Detail File Rebuild Prepare Count Detail File Rebuild Install Count Report Rebuild Install Detail Report DDNAME of File RBDPRES RBDIPARM RBDIRES RBDPPARM RBDISRES RBDIPRES RBDIVRES RBDITRES RBDILRES RBDIIRES RBDIGRES RBDICLU2 RBDIILU2 RBDIILUR RBDICLUR RBDPDTL RBDPCNT RBDICNT RBDIDTL
C-4
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
M
ME (maintain entity) action 2-7, 4-2, 4-22 MR (maintain relation) action 2-10, 4-2, 4-22
E
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
N
naming attributes 4-4
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
F
filters for rebuild contents ?? to 4-20
H
has-root relationship 1-5
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
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
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 Description:

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 Enterprise Rebuild Guide September, 2002

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

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

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

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

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

UNDERSTANDING REBUILD PROCESSING

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Understanding Rebuild Package Components

Understanding Rebuild Package Components

Rebuild Processing Terms

Understanding Rebuild Processing

Rebuilding Package Entities

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Rebuilding Package Entities

Creating the Rebuild Package

Understanding Rebuild Processing

Rebuilding Package Entities

Selecting Objects for Rebuild Processing

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

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

Step 1 - Create the Rebuild Package

Host Workbench panel Host Workbench

Command ===> _______________________________________________________________

Step 1 - Create the Rebuild Package

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Step 1 - Create the Rebuild Package

Step 1 - Create the Rebuild Package

Naming the rebuild package entity Add an Entity V: 2 Project: DEV

Repository: SUNRISE Rebuild Package Name . . . . System Id . . Description .

Rebuild Package State . . . :

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

Step 1 - Create the Rebuild Package

Maintaining the rebuild package entity Maintain an Entity More +

Rebuild Package Attributes: Name . . . . . . . . . . System Id . . . . . . . . Description . . . . . . . Rebuild Package State . .

DMC_VER2_RBD AA5ENR To rebuild migrated DMC_App_l 18 N/A

Step 2 - Select Objects for Rebuild Processing

Step 2 - Select Objects for Rebuild Processing

Creating Relations from the Rebuild Package Entity

AppBuilder 2.0.3.1 Enterprise Rebuild Guide

. DMC_VER2_RBD : AGWASR . ____________ : 9 RBDA Successful w/Exceptions

Action RPREPARE

DMC_VER2_RBD_ AA5ENR ______________ 12 Rebuild Prepare Executing