synon training

5/12/2018 Synon Training - slidepdf.com

http://slidepdf.com/reader/full/synon-training 1/190

1

Advantage 2E



2

COOL:2E Training

Contents

Intr oduction to COOL:2E

Getting Started Data Modeling

Building Access Paths

Building Applications Generating Applications

COOL:2E/1E Utilities



3


What is COOL:2E?» An application development tool

» Allows efficient design, development, implementation

& maintenance of application software

» Better than third generation development methods

» Knowledge of programming language not required

» Platform independent application design



4


COOL:2E Objectives» Design closer to user requirements

» Higher quality applications

» Ease of maintenance and enhancement» Language independent design

» Applications that make effective use of platform

» Increased Productivity



5

Implementation independence

» Application design developed as high level business

logic and design» Applications stored as COOL:2E design model

» Same application design can generate application to

run on AS/400, IBM mainframes, RS/6000


COOL:2E Design Principles



6

Data-driven Design

» Application design starts with the identification of

business entities and their relationship» Entity-Relationship modeling is used to create the

COOL:2E data model

» Functions for the end user are subsequently built on

the data model


COOL:2E Design Principles (contd..)



7

Object-based Design

» Objects are database entities

» Actions are COOL:2E functions» Actions and Objects are defined once and reused.


COOL:2E Design Principles (contd..)



8

COOL:2E Rapid Pr ototyping Methodology

(RPM) is a data-driven, pragmatic appr oach to

Application Development

Rapid Pr ototyping Methodology

» Analyze

± System analysis, E-R diagram, COOL:2E Data model,Primary access paths, function flows and device designs


Application Developm

ent



9

Rapid Pr ototyping Methodology (contd...)

» Design

± Prototype application, review with user, update design,continue functions definition, action diagrams, complete

database design

» Construct

± Generate final version of application and complete unit

testing

» Implement

± Complete integration test, system test and user acceptance

test


Application Developm

ent



10

» Change design model as necessary

» Update the function design for above changes» Regenerate dependant elements


Application Maintenance



11

» COOL:2E

Application development tool for AS/400

Includes COOL:2E/1E» COOL:2E/2G

Provides PC based GUI for COOL:2E

» COOL:2E/CSG (Client Server Generator)

Option to COOL:2E which allows distributed functionality onmultiple platforms


COOL:2E Pr oducts



12

» Entity Relationship Specification

± Automatic creation of a data dictionary

± Free format text to describe any design object ± Automatic documentation of the design model

± Specification of domain checks

» Access Paths

± Logical views to support functions ± Retrieval of existing DB2/400 descriptions (assimilation)


COOL:2E Features



13

» Functions

± Auto creation of action diagram & panel/report design

± Modular design

» Panels & Reports

± Automatic design of panel & report layouts

± Interactive painting facilities

± Panel design prototyping facilities


COOL:2E Features (contd«)



14

» HLL code generation

± DDS or SQL for database

± DDS for panels & reports

± RPG/COBOL for AS/400 stand alone programs

± RPG/COBOL for server and COBOL/2 for client

± Automatic help text generation





15

» Other features ± Automatic implementation of object naming standards

± Automatic implementation of panel design standards

± Automated documentation of generated systems

± Cross reference facilities

± Integration of user source code in generated functions

± Regeneration of source code after changes in design

± Facilities for commitment control, journalling & error handling

± Automatic referential integrity & domain checks





16

Contain the files and objects needed to use

COOL:2E pr oducts

» Y1SY COOL:2E/1E Products» Y1SYVENG COOL:2E/1E National Language Library

» Y2SY COOL:2E Base products

» Y2SYVENG COOL:2E National Language Library

» Y2SYMDL COOL:2E null model» Y2SYCBL COOL:2E COBOL generators

» Y2SYRPG COOL:2E RPG generators

» Y2SYSRC COOL:2E source

Getting Started

COOL:2E Pr oduct Libraries



17

It is the model in which the development team

creates an application and in which initial

generation takes place.

Objects are tested in the development

envir onment.

Getting Started

Developm

ent Envir onm

ent



18

Model Library» Library in which the model resides

Generation Library

» Associated with each model library» Contains source files, compiled programs, help text,

access paths (created using DDS) and journals

SQL Collection

» Exists only if SQL is used for data definition» Contains files, journals, data dictionaries & SQL

access paths

Getting Started

Developm

ent Libraries



19

YCRTMDLLIB command creates a model YCRTMDLLIB Command Parameters

» Model Library Name (MDLLIB)

» Generation Library Name (GENLIB)» Design Standard (DSNSTD) like *CUATEXT etc.

» File generation method : DDS/SQL

» SQL Collection Library (SQLLIB)

» Naming Prefixes ± Object Prefix (OBJPFX)

± Message Prefix (MSGPFX)

Getting Started

Creating/Using a Model



20

YCRTMDLLIB Command Parameters (contd«)

» Message File Name (MSGVNM)

» Default HLL (HLLGEN)

» HLL Naming Convention (HLLVNM)Build Library List using YBLDLIBLST

» Change job¶s library list to contain COOL:2E

Development Libraries and Product Libraries

» Run command YBLDLIBLST <LIBL-Name>

Getting Started

Creating/Using a Model (contd«)



21

Run command YSTR Y2 <LIBL-Name> to display

COOL:2E Master Menu

User can Enter/update the COOL:2E/2 model as

Designer(*DSNR) or as a Pr ogrammer

(*PGMR)

Getting Started




22

MAIN COOL:2E Master menuLevel . : 1

System: S1017323Select one of the following:

DESIGN-MODEL 1. Enter/update COOL:2E model as *DSNR.2. Enter/update COOL:2E model as *PGMR.

? 3. Change current data model.

Other menus 4. COOL:2E commands in alphabetical order.

5. Commands to set up or alter a model.6. Commands to copy a model.7. Commands to create an application.8. Commands to document a model.

9. COOL:2E/1 Programmer aids. +

Selection or command ===>

F3=Exit F6=Messages F9=Prev. request F10=Cmd Entry F14=Submitted jobs

Getting Started




23

A Data Model is a structured description of a

set of data and its relationships which can be

used to represent the business of anorganization

Entity-Relation (E-R) modeling techniques are

used to build a conceptual data model

Conceptual data model is then entered in the

COOL:2E/2 to build COOL:2E/2 data model

Data Modeling

What is a Data Model?



24

Data Modeling

Entity-Relationship (E-R) Modeling Identify Primary Entities and their attributes

Identify Relations between Entities and

between Entities and the Attributes

Nor malize the Data Model



25

Data Modeling

Entity-Relationship (E-R) ModelingIdentifying Primary Entities

» Review the data items from the analysis of business

information

» Select objects that are important to the business e.g.entities important to end users

» Select objects about which information must be stored

» Identify the business dimensions

» Generalize or differentiate Entities



26

Data Modeling

Entity-Relationship (E-R) ModelingIdentifying Primary Entities - example

» Sales Order Entry form of ABC Inc. is shown belowABC Inc. Customer Copy

Customer Code:

Name: Phone:Address: Order No.:

Date:

Pr oduct Code Description Qty Price Total

________ ____________ ____ ____ ___

________ ____________ ____ ____ ___

» The following primary entities can be identifieda) Company b) Customer c) Order d) Pr oduct



27

Data Modeling

Entity-Relationship (E-R) ModelingIdentifying Primary Entities - example

» Further study of business of ABC Inc. revealed that products

are purchased from vendors for which purchase orders are

generated. Therefore the following additional entities wereidentifieda) Vendor b) Purchase Order

Generalize Entities» Combine two entities representing different types of the same

thing into one entityDifferentiate Entities

» Differentiate different types of the same thing as two different

entities



28

Data Modeling

Entity-Relationship (E-R) ModelingIdentifying Entity Attributes

» Identify informational details of an entity

» Each informational detail of an entity can form the

attribute of the entity» Example - Customer has the following attributes

Customer Code

Customer Name

Customer Address

» Identify Domains which are the possible values of the

identified attributes



29

Data ModelingEntity-Relationship (E-R) Modeling

Identifying Relations» Identify relations between Entity and its attributes and

between different Entities

» Categorize relationship types by ± Optional/Mandatory

± Cardinality

± Involution

» Select Primary Key or Unique Identifier for an Entity



30


