app builder enterprise application

8/14/2019 App Builder Enterprise Application

1/273

BluePhoenix AppBuilder 2.0.3.1

Enterprise Application Guide


2/273

BluePhoenix AppBuilder 2.0.3.1Enterprise Application Guide

November, 2002

Corporate Headquarters

BluePhoenix Solutions

Vlierwerf 7B4704 SB Roosendaal

The Netherlands+31 (0) 165 399 401

+31 (0) 165 396 308 faxwww.bluephoenixsolutions.nl

USA Headquarters

BluePhoenix Solutions USA, Inc.

8000 Regency ParkwayCary, NC 27511

United States+1 919.380.5100

+1 919.380.5111 faxwww.bluephoenixsolutions.com

1992-2002 BluePhoenix Solutions

All rights reserved.

BluePhoenix is a trademark of BluePhoenix Solutions. All other product and company names

mentioned herein are for identification purposes only and are the property of, and may be trademarks

of, their respective owners.

Portions of this product may be covered by U.S. Patent Numbers 5,495,222 and 5,495,610 and various

other non-U.S. patents.

The software supplied with this document is the property of BluePhoenix Solutions, and is furnishedunder 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 documentis 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 thisdocument is subject to change without prior notice and does not represent a commitment by

BluePhoenix Solutions or its representatives.
http://www.bluephoenixsolutions.com/http://www.bluephoenixsolutions.com/http://www.bluephoenixsolutions.com/http://www.bluephoenixsolutions.com/


3/273

AppBuilder 2.0.3.1 Enterprise Application Guide i

TABLE OF

CONTENTS Table of Contents

AppBuilder 2.0.3.1 Enterprise Application Guide

1 Using the Enterprise Repository Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Accessing the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1ISPF/PDF Primary Option Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

System Options Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Entities Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Using Enterprise Repository Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

List Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Detail Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Pop-up Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Using Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Navigating the Enterprise Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14ACTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

PROJECTS Changing Your Project and Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17ENTITY Listing Entity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

LE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18LR.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

UPROF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

Viewing Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22

2 Setting Enterprise Repository Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Using Object Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Modifying Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Selecting a Current Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Creating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Updating Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Summary of Access Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Using Method Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

3 Locking Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Lock Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1


4/273

i i AppBuilder 2.0.3.1 Enterprise Application Guide

LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

UNLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Accessing Locked Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

4 Defining the Application Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Building Applications with the Information Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Window View Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Adding, Saving, and Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

ADDE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

ADDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

DE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

DR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

SA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

SAVE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Maintaining Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

ME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

MR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

TXE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

TXR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

CO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Reusing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

EW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

REP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

SRCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Building Applications with Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Creating a Component to Use with a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Using a Component with Another Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

Accessing DB2 Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

Defining DB2 Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Accessing Non-DB2 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

5 Building Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Using Build Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

ACTIVATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

ASSIGNCU.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

BINDPKG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

DEACTIVE.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

DYNAMIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

GD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

LISTRBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9


5/273

Table of Contents iii

PR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Preparing Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Preparing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Preparing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Preparing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Preparing Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Preparing Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Preparing Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

PSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

RB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

RBD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27

Relinking a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

Rebinding a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29

Reinstalling a Rule into CICS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30

RDTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31

RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

RIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

STATIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

SUPERPR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35

TRANS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35

TS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35

VER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36

