App Build Information Model

BluePhoenix AppBuilder 2.1.0.
Information Model Reference Guide
BluePhoenix AppBuilder 2.1.0. Document Title April, 2003 Corporate Headquarters BluePhoenix Solutions Vlierwerf 7B 4704 SB Roosendaal The Netherlands +31 (0) 165 399 401 +31 (0) 165 396 308 fax 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-2003 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.1.0 Information Model Reference Guide
1 Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Understanding the Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Information Model Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Entity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Relationship Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Submodels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Internal Object Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Accessing Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Comparative Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Common Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Diagrammatic Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
2 Entity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Common Properties of Entity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Common Entity Type Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Entity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Bitmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Bitmap Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Business Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Component Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 Drawing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21 Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25 File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29 Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31 Logical Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33 Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36 Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38 Physical Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43 Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45 Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47 Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50 Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50 State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53 Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55 Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57 Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58 View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58 Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
3 Relationship Types
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Common Properties of Relationship Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Common Relationship Properties Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Relationship Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Relationship Type Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Relationship Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Accesses (is-accessed-by). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Affects (is-affected-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Can-Access (can-be-accessed-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Causes (is-caused-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Cites (is-cited-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Comprises (is-comprised-of) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Connects (is-connected-to) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Contains (is-contained-in) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Converses (is-conversed-by). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14 Depends-on (is-depended-on-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15 Encapsulates (is-encapsulated-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 Has (is-had-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 Has STD (has-a-state-transition-diagram) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Impacts (is-impacted-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Includes (is-included-in) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20 Influences (is-influenced-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21 Initiates (is-initiated-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22 Intersects (intersects-with) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22 Invokes (is-invoked-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23 Is-carried-out-at (Carries Out). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24 Is-composed-of (Composes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24 Is-constrained-by (Constrains) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25 Is-defined-by (Defines) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25 Is-described-by (Describes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26 Is-distributed-at (Where-is-distributed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
ii
Is-forwarded-to (Is-forwarded-from) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27 Is-implemented-by (Implements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27 Is-involved-in (Involves) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29 Is-keyed-by (Keys) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29 Is-modified-at (Where-is-modified) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 Is-modified-by (Modifies). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 Is-preconditioned-by (Preconditions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31 Is-profiled-by (Profiles). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32 Is-referenced-by (References) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32 Is-replaced-by (Replaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33 Is-related-via (Relates). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33 Is-responsible-for (is-the-responsibility-of) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34 Is-site-of (Has-as-its-site) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 Is-typed-by (Types) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 Maps (is-mapped-to). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 Member (is-member-of) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36 Owns (is-owned-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36 Partitioned (partitioned-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38 Refers-to (is-referred-to-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38 Refines-into (is-refined-from) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39 Replaces System (System is-replaced-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40 Results-in (is-the-result-of). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41 Stores (provides-storage-for) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42 Supports (Is-supported-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43 Triggers (is-triggered-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44 Uses (is-used-by) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
4 Text Property Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

General Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Abbreviation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
5 Enterprise Administration Information Model . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Administration Information Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 User Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Group Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Project Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
6 Enterprise Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Using the Enterprise Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Listing of Enterprise Repository Objects, Methods, and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
A Backwards Compatibility
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
New Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1 Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1 Database Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2 File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2 Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2 Help Text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2
Table of Contents
iii
Logical Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Rebuild Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 New Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 Is-carried-out-at. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 Is-involved-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Is-modified-by . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Is-profiled-by . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Is-responsible-for. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Is-signatured-by . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Is-site-of . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Is-supported-by . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Refines-into . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Replaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
CHAPTER
INFORMATION MODEL
The AppBuilder Information Model is the collection of object types available to business planners, analysts, system designers, and developers who work in the AppBuilder environment. This guide provides information about the entity types and relationship types within the Information Model. These entity types and relationship types are listed alphabetically, and each listing includes a description about the object and its properties.
Understanding the Information Model

The Information Model is a collection of entity types and relationship types, collectively called object types. This discussion includes: Information Model Elements Accessing Properties Comparative Terminology Common Properties Diagrammatic Summary You tailor object types when you build an application. When you assign a unique name to an object type, you create an object, which is an instance of that object type. For example, a File entity type designed to hold business addresses might be called CUSTOMER_ADDRESSES. You build models of your business and you design and develop applications by defining particular instances of these object types, making them unique by defining their properties. Thus, you use object types to create objects. You should use nouns to represent the names of instances of entity types. For example, an instance of the Rule entity type that gets customer information from a file might be called CUSTOMER_FETCHER. You should also use a noun-verb-noun combination to represent instances of relationship types. For example, the relationship instance between the rule and the file just mentioned is CUSTOMER_FETCHER accesses CUSTOMER_ADDRESSES.
1-1
Information Model Elements

The elements of the Information Model include: Entity Types Relationship Types Properties Repositories Submodels Internal Object Types
Entity Types
An entity type is essentially anything about which you can store data (for example, a table, a person, or a corporation). In Information Model diagrams, entity types appear as boxes and their names appear as nouns.
Relationship Types
A relationship type indicates how an entity type interacts with another entity type. In Information Model diagrams, relationship types appear as lines and their names appear as verbs. Because a relationship type always connects two entity types, you can view the relationship from the perspective of either entity. For example, a Process is-defined-by a Rule or a Rule defines a Process are two different ways of looking at the same relationship.
Properties
Properties (or attributes) define both entity types and relationship types. (In the Construction Workbench interface, Properties refer to properties of entity types and Relationship Properties refer to properties of relationship types. There may be several specific properties of an object type. There are three possible statuses for a property. If it is a required property, you must provide a value for it to save the instance successfully. If it is an optional property, you can save the instance without providing a value for it. If it is a generated property, the AppBuilder environment populates it and you cannot alter it.
Repositories
The models and applications that you build are stored in repositories. There are three implementations of repositories in the AppBuilder Environment: Personal (local) repository Workgroup (server) repository (also called Freeway) Enterprise (mainframe) repository
1-2
Information Model
The personal repository resides on a workstation along with a series of development tools you can use to build new or edit existing instances of repository object types. The personal repository stores the data that is accessed by all the tools. The workgroup repository is a server-based or departmental repository that resides on a network server. Developers can simultaneously view and access any objects in this repository. The enterprise repository resides on the host (mainframe). Developers can upload and download objects between this repository and a workstation Personal Repository. Repositories store data about your business and the system you are building, and all basically use the same Information Model, though there are a few differences between the workstation and host objects (see Appendix A, Backwards Compatibility). For more details, refer to the Personal Repository Administration Guide and the Freeway Repository Administration Guide.
Submodels
The Information Model can be broken down into functional subsets called submodels. For example, the part of the Information Model that deals with security can be viewed as the Security submodel (see Diagrammatic Summary on page 1-6 for more information). All object types are part of the Information Model unless otherwise noted. Generally, this guide presents a property of an object type as it appears on the workstation, which may differ slightly from the way it appears on the host. For instance, properties that appear as check boxes on the workstation usually require you to choose between two items and perform a numeric selection on the host.
Internal Object Types

There are a few entity and relationship types that the AppBuilder environment uses internally. These objects are generally invisible to you while you are working within the environment. However, you must separately upload and download these objects to and from the host; these objects are consequently visible within the Repository Maintenance tool and may be referred to during a workgroup or enterprise repository migration. This manual lists these objects in the event that you need to identify them during host communications, but they are not otherwise available for your use.
1-3
Accessing Properties
Accessing Properties
To access the properties (of entity type objects or relationship type objects), from the Construction Workbench, right-click on objects in the Hierarchy window (in any of the tabs: Project, Configuration, Repository, Inverted).
Figure 1-1 Accessing Properties from the Construction Workbench
OR
To access the properties from the Freeway Explorer, select Objects > Query. Select an object and doubleclick on the object in the main window. The Properties dialog opens (Figure 1-2). The dialog has several tabs.
Figure 1-2 Properties Dialog
The General tab contains the editable properties of that entity. The Audit tab contains the common properties of that entity. The Remote Audit tab contains information about migration of the entity to and from the enterprise repository. The Text tab contains a space for you to enter descriptive text about that entity. The Keywords tab contains a space for you to enter a list of keywords to associate with that entity.
1-4
Information Model
Comparative Terminology
Comparative Terminology
The use of entity types in AppBuilder is significantly different from the use of their third-generation language equivalents in a traditional development environment. If you have programmed using a traditional language, such as COBOL or PL/I, Table 1-1 describes the purpose of some of the Information Model entity types. Table 1-1 lists several Information Model entity types commonly used during system development, along with the closest corresponding term.
Table 1-1 Information Model Terms Compared with 3GL Terms AppBuilder term Process Rule Window Component View Field File
Traditional term Menu item Paragraph or routine Screen Subroutine Record Field or variable File or table
Keep in mind that the correspondences are not exact equivalents. For example, the View entity type is not the same as a 3GL environment Record. In AppBuilder, a View constitutes a data definition, which you can attach to a file. In this case, a view would, in effect, define a record. You also can use the same view to define the output of a rule used to populate the file, or associate it with a window used to display the data.
Common Properties
All entity types have common properties. All common properties except System ID are the entity types Audit properties. The Audit properties (except for local date and local time) are not populated until the entity type has either been created on the host (either directly or by uploading) or committed to the workgroup repository. In the enterprise repository on the host, all properties appear on the main screen for each object type, and may appear in a different order. In the personal and workgroup repositories on the workstation, Name and System ID, as well as all properties unique to each object type, appear on the General tab of the Properties dialog for that object type. Audit properties appear on the entity types Audit tab (see Figure 1-3).
1-5
Diagrammatic Summary
Figure 1-3
Audit and Remote Audit Tabs
Property names may be slightly different among the workstation and host repositories, and some properties may not appear in both (see Appendix A, Backwards Compatibility). The following list indicates how each property appears in the host and workstation repositories. If not specified, the name is the same in all repositories.
The following diagrams graphically illustrate many of the entity and relationship types described in this book. The Information Model is divided into the following views: Design and Construction: Data View Design and Construction: Data Traceability View Design and Construction: Process View Security View
1-6
Information Model
Figure 1-4
owns refines-into
Design and Construction: Data View
is-based-on
is-fowarded-to FILE
BUSINESS OBJECT
ENTITY
TABLE has has is-referenced-by
is-related-via
is-described-by
owns
relates-via
includes IDENTIFIER KEY VIEW
RELATIONSHIP is-composed-of
is-composed-of has
includes
is-described-by
ATTRIBUTE
composes
COLUMN
FIELD
is-typed-by SET composes DATA TYPE
is-constrained-by
Figure 1-5
is-implemented-by
Design and Construction: Data Traceability View
is-implemented-by connects-to ENTITY is-implemented-by is-implemented-by is-implemented-by
TABLE
RELATIONSHIP
is-implemented-by FILE
connects-to
is-implemented-by IDENTIFIER connects-to COLLECTION is-implemented-by
KEY
ATTRIBUTE
connects-to is-implemented-by
COLUMN
is-implemented-by
1-7
Figure 1-6
Design and Construction: Process View
owns
ENTITY
intersects-with
FUNCTION
depends-on is-implemented-by is-modified-by is-composed-of affects depends-on is-defined-by LOGICAL PROCESS is-implemented-by has is-fowarded-to FILE owns is-accessed-by refers-to is-accessed-by RULE triggers converses uses depends-on PROCESS impacts refines-into
refines-into
WINDOW PHYSICAL EVENT refers-to
owns
owns converses refers-to uses refers-to SET uses REPORT COMPONENT owns contains owns SECTION is-keyed-by FIELD refers-to owns includes owns VIEW includes
contains
VALUE
Figure 1-7
Security View
USER contains
PROJECT
is-member-of GROUP
has-access-to
is-owned-by
INSTANCE OF OBJECT TYPE
is-owned-by
1-8
Information Model
CHAPTER
ENTITY TYPES
An object type is anything about which information can be stored in the AppBuilder repository. Object types have properties that describe them. There are two categories of object types in the repository: entity types and relationship types. This section lists properties common to all entity types and then provides a detailed description of each entity type. This chapter includes: Common Properties of Entity Types Entity Types In the entity type descriptions, each entry starts with a description of the entity type and how it is used, a screenshot of the Properties dialog, specifically the General tab where properties can be edited, a table listing its specific properties, and the relationships associated with the entity type. Name and System ID properties are described as common properties because their general characteristics are discussed in Common Properties of Entity Types. The Relationship section describes how each Entity type is related to other Entity types. See Chapter 3, Relationship Types for details of the relationship types and their properties.
Common Properties of Entity Types

The common properties of entity types in the AppBuilder Information Model include: Name System ID Owner Project Explicit lock (Personal or Workgroup) QA status (Personal and Workgroup) Change number Created/Remote date (Personal or Workgroup) Date created (Enterprise) Created/Remote time (Personal and Workgroup)
2-1
Time created (Enterprise) Created/Remote user (Personal and Workgroup) Created by (Enterprise) Maintained/Remote date (Personal and Workgroup) Date maintained (Enterprise) Maintained/Remote time (Personal and Workgroup) Time maintained (Enterprise) Maintained/Remote user (Personal and Workgroup) Maintained by (Enterprise) Maintained/Local date (Personal and Workgroup) Maintained/Local time (Personal and Workgroup) Version (Enterprise only)
Common Entity Type Property Descriptions

Name Status: Required Unique name, up to thirty (30) characters in length, identifies each instance of an object type. Names should adhere to text standards (see Chapter 4, Text Property Conventions) in order to facilitate reuse. Since names provide information about the function and purpose of an object instance, failure to adhere to a standard naming convention makes it hard to quickly locate and use an existing instance. Follow these general guidelines for creating names: Abbreviate. Use abbreviations where necessary. (See Abbreviation Guidelines on page 4-2.) No Spaces. An instances name cannot contain spaces. To separate character strings in a name, use an underscore (_) between each word. Object-Action. Names should describe the function or purpose of an instance by first describing what it is and then describing what it does. Names are stored in uppercase. Take this into account when performing comparisons in the rule source code. System ID Status: Generated An alphanumeric string the AppBuilder environment uses internally to refer to the instance of the object type. Each instance has a unique System ID. During workstation installation, a workgroup repository (Freeway) System ID (a number between 400 and 1295) for your workstation was entered. An instances System ID is generated from this number. For an instances System IDs to be unique across an application, the Freeway System ID chosen at installation must be unique from all other developers of that application.
2-2
Entity Types
Owner Status: Generated ID of the current owner of the instance. Can be different from the ID generated for the created/remote user property. Project Status: Generated Name of the project to which the instance belongs. Explicit lock (Personal or Workgroup) Status: Generated The field on the left side of the window indicates whether the instance is locked (Y) or not locked (N). If it is locked, the field on the right side of the window lists the ID of the user who locked it. If an instance is locked, you cannot change it in the enterprise repository either directly or by uploading. QA status (Personal and Workgroup) The AppBuilder environment does not currently use this property. Change number Status: Generated System-generated number to protect instances of an object from simultaneous changes from two users. An instance can be uploaded only if its change number matches the change number in the enterprise repository. Created/Remote date (Personal or Workgroup) Date created (Enterprise) Status: Generated Format: YY/MM/DD Date the instance was first created in the enterprise repository, either directly or by uploading. Created/Remote time (Personal and Workgroup) Time created (Enterprise) Status: Generated Format: HH:MM Time the instance was first created in the enterprise repository, either directly or by uploading. Created/Remote user (Personal and Workgroup) Created by (Enterprise) Status: Generated ID of user who created the instance in the enterprise repository, either directly or by uploading.
2-3
Entity Types
Maintained/Remote date (Personal and Workgroup) Date maintained (Enterprise) Status: Generated Format: YY/MM/DD Date the instance was last changed in the enterprise repository, either directly or by uploading. Maintained/Remote time (Personal and Workgroup) Time maintained (Enterprise) Status: Generated Format: HH:MM Time the instance was last changed in the enterprise repository, either directly or by uploading. Maintained/Remote user (Personal and Workgroup) Maintained by (Enterprise) Status: Generated ID of last user who changed the instance in the enterprise repository, either directly or by uploading. Maintained/Local date (Personal and Workgroup) Status: Generated Format: YY/MM/DD Date the instance was last changed on the workstation. Maintained/Local time (Personal and Workgroup) Status: Generated Format: HH:MM Time the instance was last changed on the workstation. Version (Enterprise only) Status: Generated Identifies the logical repository in which this instance resides.
Entity Types
The entity types in the AppBuilder Information Model (in alphabetical order) are shown in Table 2-1.
Table 2-1 Information Model Entity Types Event Field File Function Identifier Relationship Report Rule Section Server Application Configuration Attribute Bitmap Bitmap Implementation Business Object
2-4
Entity Types
Entity Types
Table 2-1 Collection Column
Information Model Entity Types (Continued) Key Logical Process Machine Migration Partition Physical Event Process State Set Symbol Table Transition Value View Window
Component Component Folder Database Data Type Drawing Entity
Properties
Refer to Common Properties of Entity Types for properties common to all entity types. Properties specific to each of the listed entity types are shown in the Properties Table under each entity heading. If there is no Properties Table, that indicates there are no properties specific to that entity type.
Application Configuration
The Application Configuration entity type (Figure 2-1) encapsulates the information needed to prepare a client-server application, to migrate it to a production environment, and to administer it at run-time.
Figure 2-1 Application Configuration Properties Dialog
Relationships Application Configuration has the Partition Inverse Relationships Application Folder contains an Application Configuration Application Configuration partitions a Function. This is the inverse relationship added for a Function; the relationship already exists in the relationships list.
Attribute
The Attribute (Figure 2-2) describes the characteristics or properties of an entity or a relationship. Typically, you define instances of Attributes during business object analysis to provide details for your data model. For example, if you have an object called Customer, you might create attributes called First_Name, Last_Name, Street_Address, and so on.
2-5
Entity Types
Figure 2-2
Attribute Properties Dialog
Table 2-2
Attribute properties Property Description Status: Required Default is Fundamental mDomAttributeType The following choices are available: Fundamental Derived Status: Optional Can contain a maximum of 240 characters
Field in Dialog
Derived
Attr_Derived
N/A
DerivationFormula
Relationships Attribute is customized to Attribute Attribute is composed of Attribute Attribute is composed of Relationship Attribute is typed by Data Type Attribute is domained by Business Data Domain Inverse Relationships Application Folder contains Attribute ER View involves Attribute Comm Flow transports Attribute Scheme maps to Attribute Value maps to Attribute Business Concept maps to Attribute Business Object is customized to Attribute Event is customized to Attribute Business Data Domain is customized to Attribute Relationship is customized to Attribute Entity is customized to Attribute Entity is described by Attribute Relationship is described by Attribute
2-6
Entity Types
Entity Types
Attribute is composed of Attribute Identifier describes Attribute
Bitmap
The Bitmap entity type (Figure 2-3) represents a bitmap. A bitmap object is used to add graphic interest to windows and to camouflage hot spot objects.
Figure 2-3 Bitmap Properties Dialog
Table 2-3
Bitmap Properties Property Description Status: Optional Default is Bitmap mDomBmpType The following choices are available: Bitmap Icon Pointer JPEG Status: Generated Can contain a maximum of 8 characters Status: Optional Up to 30 characters of additional information
Field in Dialog
Type
Bitmap_Type
Implementation Name Description
Bipmap_Imp_Name Description
Relationships Bitmap has Bitmap Implementation Inverse Relationships Application Folder contains Bitmap Function has Bitmap Process has Bitmap Report has Bitmap Rule has Bitmap Window has Bitmap
2-7
Entity Types
Bitmap Implementation
The Bitmap Implementation is entity type that manages the physical files that can comprise a bitmap. It exists to facilitate uploading objects to the host.
Table 2-4 Property Bitmap Implementation Properties Description Status: Optional Default is English (US) mDomCountryLanguage The following choices are available: English (US) English (UK) Status: Optional Can contain a maximum of 5 characters Status: Optional Can contain a maximum of 5 characters Status: Optional Default is BMP mDomBMPFormatType The following choices are available: BMP ICR PTR JPEG GIF WAV AVI MOV MPEG QTW Status: Optional Up to 30 characters of additional information that describes the bitmap
CountryLanguage
X_Res Y_Res
FormatType
Description
Inverse Relationships Bitmap is-had-by Bitmap Implementation
Business Object
The Business Object (Figure 2-4) groups together a set of entities.
2-8
Entity Types
Entity Types
Figure 2-4
Business Object Properties Dialog
Table 2-5
Business Object Properties Property Description Description Status: Optional Up to 30 characters of additional information that describes the Business Object Status: Required Default is Referential mDomBusinessObjectType Designates the type of Business Object. The following choices are available: Referential Transactional
Field in Dialog Description
Type
BusObj_Type
Relationships Business Object data-content-defined-by ER View Business Object has State Business Object has-STD Drawing Business Object owns Entity Business Object owns Event Business Object owns Business Object Business Object owns Logical Process Business Object refines-into Business Object Business Object has member Entity Business Object has member Class Property Business Object has member Class Domain Business Object has member Class Object Business Object has member Class Relationship
2-9
Entity Types
Table 2-6 FROM
Customized_To Relationships TO Logical Process Entity Attribute Critical Business Process Customized Logical Workflow Logical Business Function Business Object Business Data Domain Relationship Event
Logical Business Function Logical Workflow Business Object Attribute Logical Process Business Data Domain Event Relationship Critical Business Process Entity
Inverse Relationships Event influences Business Object Application contains Business Object Scheme maps to Business Object Value maps to Business Object Business Concept maps to Business Object Logical Business Function maps to Business Object Model Scope includes Business Object Event influences Business Object
Collection
The Collection entity type (Figure 2-5) stores internal traceability information. You can view this entity type, but you should not modify it.
Figure 2-5 Collection Properties Dialog
2-10
Entity Types
Entity Types
Table 2-7 Property Type
Collection Properties Description Status: Optional The type of the Collection. Maximum of 3 characters. Status: Required The nature of the Collection. The following choices are available: Logical Physical Relational Status: Optional The number of elements in the Collection. This can be a numeric Value from 0 to 99. Status: Optional The number of groups in the Collection. This can be a numeric Value from 0 to 99.
Nature
Number of elements Number of groups
Relationships Collection connects-to Collection Collection connects-to Column Collection connects-to Key Collection connects-to Table Collection is-implemented by Collection Collection is-implemented by Column Collection is-implemented by File Collection is-implemented by Key Collection is-implemented by Table Collection implements Collection Inverse Relationships Attribute connects-to Collection Attribute is-implemented-by Collection Collection is-connected-to Collection Collection is-implemented-by Collection Data type connects-to Collection Data type is-implemented-by Collection Entity connects-to Collection Entity is-implemented-by Collection Identifier connects-to Collection Identifier is-implemented-by Collection Relationship connects-to Collection Relationship is-implemented-by Collection Table is-implemented-by Collection
2-11
Entity Types
Column
The Column entity type (Figure 2-6) represents a column in a database.
Figure 2-6 Column Properties Dialog
Table 2-8
Column Properties Property Description Status: Optional Can contain a maximum of 30 characters Maximum of 30 alphanumeric characters (18 for DB2 and DBM Databases), the first of which must be alphabetic. Status: Required Default is Character The following choices are available: Boolean Object Reference (not implemented) Character Date Decimal Graphic Character (DBCS) Image Mixed Character Picture Small Integer or Integer Text Time Timestamp VarChar Status: Generated if column format is Date, Time, or Timestamp. Required for any other column format. Can contain a maximum of 5 characters Default is Character How large the column is. The value range for this property depends on the column format, as shown in Table 2-8. Status: Optional Can contain a maximum of 2 characters Default is 0 Number of decimal places. For decimal and picture Column Formats, the Column fraction can range from zero to the Column length. For other Column Formats, this property is irrelevant. Status: Optional Can contain a maximum of 5 characters The average length of the Column. This can be a numeric Value from 0 to 99,999.
Field in Dialog Implementation name
Col_Imp_Name
Column format
Col_Type
Column length
Col-Length
Column fraction
Col_Scale
Average length
Col_Avg_Length
2-12
Entity Types
Entity Types
Table 2-9
Minimum and Maximum Column Lengths (according to column format) Minimum length 1 4 1 1 1 1 Small: 15; Integer: 31 4 12 1 Maximum length 4,000 4 31 2,000 4,000 30 Small: 15; Integer: 31 4 12 4,000
Column Format Character Date Decimal Graphic Character (DBCS) Mixed Character Picture Small Integer or Integer Time Timestamp VarChar
Inverse Relationships Attribute connects-to Column Attribute is-implemented-by Column Collection connects-to Column Collection is-implemented-by Column Data type connects-to Column Data type is-implemented-by Column Entity connects-to Column Entity is-implemented-by Column Identifier connects-to Column Identifier is-implemented-by Column Key has Column Relationship connects-to Column Relationship is-implemented-by Column Table has Column Table is-implemented-by Column
Component
The Component entity type (Figure 2-7) contains code written in a third-generation computer language, such as C, COBOL, assembler, or PL/I, to do things that the Rules Language either cannot do, or cannot do efficiently. This might be a complicated arithmetic algorithm (such as a square root), nonSQL data access logic (such as an IMS Database interface), or hardware-specific functions. Components also support the concept of reengineering, where existing applications can be defined to the repository. Because components are written for a specific processing environment, they are not portable between environments.
2-13
Entity Types
Figure 2-7
Component Properties Dialog
Table 2-10 Component Properties Field in Dialog Description Property Component Description Status: Optional Up to 30 characters of additional information that describes the Component. Status: Required Can contain a maximum of 4 characters Default is N/A mDomCompDBMSUsage Defines if the Component accesses a Database. The following choices are available: DB2 DL/I N/A Status: Required Can contain a maximum of 6 characters Default is PC (PC Workstation) mDomCompExecEnv The following choices are available: IBM Mainframe Batch PC User Component PC Workstation IBM Mainframe (CICS) IBM Mainframe (IMS) IBM Mainframe (CICS & Batch) PC System Component
DBMS usage
DBMS_Usage
Execution environment
Exec_Environ
2-14
Entity Types
Entity Types
Table 2-10 Component Properties (Continued) Field in Dialog Implementation name Property Comp_Imp_Name Description Status: Optional Maximum of 8 alphanumeric characters, the first of which must be alphabetic. Status: Required Can contain a maximum of 8 characters Default is C mDomLanguage The Language the Component is written in. The following choices are available: Assembler , C, COBOL, PL/I, JAVA, PTAL Status: Required Can contain a maximum of 4 characters Default is N mDomExecutionMode Defines if the Component has a subroutine. The following choices are available: Has a subroutine No subroutine Status: Required Can contain a maximum of 3 characters Default is N/A
Language
Language
Subroutine (Y/N)
Exec_Mode
Sys_Source
Sys_Source
Relationships Component is-accessed-by File Component owns View Component refers-to Set Component uses Component Inverse Relationships Component is-used-by Component Partition encapsulates Component Rule uses Component
Component Folder
The Component Folder is a storage mechanism for objects (like files) that are not generated by AppBuilder. These are objects that do not fall into the usual object categories but the objects can be described (embodied) by file representations. Such objects are now represented within the repository using a Component Folder object. Each Component Folder represents one non-AppBuilder object.
2-15
Entity Types
Figure 2-8
Component Folder Properties Dialog
Table 2-11 Component Folder Properties Property Folder Type Description Description Status: Optional Can contain a maximum of 30 characters Status: Optional Can contain a maximum of 60 characters
Relationship Component Folder content is Component Folder File Inverse Relationships Application Folder contains Component Folder Function has Component Folder Process has Component Folder Report has Component Folder Component has Component Folder Window has Component Folder Rule has Component Folder
Database
The Database entity type (Figure 2-9) represents a database in a network configuration.
2-16
Entity Types
Entity Types
Figure 2-9
Database Properties Dialog
Table 2-12 Database Properties Field in Dialog Machine name Property Machine_Name Description Status: Required The Machine associated with the Database in a Partition. Maximum of 30 characters. Status: Required Default is DB2 mDomDBMStype The Database type. The following choices are available: DB2 Oracle MS-SQLServer DB2/UDB Status: Required The run time directory path. Maximum of 100 characters. Status: Optional Can contain a maximum of 30 characters
Type
DBMS_Type
Database directory path Implementation name
DB_Imp_Direct DB_Imp_Name
Relationships Database contains Table Database is-accessed-by File Database is-related-to Database Inverse Relationships Partition encapsulates Database Database relates-to Database
Data Type
The Data Type entity type (Figure 2-10) records a physical description of data. Typically, you define instances of Data Type entity types during business object analysis when you build your data model.
2-17
Entity Types
Figure 2-10
Data Type Properties Dialog
Table 2-13 Data Type Properties Property Description Status: Required Default is Character The following choices are available: Boolean Object Reference (not implemented) Character Date Decimal Graphic Character (DBCS) Image Mixed Character Picture Small Integer or Integer Text Time Timestamp VarChar Status: Generated if column format is Date, Time, or Timestamp. Required for any other column format. Can contain a maximum of 5 characters Default is Character How large the column is. The value range for this property depends on the column format, as shown in Table 2-14. Status: Optional Can contain a maximum of 2 characters Default is 0 Number of decimal places. For decimal and picture Column Formats, the Column fraction can range from zero to the Column length. For other Column Formats, this property is irrelevant.
Data Format
Data Length
Data Fraction
Table 2-14 Minimum and Maximum Field Lengths (according to data format) Data Format Character Date Decimal Graphic Character (DBCS) Mixed Character Picture Minimum length 1 4 1 1 1 1 Maximum length 4,000 4 31 2,000 4,000 30
2-18
Entity Types
Entity Types
Table 2-14 Minimum and Maximum Field Lengths (according to data format) (Continued) Data Format Small Integer or Integer Time Timestamp VarChar Minimum length Small: 15; Integer: 31 4 12 1 Maximum length Small: 15; Integer: 31 4 12 4,000
Relationships Data Type composes Data Type Data Type connects-to Collection Data Type connects-to Column Data Type connects-to Key Data Type connects-to Table Data Type is-constrained-by Set Data Type is-implemented-by Collection Data Type is-implemented-by Column Data Type is-implemented-by File Data Type is-implemented-by Key Data Type is-implemented-by Table Inverse Relationships Attribute is-typed-by Data Type Data Type is-composed-of Data Type
Drawing
The Drawing entity type (Figure 2-11) is a graphic representation of a user-defined model built of AppBuilder entity and relationship types. Drawing entity types are created on the workstation with the following tools: Entity-Relationship Diagrammer Process Dependency Diagrammer State Transition Diagrammer Matrix Builder Window Flow Diagrammer Database Diagrammer Each Drawing entity has a drawing file with references to the object types in the drawing, but not to their definition. Drawing entity type relationships may not be viewed outside of these environments.
2-19
Entity Types
Figure 2-11
Drawing Properties Dialog
Table 2-15 Drawing Properties Field in Dialog Property Description Status: Generated Can contain a maximum of 3 characters Default is State Transition mDomDrawing Drawings are diagrams that can be reused. They are created with Construction Workbench tools. The drawing type indicates the tool used to make the drawing. For example, the Entity Relationship Diagram tool creates entityrelationship diagrams. The values for the types of drawings are summarized in Table 2-17.
Type
Drawing_Type
Table 2-16 Drawing entity type Property Name System ID ShortName Description Status: Required Common Property Status: Generated Common Property Status: Optional Can contain a maximum of 8 characters Status: Generated Can contain a maximum of 3 characters Default is State Transition mDomDrawing Drawings are diagrams that can be reused. They are created with Construction Workbench tools. The drawing type indicates the tool used to make the drawing. For example, the EntityRelationship Diagrammer creates entity-relationship diagrams. The following table shows the values for the types of drawings, as shown in Table 2-17.
Drawing_Type
Table 2-17 Drawing description and values Description State Transition Entity Relationship Process Dependency Window Flow Database Diagram Physical Network Data Store vs Entity Function vs Entity Values 001 002 003 010 011 012 013 014
2-20
Entity Types
Entity Types
Table 2-17 Drawing description and values (Continued) Description Function vs Location Entity vs Location 1 Entity vs Location 2 Organization vs Entity Process vs Entity Organization vs Process Matrix System vs Process Class Interaction Values 015 016 017 018 019 020 021 022 023
Inverse Relationships Business Object has-a-state-transition Drawing Entity has-a-entity-relationship Drawing Entity has-a-state-transition Drawing Event has-a-process-dependency Drawing Logical Process has-a-process-dependency Drawing State has-a-state-transition Drawing
Entity
The Entity entity type (Figure 2-12) describes the data an enterprise or organization uses. Typically, you define instances of entity object types during business object analysis when you build the data model. For example, an enterprise that rents automobiles might have a customer entity, a reservation entity, and a rental location entity.
Figure 2-12 Entity Properties Dialog
The following entity types are available:
2-21
Entity Types
Kernel A kernel entity is a basic entity that can exist independently from other entities in a logical model. This does not imply that it cannot have a relationship with other objects; rather, it implies the entity must be a unique object with its own Identifier. A kernel entity should not need relationships with other entities to be identified. AssociativeAn associative entity associates two or more kernel or characteristic entities. Associative entities contain non-key properties and can be used to resolve many-to-many relationships. CharacteristicA characteristic entity is a weak or dependent entity because it requires the existence of another entity in a logical model. Characteristic entities describe a kernel entity. IntersectionAn intersection entity associates two or more kernel entities and contains no properties. An intersection entity is the primary way to resolve many-to-many relationships between entities.
Table 2-18 Entity Properties Field in Dialog Property Description Status: Required Can contain a maximum of 20 characters Default is Kernel mDomEntityType The following choices are available: Kernel Associative Characteristic Intersection Status: Optional Can contain a maximum of 5 characters User-defined lower limit of the expected size of the instance (number of Fields). This can be a numeric Value from 0 to 99,999. Status: Optional Can contain a maximum of 10 characters User-defined upper limit of the expected size of the instance (number of Fields). This can be a numeric Value from 0 to 9,999,999,999. Status: Required Can contain a maximum of 5 characters Default is Day mDomDurarion Time period that describes the frequency of various operations performed with instances of this entity type. The choices are: Day Week Month Year Quarter Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that instances of this entity type will be created. This can be a numeric value from 0 to 9,999. Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that instances of this entity type will be deleted. This can be a numeric value from 0 to 9,999.
Type
Ent_Type
Expected minimum rows
Exp_Min_Rows
Expected maximum rows
Exp_Max_Rows
Activity period
Exp_Duration
Avg. inserts for period
Ave_Wkly_Inserts
Avg. deletes for period
Ave_Wkly_Deletes
2-22
Entity Types
Entity Types
Table 2-18 Entity Properties (Continued) Field in Dialog Property Description Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that instances of this entity type will be updated. This can be a numeric value from 0 to 9,999. Status: Optional Can contain a maximum of 10 characters The number of instances of this entity type expected when you define the data model. This can be a numeric value from 0 to 9,999,999,999. Status: Optional Can contain a maximum of four characters
Avg. updates for period
Ave_Wkly_Updates
Expected rows
Exp_Rows
N/A
AveGrowthRate
Relationships Entity connects-to Collection Entity connects-to Column Entity connects-to Key Entity connects-to Table Entity has-a-entity-relationship Drawing Entity has-a-state-transition Drawing Entity has State Entity has Identifier Entity is-accessed-by Project Entity is-described-by Attribute Entity is-implemented-by Collection Entity is-implemented-by Column Entity is-implemented-by File Entity is-implemented-by Key Entity is-implemented-by Table Entity is-modified-by Development Project Entity is-modified-by Logical Process Entity is-related-via Relationship Entity owns View Inverse Relationships Assumption is-supported-by Entity Business Object owns Entity ER View involves Entity Function intersects-with Entity Goal is-supported-by Entity Information Need is-supported by Entity
2-23
Entity Types
Logical Process affects Entity Problem affects Entity Problem is-caused by Entity Process impacts Entity Success Factor is-supported-by Entity
Event
The Event entity type (Figure 2-13) represents an incident that acts as a stimulus to a business, system or object. It usually causes some activity or processing to be undertaken and may change the state of objects within the business or system. Events can be classified as external, internal or temporal. Examples are Customer_Calls, Accident_Reported, or Customer_Enters.
Figure 2-13 Event Properties Dialog
Table 2-19 Event Properties Field in Dialog Description Property Event_Description Description Status: Optional Up to 30 characters of additional information that describes the event. Status: Optional Up to 10 characters of additional information that describes the type of event. Status: Required Can contain a maximum of 2 characters Default is External mDomEventClass The choices are: External, Internal, Temporal
Event type
Event_Type
Event class
Event_Class
Relationships Event causes Transition Event composes Event Event is-composed-of Event Event has-a-process-dependency Drawing Event influences Business Object
2-24
Entity Types
Entity Types
Event triggers Process Event triggers Logical Process Inverse Relationships Logical Process initiates Event Business Object owns Event
Field
The Field entity type (Figure 2-14) records information about part of a file (such as a column in a DB2 Table), or part of the input or output definition of other entity types (such as the view owned by a window). The properties of a field describe the type and size of the data it contains. The Field entity type is where you store the definition for each of the fields your application uses. The properties of the Field entity type allow you to specify particular qualities for the data that can populate that field (such as integers, characters, and decimals). Also, see Includes (is-included-in) on page 3-20, and View on page 2-58.
Figure 2-14 Field Properties Dialog
2-25
Entity Types
Table 2-20 Field Properties Field in Dialog Property Description Status: Required if Field format is Picture Status: Irrelevant for other Field formats Form in which the Fields Value should be stored, using the standard COBOL editing characters S (signed number), V (virtual decimal point), and 9 (numeric Value). Status: Optional if Field format is Picture Status: Irrelevant for other Field Formats Displays the Field Values as shown in Table 2-21, using the standard COBOL editing characters. Note: A picture Field can accept 30 display characters, but only 18 of them can be numeric Value (9) characters. This is a COBOL limitation. Status: Optional Static text Window Painter and Report Painter use as a Field label when the Field is pasted onto a window. Maximum of 24 characters. Status: Required Default is Character mDomFieldType The Fields data type. The following choices are available: Boolean Object Reference Character Date Decimal Graphic Character (DBCS) Image Mixed Character Picture Small Integer or Integer Text Time Timestamp VarChar Status: Generated if Field Format is Date, Picture, Time, or Timestamp Status: Required for any other Field Format Can contain a maximum of 5 characters Default is 15 The Value range for this Attribute depends on the Field Format, as shown in Table 2-22. Status: Generated if Field Format is Picture Status: Required if Field Format is Decimal Status: Irrelevant for any other Field Format Can contain a maximum of 2 characters Default is 0 Number of decimal places in the Field. For Decimal Fields, the Field fraction must be greater than or equal to 0 and less than or equal to the Field length. Status: Optional if Field Format is Decimal, Integer, Small Integer, or Picture Status: Irrelevant for other formats Can contain a maximum of 30 characters The minimum value that can be stored in this field.
Field picture-storage
DB_Pic
Field picture-display
Screen_Pic
Screen literal-long
Screen_Lit
Field format
Field_Type
Field length
Fld_Len
Field fraction
Fld_Frac
Range-minimum value
Field_Min
2-26
Entity Types
Entity Types
Table 2-20 Field Properties (Continued) Field in Dialog Property Description Status: Optional if Field Format is Decimal, Integer, Small Integer, or Picture Status: Irrelevant for other formats Can contain a maximum of 30 characters The maximum Value that can be stored in this field. Status: Optional Can contain a maximum of 8 characters System ID of the instance of the set entity type associated with the field and that lists acceptable inputs. Status: Optional Up to 12 characters of static text that report Painter uses as a fields short screen literal property. Status: Optional Name that becomes the DB2 column name. It is limited to 18 characters and must conform to the naming standards for the applications database.
Range-maximum value
Field_Max
Reference table name
Field_Ref
Screen literal-short
Screen_Lit_Short
Implementation name
Field_Imp_Name
Table 2-21 COBOL Editing Characters and Field Display Forms COBOL editing characters 9 * , + $ . S Z B CR DB Field display form numeric value check protection comma plus sign minus sign floating currency symbol decimal point sign leading zero suppression embedded blank credit debit
Table 2-22 Minimum and Maximum Field Lengths (according to field format) Field format Character Date Decimal Graphic character (DBCS) Mixed character Picture Small integer or integer Time Timestamp VarChar Minimum length 1 4 1 1 1 1 Small: 15; Integer: 31 4 12 1 Maximum length 4,000 4 31 2,000 4,000 30 Small: 15; Integer: 31 4 12 4,000
2-27
Entity Types
Relationships Field has Help Text Field refers-to Set Field uses Language Inverse Relationships File is-keyed-by Field View includes Field
File
The File entity type (Figure 2-15) represents a physical data file on a disk. Rules and components can read from and write to disk files whose file entity types they are related to. Files can be automatically generated by AppBuilder tools.
Figure 2-15 File Properties Dialog
Table 2-23 File Properties Field in Dialog Property Description Status: Required Can contain a maximum of 6 characters Default is DB2 mDomFileType The following value is available in the list box: XA DB2 File DBM Informix Sybase Oracle DB2/2 DB2/6000 Tandem Illustra Ingres DB2/400 MS-SQLServer DB2/UDB Status: Required Name that becomes the DB2 Table name. It is limited to 30 characters and must conform to the naming standards for the applications database.
File type
File_Type
Implementation name
File_Imp_Name
2-28
Entity Types
Entity Types
Relationships File is-forwarded-to File File is-keyed-by Field File owns View Inverse Relationships Attribute is-implemented-by File Collection is-implemented-by File Component is-accessed-by File Partition encapsulates File Data type is-implemented-by File Database is-accessed-by File Entity is-implemented-by File Identifier is-implemented-by File Relationship is-implemented-by File Rule is-accessed-by File Table is-implemented-by File
Function
The Function entity type (Figure 2-16) represents one of the major classes of activities for an enterprise, such as leasing, sales, and inventory control. Typically, you define instances of function entity types when you build the process model during analysis. In the execution environment, function names appear on the start-up menu bar. A function typically decomposes into one or more processes that can further decompose into additional processes.
Figure 2-16 Function Properties Dialog
2-29
Entity Types
Table 2-24 Function Properties Field in Dialog Menu description Property Menu_Desc Description Status: Required Up to 30 characters of text that appears as the first level of the menu bar. Status: Required Default is Menu Bar mDomChildMenu Indicates how the processes under this function appear in the interface. The choices are: Menu Bar Pull-Down No menu (Batch) Status: Optional Up to 8 characters that identify a group of applications grouped under this function.
Sub-process menu type
Child_Menu
Application ID
Work_Station_Group
Relationships Function has Bitmap Function intersects-with Entity Function refines-into Process Function partitioned by Application Configuration; the relationship already exists in the list of relationships Inverse Relationships Partition encapsulates Function
Identifier
The Identifier entity type (Figure 2-17) is a logical key that becomes a physical key during database design. An identifier consists of one or more properties that uniquely identify an instance of a parent entity or cross-reference another entity.
Figure 2-17 Identifier Properties Dialog
2-30
Entity Types
Entity Types
Table 2-25 Identifier Properties Field in Dialog Property Description Status: Required Default is Primary mDomIdentifierType The following choices are available in the list box: Primary (key most frequently used) Alternate (second most frequently used key) Candidate (potential, but not preferred key)
Type
Ident_Type
Relationships Identifier connects-to Collection Identifier connects-to Column Identifier connects-to Key Identifier connects-to Table Identifier is-composed-of Relationship Identifier is-composed-of Attribute Identifier is-implemented-by Collection Identifier is-implemented-by Column Identifier is-implemented-by File Identifier is-implemented-by Key Identifier is-implemented-by Table Inverse Relationships ER View involves Identifier Entity has Identifier
Key
The Key entity type (Figure 2-18) describes a key in a database. You can use a key to enforce referential integrity and uniqueness constraints.
Figure 2-18 Key Properties Dialog
2-31
Entity Types
The types of key are: ForeignA foreign key is a unique index into another table and can be used to join two tables. A foreign key is one or more columns that uniquely identify rows in another table that associates two entities through a relationship. PrimaryA primary key (the only required key) is one or more unique columns that identifies a single instance (a row in a table) of an entity. IndexAn index key is one or more non-unique columns that can locate more than one of an entitys instances.
Table 2-26 Key Properties Field in Dialog Property Description Status: Required Default is Index mDomDBtypeKey The type of the key. The following choices are available in the list box: Foreign Primary Index Status: Required mDomBoolean Specifies whether the key is unique. The choices available are: Yes No Status: Required Default is Null mDomKeyDeleteRule Indicates the method of the rule deletion. The following choices are available in the list box: Restrict Cascade Null Status: Optional Maximum of 30 characters Status: Optional
Type
Key_DBType
Unique (check box)
Unique
Deletion method
Key_Delete_Rule
Implementation name N/A
Key_Imp_Name Update_Rule
Relationships Key has Column Inverse Relationships Attribute connects-to Key Attribute is-implemented-by Key Collection connects-to Key Collection is-implemented-by Key Data type connects-to Key Data type is-implemented-by Key Entity connects-to Key Entity is-implemented-by Key
2-32
Entity Types
Entity Types
Identifier connects-to Key Identifier is-implemented-by Key Relationship connects-to Key Relationship is-implemented-by Key Table is-implemented-by Key Table has Key Table table is-referenced-by Key
Logical Process
The Logical Process entity type (Figure 2-19) represents an action performed to satisfy a business requirement. A logical process is the smallest unit of work that it is useful to describe.
Figure 2-19 Logical Process Properties Dialog
Table 2-27 Logical Process Properties Property Description Description Status: Optional Up to 30 characters of additional information that describes the Logical Process. Status: Required Default is Capture mDomLogicalProcessType Designates the action the Logical Process performs. The following choices are available in the list box: Capture Update Delete Associate Retrieve Calculate Validate Status: Required Default is Action mDomLogicalProcessMode Designates the type of Logical Process. The following choices are available in the list box: Decision Action Logical function
LogPro_Type
LogPro_Mode
2-33
Entity Types
Table 2-27 Logical Process Properties (Continued) Property Description Status: Optional Default is Day mDomDuration The following choices are available in the list box: Day Week Month Year Quarter Minute Hour Second Status: Optional Default is No mDomBoolean The following choices are available in the list box: Yes No Status: Optional Default is No mDomBoolean The following choices are available in the list box: Yes No Status: Optional Default is No mDomBoolean The following choices are available in the list box: Yes No Status: Optional Can contain a maximum of 4 character Default is 0 Status: Optional Default is Day mDomDuration The following choices are available in the list box: Day Week Month Year Quarter Minute Hour Second
ResponseNeeded
TransationCenter
CentralTransform
LeafProcess
Frequency
FrequencyUnit
Relationships Logical Process affects Entity Logical Process contains Data Flow Logical Process data-content-defined-by ER View Logical Process depends-on Logical Process Logical Process has-process-dependency Drawing Logical Process initiates Event
2-34
Entity Types
Entity Types
Logical Process is-composed-of Logical Process Logical Process is-implemented-by Rule Logical Process is-signatured-by Data Flow Logical Process is-supported by Opportunity Logical Process is-supported by Problem Logical Process supports Information Need Logical Process supports Success Factor Inverse Relationships Assumption is-supported-by Logical Process Business Object owns Logical Process Context Diagram contains Logical Process Development Project includes Logical Process Entity is-modified-by Logical Process Event triggers Logical Process Goal is-supported by Logical Process Problem affects Logical Process Problem is-caused by Logical Process Transition triggers Logical Process
Machine
The Machine entity type (Figure 2-20) represents a workstation in a physical network.
Figure 2-20 Machine Properties Dialog
2-35
Entity Types
Table 2-28 Machine Properties Field in Dialog Property Description Status: Required Default is MS-Windows NT mDomOSType The operating system executing on the machine. The following choices are available in the list box: AIX CICS/MVS CICS/OS2 HPUX IMS MVS OS/2 OS/400 SunOS Windows NT Status: Optional The version of the operating system executing on the machine. Maximum of 30 characters. Status: Optional The group to which the machine belongs. Maximum of 30 characters. Status: Optional Can contain a maximum of 30 characters Default is Local
Operating system
OS_Type
OS release
OS_ Release
Machine group
Mc_Group
Implementation name
Mc_Imp_Name
Relationships Machine can-access Machine Inverse Relationships Cell contains Machine Partition encapsulates Machine
Migration
The Migration entity type (Table 2-29) is the focus of all migration activity. You use it to find information about migration, to specify migration action processing options, to view the results of batch processing jobs, and to organize and manage routine migrations. It can be thought of as the envelope that contains the object, object hierarchies, or migration root entity during source repository processing.
2-36
Entity Types
Entity Types
Table 2-29 Migration Properties Property Description Status: Optional Can contain a maximum of 4 characters Default is No Action Executed mDomMigState Refer to Table 2-30for a list of migration states and their values. Status: Optional Can contain a maximum of 44 characters Status: Optional Can contain a maximum of 4 characters
Mig_State
Mig_DSN Return_Code
The values for the migration states are summarized in Table 2-17.
Table 2-30 Migration states Description No Action Executed Export Job Submitted Export Job Executing Export Job Failed Export Job Successful Export Job Approved Load Job Submitted Load Job Executing Load Job Failed Load Job Successful Load Job Approved Analyze Job Submitted Analyze Job Executing Analyze Job Failed Analyze Job Successful Analyze Job Approved Import Job Submitted Import Job Executing Import Job Failed Import Job Successful Import Job Approved Values 0 0001 0002 0003 0004 0005 1001 1002 1003 1004 1005 2002 2002 2003 2004 2005 3001 3002 3003 3004 3005
Relationships Migration is-profiled-by Group
Note
The Migration entity type can also be related to all other named entity types. For example, a Migration entity type can have as its root an Application Configuration entity type or an Attribute entity type, or any other named entity type.
2-37
Entity Types
Partition
The Partition entity type (Figure 2-21) is an association between a client or server process and a machine and its database.
Figure 2-21 Partition Properties Dialog
The method of linking a rule that belongs to the associated server can be: DynamicThe code needed to resolve external references is shared with other rules and so any external references are resolved at run time. StaticThe code needed to resolve external references is copied into the rules executable load module at link time so any external references are resolved at prepare time.
2-38
Entity Types
Entity Types
Table 2-31 Partition Properties Property Description Status: Required Default is Java mDomGeneratedLanguage The following choices are available: Java Status: Required Maximum of 30 characters. Status: Required Default is mDomServerInterface The network protocol on which the associated Server listens can be: EJB RMI NetEssential MQSeries WebServer Status: Required Default is Dynamic mDomSrvLinkType The method of linking a rule that belongs to the associated server can be: Dynamic Static Status: Required Default is Client mDomPartitionType The method of starting the associated Server can be: Client Server Gateway Status: Optional This can be a numeric Value from 0 to 9. Status: Optional Can contain a maximum of 8 characters The identifier according to which a DB2 plan or package is prepared for all rules that belong to the associated server. Maximum of 30 characters. Status: Optional The DB2 identifier for all unqualified host SQL calls associated with the configuration unit. Maximum of 30 characters. Status: Optional The DB2 plan for the associated rules. Maximum of 30 characters. Status: Optional The DB2 collection ID to be used for objects that are connected to this configuration unit. Maximum of 30 characters.
GeneratedLanguage
ImplementationPackage
ServerInterface
Srv_LinkType
PartitionType
Srv_CellRank
Srv_Owner
Srv_Qualifier
Srv_PlanName
CollectionId
2-39
Entity Types
Table 2-31 Partition Properties (Continued) Property Description Status: Required Default is Cursor Stability mDomIsolationMode The isolation mode to be used for objects that are connected to this configuration unit. The following choices are platform specific and are dependent on DB2 settings: Committed Read Cursor Stability Dirty Read Repeatable Read Not Applicable Status: Optional Can contain a maximum of 8 characters The starting trans ID to be used for objects that are connected to this configuration unit. Status: Optional Can contain a maximum of 8 characters The ending trans ID to be used for objects that are connected to this configuration unit. Status: Required Default is Event Driven mDomClientType The following choices are available: HTML Event Driven Converse
IsolationMode
MinTranId
MaxTranId
ClientType
Relationships Partition encapsulates Component Partition encapsulates Database Partition encapsulates File Partition encapsulates Function Partition encapsulates Machine Partition encapsulates Process Partition encapsulates Report Partition encapsulates Rule Partition encapsulates Server Partition encapsulates Set Partition encapsulates Window Partition is-had-by Application Configuration Partition uses Language
2-40
Entity Types
Entity Types
Physical Event
The Physical Event entity type (Figure 2-22) represents a user-defined (business) event. Examples of such an event could be a change in the price of a stock or the withdrawal of money greater than a specified amount.
Figure 2-22 Physical Event Properties Dialog
Table 2-32 Physical Event properties Property Event_Description PhyEvent_Type Description Status: Optional Up to 30 characters of additional information that describes the event. Status: Optional Can contain a maximum of 32 characters Status: Required Can contain a maximum of 2 characters Default is External mDomEventClass The following choices are available: External Internal Temporal Status: Required Default is Global mDomEventScope The following choices are available: Local Global Cell
Event_Class
Event_Scope
Relationships Physical Event has Rule Physical Event owns View Inverse Relationships Rule triggers Physical Event
Process
The Process entity type (Figure 2-23) is an activity that comprises logical units of work (LUWs). Each process represents a single application (leaf process) or a set of applications. The hierarchy of processes
2-41
Entity Types
you create in your repository is transformed in the application execution environment into an end-user menu.
Figure 2-23 Process Properties Dialog
Table 2-33 Process Properties Property Proc_Name Description Status: Optional Can contain a maximum of 18 characters Status: Required Up to 30 characters of text for the menu choice the user chooses to invoke the process. Status: Optional Can contain a maximum of 8 characters Status: Required Default is Menu Bar mDomChildMenu Indicates whether the processes under this function appear on a pull-down menu or on a new menu bar at the top of a window. The following choices are available in the list box: Menu Bar Pull-Down Hidden (Batch) Status: Generated Can contain a maximum of 8 characters Default is PC Workstation mDomChildMenu This property appears only after a Super Prepare or a Setup action has been performed. This property may be one of the following values: Not Applicable IBM Mainframe (CICS) PC Workstation PC & IBM Mainframe (CICS) PC & IBM Mainframe (IMS) IBM Mainframe (IMS)
Menu_Desc
Work_Station_Group
Child_Menu
Process_Execenv
Relationships Process depends-on Process Process has Bitmap Process impacts Entity Process is-defined-by Rule
2-42
Entity Types
Entity Types
Process refines-into Process Inverse Relationships Partition encapsulates Process Event triggers Process Function refines-into Process Process is-dependent-on Process Process is-refined-from Process
Relationship
The Relationship entity type (Figure 2-24) records information about the relationship type between two or more entities, between an entity and another relationship, or between two or more relationships. Typically, you define instances of relationship entity types during business object analysis when you build your data model. For example, if you have two entity instances, Reservation and Car Type, you might have an instance of a relationship called Specifies to describe how they are connected.
Figure 2-24 Relationship Properties Dialog
2-43
Entity Types
Table 2-34 Relationship Properties Property Description Status: Required Default is Regular mDomComplexIndicator The following values are available: Regular AND XOR IOR Subtype You can change the value of this property only by changing the type of the relationship in the Entity-Relationship Diagrammer. The values AND, IOR, and XOR that appear in the enterprise repository are reserved for future use. Status: Optional Can be a maximum of 5 characters. User-defined lower limit of the expected size of the instance of the entity type (number of Fields). This can be a numeric value from 0 to 99,999. Status: Optional Can be a maximum of 10 characters. User-defined upper limit of the expected size of the instance of the entity type (number of fields). This can be a numeric value from 0 to 9,999,999,999. Status: Required Can contain a maximum of 5 characters Default is Day mDomDuration The following values are available: Day Week Month Year Quarter Minute Hour Second Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that the instance of this entity type will be created. This can be a numeric value from 0 to 9,999. Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that the instance of this entity type will be deleted. This can be a numeric value from 0 to 9,999. Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that the instance of this entity type will be updated. This can be a numeric value from 0 to 9,999. Status: Optional Can contain a maximum of 10 characters The number of instances of this entity expected when you define the data model. This can be a numeric value from 0 to 9,999,999,999.
Cmpx_Indicator
Exp_Min_Rows
Exp_Max_Rows
Act_Period
Ave_Wkly_Inserts
Ave_Wkly_Deletes
Ave_Wkly_Updates
Exp_Rows
Relationships Relationship connects-to Collection Relationship connects-to Column Relationship connects-to Key
2-44
Entity Types
Entity Types
Relationship connects-to Table Relationship is-described-by Attribute Relationship is-implemented-by Collection Relationship is-implemented-by Column Relationship is-implemented-by File Relationship is-implemented-by Key Relationship is-implemented-by Table Relationship relates-via Relationship Inverse Relationships Attribute is-composed-of Relationship Identifier is-composed-of Relationship Entity is-related-via Relationship ER View involves Relationship Relationship is-related-via Relationship
Report
The Report entity type (Figure 2-25), in conjunction with the section entity type, defines the paperbased output that an application produces for the end user. This application is usually a batch application. You typically define an instance of a report entity type using the Report Painter tool in the Construction Workbench.
Figure 2-25 Report Properties Dialog
2-45
Entity Types
Table 2-35 Report Properties Property Description Status: Required Can contain a maximum of 6 characters Default is MVSBAT mDomReportExecEnv The following values are available: IBM Mainframe Batch IBM Mainframe (CICS) Workstation PM Status: Required Can contain a maximum of 4 characters Default is 60 Number of lines or inches (depending on the printer type) per page for the report. This can be a numeric value from 1 to 500. Status: Required Can contain a maximum of 4 characters Default is 72 Width in characters or inches (depending on the printer type) per line for the report. This can be a numeric value from 1 to 132. Status: Required Can contain a maximum of 4 characters Column number where printing begins. This can be a numeric value from 0 to the line size. Status: Required Can contain a maximum of 4 characters Row number where printing begins. This can be a numeric value from 0 to the page size. Status: Required Default is Generic mDomPrinterType The following choices are available in the list box: Generic (character specification) 38000 (inches/10 specification) Page size and line size width are interpreted as tenths of an inch for 3800 printers and the number of characters for generic printers. Status: Required Default is Portrait mDomOrentation The following choices are available in the list box: Portrait Landscape Status: Optional Maximum of 7 alphanumeric characters, the first of which must be alphabetic.
Exec_Environ
Page_Size
Line_Size
Left_Margin
Top_Margin
PrinterType
Orientation
Report_Imp_Name
Relationships Report contains Section Report has Bitmap Report has Form Report owns View Report refers-to Set
2-46
Entity Types
Entity Types
Inverse Relationships Partition encapsulates Report Rule converses Report
Rule
The Rule entity type (Figure 2-26) records reusable procedural system specifications for your application. Rules define the logic of a process, control the execution of other rules and components, invoke windows and reports, and access files. The logic in a rule is specified using the Rules Language. Ideally, each rule represents one logical unit of work. That is, each rule should accomplish one task only. This approach maximizes the potential for reuse. If you combine several tasks into one rule, and then perform one or two of them again, it may not be feasible to reuse your original rule because it also performs unneeded tasks.
Figure 2-26 Rule Properties Dialog
2-47
Entity Types
Table 2-36 Rule Properties Property Description Status: Required Can contain a maximum of 6 characters Default is PC Workstation mDomRuleExecEnv The following choices are available in the list box: IBM Mainframe (CICS & Batch) PC Workstation IBM Mainframe (IMS) IBM Mainframe (CICS) IBM Mainframe Batch PC & IBM Mainframe (CICS) PC & IBM Mainframe (IMS) Status: Required Can contain a maximum of 8 characters Status: Required Can contain a maximum of 3 characters Default is Not Applicable mDomRuleDBMSUsage Defines whether the rule accesses a database table. The following choices are available in the list box: DB2 Not Applicable Note: Use the DB2 value whether the database is DB2, DBM, Informix or other databases. Status: Required Can contain a maximum of 30 characters Status: Required Can contain a maximum of 5 characters Default is Synchronous execution mDomExecuteMode Defines the type of processing during execution. The following choices are available in the list box: Synchronous execution Asynchronous execution Event Driven execution Status: Optional Can contain a maximum of 8 characters Status: Optional Maximum of 8 alphanumeric characters, the first of which must be alphabetic. Status: Optional The name of the LANDP Server that the rule accesses. Maximum of 8 alphanumeric characters. Any character but the first can also be a number sign (#). Status: Required Default is Committed Read mDomIsolationMode The following choices are available in the list box: Committed Read Cursor Stability Dirty Read Repeatable Read Not Applicable
Exec_Environ
Rule_Source
Sys_Source
Rule_Name
Rule_Str_Id
Rule_TranId Rule_Imp_Name
Package
Isolation_Mode
Relationships Rule converses Report Rule converses Window
2-48
Entity Types
Entity Types
Rule depends-on Rule Rule has Bitmap Rule is-accessed-by File Rule owns View Rule refers-to Set Rule triggers Physical Event Rule uses Component Rule uses Rule Inverse Relationships Partition encapsulates Rule Logical Process is-implemented-by Rule Physical Event has Rule Process is-defined-by Rule Rule is-depended-on-by Rule Rule is-used-by Rule Server contains Rule
Section
The Section entity type (Figure 2-27), in conjunction with the Report entity type, defines the paperbased output that an application produces for an end user. The application is usually a batch application. Each section includes definition information about a particular part of the report, such as a header section or a footer section. You typically create a report and its associated sections with the Report Painter tool.
Note
The particular part of a report defined by each of its sections is determined by an property of the contains relationship type, not an property of the section entity type. Section Properties Dialog
Figure 2-27
2-49
Entity Types
Table 2-37 Section Properties Property ShortName Section_Imp_Name Description Status: Optional Can contain a maximum of 8 characters Status: Optional Maximum of 8 alphanumeric characters, the first of which must be alphabetic
Relationships Section owns View Section uses Language Inverse Relationships Report contains Section
Server
The Server entity type represents a Server Process in a network configuration.
Figure 2-28 Server Properties Dialog
Table 2-38 Server Properties Property Srv_Imp_Name Description Status: Optional Can contain a maximum of 30 characters
Relationships Server contains Rule Inverse Relationships Partition encapsulates Server
Set
The Set entity type (Figure 2-29) provides a way to create a named value in the repository that can be referred to by any number of rules in any number of applications. Sets can be used in the following ways:
2-50
Entity Types
Entity Types
System Choices This use of a set allows choices from a combination box in an applications window. For example, a user might have to choose the type of car: Compact, Sub-Compact, or Full-Size. Messages Predefined messages can be defined in a set referred to by the standard component:
SET_WINDOW_MESSAGE
to display an error: Symbolic name Sets Messages are used primarily to make Rules Language code more readable by allowing developers to substitute meaningful references for cryptic variables. For example, when you create a message set, each message is associated with a value (such as 100). To invoke a particular message you can specify that value in your Rules Language code. Alternately, you can associate a meaningful symbolic name with the message (for example, RECORD_NOT_FOUND) and refer to the message using the symbolic name instead of the value. For more information on sets, see Contains (is-contained-in) on page 3-10.
Figure 2-29 Set Properties Dialog
2-51
Entity Types
Table 2-39 Set Properties Field in Dialog Property Description Status: Required Default is Small Integer or Integer mDomSetType Data type of the Set values. The following choices appear in the list box: Character Decimal Graphic Character (DBCS) Mixed Character Small Integer or Integer Status: Required Can contain a maximum of 5 characters Default is 0015 The value range for this property depends on the Set Type, as shown in Table 2-39. Status: Required if Set Format is Decimal Status: Irrelevant for any other Set Format Can contain a maximum of 2 characters Number of decimal places in the sets values. For decimal sets, the set fraction must be greater than 0 and less than or equal to the Set length. Status: Optional Can contain a maximum of 8 alphanumeric characters, the first of which must be alphabetic Status: Required Default is Values mDomSetStyle The following choices are available in the list box: Define Error Lookup Values Refer to Table 2-41 for a summary of Style restrictions. Status: Optional Can contain a maximum of 2 characters whose numeric value must be from 0 to 99
Set format
Set_Type
Set length
Set_Length
Set fraction
Set_Fraction
Implementation name
Set_Imp_Name
Style
Set_Style
Representation length
RepresentationLen
Table 2-40 Set Lengths by Set Format Set length Set format Character Decimal Graphic character (DBCS) Mixed character Small integer or integer Minimum length 1 1 1 1 Small: 15; Integer: 31 Maximum length 30 31 15 30 Small: 15; Integer: 31 Set fraction -No more than Set length. ----
2-52
Entity Types
Entity Types
Table 2-41 Set Styles Style Define Error Lookup Description For restrictions on Define and Encoding properties, refer to Symbol. Define and Encoding properties are required and Define must be unique. The Define, Encoding, and Display fields are required and must have unique values. The Set type can only be Small Integer. The Define, Encoding, and Display fields are required and must have unique values.
Relationships Set contains Symbol Set contains Value Inverse Relationships Component refers-to Set Configuration unit encapsulates Set Data type is-constrained-by Set Field refers-to Set Report refers-to Set Rule refers-to set Set Window refers-to set Set
State
The State entity type (Figure 2-30) is a discrete set of properties, values, and relationships a data object holds at a point in time.
Figure 2-30 State Properties Dialog
2-53
Entity Types
Table 2-42 State Properties Property Description Description Status: Optional Up to 30 characters of additional information that describes the state Status: Required Default is Intermediate mDomStateType Designates the type of state. The following choices are available in the list box: InitialAn initial state represents the condition of a data object before any processing and transitions IntermediateAn intermediate state is a state a data object resides in during most of its life cycle, and which it leaves or enters only when some external or internal event triggers a state change FinalA final state is a state the data object enters and does not leave
State_Type
Relationships State has-a-state-transition Drawing Inverse Relationships Business Object has State Entity has State Transition is-preconditioned-by State Transition results-in State
Symbol
The Symbol entity type (Figure 2-31) is used for the items in a set. The properties dialog is available using the Freeway Explorer.
Figure 2-31 Symbol Properties Dialog
2-54
Entity Types
Entity Types
Table 2-43 Symbol properties Property Description Status: Optional Can contain a a maximum of 8 characters The name that is used in a rule to refer to the symbol. (Example: red in SET_OF_COLORS) Should start with a letter or underscore (_) followed by a sequence of letters, digits, or underscores. Status: Optional Can contain a a maximum of 8 characters The value of the symbol that is stored in fields. (Example: 1) Status: Optional Can contain a a maximum of 8 characters The display value of the symbol used for lookup sets. (Example: Red)
Define
Encoding
Display
Relationships Symbol uses Language Inverse Relationships Set contains Symbol
Table
The Table entity type (Figure 2-32) describes a table or view in a database. Its properties store volumetric and implementation data.
Figure 2-32 Table Properties Dialog
2-55
Entity Types
Table 2-44 Table Properties Property Description Status: Required Default is Table mDomTableView The following choices are available in the list box: Table View Status: Required Can contain a maximum of 30 characters Status: Optional Can contain a maximum of 5 characters User-defined lower limit of the expected size of the instance (number of fields). This can be a numeric value from 0 to 99999 that is less than the expected maximum rows property. Status: Optional Can contain a maximum of 10 characters User-defined upper limit of the expected size of the instance (number of fields). This can be a numeric value from 0 to 9999999999. Status: Required Default is Day mDomDuration_s Time period that describes the frequency of various operations performed with instances of this entity type. The following choices are available in the list box: Day Week Month Year Quarter Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that instances of this entity type will be created. This can be a from 0 to 9999. Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that instances of this entity type will be deleted. This can be a numeric value from 0 to 9999. Status: Optional Can contain a maximum of 4 characters Estimated number of times during implementation that instances of this entity type will be updated. This can be a numeric value from 0 to 9999. Status: Optional Can contain a maximum of 8 characters
Table_View
Tbl_Imp_Name
Exp_Min_Rows
Exp_Max_Rows
Act_Period_s
Ave_Inserts
Ave_Deletes
Ave_Updates
Creator
Relationships Table has Column Table has Key Table implements Table Table is-based-on Table Table is-implemented-by Collection Table is-implemented-by Column Table is-implemented-by File
2-56
Entity Types
Entity Types
Table is-implemented-by Key Table is-implemented-by Table Table is-referenced-by Key Inverse Relationships Attribute connects-to Table Attribute is-implemented-by Table Collection connects-to Table Collection is-implemented-by Table Data type connects-to Table Data type is-implemented-by Table Database contains Table Entity connects-to Table Entity is-implemented-by Table Identifier connects-to Table Identifier is-implemented-by Table Relationship connects-to Table Relationship is-implemented-by Table
Transition
The Transition entity type (Figure 2-33) represents an event and the processes it triggers that cause an entity to move from one state to another.
Figure 2-33 Transition Properties Dialog
Relationships Transition data-content-defined-by ER View Transition is-caused-by Event Transition is-preconditioned-by State Transition results-in State Transition triggers Logical Process
2-57
Entity Types
Inverse Relationships Event causes Transition

Table 2-45 Transition entity type Property Name System ID ShortName Description Status: Required Common Property Status: Generated Common Property Status: Optional Can contain a maximum of 8 characters
Value
The Value entity type (Figure 2-34) represents the Value entity.
Figure 2-34 Value Properties Dialog
Table 2-46 Value Properties Field in Dialog Value Property Description Description Status: Optional Up to 30 characters of additional information that describes the Value.
Relationships Value is-classified-by Scheme (Implemented as: Value classifies Scheme) Inverse Relationships has Value
View
The View entity type (Figure 2-35) defines data structures in the AppBuilder environment. For example, a view defines the input to or the output from a rule, or the fields that can appear on a window. Each view can be thought of as a node in a data tree, the leaf nodes of which are fields. The root view of each such structure is associated with a rule, a component, a window, a file, or a section entity type through an owns relationship type, and with fields and other views through an includes relationship type. Any included views can include other views and fields.
2-58
Entity Types
Entity Types
Each view in a data tree can be considered the root node of a subtree. In the AppBuilder environment, each of these subtrees containing a view, and the views and fields that descend from it, is called a view structure. Various configurations of view structures make up all AppBuilder environment data structures. Through their views, rules can accept parameters, return data, and communicate with the end user through windows. For example, a rule can place data in the input view of a rule it uses, call the rule, and, when the called rule terminates, read the returned data from its output view. A rule can also place data into the fields of the window view of a window it converses, then call the window to display the data to the end user. When the end user closes the window, the rule can read the fields the end user changed.
Figure 2-35 View Properties Dialog
Table 2-47 View Properties Property View_Name Description Status: Optional Can be a maximum of 18 characters of additional information that describes the view Status: Optional Can be a maximum of 8 alphanumeric characters, the first of which must be alphabetic
View_Imp_Name
Relationships View includes Field View includes View Inverse Relationships View is-included-in View Component owns View Entity owns View File owns View Physical Event owns View Report own View Rule owns View Section owns View Window owns View
2-59
Entity Types
Window
The Window entity type (Figure 2-36) is the logical representation in a repository of a window the user sees on the workstation screen or a 3270 panel. You create the window using the Window Painter tool of the Construction Workbench. The description of your panel is then stored in the repository as a window entity type. Each window is associated with one view, called its window view, through the owns relationship type. This view stores input to and output (new or modified data for the end user) from the window.
Figure 2-36 Window Properties Dialog
Table 2-48 Window Properties Property Window_Name Description Status: Optional Can be a maximum of 18 characters of additional information that describes the view Status: Optional Can be a maximum of 8 alphanumeric characters, the first of which must be alphabetic
Window_Imp_Name
Relationships Window has Bitmap Window has Panel Window has Help Window has Help Text Window has Window Content Window owns View Window refers-to Set Inverse Relationships Partition encapsulates Window Rule converses Window
2-60
Entity Types
CHAPTER
RELATIONSHIP TYPES
A relationship type allows you to describe different forms of association between entity types. It can be thought of as the verb that connects the two entities. A relationship type takes its name from this definition. The name is a concatenation of: subject entity type + relationship type + object entity type For example, the relationship name for a uses relationship type between two rules is: Rule uses Rule Relationship types (relationships between entity types), just as entity types themselves, are object types in the repository. The vast majority of relationship types are fixed; that is, they relate specific entity types in specific ways that seldom change. For the most part, these relationship types do not have properties associated with them, aside from a sequence number (for example, so you can tell which field has precedence in a data structure). This topic includes: Common Properties of Relationship Types Relationship Types There are two ways to view a relationship type: from the point of view of the parent entity type or from the point of view of the child entity type. That is, given a converse relationship between a rule and a window, the Rule converses the Window, and the Window is-conversed-by the Rule. The use of the parent name to child name relationship perspective is preferred. Later in this chapter, the relationship types are listed in alphabetical order by the preferred name; proper terminology for the secondary namegenerally, the child-to-parent relationship perspectiveis shown in parentheses.
Common Properties of Relationship Types

All relationship types have common properties. All common properties, except parent name, child name, sequence number, and separator identifier are the relationship types audit properties. The audit properties (except for local date and local time) are not populated until the object type has been uploaded to the host.
3-1
In the personal repository on a workstation, parent name, child name, sequence number, and separator identifier, as well as all properties unique to each relationship type, appear on the General tab of the Properties dialog for that relationship type. Audit properties appear on the relationship types Object Audit Information window (see Figure 1-3 on page 1-6). Properties are displayed differently in the enterprise repository on the host. All properties appear on the main screen for each relationship type. Parent name is the first entity type listed on the screen, and child name is the second one listed. In the personal repository, parent and child names are generated from the position of objects in drawings. In the enterprise repository, you enter these names to establish the relationship type. Property names are slightly different in the three repositories, and some properties do not appear in all. The following list indicates how each property appears in the repositories. If not specified, the name is the same in all repositories. The common properties of relationship types in the AppBuilder Information Model include: Parent Name Child Name Sequence Number (Personal or Workgroup only) Separator Identifier (Personal or Workgroup only) Internal Name (visible in Personal or Workgroup only) QA Status (Personal or Workgroup only) ChangeNumber Created/Remote date (Personal or Workgroup) Date created (Enterprise) Created/Remote time (Personal or Workgroup) Time created (Enterprise) Created/Remote user (Personal or Workgroup) Created by (Enterprise) Maintained/Remote date (Personal or Workgroup) Date maintained (Enterprise) Maintained/Remote time (Personal or Workgroup) Time Maintained (Enterprise) Maintained/Remote user (Personal or Workgroup) Maintained by (Enterprise) Maintained/Local date (Personal or Workgroup only) Maintained/Local time (Personal or Workgroup only) Version (Enterprise only)
3-2
Relationship Types
Common Relationship Properties Descriptions

Parent Name Status: Generated (Personal or Workgroup)/Required (Enterprise) Name of parent object Child Name Status: Generated (Personal or Workgroup)/Required (Enterprise) Name of child object Sequence Number (Personal or Workgroup only) Status: Generated A number automatically assigned to each entity in sequence, and used to define the order of relationships attached to a common entity. You can change this number to change the order of the child entities under a parent entity. This value can be a number from 0 to 999. Separator Identifier (Personal or Workgroup only) Status: Generated Uniquely distinguishes duplicate relationships between the same parent and child entities. Internal Name (visible in Personal or Workgroup only) Status: Generated The AppBuilder environment uses this name internally to refer to the relationship type. This name is not listed with the other information for a relationship type in either repository. However, you may see this name if you encounter trouble during an upload or download. In addition, you will see this name in Repository Maintenance when you view Unit of Work. This name distinguishes the different variants of a relationship type. Because this name is not a true property, it is italicized in the descriptions that follow. QA Status (Personal or Workgroup only) AppBuilder does not currently use this property. ChangeNumber Status: Generated System-generated number to protect instances of an object from simultaneous changes from two users. An instance can be uploaded only if its change number matches the change number in the enterprise repository. Created/Remote date (Personal or Workgroup) Date created (Enterprise) Status: Generated Format: Format: YY/MM/DD Date the instance was first created in the enterprise repository, either directly or by uploading.
3-3
Created/Remote time (Personal or Workgroup) Time created (Enterprise) Status: Generated Format: HH:MM Time the instance was first created in the enterprise repository, either directly or by uploading. Created/Remote user (Personal or Workgroup) Created by (Enterprise) Status: Generated ID of user who created the instance in the enterprise repository, either directly or by uploading. Maintained/Remote date (Personal or Workgroup) Date maintained (Enterprise) Status: Generated Format: YY/MM/DD Date the instance was last changed in the enterprise repository, either directly or by uploading. Maintained/Remote time (Personal or Workgroup) Time Maintained (Enterprise) Status: Generated Format: HH:MM Time the instance was last changed in the enterprise repository, either directly or by uploading. Maintained/Remote user (Personal or Workgroup) Maintained by (Enterprise) Status: Generated ID of last user who changed the instance in the enterprise repository, either directly or by uploading. Maintained/Local date (Personal or Workgroup only) Status: Generated Format: YY/MM/DD Date the instance was last changed on the workstation. Maintained/Local time (Personal or Workgroup only) Status: Generated Format: HH:MM Time the instance was last changed on the workstation. Version (Enterprise only) Status: Generated Identifies the logical repository in which this instance resides.
3-4
Relationship Types
Relationship Types
Relationship Variants
Many relationship types have more than one variant. That is, a relationship type and its properties may vary depending on the entity types it relates. Even though two variants may have the same English language name, for practical purposes, they are different relationship types.
Relationship Type Details

After a list of Common Properties of Relationship Types, the rest of this section lists and describes the relationship types in the Information Model. All relationship types are part of the Development Information Model, unless otherwise noted. Each entry in this list starts with a description of the relationship type and which entity types it can connect. Next is a description of the relationship types properties, including whether a particular property is required, generated, or optional. Most entries include a screenshot of the relationship properties dialog, specifically the General tab where relationship properties can be edited.
Relationship Types
The Relationship Types available in the AppBuilder Information Model are listed in alphabetical order in Table 3-1.
Table 3-1 Relationship Types Is-implemented-by (Implements) Is-involved-in (Involves) Is-keyed-by (Keys) Is-modified-at (Where-is-modified) Is-modified-by (Modifies) Is-preconditioned-by (Preconditions) Is-profiled-by (Profiles) Is-referenced-by (References) Is-replaced-by (Replaces) Is-related-via (Relates) Is-responsible-for (is-the-responsibility-of) Is-site-of (Has-as-its-site) Is-typed-by (Types) Maps (is-mapped-to) Member (is-member-of) Owns (is-owned-by) Partitioned (partitioned-by) Refers-to (is-referred-to-by) Refines-into (is-refined-from) Replaces System (System is-replaced-by) Results-in (is-the-result-of)
Accesses (is-accessed-by) Affects (is-affected-by) Can-Access (can-be-accessed-by) Causes (is-caused-by) Cites (is-cited-by) Comprises (is-comprised-of) Connects (is-connected-to) Contains (is-contained-in) Converses (is-conversed-by) Depends-on (is-depended-on-by) Encapsulates (is-encapsulated-by) Has (is-had-by) Has STD (has-a-state-transition-diagram) Impacts (is-impacted-by) Includes (is-included-in) Influences (is-influenced-by) Initiates (is-initiated-by) Intersects (intersects-with) Is-carried-out-at (Carries Out) Is-composed-of (Composes) Is-constrained-by (Constrains)
3-5
Relationship Types
Table 3-1
Relationship Types (Continued) Stores (provides-storage-for) Supports (Is-supported-by) Triggers (is-triggered-by) Uses (is-used-by)
Is-defined-by (Defines) Is-described-by (Describes) Is-distributed-at (Where-is-distributed) Is-forwarded-to (Is-forwarded-from)
Properties
Refer to Common Properties of Relationship Types for properties common to all entity types. Properties specific to each of the listed Relationship Types are shown in the Properties Table under each entity heading. If there is no Properties Table, that indicates there are no properties specific to that relationship entity.
Variants
Each relationship type has the specific variants for that type listed. See Relationship Variants for a definition of variants.
Accesses (is-accessed-by)
Accesses (Figure 3-1) is a relationship type in which the first entity type gains entry to the second. For example, a rule or a component accesses or gains entry to a file.
Figure 3-1 Accesses Properties Dialog
Table 3-2 Property
Accesses Properties Description The system ID of an entity that is accessing a child entity The system ID of an entity that is being accessed by a parent entity
Parent name Child name Sequence number Separator ID Component usage
Status: Optional Can contain a maximum of 2 characters
3-6
Relationship Types
Relationship Types
Variants
Component accesses File (implemented as: File is-accessed-by Component) Database accesses File (implemented as: File is-accessed-by Database) Rule accesses File (implemented as: File is-accessed-by Rule)
Affects (is-affected-by)
Affects is a relationship type in which the first entity type has an influence on or causes a change in the second entity type.
Table 3-3 Property Create flag Read flag Update flag Delete flag Comments Affects Properties Description Status: Optional Specifies whether the instance of the first entity type creates the second Status: Optional Specifies whether the instance of the first entity type reads the second Status: Optional Specifies whether the instance of the first entity type updates the second Status: Optional Specifies whether the instance of the first entity type deletes the second Status: Optional Can contain a maximum of 30 characters
Variants
Logical Process affects Entity variant (implemented as: Entity is-affected-by Logical Process)
Can-Access (can-be-accessed-by)
Can-Access (Figure 3-2) means that the first entity type can gain entry to the second entity type.
Figure 3-2 Machine Can-Access Machine Properties Dialog
3-7
Relationship Types
Variants
Machine can-access Machine (implemented as: Machine can-be-accessed by Machine)
Causes (is-caused-by)
Causes is a relationship type in which the first entity type is the reason for or results in the second entity type.
Figure 3-3 Causes Properties Dialog
Table 3-4 Property Description
Causes Properties Description Status: Optional Can contain a maximum of 30 characters
Variants
Event causes Transition (implemented as Transition is-caused-by Event)
Cites (is-cited-by)
Cites means that the first entity mentions or brings forward as support, proof or illustration the second entity.
Comprises (is-comprised-of)
Comprises is a relationship in which the first entity type comprises the second.
Variants
Window is comprised of Window
3-8
Relationship Types
Relationship Types
Connects (is-connected-to)
Connects-to is a relationship type in which the first entity is connected to the second entity.
Figure 3-4 Connects Properties Dialog
Variants
Attribute connects-to Collection Attribute connects-to Column Attribute connects-to Key Attribute connects-to Table Collection connects-to Collection Collection connects-to Column Collection connects-to Key Collection connects-to Table Column connects-to Collection Data type connects-to Column Data Type connects-to Collection Data Type connects-to Key Data Type connects-to Table Entity connects-to Collection Entity connects-to Column Entity connects-to Key Entity connects-to Table Identifier connects-to Collection (Figure 3-4) Identifier connects-to Column Identifier connects-to Key Identifier connects-to Table Relationship connects-to Collection Relationship connects-to Column
3-9
Relationship Types
Relationship connects-to Key Relationship connects-to Table
Note
In the enterprise repository, you might see this relationship type listed under more entity types than shown here. Disregard any others and do not use them. They are reserved for future use and are not currently supported.
Caution
While you can view this relationship type, you should not modify it. Doing so can corrupt the tracing information used by the forward engineering process.
Contains (is-contained-in)
Contains (Figure 3-5) is a relationship type in which the second entity type is a part of the first entity type.
Figure 3-5 Contains Properties Dialog
Variants
This relationship type has several variants: Cell contains Cell (implemented as Cell is-contained-in Cell) Cell contains Machine (implemented as Machine is-contained-in Cell) Database contains Table Group contains Group Report contains Section Server contains Rule Set contains Symbol Set contains Value
3-10
Relationship Types
Relationship Types
Table 3-5 Property
Report contains Section Properties Description Status: Required Indicates which type of section appears in the report. The following choices are available in the list box: Break section Footer section Header section Regular section Status: Required Indicates where section is placed on the page. The following choices are available in the list box: End Page First Page Last Page Next Page Same Page Whole Page Status: Required Indicates whether the report is to be printed or not. The following choices are available in the list box: Not printed Printed Status: Optional Describes the sequence of how break sections appear in the report. The maximum value is 9,999. Status: Optional Contains the field in which a change in the data triggers the sections printing. For example, to build a report listing customers and showing a subtotal for each state, sort the records by state and designate the state field as your break field. When your application calculates customer totals, the report prints a subtotal for each state. Enter a field name, to a maximum of 30 characters, for break sections. Leave this property blank for sections other than break sections. Status: Optional Specifies the view path that includes the instance of the field named in the break field. Enter a view name, in the format Root_View_Name.Sub_View_Name. Status: Optional Specifies the left margin for that section. The maximum value is 9,999.
Section type
Page placement
Print option
Break sequence number
Break field
Break qualifier
Left margin
Set Contains Value Variant

This variant (Figure 3-6) has a special importance in the AppBuilder environment. Its symbol property can be used as a substitute for the value entity type to which it relates, as shown in Figure 3-7. For example, many sets can contain the value 1. However, the relationship type between the value 1 and the set Months can have a symbol of JAN, while the relationship type between the value 1 and the set Mode can have the symbol on.
3-11
Relationship Types
Figure 3-6
Set contains Symbol Properties Dialog
Figure 3-7
Using Symbols
Standards for the symbol (and accompanying text) for instances of the set contains a value relationship type depending on the sets usage.
Table 3-6 Property Symbol Set contains value Properties Description Status: Required Can contain a maximum of 18 characters
3-12
Relationship Types
Relationship Types
Functional Sets
You can refer to the symbol of the values in a functional set to help make your Rules Language code more readable when you use system components. Sets are used as functional sets for local validation. That is, the symbols help describe or validate the values meaning where the values themselves are designed for a specific purpose. A set is a functional set when it contains values standard system components use. Functional sets contain values that are codes the component needs to work correctly. In these cases, the symbol attached to the relationship describes the function of the value and can be used within rules code to refer to the value itself. For example, the system component SET_FIELD_COLOR requires numeric data in its input view to work correctly. You can memorize the numbers associated with the different colors, or you can use a set that contains those numbers as values, and the meaning of those values as symbols. Rules Language accepts both methods.
map 2 to ATTR_COLOR of SET_FIELD_COLOR_I

or
map BLUE in COLORS to ATTR_COLOR of SET_FIELD_COLOR_I

Both of these statements map 2 to the field ATTR_COLOR. Using the symbol property in functional sets gives you a way to keep track of the meaning of numeric codes that system components use. Note that the symbol associated with a value does not explicitly depend on that value. A value equal to 1 could have many uses (and thus many associated symbolsbut only one in a given set), because the relationship instance defines the values use, and the set itself defines the relationship instance. The text attached to the relationship instance should contain a more detailed description of the symbols meaning when necessary.
Setting Window Messages

Sets are used in association with setting window messages. The symbol property of the contains relationship type between the message set and a particular value provides a meaningful tag you can use to refer to the error set in the Rules Language code; the text associated with that contains relationship type provides the window message itself. AppBuilder provides a number of system components that allow developers to display pop-up message windows. You can use these components in conjunction with a message set to display pertinent information to your end user and thereby make your applications interface friendlier. In a message set, each value represents the number of a particular message. You can display that message by using the appropriate system component, whether by number or by symbolic name. When you use sets in this way, make sure that the symbol and associated text conform to your standards for window messages. The symbol is used in the Rules Language code, and therefore should be a unique identifier describing the condition or action resulting in the message display. The text property of the contains relationship is the content of the window message. It is important that the text not only explain the condition that resulted in the window message, but also tell the user how to proceed. Additionally, consider the texts format, because at run time the window that contains the message is generated to accommodate the format as entered behind the Set contains a Value relationship type. Remember that the text you enter is exactly what the end user sees.
3-13
Relationship Types
Server contains Rule Variant

This variant can occur only as Server contains Rule (Figure 3-8).
Figure 3-8 Server contains Rule Properties Dialog
Table 3-7 Property
Server contains Rule Properties Description Status: Optional Maximum of 30 characters Status: Required The following choices are available in the list box: Private Public When set to Private, the server root rule can only be called by a rule executing on the same machine. If a rule from another machine tries to call a Private server root rule, an AppBuilder runtime error is generated. The Private property may be used to isolate logical functionality within a machine, without allowing access to that logical functionality from the outside of the target machine. Thus, a logical subsystem can be defined, allowing compartmentalized development, and made accessible, through the private interface, only to other rules residing on the same machine When set to Public, the server root rule can be called from a rule executing on any machine.
Service name
Entry type
Converses (is-conversed-by)
Converses is a relationship type in which the first entity type causes the second entity type to be displayed on a screen, in an online application, or on paper in a batch application.
Figure 3-9 Example converses Properties Dialog
3-14
Relationship Types
Relationship Types
Variants
Rule converses Report Rule converses Window
Depends-on (is-depended-on-by)
Depends-on (Figure 3-10) is a relationship type in which interrelated processes and rules have an orderly sequence in which they are performed.
Figure 3-10 Depends-On Logical Process Properties Dialog
Table 3-8 Property Description
Logical process depends-on Logical Process Properties Description Status: Optional Can contain a maximum of 30 characters
Variants
Logical Process depends-on Logical Process (Figure 3-10) Process depends-on Process (Figure 3-11) Rule depends-on Rule Depends-on Logical Process Variant The first variant can occur only as Logical Process depends-on Logical Process. Process depends-on Process and Rule depends-on Rule Variants These variants are identical except for their internal names. Process depends-on Process (Figure 3-11) Rule depends-on Rule
3-15
Relationship Types
Figure 3-11
Process Depends-On Process Properties Dialog
Encapsulates (is-encapsulated-by)
Encapsulates (Figure 3-12) is a relationship in which the second entity type is included within the first entity type.
Figure 3-12 Encapsulates Properties Dialog
Table 3-9 Property
Partition encapsulates Properties Description Reserved for future use Reserved for future use Status: Optional Maximum of 30 characters Reserved for future use
Prepare time Object Imp name Service name Significant time
3-16
Relationship Types
Relationship Types
Table 3-9 Property
Partition encapsulates Properties (Continued) Description Status: Required The method of linking a rule that belongs to the associated server. The following choices are available in the list box: DynamicThe code needed to resolve external references is shared with other rules and so any external references are resolved at run time. StaticThe code needed to resolve external references is copied into the rules executable load module at link time so any external references are resolved at prepare time. Status: Required The identifier according to which a DB2 plan or package is prepared for all rules that belong to the associated server. Maximum of 30 characters. Status: Required The identifier for all unqualified host SQL calls associated with the Partition unit. Maximum of 30 characters. Status: Required The DB2 plan for the associated rules. Maximum of 30 characters. Status: Optional The DB2 collection ID to be used for objects that are connected to this Partition unit Reserved for future use Status: Required The isolation mode to be used for objects that are connected to this Partition unit. The following choices are platform specific and are dependent on DB2 settings: Committed Read Cursor Stability Dirty Read Repeatable Read
Server link type
Server owner
Server qualifier
Server plan name
Collection ID
Version ID
Isolation Mode
Variants
Partition encapsulates Component Partition encapsulates Database Partition encapsulates File Partition encapsulates Function Partition encapsulates Machine Partition encapsulates Process Partition encapsulates Report Partition encapsulates Rule
3-17
Relationship Types
Partition encapsulates Set Partition encapsulates Server Partition encapsulates Window
Has (is-had-by)
Has (Figure 3-13) is a relationship type in which the first entity type owns the second entity type.
Figure 3-13 Has Properties Dialog
Table 3-10 Table has Column Properties Property Null Distinct type Distinct Update percentage Description
Variants
Application Configuration has Partition Business Object has State Entity has Identifier Entity has State Scheme has Value Function has Bitmap Key has Column Physical Event has Rule Process has Bitmap Report has Form
3-18
Relationship Types
Relationship Types
Rule has Bitmap Table has Column Table has Key Window has Bitmap Window has Window Content These variants are identical except for their internal names: Application Configuration has Partition Entity has Identifier Scheme has Value Key has Column Business Object has State Entity has State Table has Key
Has STD (has-a-state-transition-diagram)

Has STD is a relationship type in which the entity is associated with State Transition diagram.
Variants
Business Object has-a-state-transition-diagram Drawing Entity has-a-state-transition-diagram Drawing State has-a-state-transition-diagram Drawing
Impacts (is-impacted-by)
Impacts (Figure 3-14) is a relationship in which the first entity type affects the second.
3-19
Relationship Types
Figure 3-14
Process Impacts Entity Properties Dialog
Table 3-11 Process impacts Entity Properties Property Create flag Read flag Update flag Delete flag Comments Description Status: Optional Specifies whether the instance of the first entity type creates the second Status: Optional Specifies whether the instance of the first entity type reads the second Status: Optional Specifies whether the instance of the first entity type updates the second Status: Optional Specifies whether the instance of the first entity type deletes the second Status: Optional Can contain a maximum of 30 characters
Variants
A Process impacts Entity
Includes (is-included-in)
Includes (Figure 3-15) is a relationship in which the second entity type is a part, an element, or a member of the first entity type.
3-20
Relationship Types
Relationship Types
Figure 3-15
Includes Properties Dialog
Table 3-12 View includes Properties Property Description Status: Required The following choices are available in the list box: Not Nulls With Default Nulls Allowed Nulls Not Allowed Status: Required In the View includes Field relationship type, this property can be set only to 0 or 1; in View includes View relationship type, this property can contain a maximum value of 999,999.
Null indicator
Occurs times
Variants
View includes Field View includes View
Influences (is-influenced-by)
Influences (Figure 3-16) is a relationship in which the first entity type affects the second.
Figure 3-16 Event Influences Business Object Properties Dialog
3-21
Relationship Types
Table 3-13 Event influences Business Object Properties Property Description Description Status: Optional Can contain a maximum of 30 characters
Variants
Event influences Business Object
Initiates (is-initiated-by)
Initiates (Figure 3-17) is a relationship in which the first entity type invokes the second.
Figure 3-17 Initiates Event Properties Dialog
Table 3-14 Logical Process initiates Event Properties Property Description Description Status: Optional Can contain a maximum of 30 characters
Variants
Logical Process initiates Event
Intersects (intersects-with)
Intersects (Figure 3-18) is a relationship in which the first entity type interacts in some fashion with the second entity type.
3-22
Relationship Types
Relationship Types
Figure 3-18
Function Intersects-With Entity Properties Dialog
Table 3-15 Function intersects-with Entity Properties Property Create flag Read flag Update flag Delete flag Comments Description Status: Optional Specifies whether the instance of the first entity type creates the second Status: Optional Specifies whether the instance of the first entity type reads the second Status: Optional Specifies whether the instance of the first entity type updates the second Status: Optional Specifies whether the instance of the first entity type deletes the second Status: Optional Can contain a maximum of 30 characters
Variants
Function intersects-with Entity
Invokes (is-invoked-by)
Invokes is a relationship in which the first entity type invokes the second.
Variants
Window invokes a Rule Window invokes a Component
3-23
Relationship Types
Is-carried-out-at (Carries Out)

Is-carried-out-at refers to the place where a function or process is performed.
Table 3-16 Is-carried-out-at location Properties Property Major involvement in function Minor involvement in function Comments Description Status: Optional Specifies how the instance is carried out at the location Status: Optional Specifies how the instance is carried out at the location Status: Optional Can contain a maximum of 30 characters
Is-composed-of (Composes)
Is-composed-of (Figure 3-19) is a relationship in which the first entity is made up of constituent parts, one of which is represented by the second entity.
Figure 3-19 Example is-composed-of Properties Dialog
Table 3-17 Attribute is-composed-of Attribute and Data Type is-composed-of Data Type Property Occurs Description Status: Optional Maximum value of 999,999
Variants
Attribute is-composed-of Attribute Attribute is-composed-of Relationship Data Type is-composed-of Data Type Event is-composed-of Event Logical Process is-composed-of Logical Process Identifier is-composed-of Attribute Identifier is-composed-of Relationship
3-24
Relationship Types
Relationship Types
Is-constrained-by (Constrains)
Is-constrained-by (Figure 3-20) the data described in a data type are limited by the data that a set contains.
Figure 3-20 Data Type Is-Constrained-By Set Properties Dialog
Variants
Data Type is-constrained-by Set.
Is-defined-by (Defines)
Is-defined-by (Figure 3-21) is a relationship type in which a leaf process has a single rule that executes the logic the leaf process represents.
Figure 3-21 Example is-defined-by Properties Dialog
Variants
Process is-defined-by Rule
3-25
Relationship Types
Is-described-by (Describes)
Is-described-by (Figure 3-22) is a relationship type in which the second entity type helps to define the first entity type.
Figure 3-22 Example is-described-by Properties Dialog
Table 3-18 Entity is-described-by Attribute Properties Property Optional Description Status: Optional Whether the second entity type is Status: Required by the first entity type or is optional
Variants
Entity is-described-by Attribute Relationship is-described-by Attribute
Is-distributed-at (Where-is-distributed)
Is-distributed-at describes the distribution of data at a given location.
Table 3-19 Entity is-distributed-at Location Properties Property Master indicator Variant indicator Partitioned indicator Replicated indicator Subset data Reorganized data Teleprocessing (remote data) Comments Description Status: Optional Indicates whether the data are master Status: Optional Indicates whether the data are variant Status: Optional Indicates whether the data are partitioned Status: Optional Indicates whether the data are replicated Status: Optional Indicates whether the data are subset Status: Optional Indicates whether the data are reorganized Status: Optional Indicates whether the data are remote Status: Optional Can contain a maximum of 30 characters
3-26
Relationship Types
Relationship Types
Is-forwarded-to (Is-forwarded-from)
Is-forwarded-to (Figure 3-23) refers to the interrelationship between files on different hardware platforms.
Figure 3-23 File Is-forwarded-to File Properties Dialog
Table 3-20 File is-forwarded-to File Properties Property Description Status: Optional Used for the Store and Forward System to send data from the source file to the target file. The default for these properties is 0. Other characters available are the suffixes of the name of the ISPF skeleton of the piece of code to be called in. Each property can contain a maximum of 1 character. Status: Optional See Store & Forward Update Rule property Status: Optional See Store & Forward Update Rule property
Store & forward update rule
Store & forward delete rule Store & forward insert rule
Variants
File is-forwarded-to File
Is-implemented-by (Implements)
Is-implemented-by (Figure 3-24) is a relationship in which the first (logical) entity is converted through the forward engineering process into the second (physical) entity.
Note
In the enterprise repository, you may see this relationship type listed under more entity types than shown here. Disregard any others and do not use them. They are reserved for future use and are not currently supported.
Caution
While you can view this relationship type, you should not modify it. Doing so can corrupt the results of the forward engineering process.
3-27
Relationship Types
Figure 3-24
Is-implemented-by Properties Dialog
Variants
Attribute is-implemented-by Collection Attribute is-implemented-by Column Attribute is-implemented-by File Attribute is-implemented-by Key Attribute is-implemented-by Table Collection is-implemented-by Collection Collection is-implemented-by Column Collection is-implemented-by File Collection is-implemented by Key Collection is-implemented-by Table Data type is-implemented-by Collection Data type is-implemented-by Column Data Type is-implemented-by File Data Type is-implemented-by Key Data Type is-implemented-by Table Entity is-implemented-by Collection Entity is-implemented-by Column Entity is-implemented-by File Entity is-implemented-by Key Entity is-implemented-by Table Identifier is-implemented-by Collection Identifier is-implemented-by Column Identifier is-implemented-by File Identifier is-implemented-by Key Identifier is-implemented-by Table Logical Process is-implemented-by Rule Relationship is-implemented-by Collection
3-28
Relationship Types
Relationship Types
Relationship is-implemented-by Column Relationship is-implemented-by File Relationship is-implemented-by Key Relationship is-implemented-by Table Table is-implemented-by Collection Table is-implemented-by Column Table is-implemented-by File Table is-implemented-by Key Table is-implemented-by Table
Is-involved-in (Involves)
Is-involved-in (Figure 3-25) is a relationship type in which the first entity is connected by association or participation to the second entity.
Figure 3-25 Organization Is-Involved-In Properties Dialog
Table 3-21 Is-involved-in Relationship Type Properties Property Responsible Major_INV Minor_INV Comments Description Status: Required Whether the entity is responsible for causing the logical process Status: Required Whether the entity that has a major involvement with the logical process Status: Required Whether the entity that has a minor involvement with the logical process Status: Optional Can contain a maximum of 30 characters
Is-keyed-by (Keys)
Is-keyed-by (Figure 3-26) is a relationship in which a field points to or serves as a key to access a file.
3-29
Relationship Types
Figure 3-26
Is-keyed-by Properties Dialog
Table 3-22 Is-keyed-by field Properties Property Description Status: Required The following choices are available in the list box: Delete Key Update Key
Update key
Variants
File is-keyed-by Field
Is-modified-at (Where-is-modified)
Is-modified-at describes the action carried out on an entity at a given location.
Table 3-23 Entity is-modified-at Location Properties Property Create flag Read flag Update flag Delete flag Comments Description Status: Optional Specifies whether the instance of the first entity type creates the second Status: Optional Specifies whether the instance of the first entity type reads the second Status: Optional Specifies whether the instance of the first entity type updates the second Status: Optional Specifies whether the instance of the first entity type deletes the second Status: Optional Can contain a maximum of 30 characters
Is-modified-by (Modifies)
Is-modified-by (Figure 3-27) is the relationship type in which the first entity is changed in form or character by the second entity.
3-30
Relationship Types
Relationship Types
Figure 3-27
Example is-modified-by Properties Dialog
Table 3-24 Is-modified-by Properties Property Description Status: Required The following choices are available: Yes No Whether the entity is altered in this manner Status: Required The following choices are available: Yes No Whether the entity is altered in this manner Status: Required The following choices are available: Yes No Whether the entity is altered in this manner Status: Required The following choices are available: Yes No Whether the entity is altered in this manner Status: Optional Can contain a maximum of 30 characters
Create
Read
Update
Delete
Comments
Variants
Entity is-modified-by Logical Process
Is-preconditioned-by (Preconditions)
Is-preconditioned-by (Figure 3-28) is the relationship type in which the second entity type is a prerequisite for the first entity type.
3-31
Relationship Types
Figure 3-28
Example is-preconditioned-by Properties Dialog
Table 3-25 Transition is-preconditioned-by State Properties Property Description Description Status: Optional Can contain a maximum of 30 characters
Variants
Transition is-preconditioned-by State
Is-profiled-by (Profiles)
Is-profiled-by is a relationship type in which the group type and migration type relate.
Variants
Migration is-profiled-by Group
Is-referenced-by (References)
Is-referenced-by (Figure 3-29) is a relationship type in which the first entity uses the second entity for determining the source of columns within a database.
3-32
Relationship Types
Relationship Types
Figure 3-29
Example is-referenced-by Properties Dialog
Table 3-26 Table is-referenced-by Key Properties Property Referential integrity Description Status: Required Whether referential integrity is enforced
Variants
Table is-referenced-by Key
Is-replaced-by (Replaces)
Is-replaced-by (Figure 3-30) is a relationship type in which the first entity is supplanting the second entity.
Figure 3-30 Example is-related-via Properties Dialog
Is-related-via (Relates)
Is-related-via (Figure 3-31) relationship type specifies the nature of a relationship.
3-33
Relationship Types
Figure 3-31
Is-related-via Properties Dialog
Table 3-27 Is-related-via Properties Property Description Status: Required The following choices are available in the list box: 1 Many Unknown This property is not applicable if the relationship entity types Complex Indicator property is SUBTYPE. Status: Optional Indicates whether the relationship is controlling Status: Optional Indicates whether the relationship is dependent Status: Optional Indicates whether the relationship is optional Status: Optional Indicates whether the relationship is abstract. Applicable only if the relationship entity types Complex Indicator property is SUBTYPE. Status: Optional Can contain a maximum of 30 characters Status: Optional Can contain a numeric value from 0 to 99,999 Can contain a numeric value from 0 to 9,999,999,999
Cardinality
Chief executive Dependent Option
Abstract
Role Minimum cardinality Maximum cardinality
Variants
Entity is-related-via Relationship
Is-responsible-for (is-the-responsibility-of)
Is-responsible-for is the relationship type in which the first entity is held accountable for the second entity.
3-34
Relationship Types
Relationship Types
Is-site-of (Has-as-its-site)
Is-site-of is a relationship type in which the location is the physical location where the second entity takes place.
Is-typed-by (Types)
Is-typed-by (Figure 3-32) allows you to give an property a data type.
Figure 3-32 Attribute Is-typed-by Data Type Properties Dialog
Variants
Attribute is-typed-by Data Type
Maps (is-mapped-to)
Maps is a relationship type in which a conceptual business model object has a mapping relationship to a logical business model object.
Table 3-28 Maps Relationships From To Entity Logical Process Value Maps To Attribute Event Relationship
3-35
Relationship Types
Table 3-29 Maps Properties Property Description Status: Optional Can contain a maximum of 1 character Default is 3 (Undefined Format) mDomMapsToType Not Defined Indirect Direct Customization
MapsTo_Type
Member (is-member-of)
Member is a relationship type that defines membership in a grouping.
Table 3-30 Member Properties Property Description Status: Optional Can contain a maximum of 1 character Default is 3 (Undefined Format) mDomMemberType Member Focal Supertype Neighbor
MemberType
Variants
Business Object has member Entity Business Object has member
Owns (is-owned-by)
Owns(Figure 3-35) is a relationship in which the second entity type is attached to the first.
Figure 3-33 Business Object owns Properties Dialog
3-36
Relationship Types
Relationship Types
Variants
This relationship type has two variants: Business Object Owns Variant Owns View Variant Business Object Owns Variant Business Object owns Entity Business Object owns Event Business Object owns Logical Process
Figure 3-34 Business Object owns Properties Dialog
Owns View Variant The view that is owned-by Entity type defines its data structure (or part of its data structure). For example, a rule might have an input view, an output view, or both. This variant can occur as: Component owns View File owns View Physical Event owns View Report owns View Rule owns View Section owns View Window owns View
Figure 3-35 Owns View Properties Dialog
3-37
Relationship Types
Table 3-31 Owns view Properties Property Description Status: Required The following choices are available in the list box to specify how a rule, file, or component uses the view: Alternative View Candidate Index View Data View Foreign Index View Global View Input & Output View Input View Output View Primary Index View Work View
View usage
Partitioned (partitioned-by)
There may be multiple Application Configurations for a partition. The Application Configuration contains partitions allowing the Function to be prepared (partitioned) to different machines.
Figure 3-36 Partitioned-by Properties Dialog
Variants
Function partitioned-by Configuration
Refers-to (is-referred-to-by)
The Refers-to (Figure 3-37) relationship type describes the data associated with another entity. For example, when a rule refers-to a set, the values associated with the set are available to that rule.
3-38
Relationship Types
Relationship Types
Figure 3-37
Refers-to Set Properties Dialog
Variants
Component refers-to Set Field refers-to Set Report refers-to Set Rule refers-to Set Window refers-to Set
Refines-into (is-refined-from)
Refines-into (Figure 3-38) is a relationship type in which the first entity can be broken down or decomposed into the second entity.
Figure 3-38 Function Refines-Into Process Properties Dialog
Table 3-32 Process refines-into Process Properties Property Condition flag Description Status: Optional Can contain up to four alphanumeric characters
3-39
Relationship Types
Variants
Business Object refines-into Business Object Function refines-into Process Process refines-into Process The third variant can occur only as Process refines-into Process (Figure 3-39).
Figure 3-39 Process Refines-Into Process Properties Dialog
Replaces System (System is-replaced-by)

Replaces (Figure 3-40) is the relationship type in which the first entity type (typically part of a newlydeveloped system) supplants all or part of the second entity type.
Figure 3-40 Process Replaces System Properties Dialog
3-40
Relationship Types
Relationship Types
Table 3-33 Process Replaces System Properties Property Currently supported Planned support Comments Description Status: Optional Indicates whether the instance is currently supported Status: Optional Indicates whether support for the instance is planned Status: Optional Can contain a maximum of 30 characters
Results-in (is-the-result-of)
Results-in (Figure 3-41) is a relationship type in which the second entity type is a product of the first entity type.
Figure 3-41 Results-in State Properties Dialog
Table 3-34 Transition Results-in State Properties Property Description Description Status: Optional Can contain a maximum of 30 characters
Variants
Transition results-in State
3-41
Relationship Types
Stores (provides-storage-for)
Stores is the relationship type used to define that one entity provide storage for another entity.
Table 3-35 Stores Properties Property Description Status: Optional Can contain a maximum of 1 character Default is 3 (Undefined Format) mDomBusDataFormat Character Numeric Code Undefined Format Date Time Status: Optional Can contain a maximum of 5 characters Default is 0015 Status: Optional Can contain a maximum of 2 characters Status: Optional Can contain a maximum of 30 characters Status: Optional Can contain a maximum of 1character Default is N mDomBoolean No Yes Status: Optional Can contain a maximum of 20 characters Status: Optional Can contain a maximum of 1characters Default is C mDomImplType Date VarChar Graphic Character (DBCS) Character Picture Mixed Character Small Integer or Integer Decimal Timestamp Time Image Undefined Code Class Instance Ref Class Instance Value Status: Optional Can contain a maximum of 5 characters Default is 15 Status: Optional Can contain a maximum of 2characters Default is 0
BusDataFormat
BusDataLen
BusDataFrac ClassInstnc
FormatOR
ImpAbbr
ImplFormatType
Fld_Len
Fld_Frac
3-42
Relationship Types
Relationship Types
Supports (Is-supported-by)
Supports (Figure 3-42) is a relationship type in which the first entity type executes the activities of the second entity type.
Figure 3-42 Organization Supports Function Properties Dialog
Table 3-36 Organization supports Function and Organization supports Process Properties Property Responsible Major involvement in function Minor involvement in function Comments Description Status: Optional Can contain a maximum of 1 character Status: Optional Specifies how the instance is supported at the location Status: Optional Specifies how the instance is supported at the location Status: Optional Can contain a maximum of 30 characters Organization Supports Entity Properties Dialog
Figure 3-43
3-43
Relationship Types
Table 3-37 Organization supports Entity Properties Property Create flag Read flag Update flag Delete flag Comments Description Status: Optional Specifies whether the instance of the first entity type creates the second Status: Optional Specifies whether the instance of the first entity type reads the second Status: Optional Specifies whether the instance of the first entity type updates the second Status: Optional Specifies whether the instance of the first entity type deletes the second Status: Optional Can contain a maximum of 30 characters
Triggers (is-triggered-by)
Triggers (Figure 3-44) is the relationship type in which the first entity type causes the second entity type to be invoked.
Figure 3-44 Event Triggers Properties Dialog
Table 3-38 Event Triggers Process Properties Property Description Status: Required The following choices are available in the list box: Exclusive Inclusive Regular Status: Required Can contain a numeric value from 0 to 999 Status: Optional Can contain a maximum of 30 characters
Inclusive flag
Exclusive/ or sequence number Description
3-44
Relationship Types
Relationship Types
Figure 3-45
Triggers Logical Process Properties Dialog
Table 3-39 Triggers Logical Process Properties Property Description Description Status: Optional Can contain a maximum of 30 characters A field provided for users to define a classification of logical processes if they wish to.
Variants
Event triggers Process Event triggers Logical Process Transition triggers Logical Process Rule triggers Physical Event The first variant can occur only as Event triggers Process. The second variant can occur as: Event triggers Logical Process Transition triggers Logical Process
Uses (is-used-by)
Uses (Figure 3-46) is a relationship type in which the first entity type invokes the second.
Figure 3-46 Rule Uses Rule Properties Dialog
3-45
Relationship Types
Table 3-40 Uses Relationship Properties Property Responsible Major_INV Minor_INV Comments Description Status: Optional Can contain a maximum of 1 character The entity that has a major involvement with the location The entity that has a minor involvement with the location Status: Optional Can contain a maximum of 30 characters
Variants
Rule uses Variant Rule uses Component Rule uses Rule
3-46
Relationship Types
CHAPTER
TEXT PROPERTY CONVENTIONS
Each object has a text property. This is a free-form text file that serves two purposes: Object specification On-screen end-user help for windows and fields You are responsible for creating and maintaining the text files for objects that you create or change. You can associate descriptive text with each object. By maintaining documentation as an property of the objects themselves, you ensure that it is as current as the objects are. The objects and their descriptions are maintained in synchronization. Guidelines include: General Guidelines Abbreviation Guidelines Keep in mind that objects you create or modify can be reused in another application, so your text should accurately document the true purpose or function the object provides. If your text is not sufficiently specific, other developers might duplicate your work inadvertently, instead of properly reusing your object. To promote efficiency and avoid redundancy, document your objects well. The following sections discuss the information you should include in text files.
General Guidelines
The text you write provides information about the object and its modifications. The text must be complete enough to let other developers determine whether they can reuse the object in a new application. Include at least the information listed below about each object instance. Object Name What the object is called. Narrative A description, written in business language, of what the object is or does and how the system uses it.
4-1
Abbreviation Guidelines
Special Considerations Information about the object that a developer who is considering reusing the object might need to know, including any limitations that might restrict its reuse in other applications. Also include information about the objects future use or updates. History The objects maintenance history, which includes any changes made to the object since it was created, and why these changes were made. Object-specific Characteristics Any special characteristics that apply to some objects. Include a short explanation of each. For example, an entity can have subtypes listed here.
Abbreviation Guidelines
Because of limitations regarding the length of names, there are times when abbreviations are required. Use the following guidelines when you create abbreviations. Limit abbreviations to a maximum of six characters. Do not use special characters in abbreviations. Do not abbreviate words containing five or fewer characters. Eliminate vowels, if possible, except for the first letter of the word. If a word contains double consonants, eliminate one of each pair, starting at the end of the word. If the word is still longer than six characters, eliminate characters that have no graphic or phonetic value in conveying meaning, starting at the end of the word. Abbreviate all descriptive words when at least one descriptive word must be abbreviated.
4-2
Text Property Conventions
CHAPTER
ENTERPRISE ADMINISTRATION INFORMATION MODEL
The Enterprise Administration Information Model is a subset of the overall AppBuilder Information Model. It includes entities and relationships that define the administration of the enterprise repository.
Administration Information Model

An Information Model is a collection of entity and relationship types, collectively called object types. You use the object types in the Administration Information Model to determine user access and to define the repository. In Information Model diagrams, boxes represent entities and lines connecting the boxes represent relationships. Because a relationship always connects two entities, you can view the relationship from the perspective of either entity. For example, user is-a-member-of group or group has-as-a-member user are two different ways of looking at the same relationship. While both perspectives indicate that user is a subordinate (or child) entity of group, the use of the parent name to child name relationship perspective is preferred. The Administration Information Model, shown in Figure 5-1, defines many-to-many relationships between several entities.
Figure 5-1 The Administration Information Model
5-1
The Administration Information Model includes the user, group, project, language, and repository entity types. You use the user, group, and project entities to define repository access, and the repository and language entities to define the repository itself. You can view the Administration Information Model entities through the Administration (ADM) project.
Note
In addition to seeing the Administration Information Model entities listed in the ADM project, you will see a migration entity. See the Enterprise Migration Guide for more information about migrations.
You select the ADM project to create, read, update, and delete all instances of the administrative entities and their relationships. You do not perform the other repository maintenance tasks within the AppBuilder environment.
User Entity
The user entity defines a user to the AppBuilder environment. Prior to being defined, the user must have a valid TSO user ID. Whenever you add an entity, you must assign values for several attributes. Each user entity has two types of attributes: user and audit. Table 5-1 describes each user entity attribute.
Note
Table 5-1 Attribute Name
Unless the attribute descriptions specify otherwise, blanks are not allowed.
User entity attributes Requirements Required Description A unique alphanumeric string up to 30 characters that identifies the user. Usually the users first initial and last name. The names should be consistent to facilitate searching and administration. 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 increments with each new creation. The last two characters are the alphanumeric repository identifier that is also defined at installation. An alphanumeric string up to 30 characters, including blanks. Usually the users full name. A unique alphanumeric string up to 7 characters, which must match the users TSO user ID. An alphanumeric string up to 30 characters, including blanks, that specifies accounting information such as billing for CPU time. An alphanumeric string up to 8 characters that specifies where the user is located in the organization (such as department or city). An alphanumeric string up to 7 characters that identifies the job for batch execution. BluePhoenix Solutions recommends that this string be the same as the user ID. A alphanumeric string up to 30 characters that specifies job options for the job card for batch execution.
System ID
Systemgenerated
User Name User ID Job Accounting Information User Location
Optional Required Required Optional
Job Name
Optional
Job Options
Optional
The system generates all of the audit attributes, which are the same for all entities. The audit attributes consist of 14 fields that indicate who created or modified the object, as well as the time and date it was created or last modified. You cannot directly edit these field values. Table 5-2 describes the entity audit attributes.
5-2
Enterprise Administration Information Model
Table 5-2 Attribute
Entity Audit Attributes Description The date (year/month/day) the entity was created. The time, based on a 24-hour clock, the entity was created. The user ID of the individual who created the entity. The date (year/month/day) the entity was last modified. The time, based on a 24-hour clock, the entity was last modified. The user ID of the individual who last modified the entity. The name of the project in which the entity was created. The number of times that the entity has been updated. A value of 0001 indicates the entity has not 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 user ID of the person who is responsible for the entity. The date (year/month/day) the entity was last modified. The time, based on a 24-hour clock, the entity was last modified. The name of the project in which the entity was created. The user ID of the person who last modified the entity. The repository version in which the entity was created.
Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project
Change #
Owner ID Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
An instance of a user entity can have the following relationships: Is-a-member-of Group Is-a-root-of Migration A user must be related to a group to have access to the repository (see Figure 5-2).
Figure 5-2 User is-a-member-of Group
When you define a user to a group, that user has access to the same objects in projects the group can access. You determine the level of access when you define the relationship attribute. Table 5-3 describes the attribute for the is-a-member-of Group relationship.
Table 5-3 Attribute Is-a-member-of Group Relationship Attribute Description Required One of the following: Project Leader Analyst Programmer Auditor
User Authority Level
5-3
Just as the system automatically generates audit attributes for the entity, the system also generates similar audit attributes for relationships. Table 5-4 describes the relationship audit attributes, which are common to all relationships.
Table 5-4 Attribute Date Created Time Created Created by Date Maintained Time Maintained Maintained by Relationship Audit Attributes Description The date (year/month/day) the relationship was created. The time, based on a 24-hour clock, the relationship was created. The user ID of the person who created the relationship. The date (year/month/day) the relationship was last modified. The time, based on a 24-hour clock, the relationship was last modified. The user ID of the person who last modified the relationship. The number of times the relationship has been updated. A value of 0001 indicates the relationship has not changed since created and 0002 indicates it was changed and saved once since 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 relationship was last modified. The time, based on a 24-hour clock, the relationship was last modified. The name of the project in which the relationship was created. The user ID of the individual who last modified the relationship. The project version in which the relationship was created.
Change #
Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Just as you can migrate objects between repositories and versions, you can migrate users (see Figure 53).
Figure 5-3 User is-a-root-of Migration
Once you create a user in one repository, you can migrate the user entity to other repositories rather than create a new user entity in each repository. When you create a relationship between a user and a migration entity, that user becomes part of a migration package. You specify that only the entity is to be migrated when you define the relationship attribute. (See Group Entity for information on migrating groups of users.) Table 5-5 describes the attribute for the is-a-root-of Migration relationship
.
Table 5-5 Attribute
Is-a-root-of Migration Relationship Attribute Description Required Entity only from the following: Entity only One level Prepare hierarchy Entity hierarchy Drawing
Scope Type
5-4
Group Entity
The Group entity lets you create teams of users who are allowed access to a specific set or sets of objects in the repository. Thus, a group entity has a subset users. Each group entity has two types of attributes: group and audit. Table 5-6 describes each group entity attribute.
Note
Table 5-6 Attribute Name
Unless specified otherwise, blanks are not allowed.
Group entity attributes Description Required A unique alphanumeric string up to 30 characters that identifies the group. System-generated A default ID that consists of 6 single-byte characters. Optional An alphanumeric string up to 30 characters, including blanks, that describes the purpose of the group.
System ID
Description
An instance of a group entity can have the following relationships: Has-as-a-member User Has Project Is-a-member-of Group Has-as-a-member Group Is-a-root-of Migration Is-profiled-by Migration Is-profiled-by Rebuild Package Users can access objects in projects only through groups (see Figure 5-4).
Figure 5-4 Group has-as-a-member User
Group has-as-a-member User is just another perspective of the User is-a-member-of Group relationship. See Table 5-3 for a description of the relationship attributes. The group relationship to a projecta set of objectsgives the members of the group access to objects in the project. See Figure 5-5.
Figure 5-5 Group has Project
5-5
Also, the group to project relationship attribute lets you apply security features that limit the actions allowed by the relationship. Table 5-7 describes each attribute for the has-project relationship.
Table 5-7 Attribute Has project Relationship Attributes Description Required Either an asterisk (*) for all methods or a single method name to specify which actions are included or excluded from the groups authority. For a list of method names, see Chapter 6, Enterprise Repository Objects Required Either an asterisk (*) to specify all objects or a single object to be included or excluded from the scope of the group relationship. For a list of objects, see Chapter 6, Enterprise Repository Objects Required One of the following choices to indicate whether the Method Name and Scope attributes are inclusive or exclusive: Include Exclude
Method Name
Scope
Scope Mode
To further define groupand therefore useraccess, you can make groups members of groups by relating them to each other (see Figure 5-6).
Figure 5-6 Group is-a-member-of Group
The is-a-member-of relationship indicates that the group is subordinate toor a child ofanother group. The has-as-a-member relationship indicates that the group is a parent of another group. By creating group-to-group relationships, the user is given access not only to objects defined to the groups to which the user has direct access, but to objects defined to subgroups as well. The group-to-group relationship has no relationship attributes, but it does have audit attributes. Just as you can migrate objects, you can migrate groups (see Figure 5-7).
Figure 5-7 Group is-a-root-of Migration
Once you create a group in one repository, you can migrate the group entity to other repositories rather than create a new group entity in each repository. When you create a relationship between a group and a migration entity, that group becomes part of a migration package. You can migrate only the group, or the group with related users and projects, by specifying scope when you define the relationship attribute. Table 5-8 describes the attribute for the is-a-root-of Migration relationship.
5-6
Table 5-8 Attribute
Is-a-root-of Migration Relationship Attribute Requirements Description Either Entity only, One level, or Entity hierarchy from the following: Entity only One level Prepare hierarchy Entity hierarchy Drawing
Scope Type
Required
Project Entity
The Project entity lets you group sets of objects. Thus, a project is a subset of the objects in a repository. Moreover, a project contains a subset of objects of particular types. An ADM project, for example, contains only objects of the Administration Information Model. Whenever you add an entity, you must assign values for several attributes. Each project entity has two types of attributes: project and audit. Table 5-9 describes each project entity attribute.
Note
Table 5-9 Attribute
Project Entity Attributes Requirements Required System-generated Description A unique alphanumeric string up to 30 characters that identifies the project. A default ID that consists of 6 single-byte characters. A unique alphanumeric string up to 4 characters that describes the purpose of the group. No blanks are allowed. The project ID is displayed in the Description column of the project list produced by the PROJECTS command. An alphanumeric string up to 30 characters, including blanks, used to describe the purpose of the group.
Project Name System ID
Project ID
Required
Description
Optional
An instance of a project entity can have the following relationships: Is-had-by Group Is-a-root-of Migration The projects to which a user is relatedthrough one or more group relationshipsdetermine the objects the user can access (see Figure 5-8).
Figure 5-8 Project is-had-by Group
Project is-had-by Group is just another perspective of the group has project relationship. See Table 5-7 for a description of the relationship attributes. Just as you can migrate objects, you can migrate projects (see Figure 5-9).
5-7
Figure 5-9
Project is-a-root-of Migration
Once you create a project in one repository, you can migrate the project entity to other repositories rather than create a new project entity in each repository. When you create a relationship between a project and a migration entity, that project becomes part of a migration package. You specify that only the entity is to be migrated when you define the relationship attribute. Table 5-10 describes the attribute for the is-a-root-of Migration relationship.
Table 5-10 Is-a-root-of Migration Relationship Attribute Attribute Requirements Description Entity only from the following: Entity only One level Prepare hierarchy Entity hierarchy Drawing
Scope Type
Required
Repository Entity
The repository entity is an object that refers to an entire repositorylocal, group, or mainframe. Repository entities always reside in version A of an enterprise repository. An administrator must be authorized to version A in order to create a repository entity.
Note
The repository entity defines whether or not a repository can export or import data. You cannot migrate without defining the repository entity.
Each repository entity has two types of attributes: repository and audit. Table 5-11 describes each repository entity attribute.
Note
Table 5-11 Repository Entity Attributes Attribute Name System ID Description Requirements Required System-generated Optional Description A unique alphanumeric string up to 30 characters, that identifies the repository. A default ID that consists of 6 single-byte characters. A unique alphanumeric string up to 30 characters, including blanks, that describes the purpose of the repository. One of the following: Freeway workgroup repository personal (local) repository enterprise (mainframe) repository A unique alphanumeric string up to 8 characters that refers to an INI file with information about the mainframe repository. The file is used during migration. For further information see Enterprise Migration Guide.
Type
Required
Implementation Name
Required for MRE only
An instance of a repository entity can have the following relationships:
5-8
Can-import-data-from Repository Can-migrate-data-to Repository

Figure 5-10 Repository can-migrate-data-to Repository
By relating repositories, the administrator defines the flow of work within a particular configuration. For example, you can determine that work can move from the development repository to the quality assurance (QA) repository, and from the QA repository back to the development repository. However, you can define the direction of work flow from the QA repository to the production repository to be can-export-to Repository only. See Figure 5-11.
Figure 5-11 Repository Work Flow
Table 5-12 describes the Has repository relationship attributes.

Table 5-12 Has repository Relationship Attributes Attribute Direction Source Version Target Version Requirements Required Required Required Description One of the following choices to indicate the direction of workflow: Can-export-to repository Can-import-from repository
5-9
5-10
CHAPTER
ENTERPRISE REPOSITORY OBJECTS
The Enterprise Repository contains the objects needed to build applications. This chapter provides a complete list of the objects, methods, and actions you can use with AppBuilder.
Using the Enterprise Repository Objects

The following tables show all the objectsentities, relationships, and typesin an enterprise repository, along with the methods or actions that can be applied to each object. When you add a group-to-project relationship to an enterprise repository, you grant users in the group access to objects in the project. In doing so, you must specify: The scope of user accesswhat types of objects the group members can access. To specify a type of object, use the name in the Object type column of the following table. The method namewhat methods group members can perform on objects. To specify a method, use the name in the Method name column of the following table. For information on granting users access to objects and methods, see the Enterprise Administration Guide.
Listing of Enterprise Repository Objects, Methods, and Actions

A/B/C/D/E/F/G/H/I/K/L/M/O/P/R/S/T/U/V/W
Table 6-1 Enterprise Repository Objects User action Method name Description
Object type A ADMIN ADMIN APPCFG APPCFG APPCFG APPCFG
ACTIONS MENU ACTIONS ADDE ADDR BE
ACTIONS SECADM ACTIONS ADDE ADDR BE
List Entity Actions Security Administration List Entity Actions Add an Entity Add a Relation Browse Entity Attributes
6-1
Table 6-1
Enterprise Repository Objects (Continued) User action BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR Method name HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR Description Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes
Object type APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB
6-2
Enterprise Repository Objects
Table 6-1
Enterprise Repository Objects (Continued) User action REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB B BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BMPIMP BMPIMP BMPIMP BMPIMP
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEA SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes
6-3
Table 6-1
Object type BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ
6-4
Table 6-1
Enterprise Repository Objects (Continued) User action REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ C CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL COLLECT COLLECT COLLECT COLLECT
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes
6-5
Table 6-1
Object type COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN
6-6
Table 6-1
Enterprise Repository Objects (Continued) User action REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR ASSIGNCU B BE BINDPKG BK BR BTXE BTXR CO DE DR EW K LE LISTRBD LOCK LR ME MR PR RB REFRESH REP RES RIN S SA SRCH SUPERPR Method name REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFACU0 HMFMEDB BE BINDPKG HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE LISTRBD HMFUOLK LISTR MAINTE MAINTR PREPCOMP HMFMBND REFRESH HMFREP RESCOMP HMFMLU2 HMFMEDS SAVEAS SEARCH SUPERPR Description Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Assign Configuration Unit Browse Source Code Browse Entity Attributes Bind DB2 Package Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances List Rebuild Contents Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Prepare Component ReBind DB2 Plans Refresh Entity Produce Report View Results of Comp Actions Re-Install into CICS Define Source Code Save As Current Entity Search for Keywords Super Prepare
Object type COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN 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 COMP COMP COMP COMP COMP COMP
6-7
Table 6-1
Enterprise Repository Objects (Continued) User action TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type COMP COMP COMP COMP COMP CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS D DATA DATA DATA DATA DATA DATA DATA DATA
ACTIONS ADDE ADDR BE BK BR BTXE BTXR
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation
6-8
Table 6-1
Enterprise Repository Objects (Continued) User action CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR B BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES S Method name HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFMEDB BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL HMFMEDS Description Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Source Code Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Define Source Code
Object type DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS
6-9
Table 6-1
Enterprise Repository Objects (Continued) User action SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG E ENT ENT ENT ENT ENT ENT
ACTIONS ADDE ADDR BE BK BR
ACTIONS ADDE ADDR BE HMFMKEYB BR
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes
6-10
Table 6-1
Enterprise Repository Objects (Continued) User action BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES Method name TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL Description Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions
Object type ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT
6-11
Table 6-1
Enterprise Repository Objects (Continued) User action SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type EVENT EVENT EVENT EVENT EVENT EVENT EVENT F FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE
ACTIONS ADDE ADDR ASSIGNCU BE BK BR BTXE BTXR CO DE DR EW GD K LE LISTRBD LOCK LR ME MR PR REFRESH REP RES SA SRCH SUPERPR TXE TXR UEMTH UNLOCK URMTH
ACTIONS ADDE ADDR HMFACU0 BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMDDL HMFMKEY0 LISTE LISTRBD HMFUOLK LISTR MAINTE MAINTR PREPFILE REFRESH HMFREP RESFILE SAVEAS SEARCH SUPERPR TEXTE TEXTR UEMTH HMFUOFR URMTH
List Entity Actions Add an Entity Add a Relation Assign Configuration Unit Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Generate DDL Statements Define Keywords List Entity Instances List Rebuild Contents Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Prepare File Refresh Entity Produce Report View Results of File Actions Save As Current Entity Search for Keywords Super Prepare Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
6-12
Table 6-1
Enterprise Repository Objects (Continued) User action ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR B BE BK BR BTXE BTXR CO DE DR EW K Method name ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFMEDB BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 Description List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Source Code Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords
Object type FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM
6-13
Table 6-1
Enterprise Repository Objects (Continued) User action LE LOCK LR ME MR REFRESH RES S SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK Method name LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL HMFMEDS SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR Description List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Define Source Code Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity
Object type FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME
6-14
Table 6-1
Enterprise Repository Objects (Continued) User action URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH REP RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW Method name URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH HMFREP RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU Description HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity Produce Report View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report
Object type FSCHEME FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE
6-15
Table 6-1
Enterprise Repository Objects (Continued) User action K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE G GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method
6-16
Table 6-1
Enterprise Repository Objects (Continued) User action UNLOCK URMTH Method name HMFUOFR URMTH Description Unlock an Entity HPS User Relation Method
Object type GROUP GROUP H HELP HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT I IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT
EW ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH
HMFXWU ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH
Extended Where Used Report List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership
6-17
Table 6-1
Enterprise Repository Objects (Continued) User action DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT K KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords
6-18
Table 6-1
Enterprise Repository Objects (Continued) User action TXE TXR UEMTH UNLOCK URMTH Method name TEXTE TEXTR UEMTH HMFUOFR URMTH Description Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type KEY KEY KEY KEY KEY L LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR K LE LOCK LR ME MR REFRESH SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity
6-19
Table 6-1
Enterprise Repository Objects (Continued) User action DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR Method name DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR Description Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation
Object type LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO
6-20
Table 6-1
Enterprise Repository Objects (Continued) User action UEMTH UNLOCK URMTH Method name UEMTH HMFUOFR URMTH Description HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type LOGPRO LOGPRO LOGPRO M MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN
ACTIONS ADDE ADDR B BE BK BR BTXE BTXR CO DE DISPCFG DR EW K LE LOCK LR ME MR REFRESH RES S SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR ANALYZE APPROVE BE BK
ACTIONS ADDE ADDR HMFMEDB BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DISPCFG DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL HMFMEDS SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR ANALYZE SIGNOFF BE HMFMKEYB
List Entity Actions Add an Entity Add a Relation Browse Source Code Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity View Machine Configuration Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Define Source Code Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Analyze Migration Impact Approve a Migration Process Browse Entity Attributes Browse Keywords
6-21
Table 6-1
Enterprise Repository Objects (Continued) User action BR BTXE BTXR CLEANUP CO COPYAPP COPYMIG COUNT DE DR EW EXPORT IMPORT K LE LISTMIG LOCK LR ME MIGRATE MR RD REFRESH REP RES SRCH TXE TXR UEMTH UNLOCK URMTH Method name BR TEXTBE TEXTBR CLEANUP HMFCOS0 COPYAPP COPYMIG COUNT DELETEE DELETER HMFXWU EXPORT IMPORT HMFMKEY0 LISTE LISTMIG HMFUOLK LISTR MAINTE MIGRATE MAINTR GARDX00 REFRESH REP RESMIG SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Browse Relation Attributes Browse Text for Entity Browse Text for Relation Clean-Up Migration Information Change Ownership Copy Application Executables Copy Migration Files Summary Counts for Migration Delete an Entity Delete a Relation Extended Where Used Report Export Migration Import Migration Define Keywords List Entity Instances List Migration Contents Lock an Entity List Relation Instances Maintain Entity Attributes Automated Migration Facility Maintain Relation Attributes Analyze Rebuild Impact Refresh Entity Report on a Migration View Results of Mig Actions Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN O ORG ORG ORG ORG ORG ORG ORG ORG ORG
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership
6-22
Table 6-1
Enterprise Repository Objects (Continued) User action DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG P PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION
ACTIONS ACTIVATE ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA
ACTIONS ACTIVATE ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS
List Entity Actions Activate Configuration Unit Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity
6-23
Table 6-1
Enterprise Repository Objects (Continued) User action SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR ASSIGNCU BE BK BR BTXE Method name SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFACU0 BE HMFMKEYB BR TEXTBE Description Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Assign Configuration Unit Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity
Object type PARTITION PARTITION PARTITION PARTITION PARTITION PARTITION PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES
6-24
Table 6-1
Enterprise Repository Objects (Continued) User action BTXR CO DE DR EW K LE LISTRBD LOCK LR ME MR PR PRB REFRESH REP RES SA SRCH SUPERPR TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR DE DR EW IMS K LE LOCK LR Method name TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE LISTRBD HMFUOLK LISTR MAINTE MAINTR PREPPROC PREPPRCB REFRESH HMFREP RESGLBL SAVEAS SEARCH SUPERPR TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR DELETEE DELETER HMFXWU IMSUTIL HMFMKEY0 LISTE HMFUOLK LISTR Description Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances List Rebuild Contents Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Prepare Execution Environment Prepare Exec Env (background) Refresh Entity Produce Report View Results of Actions Save As Current Entity Search for Keywords Super Prepare Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Delete an Entity Delete a Relation Extended Where Used Report IMS Utilities Define Keywords List Entity Instances Lock an Entity List Relation Instances
Object type PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT
6-25
Table 6-1
Enterprise Repository Objects (Continued) User action ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT R RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG
ACTIONS ADDE ADDR BE BK BR BTXE CLEANUP CO DE DR EW EXPORT K LE LISTMIG LISTRBD LOCK LR ME MR RANALYZE REFRESH REP RES RESETINS RESETPR RINSTALL RPREPARE
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE RBDCLUP HMFCOS0 DELETEE DELETER HMFXWU EXPORT HMFMKEY0 LISTE LISTMIG LISTRBD HMFUOLK LISTR MAINTE MAINTR RANALYZE REFRESH RREPORT RESRBD RESETINS RESETPR RINSTALL RPREPARE
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Clean-Up Rebuild Information Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Export Migration Define Keywords List Entity Instances List Migration Contents List Rebuild Contents Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Rebuild Analyze Refresh Entity Report View Results of Rebuild Reset Install Reset Prepare Rebuild Install Rebuild Prepare
6-26
Table 6-1
Enterprise Repository Objects (Continued) User action SA SRCH SUPERPR TXE UEMTH UNLOCK URMTH ACTIONS ADDE ADDR ASSIGNCU B BE BK BR BTXE BTXR CO DE DR EW K LE LISTRBD LOCK LR ME MR PR REFRESH REP RES S SA SRCH SUPERPR TXE TXR UEMTH UNLOCK URMTH Method name SAVEAS SEARCH SUPERPR TEXTE UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFACU0 HMFMEDB BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE LISTRBD HMFUOLK LISTR MAINTE MAINTR PREPREP REFRESH HMFREP RESREP HMFMEDS SAVEAS SEARCH SUPERPR TEXTE TEXTR UEMTH HMFUOFR URMTH Description Save As Current Entity Search for Keywords Super Prepare Define Text for Entity HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Assign Configuration Unit Browse Source Code Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances List Rebuild Contents Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Prepare Report Refresh Entity Produce Report View Results of Report Actions Define Source Code Save As Current Entity Search for Keywords Super Prepare Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT
6-27
Table 6-1
Enterprise Repository Objects (Continued) User action ACTIONS ADDE ADDR BE BK BR BTXE BTXR DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK Method name ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK Description List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity
Object type REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN
6-28
Table 6-1
Enterprise Repository Objects (Continued) User action LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR ASSIGNCU B BE BINDPKG BK BR BTS BTXE BTXR CO DE DR DYNAMIC EW K LE LISTRBD LOCK LR ME MR PR PSB RBD RDTL REFRESH Method name LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFACU0 HMFMEDB BE BINDPKG HMFMKEYB BR BTS TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFDYLK HMFXWU HMFMKEY0 LISTE LISTRBD HMFUOLK LISTR MAINTE MAINTR PREPRULE MODPSB RBDRULE RDTL REFRESH Description List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Assign Configuration Unit Browse Source Code Browse Entity Attributes Bind DB2 Package Browse Keywords Browse Relation Attributes Batch Terminal Simulation Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Establish Dynamic Linkage Extended Where Used Report Define Keywords List Entity Instances List Rebuild Contents Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Prepare Rule Modify PSB (IMS) Rebuild Entity IMS Rule Processing Detail Refresh Entity
Object type RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE
6-29
Table 6-1
Enterprise Repository Objects (Continued) User action REP RES S SA SRCH STATIC SUPERPR TE TXE TXR UEMTH UNLOCK URMTH VER Method name HMFREP RESRULE HMFMEDS SAVEAS SEARCH HMFSTLK SUPERPR HMFMBTST TEXTE TEXTR UEMTH HMFUOFR URMTH HMFLEXO Description Produce Report View Results of Rule Actions Define Source Code Save As Current Entity Search for Keywords Establish Static Linkage Super Prepare Test Batch Entity Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method Verify Hierarchy
Object type RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE S SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN
ACTIONS ADDE ADDR B BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH REP RES S SA SRCH TXE
ACTIONS ADDE ADDR HMFMEDB BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH HMFREP RESGLBL HMFMEDS SAVEAS SEARCH TEXTE
List Entity Actions Add an Entity Add a Relation Browse Source Code Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity Produce Report View Results of Actions Define Source Code Save As Current Entity Search for Keywords Define Text for Entity
6-30
Table 6-1
Enterprise Repository Objects (Continued) User action TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR B BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES S SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR ASSIGNCU BE BK BR BTXE Method name TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFMEDB BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL HMFMEDS SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFACU0 BE HMFMKEYB BR TEXTBE Description Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Source Code Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Define Source Code Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Assign Configuration Unit Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity
Object type SECTN SECTN SECTN SECTN SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SET SET SET SET SET SET SET SET
6-31
Table 6-1
Enterprise Repository Objects (Continued) User action BTXR CO DE DR EW K LE LISTRBD LOCK LR ME MR PR REFRESH REP RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR Method name TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE LISTRBD HMFUOLK LISTR MAINTE MAINTR PREPSET REFRESH HMFREP RESSET SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR Description Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances List Rebuild Contents Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Prepare Set Refresh Entity Produce Report View Results of Set Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes
Object type SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE
6-32
Table 6-1
Enterprise Repository Objects (Continued) User action REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK Method name REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB Description Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords
Object type STATE STATE STATE STATE STATE STATE STATE STATE STATE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL
6-33
Table 6-1
Enterprise Repository Objects (Continued) User action BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL T TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes
6-34
Table 6-1
Enterprise Repository Objects (Continued) User action REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity HPS User Relation Method
Object type TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS U USER USER USER USER
ACTIONS ADDE ADDR BE
ACTIONS ADDE ADDR BE
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes
6-35
Table 6-1
Enterprise Repository Objects (Continued) User action BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation User Entity Method Unlock an Entity User Relation Method
Object type USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER V VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES
ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME
ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE
List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes
6-36
Table 6-1
Enterprise Repository Objects (Continued) User action MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LR ME MR PR REFRESH REP RES SA SRCH TXE TXR UEMTH UNLOCK URMTH Method name MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LISTR MAINTE MAINTR PREPVIEW REFRESH HMFREP RESVIEW SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH Description Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Prepare View Refresh Entity Produce Report View Results of View Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation HPS User Entity Method Unlock an Entity User Relation Method
Object type VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW W WEAKENT
ACTIONS
ACTIONS
List Entity Action
6-37
Table 6-1
Enterprise Repository Objects (Continued) User action ADDE ADDR BE BK BR BTXE BTXR CO DE DR EW K LE LOCK LOCKST LR ME MR REFRESH RES SA SRCH TXE TXR UEMTH UNLOCK URMTH ACTIONS ADDE ADDR ASSIGNCU BE BK BR BTXE BTXR CO DE DR EW K Method name ADDE ADDR BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 LISTE HMFUOLK LOCKST LLISTR MAINTE MAINTR REFRESH RESGLBL SAVEAS SEARCH TEXTE TEXTR UEMTH HMFUOFR URMTH ACTIONS ADDE ADDR HMFACU0 BE HMFMKEYB BR TEXTBE TEXTBR HMFCOS0 DELETEE DELETER HMFXWU HMFMKEY0 Description Add an Entity Add a Relation Browse Entity Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords List Entity Instances Lock an Entity Get Lock Status List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Refresh Entity View Results of Actions Save As Current Entity Search for Keywords Define Text for Entity Define Text for Relation User Entity Method Unlock an Entity HPS User Relation Method List Entity Actions Add an Entity Add a Relation Assign Configuration Unit Browse Entity Attributes Browse Keywords Browse Relation Attributes Browse Text for Entity Browse Text for Relation Change Ownership Delete an Entity Delete a Relation Extended Where Used Report Define Keywords
Object type WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WEAKENT WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW
6-38
Table 6-1
Enterprise Repository Objects (Continued) User action LE LISTRBD LOCK LR ME MR PR REFRESH REP RES SA SRCH SUPERPR TS TXE TXR UEMTH UNLOCK URMTH Method name LISTE LISTRBD HMFUOLK LISTR MAINTE MAINTR PREPWIN REFRESH HMFREP RESWIN SAVEAS SEARCH SUPERPR HMFTSID TEXTE TEXTR UEMTH HMFUOFR URMTH Description List Entity Instances List Rebuild Contents Lock an Entity List Relation Instances Maintain Entity Attributes Maintain Relation Attributes Prepare Window Refresh Entity Produce Report View Results of Window Actions Save As Current Entity Search for Keywords Super Prepare Transaction Switch Define Text for Entity Define Text for Relation User Entity Method Unlock an Entity User Relation Method
Object type WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW
6-39
6-40
APPENDIX
BACKWARDS COMPATIBILITY
In AppBuilder, there are some entities and relationships that appear on the mainframe but not on the workstation (PC). These entities serve to maintain backward compatibility with earlier versions of the product. We do not recommend using these relationships or properties with newer versions of the product, and they are listed here just for informational purposes only. New Entities New Relationships There are also some new workstation features that have not yet been implemented on the host. Consequently, there are some entities and relationships that appear on the workstation, but not on the host.
New Entities
The supported platforms for each entity are outlined in the following sections:
Table A-1 Supported Platforms
Component Database Entity File Group Help Text
Logical Process Migration Project Rebuild Package Relationship
Rule Server Symbol Table User
Component
The following relationships appear on the host, but not on the workstation: A Component accesses a Database A Component is-contained-in a Server A Component is-root-of Rebuild Package
A-1
New Entities
Database Entity
The following relationships appear on the host, but not on the workstation: A Database is accessed-by a Component A Database is accessed-by a Rule
File
The following relationship appears on the host, but not on the workstation: A File is-forwarded-from a File
Group
The following relationships appear on the host, but not on the workstation: Group is Profiled by Migration Group is profiled by Rebuild Package
Help Text
The following properties appear on the host, but not on the workstation: Country Language
Logical Process
The following property appears on the workstation, but not on the host: Mode attribute called Logical Function
Migration
The following properties appear on the host, but not on the workstation: Description Data Set Prefix
A-2
Backwards Compatibility
New Entities
Project
The following relationship appears on the host, but not on the workstation: Project is-member-of Group The following properties appear on the host, but not on the workstation Project ID Description
Rebuild Package
This entity does not exist on the workstation.
Relationship
The following relationships appear on the host, but not on the workstation: A Relationship implements an Attribute A Relationship implements a Data Type A Relationship implements an Entity
Rule
The following relationship appears on the host, but not on the workstation: A Rule accesses a Database
Server
The following relationship appears on the host, but not on the workstation: A Server derives a Server
Symbol
The following properties are required on the host: Symbol define Symbol encoding
A-3
New Relationships
Table
The following relationship appears on the host, but not on the workstation: A Table is-basis-of a Table
User
The following property appears on the workstation, but not on the host: Project The following properties appear on the host, but not on the workstation: Job account information Job name Job options
New Relationships
The relationship properties support for each platform is outlined in the following sections: Is-carried-out-at Is-involved-in Is-modified-by Is-profiled-by Is-responsible-for Is-signatured-by Is-site-of Is-supported-by Refines-into Replaces
Is-carried-out-at
The following properties appear on the workstation, but not on the host: Major involvement in function Minor involvement in function
A-4
New Relationships
Is-involved-in
This relationship does not appear on the host.
Is-modified-by
Is-profiled-by
The following property appears on the host, but not on the workstation: Profile type
Is-responsible-for
Is-signatured-by
Is-site-of
Is-supported-by
Refines-into
The following property does not appear on the host: Condition flag
Replaces
A-5
New Relationships
A-6
Index
INDEX
A
abbreviations guidelines 4-2 access properties from Construction Workbench 1-4 from Freeway Explorer 1-4 Accesses relationship type 3-6 actions Enterprise Repository 6-1 Affects relationship type 3-7 Application Configuration entity type 2-5 Relationship types 2-5 Attribute entity type 2-5 audit properties entity types 1-5
Contains relationship type 3-10 functional sets 3-13 Server contains Rule variant 3-14 Set contains Value variant 3-11 setting window messages 3-13 Converses relationship type 3-14 Created/Remote date property 2-3
D
Data Type entity type 2-17 Relationship types 2-19 Database entity type 2-16 Relationship types 2-17 Date created property 2-3 Depends-on relationship type 3-15 Drawing entity type 2-19
B
Bitmap entity type 2-7 Relationship types 2-7 Business Object entity type 2-8 Relationship types 2-9
E
Encapsulates relationship type 3-16 Enterprise Administration Information Model 5-1 enterprise repository 1-3 common properties in 1-6 Enterprise Repository Objects 6-1 entity audit attributes in Enterprise Repository 5-3 Entity entity type 2-21 Relationship types 2-23 entity properties Change Number 2-3 Created/Remote Date 2-3 Date Created 2-3 Explicit Lock 2-3 Name 2-2 Owner 2-3 Project 2-3 QA status 2-3 System ID 2-2
C
Can-Access relationship type 3-7 can-be-accessed-by 3-7 Causes relationship type 3-8 Change Number property 2-3 Cites relationship type 3-8 Collection entity type 2-10 Relationship types 2-11 Column entity type 2-12 Relationship types 2-13 common properties entity types 2-1 Component entity type 2-13 Relationship types 2-15 Component Folder entity type 2-15 Comprises relationship type 3-8 Connects-to relationship type 3-9
entity types Application Configuration 2-5 Attribute 2-5 audit properties 1-5 Bitmap 2-7 Business Object 2-8 Collection 2-10 Column 2-12 common properties 2-1 Component 2-13 Component Folder 2-15 Data Type 2-17 Database 2-16 definition 2-1 Drawing 2-19 Entity 2-21 Event 2-24 Field 2-25 File 2-28 Function 2-29 Identifier 2-30 Key 2-31 Logical Process 2-33 Machine 2-35 Migration 2-36 Partition 2-38 Physical Event 2-41 Process 2-41 Relationship 2-43 Report 2-45 Rule 2-47 Section 2-49 Server 2-50 Set 2-50 State 2-53 Symbol 2-54 Table 2-55 Transition 2-57 Value 2-58 View 2-58 Window 2-60 Event entity type 2-24 Relationship types 2-24 Explicit lock property 2-3
G
generated property 1-2 Group entity 5-5
H
Has relationship type 3-18 Has STD relationship type 3-19
I
Identifier entity type 2-30 Relationship types 2-31 Impacts relationship type 3-19 Includes relationship type 3-20 Influences relationship type 3-21 Information Model Enterprise 5-1 relationship types 3-5 Initiates relationship type 3-22 internal object types defined 1-3 Intersects-with relationship type 3-22 Invokes relationship type 3-23 Is-carried-out-at relationship type 3-24 Is-composed-of relationship type 3-24 Is-constrained-by relationship type 3-25 Is-defined-by relationship type 3-25 Is-described-by relationship type 3-26 Is-distributed-at relationship type 3-26 Is-forwarded-from relationship type 3-27 Is-forwarded-to relationship type 3-27 is-had-by 3-18 Is-implemented-by relationship type 3-27 Is-involved-in relationship types 3-29 Is-keyed-by relationship type 3-29 Is-modified-at relationship type 3-30 Is-modified-by relationship type 3-30 is-owned-by 3-36 Is-preconditioned-by relationship type 3-31 Is-profiled-by relationship type 3-32 Is-referenced-by relationship type 3-32 Is-related-via relationship type 3-33 Is-replaced-by relationship type 3-33 Is-responsible-for relationship type 3-34 Is-site-of relationship type 3-35 is-the-result-of 3-41 Is-typed-by relationship type 3-35
F
Field entity type 2-25 Relationship types 2-28 File entity type 2-28 Relationship types 2-29 Freeway repository 1-3 Function entity type 2-29 Relationship types 2-30 functional sets 3-13
K
Key entity type 2-31 Relationship types 2-32
Index
ii
L
Logical Process entity type 2-33 Relationship types 2-34
property generated 1-2 optional 1-2 required 1-2 Public entry type (contains) 3-14
M
Machine entity type 2-35 Relationship types 2-36 Maps relationship type 3-35 Member relationship type 3-36 methods Enterprise Repository 6-1 Migration entity type 2-36 migration relationship attribute in Enterprise Repository 5-4
Q
QA status property 2-3
R
Refers-to relationship type 3-38 Refines-into relationship type 3-39 Relates 3-33 relationship audit attributes 5-4 Relationship entity type 2-43 Relationship types 2-44 relationship properties ChangeNumber 3-3 Child Name 3-3 Created by 3-4 Created/Remote date 3-3 Created/Remote time 3-4 Created/Remote user 3-4 Date created 3-3 Date maintained 3-4 definition 1-2 Internal Name 3-3 Maintained by 3-4 Maintained/Local date 3-4 Maintained/Local time 3-4 Maintained/Remote date 3-4 Maintained/Remote time 3-4 Maintained/Remote user 3-4 Parent Name 3-3 QA Status 3-3 Separator Identifier 3-3 Sequence Number 3-3 Time created 3-4 Time Maintained 3-4 Version 3-4
N
Name property 2-2
O
Object Audit Information pop-up window for entity types 1-5 for relationship types 3-2 objects Enterprise Repository 6-1 optional property 1-2 Owner property 2-3 Owns relationship type 3-36 business object owns variant 3-37 Owns view variant 3-37
P
Partition entity type 2-38 Relationship types 2-40 Partitioned relationship type 3-38 personal repository common properties in 3-2 Physical Event entity type 2-41 Physical Event entity type Relationship types 2-41 Private entry type (contains) 3-14 Process entity type 2-41 Relationship types 2-42 programming terminology 1-5 Project entity 5-7 Project property 2-3 properties audit 1-5 common 3-1 see common properties definition 1-2
Index
iii
Relationship types Accesses,is-accessed-by 3-6 Affects,is-affected-by 3-7 Can-Access 3-7 Causes,is-caused-by 3-8 Cites,is-cited-by 3-8 Comprises,in-comprised-of 3-8 Connects,is-connected-to 3-9 Contains,is-contained-in 3-10 Converses,is-conversed-by 3-14 Depends-on,is-depended-on-by 3-15 Encapsulates,is-encapsulated-by 3-16 Has 3-18 Has STD,has-a-state-transition-diagram 3-19 Impacts,is-impacted-by 3-19 Includes,is-included-in 3-20 Influences,is-influenced-by 3-21 Initiates,is-initiated-by 3-22 Intersects,intersects-with 3-22 Invokes,is-invoked-by 3-23 Is-carried-out-at,Carries Out 3-24 Is-composed-of,Composes 3-24 Is-constrained-by,Constrains 3-25 Is-defined-by,Defines 3-25 Is-described-by,Describes 3-26 Is-distributed-at,Where-is-distributed 3-26 Is-forwarded-to,Is-forwarded-from 3-27 Is-implemented-by,Implements 3-27 Is-involved-in,Involves 3-29 Is-keyed-by,Keys 3-29 Is-modified-at,Where-is-modified 3-30 Is-modified-by,Modifies 3-30 Is-preconditioned-by,Preconditions 3-31 Is-profiled-by,Profiles 3-32 Is-referenced-by,References 3-32 Is-related-via 3-33 Is-replaced-by,Replaces 3-33 Is-responsible-for,is-the-responsibility-of 3-34 Is-site-of,Has-as-its-site 3-35 Is-typed-by,Types 3-35 Maps,is-mapped-to 3-35 Member,is-member-of 3-36 of Application Configuration entity 2-5 of Attribute entity 2-6 of Bitmap entity 2-7 of Business Object entity 2-9 of Collection entity 2-11 of Column entity 2-13 of Component entity 2-15 of Component Folder 2-16 of Data Type entity 2-19 of Database entity 2-17 of Drawing entity 2-21 of Entity entity 2-23
of Event entity 2-24 of Field entity 2-28 of File entity 2-29 of Function entity 2-30 of Identifier entity 2-31 of Key entity 2-32 of Logical Process entity 2-34 of Machine entity 2-36 of Migration entity 2-37 of Partition entity 2-40 of Physical Event entity 2-41 of Process entity 2-42 of Relationship entity 2-44 of Report entity 2-46 of Rule entity 2-48 of Section entity 2-50 of Server entity 2-50 of Set entity 2-53 of State entity 2-54 of Symbol entity 2-55 of Table entity 2-56 of Transition entity 2-57 of Value entity 2-58 of View entity 2-59 of Window entity 2-60 Owns 3-36 Partitioned,partitioned-by 3-38 Refers-to,is-referred-to-by 3-38 Refines-into,is-refined-from 3-39 Replaces System,System-is-replaced-by 3-40 Results-in 3-41 Stores,provides-storage-for 3-42 Supports,is-supported-by 3-43 Triggers,is-triggered-by 3-44 Uses,is-used-by 3-45 relationship types common properties 3-1 definition 3-1 in Information Model 3-5 Replaces System relationship type 3-40 Report entity type 2-45 Relationship types 2-46 repository types 1-2 required property 1-2 Results-in relationship type 3-41 Rule entity type 2-47 Relationship types 2-48
S
Section entity type 2-49 Relationship types 2-50
Index
iv
Server entity type 2-50 Relationship types 2-50 Set contains Value variant 3-11 Set entity type 2-50 Relationship types 2-53 setting window messages 3-13 State entity type 2-53 Relationship types 2-54 Stores relationship type 3-42 submodels defined 1-3 Supports relationship type 3-43 Symbol entity type 2-54 Relationship types 2-55 System ID property 2-2
W
Window entity type 2-60 Relationship types 2-60 workgroup repository 1-3
T
Table entity type 2-55 Relationship types 2-56 text standards abbreviations 4-2 general guidelines 4-1 history 4-2 narrative 4-1 object name 4-1 object specific characteristics 4-2 special considerations 4-2 Transition entity type 2-57 Relationship types 2-57 Triggers relationship type 3-44
U
User entity in Enterprise Information Model 5-2 Uses relationship type 3-45
V
Value entity type 2-58 Relationship types 2-58 variants Business Object Owns 3-37 definition of relationship type 3-5 Depends-on Logical Process 3-15 Owns View 3-37 Process depends-on Process 3-15 Rule depends-on Rule 3-15 Server contains Rule 3-14 Set contains Value 3-11 View entity type 2-58 Relationship types 2-59
Index
Index
vi

App Build Information Model

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

App Build Information Model

Transféré par

Droits d'auteur :

Formats disponibles

BluePhoenix AppBuilder 2.1.0.

Information Model Reference Guide

AppBuilder 2.1.0 Information Model Reference Guide

1 Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

2 Entity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

AppBuilder 2.1.0 Information Model Reference Guide

AppBuilder 2.1.0 Information Model Reference Guide

4 Text Property Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

5 Enterprise Administration Information Model . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

6 Enterprise Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

AppBuilder 2.1.0 Information Model Reference Guide

AppBuilder 2.1.0 Information Model Reference Guide

Understanding the Information Model

AppBuilder 2.1.0 Information Model Reference Guide

Information Model Elements

Information Model Elements

Information Model Elements

Internal Object Types

AppBuilder 2.1.0 Information Model Reference Guide

AppBuilder 2.1.0 Information Model Reference Guide

Audit and Remote Audit Tabs

Design and Construction: Data View

TABLE has has is-referenced-by

includes IDENTIFIER KEY VIEW

is-typed-by SET composes DATA TYPE

Design and Construction: Data Traceability View

is-implemented-by connects-to ENTITY is-implemented-by is-implemented-by is-implemented-by

is-implemented-by IDENTIFIER connects-to COLLECTION is-implemented-by

AppBuilder 2.1.0 Information Model Reference Guide

Design and Construction: Process View

WINDOW PHYSICAL EVENT refers-to

INSTANCE OF OBJECT TYPE

AppBuilder 2.1.0 Information Model Reference Guide

Common Properties of Entity Types

AppBuilder 2.1.0 Information Model Reference Guide

Common Properties of Entity Types

Common Entity Type Property Descriptions

Common Properties of Entity Types

AppBuilder 2.1.0 Information Model Reference Guide

Table 2-1 Collection Column

Component Component Folder Database Data Type Drawing Entity

AppBuilder 2.1.0 Information Model Reference Guide

Attribute Properties Dialog

Attribute is composed of Attribute Identifier describes Attribute

Implementation Name Description

AppBuilder 2.1.0 Information Model Reference Guide

Inverse Relationships Bitmap is-had-by Bitmap Implementation

Business Object Properties Dialog

Field in Dialog Description

AppBuilder 2.1.0 Information Model Reference Guide

Table 2-6 FROM

Table 2-7 Property Type

Number of elements Number of groups

AppBuilder 2.1.0 Information Model Reference Guide

Field in Dialog Implementation name

AppBuilder 2.1.0 Information Model Reference Guide

Component Properties Dialog

AppBuilder 2.1.0 Information Model Reference Guide

Component Folder Properties Dialog

Database Properties Dialog

Database directory path Implementation name

AppBuilder 2.1.0 Information Model Reference Guide

Data Type Properties Dialog