Identifying Relations» Optional/Mandatory - Is the relationship Mandatory

or Optional?

» Cardinality - Is the connection one-to-one, one-to-many or many-to-many?

Number of entity instances for a relationship

» Involution - Does the connection exist between two

different entities or from the same entity to itself?e.g. relation between employee and a manager when

manager himself is an employee.



31


Identifying Relations» One-To-One Relation - each instance of one entity is

related to one instance of another entity

assigned toe.g. Salesperson Territory

has

» One-To-Many Relation - One instance of an entity is

related to multiple instances of another entityplaces

e.g. Customer Order

placed by



32


Identifying Relations» Many-To-Many Relation - each instance of one entity

is related to more than one instance of another entity

and vice versaorders

e.g. Order Product

ordered by



33


Identifying Relations» Select Primary Key or Unique Identifier

Primary Key - An attribute or group of attributes assigned to

an entity to uniquely identify an instance of the entity e.g.Customer

K Customer Code

Customer Name

Customer Address

Primary Key can be a single attribute, a relationship or a

combination of attributes and relationships



34


Identifying Relations» Implement Entity to Entity Relationship using

Foreign Key

Foreign Key - An attribute or group of attributes of an entitywhich connects this instance with an instance of another

entity

The primary key of one entity when used in another entity is

called a Foreign key



35


Identifying Relations - Foreign Keyexample: One-To-One relation

assigned to

Salesperson Territory

hasK Person ID K Person ID

Person Name Territory Name

example: One-To-Many relationhas

Company DivisionPart of

K Company Code K Company Code

Company Name Division Code

Division Name



36


Identifying Relations - Foreign Keyexample: Many-To-Many relation

worked on by

Project Employee

works on

worked on by has

Project Project Team Employeeworks on part of

Pr oject Employee

K Project Code K Employee CodeProject Name Employee Name

Pr oject Team

K Project Code

K Employee Code



37

Data ModelingNor malizing the Data Model

Nor malization Involves» regrouping attributes

» splitting entities

» reassigning primary keysFunctionally Dependent Attribute

» for each value of the key, there is only one value of

non-key attribute

Full Functional Dependent Attribute» non-key attributes are dependent on all the key

attributes of a composite key



38

Data ModelingNor malizing the Data Model

Pr ocess of Nor malization» Creating First Nor mal For m (1NF)

± eliminate repeating data groups

± e.g. Order splits into Order Header & Order Detail» Creating Second Nor mal For m (2NF)

± entity is 1NF

± every non-key attribute is fully functionally dependent on

primary key

» Creating Third Nor mal For m (3NF) ± entity is 2NF

± each non-key attribute is not dependent on another non-key

attribute



39

Data ModelingCOOL:2E Data Model

COOL:2E Objects (design elements)» File

± represents an entity e.g. Order

» Field ± describes an item of data e.g. Order Number

» Condition ± describes the values or set of values (domains)

» Relation ± describes connection between two files or between file and

field e.g. refers to, owned by



40


Conceptual Model COOL:2E Data

(E-R Model) Model

---------------------------------------------------------------Entity File Attribute Field

Relationship Relation

Domain Field Conditions:

Reference field types



41


COOL:2E pr ovides facilities to enter / update

the data model

Model can be accessed as designer (*DSNR)

or as pr ogrammer (*PGMR) Edit Database Relations panel allows the

entry of data model to COOL:2E



42

*DSNR GXMMDL Op: SYNGXM QPADEV0004 21/08/97 17:46:35EDIT DATABASE RELATIONS GXMMDL=> ___ _________________________ Rel lvl: ___ ___ ___ _______________________ ? Typ Object Relation Seq Typ Referenced object

__ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________

__ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________

__ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________ __ _________________________ ____________ ___ _______________________

+SEL: Z(n)-Details, N(n)-Narr, S(n)-Select, E(n)-Entries, V-Virt.fields, F-FuncsF3=Exit F5=Reload F7=Fields F9=Insert F10=Define obj. F17=Services




43


COOL:2E Files» Each COOL:2E File has a Name and a File Type

» COOL:2E File Naming rules

± must be valid COOL:2E Name ± unique within the model

± up to 25 characters including embedded blanks

± e.g. Purchase Order is a valid COOL:2E file Name

» COOL:2E File Types

File Attribute Description ExampleDatabase CPT Capture file Order Entry

REF Reference file Company file

Nondatabase STR Structure file Audit date & time

stamp



44


COOL:2E Files» Reference (REF) files

± master files that typically contain non-volatile information

± e.g. Custom

er, Pr oduct, Area Code» Capture (CPT) files

± contain transactional data that is recorded regularly

± e.g. Order, Ledger Entry

» Structure (STR) files

± contain group of fields which can be included in other filesusing Includes relation

± e.g. Audit Stamp file



45


COOL:2E Files» Default functions

± standard functions are automatically defined for files

± default functions depend on file types» Default functions for REF files

Function Access Path

CRTOBJ - Create Object UPD

DLTOBJ - Delete Object UPDCHGOBJ - Change Object UPD

SELRCD - Select Record RTV

EDTFIL - Edit File RTV



46


COOL:2E Files» Default functions for CPT files

Function Access PathCRTOBJ - Create Object UPD

DLTOBJ - Delete Object UPD

CHGOBJ - Change Object UPD



47


COOL:2E Files» Creating/Defining

± At the Edit Database Relations panel, press F10 to show

Define Objects panel ± In the Object type column, enter FIL

± Type File Name in Object Name column

± Type CPT or REF or STR in Object attr column depending

on the file type

± Defined as relation for the file is automatically created



48


Op: SYNGXM QPADEV0004 22/08/97 15:31:12DEFINE OBJECTS GXMMDL

Object Object Object Referenced Field Edittype name attr field usage field ___ ________________________ ___ ________________________ ___ _ ___ ________________________ ___ ________________________ ___ _

___ ________________________ ___ ________________________ ___ _ ___ ________________________ ___ ________________________ ___ _ ___ ________________________ ___ ________________________ ___ _ ___ ________________________ ___ ________________________ ___ _ ___ ________________________ ___ ________________________ ___ _ ___ ________________________ ___ ________________________ ___ _

+

F3=Exit



49


COOL:2E Fields» Each COOL:2E Field has a Name and a Field Type

» COOL:2E Field Naming rules

± unique within the model ± up to 25 characters including embedded blanks

± e.g. Customer Code is a valid COOL:2E Field Name

± implementation name is different

» COOL:2E Field Types

± depends on the type of values ± broadly classified as alphanumeric, numeric & special field

types



50


COOL:2E Fields» COOL:2E Field Types (contd«)

Field Type Name Description Type Length Example

CDE Code A 6 Stock Code

DTE Date P 7,0 Date of birthIGC Idegraphic text A 20 Kanji name

NAR Narrative text A 30 Comments

NBR Number P 5.0 # of employees

PCT Percentage P 5.2 Profit margin

PRC Price or tariff P 7.2 Unit Price

QTY Quantity P 5.0 Stock quantity

REF Reference - - Field based on another

SGT Surrogate P 7.0 System KeySTS Status A 1 Yes/No

TME Time P 6.0 Change Time

TXT Descriptive name A 25 Product name

VAL Monetary value P 11.2 Stock value

VNM Valid system name A 10 File name



51


COOL:2E Fields» Field Attribute Values

± Basic attributes: length, implementation name

± Text: Left Hand Side (LHS) text, Right Hand Side (RHS)Text, Column Headings

± Validation attributes: upper/lower case checking, Modulus

checking, valid name checking, validation through a check

condition



52


COOL:2E Fields» Field Usage

± Two types: Database fields and Function fields

» Database fields ± Code (CDE) fields:- used for key fields e.g. Company Code

± Data attribute (ATR) fields: used for non-key fields e.g.

Company Name

» Function fields

± fields used only in functions but do not reside in database



53


COOL:2E Fields» Function fields (contd«)

± fields used only in functions but do not reside in database

± fields can be added to data dictionary and accessed indevice designs and action diagrams

± 6 function field usage types

CNT (count) DRV (derived)

MAX (maximum) MIN (minimum)

SUM (sum) USR (user-defined)



54


COOL:2E Fields» Default Condition

± supplies the default value for a field

± *NONE: no default condition ± condition name: COOL:2E condition supplies default value