6 Writing CICS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Designing CICS using AppBuilder Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Sample COBOL II Component Line Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Sample COBOL II CICS Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Sample PL/I Component Line Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Sample PL/I CICS Component.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Component Communications Area (HPSCOMM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

PL/I Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

COBOL II Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

BAL Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

7 Preparing CICS Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Understanding CICS Pseudoconversational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Preparing an Entity for Multiple CICS Regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Using RBD to Relink a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Using RBD to Reinstall a Rule to CICS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Using RIN to Reinstall Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3


6/273

iv AppBuilder 2.0.3.1 Enterprise Application Guide

Determining Transaction IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Determining DB2 Plan Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

8 API for CICS (HPECAPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Using HPECAPI to Invoke AppBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

User COMMAREA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

RULE-NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

IV-NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

IV-PTR/ADDRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

IV-FLENGTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

OV-NAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

OV-PTR/ADDRESS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

OV-FLENGTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

HPS-USER-PARM-EYECATCHER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

HPS-USER-PARM-FUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

HPS-USER-PARM-SUBFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

HPS-USER-PARM-RET-CODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

HPS-USER-PARM-USE-TERM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4HPS-USER-PARM-USE-TRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

HPS-USER-PARM-RET-TERM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

HPS-USER-PARM-RET-TRAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

HPS-USER-PARM-ERR-MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Interface Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

CICS LINK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

CICS START. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

CICS XCTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

CICS RETURN IMMEDIATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

9 Preparing IMS Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Designing IMS Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Common IMS Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Writing and Processing IMS Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

USE RULEINIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Run Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Configuring BMP and DL/I Batch Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

IMS Actions and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

PSB - Generation Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

Updating a Rules IMS Processing Details (RDTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

IMS Run Control Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

Message Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16Rule Selection List: HPR0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

10 Writing IMS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Accessing the IMS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Mapping Input View Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Calling a PL/I Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2


7/273

Table of Contents v

Sample Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Assembler Batch (using DB2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

COBOL (using IMS AIB and Checkpoint Restart) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

PL/I (Using IMS non-AIB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9

Component Communications Area (HPSCOMM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11

11 Using IMS Interfaces: HPECAPI and HPUCV10. . . . . . . . . . . . . . . . . . . 11-1

Using IMS Interface Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

LINK Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Function Code Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

12 Generating OpenCOBOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

OpenCOBOL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Compiler Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Mapping Implementation Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Compatibility Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Configuring Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Performance Marshaling for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Host Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

VIEW Prepare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6

SET Prepare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6

Rule Prepare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Configuring the Initialization File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Defining Options in the Initialization File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

OpenCOBOL Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Rules Language Support and Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9

3270 Converse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9Native COBOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9

Large Decimals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Component Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Dynamic COBOL Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Truncating Intermediate Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

TIMESTAMP Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Mathematical Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

13 Writing Batch Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

PL/I Component STAE Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Sample BAL Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Sample C Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Sample COBOL Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Sample PL/I Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Component Communications Area (HPSCOMM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

PL/I Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

COBOL II Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5

BAL Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7

C Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9


8/273

vi AppBuilder 2.0.3.1 Enterprise Application Guide

14 Sample Batch Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Batch DB2 Command Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Batch Command Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

15 Batch API for PLI and COBOL II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1Using HPBCAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

LINK Rule Initiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Static Link Initiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

COBOL Dynamic Call Initiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

User Commarea. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

RULE-NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

IV-NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

IV-PTR/ADDRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

IV-FLENGTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

OV-NAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

OV-PTR/ADDRESS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

OV-FLENGTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4HPS-USER-PARM-EYECATCHER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

HPS-USER-PARM-FUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

HPS-USER-PARM-SUBFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

HPS-USER-PARM-RET-CODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

HPS-USER-PARM-USE-TERM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

HPS-USER-PARM-USE-TRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

HPS-USER-PARM-RET-TERM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

HPS-USER-PARM-RET-TRAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

HPS-USER-PARM-ERR-MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

Static Linkage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6

16 Configuring Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Using Configuration Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Understanding Configuration Objects and Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Setting Configuration Object Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Relating Preparable Entities to a Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6

Preparing for Multiple Execution Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6

DB2 Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7

Changing the Qualifier of DB2 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8

Changing the Owner of DB2 Plans and Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9

Changing the Isolation Mode for DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10

Using DB2 Packages and Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10

Binding with Packages and DBRMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11

Setting INI Variables for DB2 Qualifier/Owner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12

INI Variables and DB2 Binds using Partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13

INI Variables and DB2 Binds without Partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19

Examples of DB2 INI Settings without Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-23


9/273

Table of Contents vii

17 3270 Converse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Executing 3270 Converse in CICS and IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

CICS Execution Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

IMS Execution Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Prerequisites for 3270 Window Painter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Sharing Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

National Language Support/Multiple Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Host Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

Window Prepare (PR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

Results (RES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4

Preparing Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

Rule Prepare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

Hybrid Rule Execution Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

HPC7 Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

HPR0 Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

3270 Converse Application Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

3270 Converse Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8

Input Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9Multicolumn List Box Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10

Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10

Error Messages for 3270 Converse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11

Help for 3270 Converse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12

Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12

Memory Management Tips.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12

Using HPECAPI in 3270 Converse Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15

Converse Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15

Deferred Converse Components Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15

18 Advanced Topics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Linking Run-time Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Dynamic Linking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Static Linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

Run-time Communications Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3

LU2 vs. LU6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3

Passing Messages using Global Eventing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4

Posting Rule Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4

Posting Rule Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5

Receiving Rule Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5

Receiving Rule Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5Defining Repository Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6

UEMTH and URMTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i


10/273

viii AppBuilder 2.0.3.1 Enterprise Application Guide


11/273

AppBuilder 2.0.3.1 Enterprise Application Guide 1-1

CHAPTER

1

USING THE ENTERPRISE

REPOSITORY INTERFACE


The enterprise repository interface of the Host Workbench lets you access the objects in an enterprise

repository. You can navigate within the enterprise repository by moving from object to objectthat is,

from panel to panel. To find a specific object in the repository, use one of the following methods:

Select its name or system identifier from an alphabetical list of all the objects of its type in therepository

Starting from one object, traverse a chain of entities and relationships connected to the object

Search for an object based on its keywords

You typically navigate through the repository by traversing the Information Model, panel by panel. For

example, you can move from a rule to a report it converses, and you can move from a field to a view that

includes that field. You can also use the repository interface to produce reports about your applications.

Accessing the Repository

Accessing the enterprise repository involves two steps:

1. From the ISPF/PDF Primary Option menu (Figure 1-1), select the option for AppBuilder to displaythe System Options panel (Figure 1-2).

2. From the System Options panel, select the option for the enterprise repository to display the Entities

panel, which lists all the entity types in the repository (Figure 1-3).

ISPF/PDF Primary Option Menu

Access the enterprise repository through the Interactive Structured Programming Facility/Program

Development Facility (ISPF/PDF) Primary Option menu (Figure 1-1). On the command line, type the

letter used to access the enterprise repository and press Enter. You specify this letter when you install the

AppBuilder (it is Hin the example). The System Options panel is then displayed.


12/273

1-2 Using the Enterprise Repository Interface


Figure 1-1 ISPF/PDF Primary Option Menu

System Options Panel

The System Options panel (Figure 1-2) is your entry point to the enterprise repository. The number of

options available depends on your installation. To access the enterprise repository, select option 1 (ER)

from the System Options panel and press Enterto display the Entities panel (Figure 1-3).


13/273



Figure 1-2 System Options Panel

Entities Panel

The Entities panel (Figure 1-3) lists all entity types in the enterprise repository. Relationships are not

included on the Entities panel because they pertain only to the entities they connect. You can access a

particular relationship, or list of pertinent relationships, by navigating from a specific entity.

The Entities panel is the first panel in the enterprise repository interface, and you can view it at any time

by typing ENTITYat the command line of any repository interface panel.


14/273


Using Enterprise Repository Panels

Figure 1-3 Entities Panel


The enterprise repository interface includes three types of panels:

List Panels

There are two kinds of list panels: Entity List Panelsand Relationship List Panels.

To scroll the entries in a list, in addition to the default function keysF7 to scroll up, F8 to scroll

downyou can also use the following standard ISPF/PDF commands: TOP, BOTTOM, UP, DOWN,and L (locate).

Entity List Panels

An entity list panel displays a list of instances of a specific entity typeall the rules in a repository, for

example. To access an entity list panel:

1. Type LEnext to the entity type on the Entities panel. Figure 1-4shows Rule being selected.

Table 1-1 Enterprise Repository Panel Types

List Panels Display a list of either entity or relationship instances

Detail Panels Display the attributes of a particular entity or relationship instance

Pop-up Panels Solicit information needed to process repository actions; seek

confirmation of actions, such as delete; and display information such as

error and other messages


15/273



Figure 1-4 Select Entity to be Listed

2. On the Action Information pop-up panel that appears (Figure 1-5 on page 1-5), specify how you

want the list of instances to appearfor example, sorted by name or system ID, in ascending or

descending order.

Note that with your user profile, you can suppress the Action Information pop-up panel (see

UPROFon page 1-20). If it is suppressed, then the list of entities is displayed as you specify in

your user profile.

Figure 1-5 Setting List Specifications

An entity list panel displays in columns all attribute values of each entity instance. To display columns

not visible, press F10to scroll left, or F11 to scroll right. To display more entity instances, press F8 to

scroll down or F7 to scroll up.

Figure 1-6shows an example of an entity list panel. It lists a page of rules from the enterprise repository

in ascending order by name.

LE


16/273



Figure 1-6 Entity List Panel for Rules

Relationship List Panels

A relationship list panel displays a list of relationships between a specific entity and some or all of the

entities to which it is related. You normally access a relationship list panel from an entity list panel.

1. On the entity list panel, type LRin the Action field beside the entity instance whose relations you

want to view and then press Enter. Figure 1-7shows view ACCOUNT_LST being selected.

Figure 1-7 Specifying Entity Relationships

2. The Relation Options panel is displayed. Type Sin the Select field for the relation type(s) you want

to view and then press Enter. Figure 1-8 on page 1-7shows a Relations Options pop-up panel onwhich two relationship types are selected.

LR


17/273



Figure 1-8 Relation Options Panel

3. A Relation List panel is displayed. If you select only one relationship, the Relation List panel looks

like Figure 1-9.You can use a function key (F10 and F11) to scroll through the relationship

attributes, which are shown in columns on the right side of the panel.

Figure 1-9 Relation List Showing a Single Relationship Type

If you select multiple relationships, the Relation List panel looks like Figure 1-10.When multiple

relationships are displayed, the relationship attributes are not displayed because not all attributes

are common to all relationships (however, you can use F10 and F11 to view the system ID or name).


18/273



Figure 1-10 Relation List Showing Multiple Relationship Types

Detail Panels

For each object in the enterprise repository, you can access a detail panelthat displays all of the available

information about a selected entity or relationship instance. Figure 1-11shows an entity detail panel,and Figure 1-12shows a sample relationship detail panel for the uses-rule relationship. (The level

number changes depending on when each panel is displayed. Level numbers are explained in Levelson

page 1-13.)

Detail panels display the available detailed information about a selected entity or relation instance.

These panels are accessed using the commands:

BE (browse entity)

BR (browse relationship)

ME (maintain entity)

MR (maintain relationship)

Chapter 4, Defining the Application Modelprovides specific information on these commands.

Figure 1-11shows an entity detail panel from a BE (browse entity) command for a Rule entity.

AppBuilder Relation List for Entity View

Command ===> _______________________________________________________________

Repository: DEVRISE V: 1 Project: DEV Level: 3

Entity Name: VIEWTE1

Action Relation Type Name

________ Includes Field FIELD1A

________ Includes Field FIELD1B

________ Owned-By Rule RBATCH1

******************************* BOTTOM OF DATA ********************************


19/273



Figure 1-11 Detail Panel for Browsing Entities

Figure 1-12shows a relationship detail panel from a BR (browse relation) command for an Owns View

relationship.

Figure 1-12 Detail Panel for Browsing Relations

Displaying Multiple-Choice Options

If a panel contains an option for which multiple choices are possible, by default only the selected choice

is displayed. For example, in Figure 1-11 on page 1-9only choice 1IBM Mainframe (CICS)is shown

for the Execution Environment option. You can use the EXPAND action to display all the choicestheoption domainas shown in Figure 1-13.Use the COLLAPSE action to display a single choice. Another

way to display all the choices is to type an obviously invalid choice, such as ?in the field, which resultsin the panel showing the domain for that option.


20/273



Figure 1-13 Detail Panel for Maintaining Entities

More Indicator

Some panels have a More indicator in the upper right corner, indicating additional data (for example,

see Figure 1-13 on page 1-10). The More indicator appears only when a fixed amount of data is

displayed. The More indicator is displayed in one of three ways, as shown in Table 1-2.

Pop-up Panels

A pop-up panel is displayed in front of a list panel or detail panel. You cannot continue with the list

panel or detail panel until you close the pop-up panel.

There are several types of pop-up panels:

Projects

When you type PROJECTSat the command line, a pop-up panel lists the projects to which youhave access. You can select a project as your new project, or exit to retain your current project. See

PROJECTS Changing Your Project and Version.

Actions

When you type ACTIONSat the command line, a pop-up panel lists the actions available for a par-

ticular entity type. You can select an action you want to perform. (See ACTIONS.)

Table 1-2 More Indicator Display Options

Indicator Description

More + More information is present belowthe current panel. To view it, press F8 to scroll down.

More - + More information is present aboveand belowthe current panel. Press F7 to scroll up, or press F8

to scroll down.More - More information is present abovethe current panel. To view it, press F7 to scroll up.


21/273


AppBuilder 2.0.3.1 Enterprise Applicat ion Guide 1-11

Action Information

This panel is displayed whenever AppBuilder needs additional information to carry out an action.

For example, when you type LEto list instances of an entity type, an action information pop-up

panel allows you to tailor the list. (See LE.) When you type ADDEor ADDRto add an entity instance

or entity relationship, an action information pop-up panel lets you specify information that all enti-

ties and relationships must have. See Adding, Saving, and Deleting Objectson page 4-3.

Action Confirmation

When you type DEor DRto delete an entity or relationship, a pop-up panel asks you to confirm the

deletion.

Using the Command Line

Use the command line of an enterprise repository panel to enter an action or command string. Actions

entered on the command line of a list panel are global actions that apply to the enterprise repository as a

whole. Actions entered on the command line of a detail panel can be either global actions or actions

specific to the object being edited. (See UPROFfor more information.)

To execute a TSO command or an AppBuilder action, move the cursor to the command line, type a

command, and press Enter.

Using Function Keys

Function keys (PF keys) are single keys you use to issue commands, such as Refresh, Help, Exit, Cancel,

Keys, and Prompt. You can also issue these commands from the command line.

You can define your function keys to issue any of the following commands:

Table 1-4shows the default function-key assignments. The first 12 keys are standard for ISPF. The

remaining keys are specific to AppBuilder. These keys are active for the duration of the dialog; however,

they may not be applicable to specific dialog panels. If a key is not available for a given panel, a

Command not availablemessage is displayed.

Note Your ISPF profile determines whether the command line is on the bottom or the top of the panel.

Table 1-3 Function Key Options

All methods Sets any method command displayed with the Actions command

Cancel Exits a full panel edit (such as ADDE or ME) without saving and returns to the

previous panel

Save Saves the data on an edit panel to the database


22/273



Use the commands listed in Table 1-5to tailor your function key settings. The PFSHOW command is a

standard ISPF command that controls whether and how function-key assignments are displayed.

Table 1-4 Default Function-key Commands

Key Command Description

F1 Help Displays help for the current panel.

F2 Split Splits panel into two windows.

F3 End Returns you to the previous panel.

F4 Return Returns you to the primary entities panel.

F5 Rfind Repeats the previous Find command.

F6 Rchange Copies (repeats) changes you make to an object.

F7 Backward Scrolls back (up) one full panel.

F8 Forward Scrolls forward (down) one full panel.

F9 Swap Toggles between two panels on a split panel.

F10 Left Scrolls the current panel to the left.

F11 Right Scrolls the current panel to the right.

F12 Retrieve Retrieves the last user command.

F13 Actions Displays the available action list for a given entity or relation.

F14 Entity Displays the entity list.

F15 Collapse Collapses expanded field domains definitions, displaying only the

selected type.

F16 Expand Expands collapsed field definitions to display all domains.

F17 Projects Displays a pop-up panel listing the projects to which an administrator

has given you access.

F18 Save As Saves the current entity as a new entity by using the existing entitys

attributes as a template.

F19 Refresh Lets you undo changes before saving by restoring from the database an

entitys attributes that you overtyped.

F20 All Selects all possible choices from a selection list.

F21 Print Prints a results file to a host printer.

F22 Clear Clears fields that users can edit.

F23 UndoClr Resets all fields to the values that existed prior to executing a Clear

command (F22).

F24 Cursor Places the cursor on the command line.


23/273



Levels

At the top of each panel in the repository interface is an indicator of the levelof the panel. The initial

Entities panel of the repository interface is at level 1. Each time you open a new panel from an active

panel, the level number increases one. Each time you close a panel to return to the previous one, the level

number decreases one.

For example, if you issue the LE(list entities) command for a Rule entity type from the Entities panel

(level 1), the panel showing the list of rule instances is at level 2. If you then issue the ME(maintain

entity) command for one of the rules from the list of rule instances, the panel showing the details of thatrule is at level 3. A high number of nesting levels causes the repository interface s performance to slow.

Command Error Messages

If an error occurs or the system does not understand the command, the system displays a message

directly below the command line. Refer to the Messages Reference Guide for descriptions of individual

messages.

Table 1-5 Commands for Tailored Function-key Settings

Command Description

PFSHOW ON Displays the settings of the function keys. This is a standard ISPF command.

PFSHOW OFF Turns the display of function keys off. This is a standard ISPF command.

PFSHOW TAILOR Displays a customization panel that lets you tailor which set of function keys is displayed,

the number of keys to be displayed, and the number of keys displayed per line. This is a

standard ISPF command.

KEYS Lets you change your function key definitions to any selected set of commands. Default

function keys are set the first time you enter into host dialog, so these customized key

settings remain in effect in subsequent sessions. This is a standard ISPF command.

AUTOSAVE Reports the current sett ing of the Autosave options. This is an AppBuilder command.

AUTOSAVE ON Saves automatically when exiting any edit. Any failed edit checks are displayed, and you

can correct or cancel the changes by typing CANCELon the command line. This is an

AppBuilder command.

AUTOSAVE OFF Does not save changes during edits. If you update the data, you are prompted to save or

cancel the pending changes. You can leave an edit without saving changes by typing

CANCELon the command line any time prior to saving the data. This is an AppBuilder

command.


24/273


Navigating the Enterprise Repository


You can enter repository actions at the command line of any repository panel. Type ACTIONS to display

a list of actions that are valid for the current panel. An action you enter at the command line is

independent of the repository panel from which you enter it.

For example, if you enter LR(list relationships) at a list panels command line, then even if the paneldisplays only one entity, the LR action does not apply to that entity. A pop-up panel prompts you for the

name of the entity whose relationships you want to list.

By contrast, when you type an action next to the name of an entity type or instance on a list panel, the

action applies to that type or instance. This process allows you to navigate the enterprise repository

using the following procedure:

1. List entity types in the repository.

2. Type LE(list entity instances) next to an entity type to display a list of instances of that type.

3. Type an action next to an entity instance, or typeACTIONSto obtain a list of available actions.

Typical actions include:

ME(maintain entity) to view and change the attributes of that entity instance.

ADDR(add relationship) to establish a relationship between that instance and another entity

instance.

LR(list relationships) to list the relationships the entity instance has to other objects. From thelist of relationships, you can enter MR(maintain relationship) to view and change the attributes.

The process of listing objects and performing actions is repeatable. For example, you can list all the fields

that a particular view contains and then for one of those fields you can list all the views that contain it.

So, by alternately listing entities and their relationships you can navigate to all the entities and

relationships in an enterprise repository.

ACTIONS

There are two kinds of actions available to you in the enterprise repository:

Global Actions- Actions that pertain to the entire enterprise repository.

Object-specific Actions- Actions that apply to a specific object.

Global ActionsIf you type ACTIONSfrom the command line of any panel, an Available Actions panel displays (Figure

1-14) listing all available global actions.

Note In previous releases of AppBuilder, a distinction was made between methods and actions. This distinctionis no longer applicablethe two terms are used interchangeably.


25/273



Figure 1-14 Global Actions Panel

Table 1-6lists the available global actions. Global actions can also have entity-specific actions, if an

object is in context.

Object-specific Actions

If you type ACTIONSnext to the name of an object instance or object type on any list panel, an

Available Actions panel displays listing the available actions for the selected object type or object

instance. If the actions available cannot fit on one panel, you can use function keys to scroll forward to

see them. Figure 1-15shows a sample Available Actions panel listing object-specific actions.

Table 1-6 Global Actions

Action Description

ACTIONS Lists available actions.

AUTOSAVE Allows a user to turn autosave on or off. When autosave is on, changes to an object are

saved when the panel on which the changes are made is closed.

DEBUG Displays an updatable profile of debug settings.

ENTITY Displays an Entity List panel listing all the entity types in the repository.

INIDISP Displays AppBuilder INI files in read-only mode.

PROJECTS Displays a list of projects to which the user has access, and allows the user to change

projects.

SRCH Displays the Search-for-Keywords panel.

UPROF Displays the users current profile settings and allows them to be changed.


26/273



Figure 1-15 Object-specific Actions Panel

Select an action by typing the action identifier (for example, ADDEor EW) on the command line of the

pop-up panel and pressing Enter.

Table 1-7shows the object-specific actions available in an enterprise repository for developing

AppBuilder applications.

Table 1-7 Object-specific Actions

Action Description

ACTIONS List available actions for object type or object instance.

ACTIVATE Activate a partition.

ADDE Add an entity to the repository.

ADDR Add a relation.

ASSIGNCU Assign a preparable entity to the active part ition.

BE Browse entity attributes.

BK Browse object keywords

BR Browse relation attributes

BINDPKG Bind DB2 package

BTXE Browse text for an entity

BTXR Browse text for a relation

CO Change owner

DE Delete an entity

DR Delete a relation

DYNAMIC Establish dynamic linkage

EW Extended where-used report

GD Generate DDL for a file

K Define keywords

LE List entity instances

LISTRBD List Rebuild contents

LOCK Lock an entity

LR List relation instances

ME Maintain entity attributes


27/273



PROJECTS Changing Your Project and Version

Whenever you work with an enterprise repository, you must select a project to work inyour currentproject. Because a project exists within a version of the repository, the project you select determines the

version and the objects to which you have access. The selected project is used for auditing when you

create an update objects. Your access to objects depends on your cumulative authorization to the various

projects. Your current project and version are displayed at the top of repository interface panels.

To select a project as your current project, type PROJECTSat the command line of any repository

interface panel. You are presented with a list of all the projects to which an administrator has given you

access (Figure 1-16). The list shows in what version of the repository the project exists (and thus the

version you can access). Enter any character next to the project to select it. For more information on

projects and versions, see Chapter 2, Setting Enterprise Repository Security

MR Maintain relation attributes

PR Prepare an entity

PRB Prepare process execution environment in background. See page 5-14.

PSB Modify PSB (IMS)

RB Rebind DB2 plan for a component

RBD Relink a rule, rebind its DB2 plan, and reinstall into CICS

RDTL Update IMS processing details

REFRESH Refresh a panel with an objects attributes from the repository. See page 1-11.

REP Produce report

RES Display preparation results

RIN Reinstall a component into CICS

SA Save as

SRCH Search for keywords

STATIC Establish static linkage

SUPERPR Superprepare

TE Test a batch entity

TRANS Assign a CICS transact ion code to a rule

TS Transaction switch

TXE Define text for entity

TXR Define text for relation

UEMTH and URMTH Run a user-written method for an entity

UNLOCK Unlock an entity

VER Verify a hierarchy

Table 1-7 Object-specific Actions (Continued)

Action Description
http://-/?-http://-/?-http://-/?-


28/273



Figure 1-16 Projects Selection Panel

Each time you quit working with the enterprise repository, your user profile remembers your current

project the next time you use the repository interface.

ENTITY Listing Entity Types

The first panel of the enterprise repository interface is the Entities panel, which lists all the types of

entities to which your current project gives you access. You can display the Entities panel at any time by

typing ENTITYat any repository panels command line.

From the Entities panel, you can:

List entities of a particular type (see LE).

Add an entity instance of a particular type, or add a relationship to an entity of a particular type (see

Adding, Saving, and Deleting Objectson page 4-3).

List relationships of an entity of a particular type (see LR).

Perform any action or method on an instance of an entity type. If you enter an action or methodnext to the entity type in the Entities panel, you are prompted for the name of the instance to which

the action or method applies, unless prompting is turned off.

LE

Type LE(list entity instances) next to an entity type in the Entities panel to list all the instances of that

type. When you press Enter, an Action Information pop-up panel appears (Figure 1-17) on which you

can tailor the list of entity instances. If you simply press Enterwithout entering information, your list

contains all instances of the entity type. For information on saving the choices you make on the Action

Information panel, and for using those choices subsequently without having to retype them on the pop-

up panel, see UPROFon page 1-20.

Note Your position in the Entities panel is saved in your user profile and restored the next time you log on toAppBuilder.

Note If you receive a DB2 error during the List Entity or List Relations actions, issue the REFRESH command.At the time of the error, ISPF has control of the panel and does not accept any responses from the

program (see ISPF/PDF Primary Option Menu).


29/273



Tailoring the List of Entity Instances

When you list entity instances, you can tailor the list using the Action Information pop-up panel in

Figure 1-17.

Figure 1-17 Action Information Pop-up Panel

After typing your choices, you can:

Type SAVEfrom the command line to save your choices in your user profile for subsequent use.

Press Enterto close the pop-up panel and cause the list to be displayed, tailored as you specified

The Action information pop-up panel contains the following fields:

Use

Specifies whether the list is sorted by entity name or system ID. Whichever field the list is sorted by

is displayed as the first column of the list.

Name/System ID

Determines the first entry displayed in the list of instances. If you specify a character string in this

field, the first entry is the one whose name or system ID (depending on which you choose in the Use

field) is greater-than-or-equal-to the string you specify. Although you can specify any length

stringeven a single characterfor performance reasons you should specify more than one char-

acter to facilitate the search. No matter what entry is displayed first, you can scroll up to see earlierentries in the list.

This option applies only if you set Prompt for Input on in your user profile.

Sort Order

Specifies whether the list is sorted in ascending or descending order.

Like Name/System ID

Limits the entries in the list of instances. Only instances whose name or system ID matches the pat-

tern you specify are listed. You can use the following wild-card characters in your pattern:

For example, entering %T3lists only those instances whose name or system ID begins with zero or

more characters followed by T3. Entering B_C lists those instances whose name or system ID begins

with a B followed by exactly one character, followed by C.

This option applies only if you set Prompt for Input on in your user profile.

% Matches any string of zero or more characters

_ Matches any one character


30/273



Note that AppBuilder adds an implicit % to the end of whatever you type in this field so that all

entities are listed whose name or system ID begins with the characters you type, followed by any

other characters.

Prompt for Input

Suppresses the Action Information pop-up panels. If you choose No, the panel is not displayed sub-

sequently. Lists are tailored according to the criteria last saved in your user profile.To view Action Information pop-up panels again, type UPROFfrom the command line of any

repository interface panel and select Yeson the Prompt for Input field.

For more information, see UPROFon page 1-20.

LR

Use the LR action to list relationship instances for any entity instance in the enterprise repository.

Type LRnext to an entity type in the Entities panel and the repository interface prompts you for the

instance name. Or you can type LR next to the name of an instance in a list of entity instances. TheRelation Options pop-up panel is displayed (Figure 1-18) that identifies all the relation types the entity

instance participates in. You can select one, several, or all types for display.

Type any character next to a relationship to select it. Type ALLon the command line to list all

relationship entities and their relationship type for a given entity. The resulting panel is a relationship list

panel.

Figure 1-18 Relation Options pop-up panel

UPROF

The User Profile panel allows you to save the information you type on an Action Information pop-up

panel. Type SAVE at the command line. The information is saved in your user profile. Once saved, therepository interface pre-fills fields on subsequent Action information panels and in performing actions.

On the Action Information panel that appears (Figure 1-19), specify how you want the list of instances

to appearfor example, sorted by name or system ID, in ascending or descending order.

To view the current values in your user profile, type UPROFat the command line of any panel.


31/273



Figure 1-19 User Profile in Action Information Panel

The user profile panel prompts you to input the following values:

Use

Action

Name/System ID

Sort Order

Like Name/System ID

Version

Prompt for Input

LR - Display Existing Relations

The value of VER(Version) determines which version entities are listed and created in. This field is

protected on the panel unless your current project is associated with version A (for all versions), in

which case you choose a version. If your current project is not associated with version A, this field is

protected because you can list and create objects only in the version with which your current project isassociated. (For more information on versions and projects, see Chapter 2, Setting Enterprise

Repository Security).

LRdisplays existing relations that have been defined for the user profile.


32/273


Viewing Repository Objects

Viewing Repository Objects

A number of methods allow you to view repository objects without risk of modifying them. The

following methods allow you to look at objects in read-only mode:

B

BE

BK

BR

BTXE

BTXR

B

The Browse Source action displays an entitys source code in read-only mode.

BE

The Browse Entity Attributes action displays an entitys attributes in read-only mode.

BK

The Browse Keywords action displays an objects keywords in read-only mode.

BR

The Browse Relationship Attributes action displays a relations attributes in read-only mode.

BTXE

The Browse Text for an Entity action displays an entitys text in read-only mode.

BTXR

The Browse Text for a Relation action displays a relations text in read-only mode.


33/273

2-1

CHAPTER

2

SETTING ENTERPRISE REPOSITORY

SECURITY


Enterprise repository security prevents unauthorized modification of objects in the repository.

Repository security includes:

Using Object Security

What objects in the repository you can act on

Using Method Security

What actions you can perform on those objects

Contact your System Administrator if you need access to objects or methods that you cant access now.The next chapter, Chapter 3, Locking Objectsdiscusses a form of object security that is under your

control without administrator assistance.

For detailed information and instructions on setting security parameters for your enterprise, see the

Enterprise Administration Guide.


Object security controls what you can do in a repository by controlling:

Access type

The type of access (create, read, update, delete) you have to objects in the repository

Entity type

The type of objects you can access


34/273

2-2 Setting Enterprise Repository Security


Modifying Objects

There are four kinds of actions available to modify objects in a repository:

Create

Read

Update

Delete

Table 2-1classifies all repository actions and methods by the type of access to objects required for each..

Selecting a Current Project

A project defines a subset of objects belonging to a version. Projects provide the ability to group the

objects in a version according to function, security level, or whatever category you want. Typically a

version contains more than one project.

When you use an enterprise repository, you must select a project as your currentproject (see

ACTIONSon page 1-14). The project you select determines your current versionthe version you are

working in. When you list objects in a repository (using the LE or LR actions), you can see all the objects

in the current version and have read access to all the objects in the projects in the current version that

you have access to.

Although most projects give you access to just one version, there is a special version that gives you access

to objects in all versions of a repository. This version is called version A for allversions. If you select aproject in version A, you have access (based on your authorization level) to all objects in all versions.

See the Enterprise Administration Guide for detailed information about security and versioning in

repositories.

Table 2-1 Access Types

Access type Action

Create

ADDE (add entity)

ADDR (add relationship)

SA (save as)

Read All actions other than those listed under Create, Update, and Delete require Read access

Update

CO (change ownership)

K (define keywords) ME (maintain entity)

MR (maintain relationship)

P(Prepare method)

S (source)

TXE (define text for entity)

TXR (define text for relationship)

Delete DE (delete entity)

DR (delete relationship)

Note Read access depends upon both the repository version and the project.


35/273



Project Types

In addition to governing what you can see in a repository by granting you access to particular versions,

projects determine what you can see in another way. Each project provides a view of a repository. That is,

each project allows you to see only a subset of all the entity types in a repository. All the projects

mentioned so far provide a development view of a repository. They allow you to see the AppBuilder

entities of interest to a developer, such as rules, views, and fields.

There are other types of projects that give a different view of a repository. For instance, an ADM project

lets users of that project see only the entities of interest to an administrator, such as users, other projects,

and groups. Like other projects, ADM projects provide a view of a particular version, or of all versions,

of a repository. Only the person who installed the AppBuilder Environment, or another administrator,

can give you access to an ADM project.

Table 2-2shows all the types of projects and the view of the repository that they provide.

Creating Objects

Except for auditors (who have only read access to repository objects), projects give you the ability to

create objects as well as to read and update them. You can create an object only in your current project

but you can change the project to which an object belongs using the CO (change owner) action. You can

create an object in any version of the repository to which you have access.

If your current project is associated with version A when you create an object, you are prompted to

specify the version it is to be created in. If prompting is off, the version is determined from your user

profile.

Updating Objects

The objects you can update in a version of a repository depend on the following factors:

Owner

Creating an object makes you the objects owner. Ownership can be changed using the CO (changeowner) action.

Project

Your ability to update an object depends in part on what your current projectis, the projects an

administrator has given you access to, and the project the object you want to update belongs to.

Authorization level

When an administrator gives you access to a project, the administrator assigns you an authorization

level in that project. An authorization levelis a set of privileges relative to objects in a project. All

projects have four authorization levels: programmer, analyst, project leader, auditor.

Table 2-2 Project Type Views

Project type View type

DEV Development Information Model

ADM Administration Information Model

SEC Security Information Model

SDS Software Distribution Model


36/273

2-4 Setting Enterprise Repository Security


Table 2-3shows how owner, project, and authorization level determine whether you are permitted to

update an object in a version of the repository to which you have access.

Deleting Objects

Table 2-4shows how owner, project, and authorization level determine whether you are permitted to

delete an object in a version of the repository to which you have access.

Summary of Access Types

Table 2-5summarizes what kind of access you can have to objects in the repository.

Table 2-3 Update Permission Options

Authorization

level in project

Object you own in a

project you can access

Someone elses object in

a project you can access

Object in a project you

app builder enterprise application

Documents