± *DTAARA: Default field value is retrieved from data area

specified for the Dataarea field

» Defining Field as a Data Area

± specify *DTAARA as default condition



55


COOL:2E Fields» Creating/Defining

± In the Object type column of Define Objects panel, enter

FLD ± Type Field Name in Object Name column

± Type COOL:2E field type in the Object attr column

± Type Referenced field if the field refers to another field for

domain

± In the Field Usage column, type CDE (Code) or ATR(attribute) or a function field usage



56

Op: SYNGXM QPADEV0004 22/08/97 15:31:12DEFINE OBJECTS GXMMDL

Object Object Object Referenced Field Edittype name attr field usage field FIL DealerFIL Dealer groupFLD Dealer Code CDEFLD Dealer name ATR FLD Dealer Address 1 ATR FLD Dealer Address 2 ATR FLD Dealer Group Code CDEFLD Dealer Group Name ATR FLD Dealer Group Credit Limit ATR

+

F3=Exit




57


COOL:2E Condition» Specifies the values or set of values a field may take

» Condition has a Name, a type and an associated

value» Condition Types

± VAL (Value) and LST (Value List) are valid condition types

for status fields

± CMP (Compare) and RNG (Range) are valid condition types

for non-status fields



58


COOL:2E Condition» Value (VAL) Condition

± used to specify single values that status field can take

± two related values:internal value - value in the implemented database

external value - value displayed/entered on the screen

± e.g. Premium paid condition has file value ³Y´

» List (LST) Condition

± used to specify list of values that status field can take ± screen functions implement prompt key (F4)

± e.g. Invoice Flag can have valid values U, D, P, H, C and the

condition Invoice not due has file value ³U´



59


COOL:2E Condition» Compare (CMP) Condition

± defined in terms of a fixed value and an operator

± valid operators: *EQ, *NE, *GT, *LT, *GE, *LE ± e.g. Order Quantity field can have an associated condition

by name greater than 10 with operator *GT and value 10

» Range (RNG) Condition ± defines range of values that field can take

± defined in terms of From and To values ± e.g. Stock Quantity field can have an associated condition

by name between 10 and 100 with From value as 10 and

To value as 100



60


COOL:2E Relation» Expresses association between two files or between a

file and a field

» Eight relation typesDefined as, Extended by, Has, Includes, Known by, Owned

by, Qualified by and Refers to

» 3 different relation usage groupsDefinition relations - declare files to exist

Key relations - define the keys in files Attribute relations - declare non-key fields in files

» Database relations can be entered using Edit

Database Relations panel



61


COOL:2E Relation

Usage Type Relation Used f or

Definition Defined as File-to-file relationship

Key Owned by File-to-file relationship

Known by File-to-field relationship

Qualified by File-to-field relationship

Attribute Refers to File-to-file relationship

Includes File-to-field relationship

Has File-to-field relationship

Other Extended by File-to-file relationship



62


COOL:2E Relation» Defined as Relation

± File-to-file relation

± declares that a file exists ± e.g.

Product Defined as Product

± Defined as relation is automatically created for a file if a

reference is made to a non-existing file



63


COOL:2E Relation» Owned by Relation


± denotes a parent-child relationship ± primary key(s) of owning file become part of primary key of

the owned by file

± keys of owning file are incorporated as high order keys in

the owned file

± e.g.Order Detail Owned by Order



64


COOL:2E Relation» Known by Relation

± File-to-field relation

± specifies the key field(s) for a file ± e.g.

FIL Order Known by FLD Order Number

FIL Order Has FLD Quantity

» Qualified by Relation

± File-to-field relation ± to qualify a file identifier by one or more variable factors like

date, time, sequence number etc



65


COOL:2E Relation» Qualified by Relation

± used for entities which represent continuum of values like

currency rates having effective date ± appropriate fields of referring file can be redirected (RDR) to

the effective field in referred file with a possibility of

specifying *PREVIOUS or *NEXT

± field in the relation must be ATR and not CDE

± e.g.Product Price Owned by Product Code

Product Price Qualified by Effective date

Product Price Has Product price



66


COOL:2E Relation» Refers to Relation


± specifies that a file refers to another file

± Allows access to any of the fields on the referred to file from

a referring file

± Primary key of the referred file becomes foreign key in the

referring file

± Virtual field is created in the referring file and cannot beupdated from the referring file

± e.g.

Order Detail Refers to Product



67


COOL:2E Relation» Includes Relation


± file includes all the fields of a structure (STR) file

± e.g.

Product Includes Audit Stamp

» Has Relation ± File-to-field relation

± declares a field to be present in a file as an attribute

± e.g.

FIL Order Has FLD Quantity



68


COOL:2E Relation» Extended by Relation


± declares a file to be extension of another file

± If used with Owned by relation, the fields of the extended file

are available as V irtual Fields in the file being extended

± It is recommended to use Extended by relation along with

Owned by relation

± e.g.Customer Extended by Customer Detail



69


COOL:2E Relation» For Text

± For Text clause can be added to a relation to further clarify

the description of a relationship

± If a file refers to another file more than once, For Text clause

can be used for further clarification

± e.g.

Order Refers to Customer

For: Ordering Sharing: *ALLOrder Refers to Customer

For: Invoicing Sharing: *ALL



70


COOL:2E Relation» Creating/Defining

± At the Object column of Edit Database Relations panel,

enter the file name

± Type the relationship in Relation column

± Type the referenced object (File or Field) in the Referenced

Object column

» Edit File Entries

± Type E in front of any relation to display Edit File Entriespanel



71

*DSNR GXMMDL Op: SYNGXM QPADEV0004 22/08/97 15:25:26EDIT DATABASE RELATIONS GXMMDL=> Rel lvl:? Typ Object Relation Seq Typ Referenced object

FIL Dealer Owned by FIL Dealer groupFIL Dealer Known by FLD Dealer CodeFIL Dealer Has FLD Dealer name

FIL Dealer Has FLD Dealer Address 1FIL Dealer Has FLD Dealer Address 2

FIL Dealer Group Known by FLD Dealer Group CodeFIL Dealer Group Has FLD Dealer Group NameFIL Dealer Group Has FLD Dealer Group Credit Limit

+SEL: Z(n)-Details, N(n)-Narr, S(n)-Select, E(n)-Entries, V-Virt.fields, F-FuncsF3=Exit F5=Reload F7=Fields F9=Insert F10=Define obj. F17=Services'Dealer' type FIL not found.




72

Op: SYNGXM QPADEV0004 22/08/97 16:11:55EDIT FILE ENTRIES GXMMDL

File . . . . . . : Dealer

? Field Type Ocr Et Ksq GEN name Length Renamed

Dealer Group Code CDE K 1 AICD 6Dealer Code CDE K 2 AHCD 6Dealer name TXT A AJTX 25Dealer Address 1 TXT A AKTX 25Dealer Address 2 TXT A ALTX 25

SEL: Z-Details, R-Replace field, U-Usage, M-Mapped field parameters.F3=Exit




73


COOL:2E Relation» Edit Field Details

± Type E2 in front of the File-field relation to display Edit Field

Details panel for the field OR

± Type Z in front of the field entry in the Edit File Details panel



74

Op: SYNGXM QPADEV0004 22/08/97 16:11:55EDIT FIELD DETAILS GXMMDL

Field name . . . . . : Booking payment status Document¶n seq . :Type . . . . . . . . : STS REF: Payment Status Field usage . : ATR Internal length. . . : 1 Data type : A lowercase: GEN name . : BKST

K¶bd shift :

Headings . . . . . . : -Text . . . . . . . . : Booking payment statusLeft hand side . . . : Booking payment statusRight hand side. . . : ValueColumn headings. . . : Booking

: payment: status

Validation . . . . . : -Default condition. . : *NONE

Check condition. . . : *NONE Mandatory fill . . . : (Y, ) Valid System name. . : (Y,¶ µ) Translate cnd vlues : Blank (Y,¶ µ)

F3=Exit no update F8=Change name/type F9=Conditions F20=Narrative




75


COOL:2E Relation» Edit Field Condition

± Field condition can be added/modified using the Edit Field

Condition and Edit Field Condition Detail panels

± Press F9 on the Edit Field Details panel to display Edit Field

Condition panel

± In the Edit Field Condition panel, type condition name and

condition type (VAL, LST, CMP, or RNG) and press Enter to

display Edit Field Condition Details panel

± In the Edit Field Condition Details panel, type the

appropriate condition details like value, range etc.



76

Op: SYNGXM QPADEV0004 22/08/97 16:11:55EDIT FIELD CONDITION DETAILS GXMMDL

Field name . . . . . : Credit status Attr: STS Mode: *ADDLength of file . . . : 1

on display. . : 4

Condition. . . . . . : Blue chipType . . . . . . . . : VAL

File value Display valueStatus value A A1

F3=Exit F8=Change name F20=Narrative




77

Building Access PathsIntr oduction

» COOL:2E creates default access paths (PHY, RTV &

UPD) when a file is defined

» Additional access paths may be created

» COOL:2E access paths are implemented as one or more objects

» Access path defines a physical file or the logical view

of that file

» Access path can be used to define order, column

selection & record selection



78

Six types of Access Paths

» Physical (PHY)

» Update (UPD)» Retrieval (RTV)

» Resequence (RSQ)

» Query (QR Y)

» Span (SPN)

Building Access PathsIntr oduction



79

Building Access PathsPhysical (PHY) Access Path

Single f or mat file containing fields derived

fr om resolution of all relations on the file.

» Not keyed

» No virtual fields

» Created automatically for every REF/CPT file

» Not referenced directly by functions

» No additional PHY access paths allowed for a file» Created if a PF is retrieved through assimilation



80

Building Access PathsUpdate (UPD) Access Path

Uniquely keyed, single f or mat access path

which is used by functions f or updation

» Keyed on the fields that identify the file

» No Virtual fields


» Additional UPD access paths may be created with the

same key but subset of fields



81


Retrieval (RTV) Access Path Uniquely keyed, single f or mat access path

used by functions to retrieve records

» Keyed exactly as the UPD access path

» Allows virtual fields


» Associated with the UPD access path

» Non-key fields can be dropped

» Can select/omit records

» Possible to define multiple RTV access paths for a

given file, but all should have same key fields



82


Resequence (RSQ) Access Path Uniquely or non-uniquely keyed single f or mat

access path used by functions to retrieve

records

» Must be created explicitly

» Defaults to the keys of the based on file

» Allows default keys to be changed which need not be

unique

» Allows virtual fields

» Associated with RTV, which points to a UPD

» Many RSQ access paths possible for single file



83

Building Access PathsQuery (QR Y) Access Path

Keyed single f or mat access path used by

functions to retrieve records


» Allows virtual fields on key & non-key fields» Available only for Print Object/Print File functions

» Defaults to the keys of the based on file

» Allows default keys to be changed

» Associated with RTV, which points to a UPD

» Many QRY access paths possible for single file

» Implemented by OPNQRYF or Dynamic SQL



84


Span (SPN) Access Path Keyed multi-f or mat access path

Used by Edit & Display transaction functions

to retrieve records fr om a pair of related files


» Defaults to keys of based on files

» These keys can be changed

» Allows virtual fields» Associated with RTV, which points to a UPD

» Many SPN access paths possible for single file



85

Building Access PathsAccess Path Summary

# AccessPath Type

RealFields

Key Fields VirtualFields

Virtual Keys

1. PHY x x x

2. UPD Relation x x

3. RTV Relation x

4. RSQ User x

5. QRY User

6. SPN User x



86

Building Access PathsAdding an Access Path

*DSNR SYNGXMMDL Op: SYNGXM QPADEV0007 11/02/98 12:02:11

EDIT DATABASE RELATIONS SYNGXMMDL

=> Rel lvl:

? Typ Object Relation Seq Typ Referenced object

FIL Customer Known by FLD Customer Code

FIL Customer Has FLD Customer Name

FIL Customer Has FLD Customer Address 1FIL Customer Has FLD Customer Address 2

FIL Customer Has FLD Customer Address 3

FIL Customer Has FLD Customer Credit Limit

FIL Customer Has FLD Customer Limit Used

FIL Inventory Known by FLD Item Code

FIL Inventory Has FLD Item Name

FIL Inventory Has FLD Item Quantity

FIL Sales Order Header Known by FLD Sales Order Number

FIL Sales Order Header Refers to FIL Customer

FIL Sales Order Header Has FLD Sales Order DateFIL Sales Order Header Has FLD Shipment Date

FIL Sales Order Lines Owned by FIL Sales Order Header

+

SEL: Z(n)-Details, N(n)-Narr, S(n)-Select, E(n)-Entries, V-Virt.fields, F-Funcs

F3=Exit F5=Reload F7=Fields F9=Insert F10=Define obj. F17=Services



87


» Type Z against any relation on the Edit Database

Relations panel for the file and press Enter

» On the resulting Edit File Details panel, enter Access

Path name and type and press Enter

» Type Z to zoom into the new access path and specify

details on the Edit Access Path Details panel

» Type Z on the Edit Access Path Details panel to go to

Edit Access Path Format Entries panel



88

Op: SYNGXM QPADEV0007 11/02/98 12:10:57

EDIT FILE DETAILS SYNGXMMDL

File name . . . . . . . . : Customer

Attribute . . . . . . . . : REF Field reference file. : *NONE

Documentation sequence. . : Source library. . . . : SYNGXMGEN

GEN format prefix . . . . : AB Distributed . . . . . : N (Y,N)

Assimilated physical. . . :Record not found message. : Customer NF Msgid. : USR0001

Record exists message . . : Customer EX Msgid. : USR0002

? Typ Access path Source mbr Key Maint Held

PHY Physical file UUABREP NONE

UPD Update index UUABREL1 UNIQUE IMMED

RTV Retrieval index UUABREL0 UNIQUE IMMED

RSQ Customer by Name

SEL: Z-Details, G/J-Generate, E-STRSEU, D-Delete, N-Narrative,

H-Hold/Release, O-Overrides, U-Usage, F-Function refs., L-Locks.

F3=Exit F5=Reload F7=Functions F8=Change name F17=Services F20=Narrative




89

Op: SYNGXM QPADEV0007 11/02/98 12:17:29

EDIT ACCESS PATH DETAILS SYNGXMMDL

File name . . . . . . . . : Customer Attribute . : REF

Access path name. . . . . : Customer by Name Type. . . . : RSQ

Unique key. . . . . . . . : (Y, blank)

or Duplicate sequence . . : F (F-FIFO, L-LIFO,

Maintenance . . . . . . . : I (I-IMMED, D-DLY, R-REBLD) Alternate collating table :

Allow select/omit . . . . : (S-Static, D-Dynamic, ' '-None)

Generation mode . . . : M (M-MDLVAL, D-DDS, E-EXP, S-SQL, X-UNX)

Source member name . . : UUABREL2

Source member text . . : Customer Customer by Name

Format Format text Associated

? Seq name (Based on file) Retrieval access path

1 FABREAO Customer Retrieval index

SEL: Z-Acp.entries, R-Acp.relations, S-Select/omit sets, A-Associated Acps.

F3=Exit F8=Rename F20=Narrative




90

Op: SYNGXM QPADEV0007 11/02/98 12:19:24

EDIT ACCESS PATH FORMAT ENTRIES SYNGXMMDL

File name . . . . . . . . : Customer Attribute . : REF

Access path name. . . . . : Customer by Name Type. . . . : RSQ

Format text . . . . . . . : Customer

Based on. . . . . . . . . : Customer Format No . : 1

GEN Key Altcol Ref

? Field Name Type no. Dsc seq cnt

Customer Code CDE ABCD K 1 1

Customer Name TXT ABTX A 1

Customer Address 1 TXT ACTX A 1

Customer Address 2 TXT ADTX A 1

Customer Address 3 TXT AETX A 1

Customer Credit Limit VAL AAVA A 1

Customer Limit Used VAL ABVA A 1

SEL: Z-Field details.

F3=Exit F7=Relations




91

Span (SPN) Access Path

» A SPN access path can only be specified over files

with Owned by or Refers to relationships

» A SPN access path must be created over an owning

or referred to file

» Press F9 on Edit Access Path Details panel to first

select the primary format and then the secondary

format




92

Following may be changed fr om Edit Access

Path Details panel

» Unique/Duplicate key sequence

» Access Path Maintenance (Immed, Rebld, Dly)

» Alternate Collating Sequence

» Select/Omit Criteria

» Generation Mode (DDS/SQL)» Source member name & text

Building Access PathsModifying an Access Path

B ildi A P h



93

Building Access PathsArrays

» Arrays have a defined layout with each element

having the same layout

» Must have a defined key that acts as an index

» Key is any subset of the fields with a maximumcomposite key length of 990

» Sequence of equally keyed elements in a non-unique

array is not guaranteed

» Each key in the composite key acts as a different

array dimension

» Key can be ascending/descending

» For key sequence, signs are ignored

B ildi A P th



94


Arrays can be used by the f ollowing f our

functions:

» CRTOBJ - to add an element

» CHGOBJ - to change an element

» DLTOBJ - to delete an element

» RTVOBJ - to read an element or set of elements

B ildi A P th



95


Features

» Can be used to define a set of fields to be used as a

parameter entry to a function

» Arrays are initialized on the first program call

» Subsequent calls will not clear the array

B ildi A P th



96

Adding/Changing/Deleting Arrays

» Enter *a in the option field or *ARRA YS in the

positioner field of Edit Database Relations panel

» Enter Z against *Arrays file in the resulting panel tosee a list of arrays

» Type an array name and press Enter

» Type Z against the array name and press Enter to

define fields

» Type D against an existing array and press Enter to

delete


B ildi A P th



97

Building Access PathsGenerating & Compiling

» Generate source members and compile the

generated source to produce objects, files & tables

» From Edit Database Relations panel, press F17 for

services» On Display Services Menu, type 8 at bottom of

screen to display Display All Access Paths panel

» Type J (batch generation) or G (interactive

generation) and press Enter



98

Building ApplicationsCOOL:2E Functions

COOL:2E function is a pr ocess that operates

on files & fields

COOL:2E Functions can be linked to createlarger pr ocesses that become the building

blocks of an application

Several COOL:2E functions may be

implemented in a single HLL pr ogram

B ildi A li ti



99

Building ApplicationsImplementation of Functions

COOL:2E functions are implemented in two

ways

» External - the function is implemented as a separateHLL program

» Internal - the function is implemented as source code

inside the calling function

Building Applications



100

Building ApplicationsCOOL:2E Function Types

4 COOL:2E functions types

» Standard Functions

» Built-In Functions

» Functions Fields

» Message Functions

Standard functions

» specify the entire programs or subroutines» User-defined processing can be specified

» Provide building blocks of an application




101

Standard Functions

» Divided into 3 categories

± Database Functions

± Device Functions

± User Functions

Built-in Functions

» Execute functions like arithmetic operations, stringmanipulation, control operations like commitment

control & program exit





102

Built-in Functions

» Specified within action diagrams

» Implemented as in-line source code within calling

functions

» The Built-in functions are

1) Add 2) Commit

3) Compute 4) CONCAT -Concatenation

5) CVTVAR - Convert Variable

6) DIV - Divide 7) DIV WITH REMAINDER

8) Exit Program 9) Modulo





103

Built-in Functions

» The Built-in functions are (contd«)

10) Move 11) Move All

12) MULT - Multiply 13) Quit

14) RTVCND - Retrieve Condition

15) Rollback 16) Set Cursor

17) Substring 18) SUB - Subtract





104

Function Fields

» A field whose value is not physically stored in the

database

» Derived from other fields or files» One result parameter - the derived field

» Variable number of input parameters used to derive

the value

» COOL:2E provides ready-made function fields

1) SUM - Sum 2) MAX - Maximum 3) MIN - Minimum

4) CNT - Count 5) DRV - Derived 6) USR - User





105


Message Functions

» Define workstation messages

» Implemented using OS/400 message descriptions

» Sent by a call to a CL subroutine

» Can make direct references to fields in the data

model




106


Message Functions

» The Message functions are

1) SNDERRMSG - Send Error Message

2) SNDINFMSG - Send Information Message

3) SNDCMPMSG - Send Complete Message

4) SNDSTSMSG - Send Status Message

5) RTVMSG - Retrieve Message

6) EXCMSG - Execute Message




107

Building ApplicationsStandard Functions

Database Functions

» Basic routines for accessing the database

» Implemented as part of an external function

» Can be used in many different functions

» There are 4 database functions

1) CRTOBJ - Create Object

2) CHGOBJ - Change Object

3) DLTOBJ - Delete Object

4) RTVOBJ - Retrieve Object




108


Device Functions

» Used in interactive & report programs

» Consist of panel/report design & action diagram

» All device functions are external functions except for

PRTOBJ function

» Implemented as programs that operate over

databases




109


Device Functions (contd«)

» The Device Functions are

1) DSPRCD - Display Record

2) DSPRCD2 - Display Record 2 panels

3) DSPRCD3 - Display Record 3 panels

4) PMTRCD - Prompt Record

5) EDTRCD - Edit Record

6) EDTRCD2 - Edit Record 2 panels

7) EDTRCD3 - Edit Record 3 panels




110


Device Functions (contd«)

» The Device Functions are

8) DSPFIL - Display File

9) EDTFIL - Edit File

10) SELRCD - Select Record

11) DSPTRN - Display Transaction

12) EDTTRN - Edit Transaction

13) PRTFIL - Print File

14) PRTOBJ - Print Object




111


User Functions

» Means of incorporating user programs or subroutines

into COOL:2E generated applications

» Processing steps can be specified with action

diagrams or user-written HLL

» Implemented as inline code (internal functions) or call

to programs (external functions)




112


User Functions

» The User Functions are

1) EXCINTFUN - Execute Internal Function

2) EXCEXTFUN - Execute External Function

3) EXCUSRPGM - Execute User Program

4) EXCUSRSRC - Execute User Source




113

Building ApplicationsBasic Function Pr operties

Function Name

» up to 25 characters long including embedded blanks

& must be unique within a file

Function Components» Function options

± allow the user to customize function features like database

changes, display features, exit control, commitment control,

exception routines, generation options & environmentoptions




114


Function Components

» Function Parameters

± specify the input and output parameters. Parameters are

also used to define local variables for the function» Device Designs

± specify the visual presentation of the 2 types of devices

used by functions: Panels & Reports

» Action Diagrams ± specify the processing steps for function logic. This is a

combination of default COOL:2E supplied and optional user

defined processing logic




115


Function class Parameters DeviceDesign

ActionDiagrams

FunctionOptions

Device Functions

Database FunctionsUser Functions

xx

x, x

1

x, x

3

Messages

Function Fields

x

x

x

, x2

x

x

Built-In Functions x x x

1 EXCINTFUN & EXCEXTFUN have action diagrams

2 Only DRV (Derived) function fields have action diagrams

3 EXCEXTFUN is the only user function with function options

Function Components




116


Default Device Function Pr ocessing

» Default Device functions compile into working

programs with default processing

» Additional logic required for business processing




117

Building ApplicationsFunctions & Access Paths

Functions & Access paths

» Functions operating on a file are always attached to it

by an access path

» Functions can access many files with access pathsbased on several files

» A generated program can be made up of several

functions each accessing a different access path

» Default panel/report formats are derived from thefunction¶s access path




118

Building ApplicationsAdditional Pr ocessing

Automatic additional logic f or functions

» Integrity Checking

± Domain integrity checking for allowed values. Enforced by

fields having same reference file. ± Referential Integrity Checking to ensure that relations

specified in the model are satisfied

» Field Validation

± upper/lower case validation ± valid name checking

± validation through a check condition.




119

Building ApplicationsAdditional Pr ocessing

Automatic additional logic f or functions

» Linking Functions

± Automatically links certain functions together

± External update functions like EDTFIL are automaticallylinked to database function like CHGOBJ

Building Blocks Appr oach

» Functions are building blocks

» By linking functions together, required functionality

can be achieved




120

Building ApplicationsDefining Functions

Accessing Functions

» Display All Functions panel

± select option from the Services Menu

» Display File Functions panel ± option F on a file in Edit Database Relations panel

Shipped Files Fields

» COOL:2E shipped files contain the default data like

built-in functions, messages etc.

» Type * in the Object field & DFN in relations field of

Edit Database Relations panel to access




121

Op: SYNTHS QPADEV0004 18/02/98 13:52:40

DISPLAY ALL FUNCTIONS SYNSXT

Application area. : Source library: SYNSXTGEN

? File Function Type GEN name

Commodity Change Commodity CHGOBJ *N/A

Commodity Create Commodity CRTOBJ *N/A

Commodity Delete Commodity DLTOBJ *N/ACommodity Edit Commodity EDTFIL SXACEFR

Commodity Select Commodity SELRCD SXABSRR

Commodity Price Change Commodity Price CHGOBJ *N/A

Commodity Price Create Commodity Price CRTOBJ *N/A

Commodity Price Delete Commodity Price DLTOBJ *N/A

Commodity Price Edit Commodity Price EDTFIL SXAEEFR

Commodity Price Select Commodity Price SELRCD SXADSRR

SEL: Z-Dtls, P-Parms, N-Narr., F-Action diagram, S-Device Design, T-Structure,

A-Acp, G/J-Gen, E-STRSEU(pgm), L-Locks, D-Delete, U-Where used, 3-Doc.

F3=Exit F5=Reload





122

Op: SYNTHS QPADEV0004 18/02/98 13:48:09

EDIT FUNCTIONS SYNSXT

File name. . . : Commodity ** 1ST LEVEL **

? Function Function type Access path

Change Commodity Change object Update index

Create Commodity Create object Update index

Delete Commodity Delete object Update indexEdit Commodity Edit file Retrieval index

Select Commodity Select record Retrieval index

+

SEL: Z-Details, P-Parameters, F-Action diagram, S-Device design, N-Narrative,

T-Structure, A-Access path, U-Usage, G/J-Generate, D-Delete, C-Copy, L-Lock.

F3=Exit F5=Reload F7=File details F9=Add F17=Services





123

*DSNR SYNSXT Op: SYNTHS QPADEV0004 18/02/98 13:40:46

EDIT DATABASE RELATIONS SYNSXT

=> * Rel lvl: DFN

? Typ Object Relation Seq Typ Referenced object

FIL *Arrays Defined as FIL *Arrays

FIL *Built in functions Defined as FIL *Built in functions

FIL *Configuration Table Defined as FIL *Configuration Table

FIL *Distributed File Defined as FIL *Distributed FileFIL *External Data Access API Defined as FIL *External Data Access API

FIL *Field attribute types Defined as FIL *Field attribute types

FIL *Job data Defined as FIL *Job data

FIL *Messages Defined as FIL *Messages

FIL *Program data Defined as FIL *Program data

FIL *Standard header/footer Defined as FIL *Standard header/footer

FIL *COOL:2E reserved pgm data Defined as FIL *COOL:2E reserved pgm data

FIL Audit Information Defined as FIL Audit Information

FIL Commodity Defined as FIL Commodity

FIL Commodity Price Defined as FIL Commodity Price

FIL Company Defined as FIL Company

+

SEL: Z(n)-Details, N(n)-Narr, S(n)-Select, E(n)-Entries, V-Virt.fields, F-Funcs

F3=Exit F5=Reload F7=Fields F9=Insert F10=Define obj. F17=Services





124

Building ApplicationsDatabase Functions

What are Database functions?

» means of performing actions on database

» defined as HLL subroutine

4 Database functions

1) CRTOBJ - routine to add a record to a file.

2) CHGOBJ - routine to update a record.

3) DLTOBJ - routine to delete a record.4) RTVOBJ - routine to retrieve one or more records.




125

Default versions of CRT, CHG and DLT

database functions are created f or all REF &

CPT files.

RTVOBJ must be created if needed.

Additional pr ocessing bef ore and after

database access may be specified in the

action diagram.

g ppDatabase Functions




126

Function Purpose Access Path

CRTOBJ

CHGOBJDLTOBJ

Add a single record

Update a single recordDelete a single record

UPD

UPDUPD

RTVOBJ Read a record or record s RTV, RSQ





127

Array Pr ocessing

» Even though arrays are not implemented as database

files, the 4 database functions can be defined over an

array and used.» DLTOBJ with no parameter will clear an array





128

g ppDevice Functions

What are Device Functions?

» Interactive panels or reports

» Panel device functions for interactive user interface

between end user and application

» Report device functions for written presentation of

data

» All device functions except PRTOBJ function are

implemented as external functions




129


Interactive device design editor

» Allows defining of

± field attributes

± positioning

± conditioning

± user function keys

± literals

» Can be accessed from Edit Functions, Edit All Functions, Edit Function Devices, or the Display All

Functions panels




130

Device Standard Header device functions

» Define Screen Format (DFNSCRFMT)

± to define standard screen header and footer for use by

other functions with attached screen design

» Define Report Format (DFNRPTFMT)

± to define standard report header and footer for use by Print

File report functions





131

Single record device functions

» Prompt Record (PMTRCD)

± defines a program to prompt for a list of fields defined by a

specified access path ± validated values can be passed to another function

» Display Record (DSPRCD)

± defines a program to display a single record from a

specified database file ± If no key is specified, a key panel prompts for a key





132

Single record device functions (contd...)

» Display Record 2 panels (DSPRCD2)

± identical to DSPRCD except that it allows the record details

to extend into 2 device pages» Display Record 3 panels (DSPRCD3)

± identical to DSPRCD except that it allows the record details

to extend into 3 device pages





133

Single record device functions (contd«)

» Edit Record (EDTRCD)

± defines a program to maintain (add, change or delete)

records one at a time. ± If no key is specified, a key panel prompts for a key.

» Edit Record 2 panels (EDTRCD2)

± identical to EDTRCD except that it allows the record details

to extend into 2 device pages.» Edit Record 3 panels (EDTRCD3)

± identical to EDTRCD except that it allows the record details

to extend into 3 device pages.





134

Multiple record device functions

» Display File (DSPFIL)

± defines a program to display the records in a file many at a

time, using a subfile ± the subfile is loaded one page at a time when the user

presses ROLLUP/F8

» Edit File (EDTFIL)

± defines a program to maintain the records in a file many ata time, using a subfile

± the subfile is loaded one page at a time when the user

presses ROLLUP/F8.





135

Multiple record device functions (contd«)

» Select Record (SELRCD)

± defines a program to display the records in a file many at a

time, using a subfile ± allows the user to select one record which is returned to the

calling program

± called from a function that requests a selection list.





136

Single & multiple record device functions

» Display Transaction (DSPTRN)

± defines a program to display the records from a selected

pair of database files ± the pair must be connected by an Owned by or Refers to

relation

» Edit Transaction (EDTTRN)

± defines a program to maintain the records from a selectedpair of database files

± the pair must be connected by an Owned by or Refers to

relation.

Device Functions




137

Printer device functions

» Print File (PRTFIL)

± defines a program to print records from a specified access

path.» Print Object (PRTOBJ)

± defines a particular report fragment which will print the

records from a specified access path at any point within a

PRTFIL function ± can be embedded within other PRTOBJ functions.

Device Functions




138

Standard Features of Device Functions

» Diagnostic messages

± message sent to program¶s message queue

± message subfile to show the pending messages ± allows second level text and substitution variables

» Highlighting of Errors

± a field in error is highlighted in reverse image

± cursor is positioned at first such field» On-line Help Text

± pressing HELP key or F1 key results in call to a help

program

Device Functions




139


» Print Key

± print key is enabled to allow panel prints

± print file is controlled by YPK YVNM model value» Selection Columns

± Selection subfiles have selection column on the left

» Function key Usage

± CUA standards are followed e.g. F3 is exit» Positioning facilities

± subfile programs have a positioning field

Device Functions




140


» Single Page Subfile load up

± subfiles are loaded on demand basis

± only when F8

or ROLLUP keys are pressed» Concurrency checking and record locking

± updation programs do not hold locks upon database while

changes are entered or validated

± includes logic at the point of update to check for record lock

by other users

» Overflow Handling

± report functions include handling of page overflow

Device Functions




141

What are User Functions?

» means of implementing additional user processing

within an existing function or as an independent

implementation along with an existing function

» e.g. batch functions for updating database having no

associated device or a user-written HLL program

which has to be integrated to COOL:2E generated

application

User Functions




142

Two types of User Functions

» Free-Form User functions

± specify actions that can be used within a function or called

from a function

± processing logic is defined through the Action Diagram

editor

» User Coded User functions

± functions are user-written in HLL

± can be called or embedded

User Functions




143

Free-For m User Functions

» Execute Internal Function (EXCINTFUN)

± allows specification of a section of an action diagram for

repeated use in other functions

± implemented as Internal function

» Execute External Function (EXCEXTFUN)

± allows specification of an HLL program using an action

diagram

± implemented as External function

User Functions




144

User Coded User Functions

» Execute User Program (EXCUSRPGM)

± describes interface to a user written HLL program

± parameters can be specified on the call» Execute User Source (EXCUSRSRC)

± specifies that user-written HLL code be included within the

HLL source generated by COOL:2E for an external function

User Functions




145

What are Message Functions?

» means of defining messages of various types,

specifying different message files for the message,

specifying substitution variables and changing

message identifiers

» can be accessed by looking at functions of

*MESSAGES file

Message Functions




146

6 Message Functions

» Send Error Message (SNDERRMSG)

± error message to be sent to a calling function

± used for diagnostic messages arising from user validation

» Send Information Message (SNDINFMSG)

± information message be sent to the message queue of the

calling program

» Send Completion Message (SNDCMPMSG)

± completion message to be sent to a calling function

Message Functions




147

6 Message Functions

» Send Status Message (SNDSTSMSG)

± status message to be sent to a calling function

± informs of the progress of a long-running process

» Retrieve Message (RTVMSG)

± to retrieve message text from message in message file

» Execute Message (EXCMSG)

± specifies that a request message has to be executed

Message Functions




148

What are Function Fields?

» Special types of fields that can be used in device

designs and action diagrams

» based on other fields

» processing can be specified for a function field

Function Fields

Building ApplicationsF i Fi ld



149

Function field Usages

» Sum (SUM)

± contains sum of values of another field

± Input Parameter is the field whose sum is to be calculated ± Result Parameter is the field containing the sum

» Count (CNT)

± defines count of a set of records in EDTTRN, DSPTRN,

PRTFIL & PRTOBJ functions

± Input Parameter is field on the detail or subfile record

± Output field contains the count

Function Fields

Building ApplicationsF ti Fi ld



150


» Maximum (MAX)

± contains the highest value of another field

± Input Parameter is the field whose maximum is to becalculated

± Result Parameter is the field containing the maximum

» Minimum (MIN)

± contains the lowest value of another field

± Input Parameter is the field whose minimum is to be

calculated

± Result Parameter is the field containing the minimum

Function Fields

Building ApplicationsF ti Fi ld



151


» Derive (DRV)

± performs user-defined action to derive result

± action diagram is attached where processing can bespecified for deriving the result

± Multiple input Parameters can be specified

± One Resulting Parameter

» User (USR)

± reserved for work fields needed in device design or action

diagram e.g. menu options, command string

± can be input-capable or output only

Function Fields

Building ApplicationsF ti O ti



152

What are Function Options?

» Function options control the features of functions

» Function Options for

± Database Changes ± Display Features

± Exit Control

± Commitment Control

± Exception Routine ± Generation

± Environment

Function Options




153

Database Changes Function options

» determine if program allows add, change or delete

capabilities or a combination

Display Features Function options» Confirmation - function prompts for confirmation

» Initial value for Confirmation

» Standard Header/Footer selection

» Subfile Selection Column

» Dynamic Program Mode - function determines initial

mode of execution

Function Options




154

Display Features Function options

» Exit after Add - for EDTRCD functions

» Repeat Prompt - whether prompt (PMTRCD) to be

redisplayed after user processing» Bypass Key Screen - whether key screen to be

displayed before displaying detail screen

» Post Confirm Pass - to re-read database file and

update subfile after confirmation» Send All Messages - whether message subfile at

bottom of panel for first or all errors

Function Options




155

Exit Contr ol

» Determines execution characterstics of programs

» Closedown Program - whether program will terminate

or remain invoked but inactive» Reclaim Resources - whether RCLRSC command

will be invoked after program call

» CopyBack Messages - whether pending messages in

program message que to be copied to programmessage queue of calling program

Function Options




156

Commitment Contr ol

» Determines commitment control regime for a program

namely MASTER, SLAVE or NONE

» MASTER - program contains commit points and theprogram ensures that commitment is active

» SLAVE - program contains commit points but the

program does not ensure that commitment is active

» NONE - program does not run under commitmentcontrol

Function Options




157

Exception Routine

» Generate Exception Routine - specifies whether code

for exception routine (*PSSR) should be generated

Generation Options» Generation Mode - specifies database access used

for functions

D for DDS access method; S for SQL access method

E for External Source Format; M for model value

A if generation value of primary path to be used

Function Options

Building ApplicationsFunction Options



158

Generation Options

» Generate Help - specifies whether help is generated

» Screen Text Constants

L results in panel literals being hardcoded in sourceM results in panel literals to be stored in message file

D means model value to be used

Function Options

Building ApplicationsFunction Parameters



159

What are Function Parameters?

» Specifies the fields passed between functions

Basic pr operties of function parameters

» Name» Usage Type

± Input only, Output only, Both, Neither

» Flag Error Status

± specifies error in the called function

± allowed in SNDERRMSG, EXCMSG or any external

function

Function Parameters




160

Neither Parameters

» No value passed or returned for a parameter

» Neither parameters are available for use as local

variables within the functionDefault parameters of functions

Function Default parameters Usage

CHGOBJ All fields of Update index I

CRTOBJ All fields of Update index IDLTOBJ Key fields of Update index I

RTVOBJ Key fields of attached acc. path I

SELRCD Key fields of Update index B

Function Parameters




161

Return Code Parameter

» Informs the calling program of the state under which

called program was exited

» All functions except EXCUSRPGM & EXCUSRSRChave implicit return code parameter as first parameter

» The values of Return Code parameter are

*DBF error; *Normal; *Record already exists;

*Record does not exist; *Substring error;*User Quit requested

Function Parameters




162

Parameter Roles

» Specifies the use of parameter in function

» Following are the parameter roles

Map Parameter - the parameter is added automatically to thecorresponding field on the receiving function¶s panel

design. Map Neither parameter adds field to panel design

without passing a value

Restrictor Parameter - the parameter restricts the updation

of field by making it input only fieldPositioner Parameter - the parameter is used to position a

function to start reading records from a particular record

Function Parameters




163

Parameter RolesVary Parameter - the parameter can have a varying length.

Useful for interfacing with user-written functions

Defining Function Parameters

» in the Edit Functions panel, type P next to the

selected function

» specify a field or a set of fields in Edit Function

Parameters panel

» Type Z for a parameter to specify Role/Usage

through Edit Function Parameter Details panel

Function Parameters




164

Function Parameters

Op: SYNTHS QPADEV0007 19/02/98 10:38:58

EDIT FUNCTION PARAMETERS SYNSXT

Function name. . : Delete Commodity Type : Delete object

Received by file : Commodity Acpth: Update index

Passed

? File/*FIELD Access path/Field as Seq

Commodity Update index KEY

|

Values

FLD: One parameter per fieldRCD: One parameter for all fields

KEY: One parameter for key fields only

SEL: Z-Details (field selection).

F3=Exit F5=Reload




165

Function Parameters

Op: SYNTHS QPADEV0007 19/02/98 10:40:20

EDIT FUNCTION PARAMETER DETAILS SYNSXT

Function name. . : Delete Commodity Type : Delete object

Received by file : Commodity Acpth: Update index

Parameter (file) : Commodity Passed as: KEY

? Field Usage Role

Commodity Code I

SEL: Usage: I-Input, O-Output, B-Both, N-Neither, D-Drop.

Role: R-Restrict, M-Map, V-Vary length, P-Position.

F3=Exit

Building ApplicationsDevice Designs



166

Device Designs

What are Device Designs?

» Specifies the layouts of fields and constants on the

panels or report designs for a function

Basic pr operties of Device Designs» Device Design Standard

± depends on the function type and associated standard

header/footer functions

» Device Design Format ± Formats are created from the fields of the based-on access

path and their associated text




167

Device Designs

Basic pr operties of Device Designs

» Device Design Field

± fields come from access path, function parameters and

Header/Footer

Editing Device Design

» in the Edit Functions panel, type S next to the

selected function to display the device design

» use function keys to edit the device design ± F1 moves the field 40 columns

± F3 exits the panel




168

Device Designs


» use function keys to edit the device design

± F4 move the field 40 columns to the right

± F5 edits device format details

± F6 cancels the pending operations

± F7 displays Edit Device Design Format Relations

± F8 moves the selected field to the cursor position

± F9 wraps text onto next line

± F10 moves text one column to the right

± F11 removes the line

± F12 aligns text below cursor position




169

Device Designs



± F13 fast exits the panel

± F15 moves panel window to left margin

± F16 moves window to right margin

± F17 displays a list of device formats

± F18 displays the Edit Field Attributes panel

± F19 adds new function field to the device

± F20 edits function field on the device

± F21 adds a line above cursor

± F22 moves text one column to the left




170

Device Designs



± F23 adds constant field to the device design

± F25 aligns all fields under the cursor position

Building ApplicationsAction Diagrams



171

Action Diagrams

What are Action Diagrams?

» Action Diagrams record the basic constructs that

make up a procedure

» the procedural steps encompass a list of actions likecall to another function or a low-level built-in function

Displaying Action Diagram of a function

» Type F next to the selected function in the Edit

Functions panel




172

Action Diagrams

EDIT ACTION DIAGRAM Edit SYNSXT Commodity

FIND=> Edit Commodity

> Edit Commodity

.--

. ...Initialize <--

. .=REPEAT WHILE

. |-*ALWAYS

. | ...Load first subfile page <--

. | PGM.*Reload subfile = CND.*NO

. | > Conduct screen conversation

. | .=REPEAT WHILE

. | |-PGM.*Reload subfile is *NO

. | | Display screen

. | | ...Process response <--

. | '-ENDWHILE

. '-ENDWHILE

. ...Closedown <--'--

F3=Exit F5=User points F6=Cancel pending moves F7=Forward F8=Backward

F9=Edit parameters F15=Open Functions F16=Toggle Change Date F24=More keys




173

Action Diagrams

User Points

» COOL:2E/2 functions except EXCUSRSRC &

EXCUSRPGM have default action diagram

» some portions of default action diagrams which depictessential processing are not alterable

» areas which can be modified and where business

logic can be entered are called User Points

» Press F5 on the action diagram to display user pointsfor the function




174

Action Diagrams

EDIT ACTION DIAGRAM Edit SYNSXT Commodity

FIND=> Edit Commodity

..............................................................

> Edit : ACTION DIAGRAM EXIT POINTS F3=Exit SEL:X,Z-Select. :

.-- : USER: Initialize program :

. ...I : USER: Initialize subfile header : <--

. .=RE : USER: Initialize subfile record (existing record) :

. |-*A : USER: Initialize subfile record (new record) :

. | .. : CALC: Subfile control function fields : <--

. | PG : USER: Validate subfile control :

. | > : USER: Validate subfile record fields :

. | .= : CALC: Subfile record function fields :

. | |- : USER: Validate subfile record relations + :

. | | :............................................................:

. | | ...Process response <--

. | '-ENDWHILE

. '-ENDWHILE

. ...Closedown <--'--

F3=Exit F5=User points F6=Cancel pending moves F7=Forward F8=Backward

F9=Edit parameters F15=Open Functions F16=Toggle Change Date F24=More keys




175

Action Diagrams

Action Diagram Constructs

» Sequential - specify a list of actions or other

constructs that are executed in a sequential order.

Denoted by brackets enclosing dotted lines

___

: «.

: «.

:___




176

Action Diagrams


» Conditional - actions are conditionally executed and

are called CASE blocks. Denoted by CASE and

ENDCASE statements

_ CASE

: «.

: «.

:_ ENDCASE




177

Action Diagrams


» Iterative - represents repetitive logic. Denoted by

REPEAT WHILE and ENDWHILE statements

_ REPEAT WHILE

: «.

: «.

:_ ENDWHILE




178

Action Diagrams

Context» instances of a field that are available for use at a

particular processing step

» Database Contexts - instances of same database

field available in more than one file

» Device Contexts - instances of same device field

available in more than one format

» Literal Contexts - instances of field available from

literals like condition etc.

» System Contexts - instances of fields available from

various system values




179

Action Diagrams

Context» Function Contexts - instances of field available from

function attributes like parameter

Database Contexts» DB1 - fields are in the first or the only format of the

based-on access path

» DB2 - fields are from second format of the based on

access path e.g. in SPN access path




180

Action Diagrams

Device Contexts

» KE Y - fields are from the key panel display in case of

EDTRCD or DSPRCD functions

» DTL - fields are from the first panel of EDTRCDn or DSPRCDn functions

» 2ND - fields are from the second panel of EDTRCDn

or DSPRCDn functions

» 3RD - fields are from the third panel of EDTRCDn or DSPRCDn functions




181

c g

Device Contexts

» CTL - fields are from the subfile control record format

» RCD - fields are from the subfile record format

» CUR - fields are from the current report format inPRTOBJ and PRTFIL functions

» NXT - fields are from the next active report format in

PRTOBJ and PRTFIL functions




182

g

Literal Contexts

» CND - particular field condition is specified as a value

» CON - constant context contains a literal value for

non-status type fieldsSystem Contexts

» JOB - contains system fields having execution time

information of the job e.g. *USER, *JOB

» PGM - contains system fields that control theexecution like *Program Mode, *Return Code




183

g

Function Contexts

» PAR - parameter fields as field values

» WRK - program variables not declared as any context

as field values e.g. any field in data dictionaryAction Diagram Editor

» allows modification of Action Diagram

» line commands allow the modification




184

g

Action Diagram Editor

» Line Commands* Activate/Inactivate construct (Comment out)

** Place block Activate/Inactivate boundary

A Place copied or moved construct after this line

B Place copied or moved construct before this line

C Copy construct to a point indicated by 'A' or 'B'

CC Place block Copy boundary

D Delete this construct

DD Place block Delete boundary

F Edit action or condition details for line

FF Edit action parameters

H Hide construct

I+ Insert *ADD built-in function

I+F Insert and Prompt *ADD built-in function

I* Insert Comment

I*F Insert and Prompt Comment




185

g


» Line CommandsI- Insert *SUB built-in function

I-F Insert and Prompt *SUB built-in function

I= Insert *MOVE built-in function

I=A Insert and Prompt *MOVE ALL built in functionI=F Insert and Prompt *MOVE built-in fucntion

IA Insert Action

IAF Insert and prompt Action

IC Insert Case condition

ICF Insert and Prompt Case condition

II Insert Iteration

IIF Insert and Prompt Iteration

IM Insert Message functionIMF Insert and Prompt Message function

IO Insert *OTHERWISE condition

IOF Insert and prompt *OTHERWISE condition




186

g


» Line CommandsIS Insert Sequence

ISF Insert and Prompt Sequence

IX Insert New condition within Case

IXF Insert and Prompt New condition within Case

M Move construct to a point indicated by 'A' or 'B'

MM Place block Move boundary

NA Copy to notepad & append to contents of notepad

NAA Place block notepad append boundary

NI Insert entire contents of notepad after this line

NR Copy to notepad & replace contents of notepad

NRR Place block notepad replace boundary

S Show construct

T Return to top level of action diagram

U Unzoom out of construct to previous construct

Z Zoom into construct

Generating ApplicationsCOOL:2E Generator



187

Generation» Data Model is translated into either DDS sources or

SQL collections

± Access Paths into Physical and Logical files

» COOL:2E functions are translated into HLL programs

- COBOL, RPG or both

» Device designs attached to functions are generated

as DDS sources of Display and Printer files

» Compilation of generated code is automatically

submitted

Generating ApplicationsCOOL:2E Generator



188

Generating Code» from the Services Menu, take option for displaying all

access paths or all functions

» Take option J(batch) or G(online) for the item that has

to be generated

COOL:2E/1E UtilitiesMenus



189

COOL:2E/1E Menus

» dynamic menu system

» removes the need of individual OS/400 display file for

each application menu» Menus stored in special form and displayed using

COOL:2E commands YWRKMNU & YGO

» Menus are stored in a database file member

» YDSNMNU is the default menu file supplied with

COOL:2E/1E

COOL:2E/1E UtilitiesMenus



COOL:2E/1E Menus

» YCRTDSNF command can create a new design file

» YADDDSNFM adds new member to design file

» 2 types of COOL:2E menus

± Single option

± Multiple option

synon training

Documents

applications cool

2e1e cool

e null model cool

e base products cool

e rpg generators cool

e cobol generators cool

design facilities

function design