COOL2E TRG ppt1

8/3/2019 COOL2E TRG ppt1

http://slidepdf.com/reader/full/cool2e-trg-ppt1 1/192



Accenture-Internal Use Only 3

COOL:2E Training

Contents

•Introduction to COOL:2E

•Getting Started

•Data Modeling

•Building Access Paths

•Building Applications

•Generating Applications

•COOL:2E/1E Utilities




Introduction to COOL:2ECOOL:2E Objectives

– An application development tool

– Allows efficient design, development,implementation & maintenance of applicationsoftware

– Better than third generation development methods

– Knowledge of programming language not required

– Platform independent application design


http://slidepdf.com/reader/full/cool2e-trg-ppt1 5/192Accenture-Internal Use Only 5

Introduction to COOL:2ECOOL: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



Implementation independenceApplication 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

Introduction to COOL:2ECOOL:2E Design Principles



Data-driven DesignApplication 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 datamodel

Introduction to COOL:2ECOOL:2E Design Principles (contd..)



• COOL:2E Rapid Prototyping Methodology (RPM) is adata-driven, pragmatic approach to ApplicationDevelopment

• Rapid Prototyping Methodology

– Analyze

• System analysis, E-R diagram, COOL:2E Datamodel, Primary access paths, function flows anddevice designs

Introduction to COOL:2EApplication Development



– Change design model as necessary

– Update the function design for above changes

– Regenerate dependant elements

Introduction to COOL:2EApplication Maintenance

I d i COOL 2E




COOL:2E

Application development tool for AS/400

Includes COOL:2E/1E

COOL:2E/2G

Provides PC based GUI for COOL:2ECOOL:2E/CSG (Client Server Generator)

Option to COOL:2E which allows distributed functionality

on multiple platforms

Introduction to COOL:2ECOOL:2E Products




– 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)

Introduction to COOL:2ECOOL:2E Features




– 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

Introduction to COOL:2ECOOL:2E Features (contd…)




– 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


COO




– 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, journaling & errorhandling

• Automatic referential integrity & domain checks


Getting Started




Contain the files and objects needed to use COOL:2E products – 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 StartedCOOL:2E Product Libraries

G tti St t d




It is the model in which the development team creates anapplication and in which initial generation takes place.

Objects are tested in the development environment.

Getting StartedDevelopment Environment

Getting Started




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

Development Libraries

Getting Started




YCRTMDLLIB command creates a modelYCRTMDLLIB Command Parameters

Model Library Name (MDLLIB)

Generation Library Name (GENLIB)

Design Standard (DSNSTD) like *CUATEXT etc.

File generation method : DDS/SQLSQL Collection Library (SQLLIB)

Naming Prefixes

Object Prefix (OBJPFX)

Message Prefix (MSGPFX)

Getting Started

Creating/Using a Model

Getting Started




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 DevelopmentLibraries and Product Libraries

Run command YBLDLIBLST <LIBL-Name>

Getting Started

Creating/Using a Model (contd…)

Getting Started




User Can go through the menu options in ADR1, selectingSYNON/2E option

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

Designer(*DSNR) or as a Programmer (*PGMR) or (*USER)

Getting Started


Getting Started




MAIN COOL:2E Main Menu

Level . : 1System: XXXX

Select one of the following:

Design Model 1. Display Designer (*DSNR) menu2. Display Programmer (*PGMR) menu3. Display User (*USER) menu

8. Work with Model Object Lists9. Change to work with another model

Commands 50. COOL:2E commands in alphabetical order

51. Commands to set up or alter a model52. Commands to copy a model53. Commands to create an application

54. Commands to document a model More...Selection or command _________________________________________===>

Getting Started


Data Modeling




•A Data Model is a structured description of a set of data and its

relationships which can be used to represent the business of an

organization

•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?

Data Modeling




Data Modeling

Entity-Relationship (E-R) Modeling

•Identify Primary Entities and their attributes

•Identify Relations between Entities and between Entities and

the Attributes

•Normalize the Data Model

Data Modeling





Identifying Primary EntitiesReview 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 storedIdentify the business dimensions

Generalize or differentiate Entities

Data Modeling





Identifying Primary Entities - example

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

Customer Code:

Name: Phone:

Address: Order No.:

Date:

Product Code Description Qty Price Total

________ ____________ ____ ____ ___

________ ____________ ____ ____ ___

The following primary entities can be identified

a) Company b) Customer c) Order d) Product

Data Modeling




g


Identifying 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 were

identified

a) Vendor b) Purchase OrderGeneralize Entities

Combine two entities representing different types of the same

thing into one entity

Differentiate Entities

Differentiate different types of the same thing as twodifferent entities

Data Modeling




Data Modeling


Identifying Entity AttributesIdentify 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 theidentified attributes

Data Modeling




Data Modeling


Identifying RelationsIdentify relations between Entity and its attributes and

between different Entities

Categorize relationship types by

Optional/Mandatory

CardinalityInvolution

Select Primary Key or Unique Identifier for an Entity

Data Modeling

E tit R l ti hi (E R) M d li





Identifying RelationsOptional/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 relationshipInvolution - 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.

Data Modeling





Identifying Relations

One-To-One Relation - each instance of one entity is related to

one instance of another entity

assigned to

e.g. Salesperson Territory

has

One-To-Many Relation - One instance of an entity is related tomultiple instances of another entity

places

e.g. Customer Order

placed by

Data Modeling

Entity Relationship (E R) Modeling





Identifying RelationsMany-To-Many Relation - each instance of one entity is

related to more than one instance of another entity and vice

versa

e.g.

orders

ordered byOrder Product

Data Modeling

E i R l i hi (E R) M d li





Identifying RelationsSelect 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

Data Modeling

E tit R l ti hi (E R) M d li





Identifying RelationsImplement Entity to Entity Relationship using Foreign

Key

Foreign Key - An attribute or group of attributes of an

entity which 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



Data Modeling

Entity Relationship (E R) Modeling





Identifying Relations - Foreign Key

example: Many-To-Many relationworked on by

Project Employeeworks on

worked on by has

Project Project Team Employeeworks on part of

Project Employee

K Project Code K Employee Code

Project Name Employee Name

Project TeamK Project Code

K Employee Code

Data Modeling

Normalizing the Data Model





Normalization Involvesregrouping attributes

splitting entities

reassigning primary keys

Functionally Dependent Attribute

for each value of the key, there is only one value of non-keyattribute

Full Functional Dependent Attribute

non-key attributes are dependent on all the key attributes of

a composite key

Data Modeling

N li i th D t M d l




Process of NormalizationCreating First Normal Form (1NF)

eliminate repeating data groups

e.g. Order splits into Order Header & Order Detail

Creating Second Normal Form (2NF)

entity is 1NFevery non-key attribute is fully functionally dependent

on primary key

Creating Third Normal Form (3NF)

entity is 2NF

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


Data Modeling

COOL:2E Data Model




COOL: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

Conditiondescribes the values or set of values (domains)

Relation

describes connection between two files or between file and

field e.g. refers to, owned by

Data Modeling

COOL:2E Data Model




COOL:2E Data Model

Conceptual Model COOL:2E Data(E-R Model) Model

---------------------------------------------------------------

Entity File

Attribute Field

Relationship RelationDomain Field Conditions:

Reference field types

Data Modeling

COOL:2E Data Model




COOL:2E Data Model

•Model can be accessed as designer (*DSNR) or as programmer(*COOL:2E provides facilities to enter / update the data model

•PGMR)

•Edit Database Relations panel allows the entry of data model to

COOL:2E



Data Modeling

COOL:2E Data Model




COOL:2E Data Model

COOL:2E Files

Each COOL:2E File has a Name and a File TypeCOOL: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 NameCOOL:2E File Types

File Attribute Description Example

Database CPT Capture file Order Entry

REF Reference file Company file

Non database STR & RCD Structure file Audit date &timestamp

Data Modeling

COOL:2E Data Model




COOL:2E Files

Reference (REF) files

master files that typically contain non-volatile information

e.g. Customer, Product, Area Code

Capture (CPT) files

contain transactional data that is recorded regularlye.g. Order, Ledger Entry

Structure (STR) files

contain group of fields which can be included in other files

using Includes relation

e.g. Audit Stamp file

Data Modeling

COOL:2E Data Model




COOL:2E Data Model

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 UPD

CHGOBJ - Change Object UPD

SELRCD - Select Record RTVEDTFIL - Edit File RTV

Data Modeling

COOL:2E Data Model




COOL:2E Files

Default functions for CPT files

Function Access Path

CRTOBJ - Create Object UPD

DLTOBJ - Delete Object UPDCHGOBJ - Change Object UPD

Data Modeling

COOL:2E Data Model




COOL:2E Data Model

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 columnType CPT or REF or STR in Object attr column

depending on the file type

Defined as relation for the file is automatically created

Data Modeling

COOL:2E Data Model




Op: XXXXXXXX XXXXXXXXXX 22/05/06 15:31:12

DEFINE OBJECTS XXXXXX

Object Object Object Referenced Field Edittype name attr field usage field

___ ________________________ ___ ________________________ ___ ____ ________________________ ___ ________________________ ___ ____ ________________________ ___ ________________________ ___ _

___ ________________________ ___ ________________________ ___ ____ ________________________ ___ ________________________ ___ _

___ ________________________ ___ ________________________ ___ ____ ________________________ ___ ________________________ ___ ____ ________________________ ___ ________________________ ___ _

+

F3=Exit



Data Modeling

COOL:2E Data Model




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

Data Modeling

COOL:2E Data Model




COOL:2E Fields

Field Usage

Two types: Database fields and Function fields

Database fields

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

CodeData 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

Data Modeling

COOL:2E Data Model




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 in

device designs and action diagrams

6 function field usage typesCNT (count) DRV (derived)

MAX (maximum) MIN (minimum)

SUM (sum) USR (user-defined)

Data Modeling

COOL:2E Data Model




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 Data area field

Defining Field as a Data Area

specify *DTAARA as default condition

Data Modeling

COOL:2E Data Model




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 columnType 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

Data Modeling

COOL:2E Data Model




Op: XXXXXXXX QPADEV000H 22/05/06 15:31:12

DEFINE OBJECTS XXXXX

Object Object Object Referenced Field Edittype name attr field usage field

FIL DealerFIL Dealer groupFLD Dealer Code CDE

FLD Dealer name ATRFLD Dealer Address 1 ATRFLD Dealer Address 2 ATR

FLD Dealer Group Code CDE

FLD Dealer Group Name ATRFLD Dealer Group Credit Limit ATR

+

F3=Exit

Data Modeling

COOL:2E Data Model




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 fieldsCMP (Compare) and RNG (Range) are valid condition

types for non-status fields

Data Modeling

COOL:2E Data Model




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

screene.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 thecondition Invoice not due has file value “U”

Data Modeling

COOL:2E Data Model




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 10Range (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 andTo value as 100

Data Modeling

COOL:2E Data Model




COOL:2E Relation

Expresses association between two files or between a file and

a field

Eight relation types

Defined as, Extended by, Has, Includes, Known by,

Owned by, Qualified by and Refers to3 different relation usage groups

Definition 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

Data Modeling

COOL:2E Data Model




COOL:2E Relation

Usage Type Relation Used for

Definition Defined as File-to-file relationship

Key Owned by File-to-file relationship

Known by File-to-field relationshipQualified 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

Data Modeling

COOL:2E Data Model




COOL:2E Relation

Defined as Relation

File-to-file relation

declares that a file exists

e.g.

Product Defined as ProductDefined as relation is automatically created for a file if a

reference is made to a non-existing file

Data Modeling

COOL:2E Data Model




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 filekeys of owning file are incorporated as high order keys in

the owned file

e.g.

Order Detail Owned by Order

Data Modeling

COOL:2E Data Model




COOL:2E RelationKnown by Relation

File-to-field relation

specifies the key field(s) for a file

e.g.

FIL Order Known by FLD Order NumberFIL 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

Data Modeling

COOL:2E Data Model




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 dateProduct Price Has Product price

Data Modeling

COOL:2E Data Model




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 be

updated from the referring file

e.g.Order Detail Refers to Product



Data Modeling

COOL:2E Data Model




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 Virtual 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

Data ModelingCOOL:2E Data Model




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: *ALL

Order Refers to Customer

For: Invoicing Sharing: *ALL





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 Entries

panel

Data Modeling

COOL:2E Data Model




• *DSNR XXXXXX Op: XXXXXXXX QPADEV000H 22/05/06 15:25:26• EDIT DATABASE RELATIONS XXXXXX• => Rel lvl:

• ? Typ Object Relation Seq Typ Referenced object• FIL Dealer Owned by FIL Dealer group• FIL Dealer Known by FLD Dealer Code• FIL Dealer Has FLD Dealer name

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

• • FIL Dealer Group Known by FLD Dealer Group Code•

FIL Dealer Group Has FLD Dealer Group Name• FIL 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-Funcs

• F3=Exit F5=Reload F7=Fields F9=Insert F10=Define obj. F17=Services• 'Dealer' type FIL not found.

Data Modeling

COOL:2E Data Model




• Op: XXXXXXXX QPADEV000H 22/05/06 16:11:55• EDIT FILE ENTRIES XXXXXXX• • File . . . . . . : Dealer

• • ? Field Type Ocr Et Ksq GEN name Length Renamed• • Dealer Group Code CDE K 1 AICD 6• Dealer Code CDE K 2 AHCD 6• Dealer name TXT A AJTX 25• Dealer Address 1 TXT A AKTX 25• Dealer Address 2 TXT A ALTX 25• • • • • • • • • • SEL: Z-Details, R-Replace field, U-Usage, M-Mapped field parameters.• F3=Exit





COOL:2E Relation

Edit Field DetailsType 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

Data Modeling

COOL:2E Data Model





EDIT FIELD DETAILS XXXXXX

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 . : BKSTK’bd shift :

Headings . . . . . . : -Text . . . . . . . . : Booking payment statusLeft hand side . . . : Booking payment status

Right hand side. . . : Value

Column headings. . . : Booking: payment

: statusValidation . . . . . : -Default condition. . : *NONECheck 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





COOL:2E Relation

Edit Field ConditionField 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.





Op: XXXXXXXX QPADEV000H 22/05/06 16:11:55 EDIT FIELD CONDITION DETAILS GXMMDL

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

on display. . : 4

Condition. . . . . . : Blue chip

Type . . . . . . . . : VAL

File value Display valueStatus value A A1

F3=Exit F8=Change name F20=Narrative

Building Access PathsIntroduction




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

when a file is definedAdditional 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

Building Access Paths

Introduction




Six types of Access Paths

Physical (PHY)

Update (UPD)

Retrieval (RTV)

Resequence (RSQ)

Query (QRY)Span (SPN)


Physical (PHY) Access Path




•Single format file containing fields derived from 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




Retrieval (RTV) Access Path




•Uniquely keyed, single format access path used by functions to

retrieve recordsKeyed exactly as the UPD access path

Allows virtual fields

Created automatically for every REF/CPT file

Associated with the UPD access path

Non-key fields can be droppedCan select/omit records

Possible to define multiple RTV access paths for a given file, but

all should have same key fields

Building Access PathsResequence (RSQ) Access Path




•Uniquely or non-uniquely keyed single format access path used by

functions to retrieve recordsMust 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

Building Access PathsQuery (QRY) Access Path




•Keyed single format access path used by functions to retrieve

recordsMust be created explicitly

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 changedAssociated with RTV, which points to a UPD

Many QRY access paths possible for single file

Implemented by OPNQRYF or Dynamic SQL

Building Access PathsSpan (SPN) Access Path




•Keyed multi-format access path

•Used by Edit & Display transaction functions to retrieve recordsfrom a pair of related files

Must be created explicitly

Defaults to keys of based on files

These keys can be changed

Allows virtual fieldsAssociated with RTV, which points to a UPD

Many SPN access paths possible for single file

Building Access PathsAccess Path Summary




# Access PathType

Real Fields Key Fields VirtualFields

Virtual Keys

1. PHY Yes x x x

2. UPD Relation x x

3. RTV

Relation

x4. RSQ User x

5. QRY User

6. SPN User x



Building Access PathsAdding an Access Path




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






EDIT FILE DETAILS SYNGXMMDL

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

Attribute . . . . . . . . : REF Field reference file. : *NONEDocumentation 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






EDIT ACCESS PATH DETAILS SYNGXMMDL

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

Access path name. . . . . : Customer by Name Type. . . . : RSQUnique 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


Adding an Access Path





EDIT ACCESS PATH FORMAT ENTRIES SYNGXMMDL

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

Access path name. . . . . : Customer by Name Type. . . . : RSQFormat 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 1Customer Limit Used VAL ABVA A 1

SEL: Z-Field details.

F3=Exit F7=Relations


Adding an Access Path




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 theprimary format and then the secondary format

Building Access PathsModifying an Access Path




Following may be changed from 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 PathsArrays




Arrays have a defined layout with each element having the same

layoutMust have a defined key that acts as an index

Key is any subset of the fields with a maximum composite key

length of 990

Sequence of equally keyed elements in a non-unique array is not

guaranteedEach key in the composite key acts as a different array

dimension

Key can be ascending/descending

For key sequence, signs are ignored





Arrays can be used by the following four functions:

CRTOBJ - to add an elementCHGOBJ - to change an element

DLTOBJ - to delete an element

RTVOBJ - to read an element or set of elements





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





Adding/Changing/Deleting Arrays

Enter *a in the option field or *ARRAYS in the positional field of Edit Database Relations panel

Enter Z against *Arrays file in the resulting panel to see a list of

arrays

Type an array name and press Enter

Type Z against the array name and press Enter to define fieldsType D against an existing array and press Enter to delete

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) andpress Enter

Building Applications

COOL:2E Functions

• COOL 2E f ti i th t t fil & fi ld




• COOL:2E function is a process that operates on files & fields

• COOL:2E Functions can be linked to create larger processes thatbecome the building blocks of an application

• Several COOL:2E functions may be implemented in a single

HLL program


Implementation of Functions




• COOL:2E functions are implemented in two ways

– External - the function is implemented as a separate HLL

program

– Internal - the function is implemented as source code inside

the calling function


COOL:2E Function Types

• 4 COOL:2E functions 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

• Standard Functions

Building ApplicationsCOOL:2E Function Types




Standard Functions

– Divided into 3 categories• Database Functions

• Device Functions

• User Functions

• Built-in Functions

– Execute functions like arithmetic operations, string

manipulation, control operations like commitment control

& program exit

Built in Functions





Built-in Functions

Specified within action diagramsImplemented 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 Variable6) DIV - Divide 7) DIV WITH REMAINDER

8) Exit Program 9) Modulo





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

Function Fields





Function Fields

A field whose value is not physically stored in the databaseDerived 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 - Minimum4) CNT - Count 5) DRV - Derived 6) USR - User


Message Functions




Message Functions

Define workstation messagesImplemented using OS/400 message descriptions

Sent by a call to a CL subroutine

Can make direct references to fields in the data model


Message Functions




g

The Message functions are1) SNDERRMSG - Send Error Message

2) SNDINFMSG - Send Information Message

3) SNDCMPMSG - Send Complete Message

4) SNDSTSMSG - Send Status Message

5) RTVMSG - Retrieve Message6) EXCMSG - Execute Message


Standard Functions

Database 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


Standard Functions

• 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


Standard Functions

• 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 Record5) EDTRCD - Edit Record

6) EDTRCD2 - Edit Record 2 panels

7) EDTRCD3 - Edit Record 3 panels


Standard Functions

• 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


Standard Functions

• U F ti




• 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)


Standard Functions

User Functions




• User Functions

– The User Functions are

1) EXCINTFUN - Execute Internal Function

2) EXCEXTFUN - Execute External Function

3) EXCUSRPGM - Execute User Program4) EXCUSRSRC - Execute User Source

Building ApplicationsBasic Function Properties

• Function Name




– up to 25 characters long including embedded blanks & mustbe unique within a file

• Function Components

– Function options

• allow the user to customize function features likedatabase changes, display features, exit control,

commitment control, exception routines, generation

options & environment options


Basic Function Properties

Function Components




Function Parametersspecify 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 & ReportsAction Diagrams

specify the processing steps for function logic. This is a

combination of default COOL:2E supplied and optional

user defined processing logic



Function Components




Function class Parameters DeviceDesign

ActionDiagrams

Device Functions

Database Functions

User Functions

x

x

x

, x1

Messages

Function Fields

x

x

x

, x2 Built-In Functions x x



Default Device Function Processing




Default Device functions compile into working programswith default processing

Additional logic required for business processing

Building ApplicationsFunctions & Access Paths

Functions & Access paths




Functions operating on a file are always attached to it by anaccess path

Functions can access many files with access paths based on

several files

A generated program can be made up of several functions each

accessing a different access pathDefault panel/report formats are derived from the function’s

access path




Additional Processing

Automatic additional logic for functions

Linking Functions




Linking Functions

Automatically links certain functions together

External update functions like EDTFIL are automatically

linked to database function like CHGOBJ

Building Blocks Approach

Functions are building blocksBy linking functions together, required functionality can be

achieved


Defining Functions

Accessing Functions

Display All Functions panel




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-infunctions, messages etc.

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

Database Relations panel to access

DISPLAY ALL FUNCTIONS

Application area. : Source library: XXXXXXXX

? File Function Type GEN name


Defining Functions




Commodity Change Commodity CHGOBJ *N/ACommodity Create Commodity CRTOBJ *N/A

Commodity Delete Commodity DLTOBJ *N/A

Commodity 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

XXXXXXXX QPADEV000H 22/05/06 16:11:55

EDIT FUNCTIONS SYNSXT

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


Defining Functions




? Function Function type Access pathChange Commodity Change object Update index

Create Commodity Create object Update index

Delete Commodity Delete object Update index

Edit 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

*DSNR SYNSXT Op: XXXXXXXX QPADEV0012 11/02/06

EDIT DATABASE RELATIONS XXXXX

=> * Rel lvl: DFN

Building Applications Defining Functions




? Typ Object Relation Seq Typ Referenced objectFIL *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 File

FIL *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 dataFIL *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

+

Z(n)=Details F=Functions E(n)=Entries S(n)=Select F23=More optionsF3=Exit F5=Reload F6=Hide/Show F7=Fields F17=Services

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.

• Default versions of CRT, CHG and DLT database

functions are created for all REF & CPT files.


Database Functions




a a a

• RTVOBJ must be created if needed.

• Additional processing before and after database accessmay be specified in the action diagram.


Database Functions




Function Purpose Access PathCRTOBJCHGOBJDLTOBJ

Add a single recordUpdate a single recordDelete a single record

UPDUPDUPD

RTVOBJ Read a record or record(s) RTV, RSQ

• Array Processing


Database Functions




– Even though arrays are not implemented as database files, the4 database functions can be defined over an array and used.

– DLTOBJ with no parameter will clear an array

Building ApplicationsDevice 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

Building ApplicationsDevice Functions

• Interactive device design editor

– Allows defining of




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

• Device Standard Header device functions


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



• Single record device functions (contd...)


Device Functions




– 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

• Single record device functions (contd…)

– Edit Record (EDTRCD)


Device Functions




• 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 recorddetails 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.



• Multiple record device functions (contd…)


Device Functions




– 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.

• Single & multiple record device functions

– Display Transaction (DSPTRN)

d fi di l h d f


Device Functions




• defines a program to display the records from aselected pair of database files

• the pair must be connected by an Owned by orRefers to relation

– Edit Transaction (EDTTRN)

• defines a program to maintain the records from aselected pair of database files

• the pair must be connected by an Owned by or

Refers to relation.

• Printer device functions

– Print File (PRTFIL)


Device Functions




• defines a program to print records from a specified

access path.

– Print Object (PRTOBJ)

• defines a particular report fragment which will printthe records from a specified access path at any point

within a PRTFIL function

• can be embedded within other PRTOBJ functions.

• Standard Features of Device Functions

– Diagnostic messages

t t ’


Device Functions




• 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 ahelp program


– Print Key

i t k i bl d t ll l i t


Device Functions




• print key is enabled to allow panel prints

• print file is controlled by YPKYVNM 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


– Single Page Subfile load up

bfil l d d d d b i


Device Functions




• 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 forrecord lock by other users

– Overflow Handling

• report functions include handling of page overflow

• What are User Functions?

means of implementing additional user processing within


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 whichhas to be integrated to COOL:2E generated application

• Two types of User Functions

Free Form User functions


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

• Free-Form User Functions

Execute Internal Function (EXCINTFUN)


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 Coded User Functions

Execute User Program (EXCUSRPGM)


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 includedwithin the HLL source generated by COOL:2E for

an external function

• What are Message Functions?

means of defining messages of various types specifyingdiff fil f h if i


Message Functions




– means of defining messages of various types, specifyingdifferent message files for the message, specifying

substitution variables and changing message identifiers

– can be accessed by looking at functions of *MESSAGES file

• 6 Message Functions

– Send Error Message (SNDERRMSG)

• error message to be sent to a calling function


Message Functions




• error message to be sent to a calling function

• used for diagnostic messages arising from uservalidation

– Send Information Message (SNDINFMSG)

• information message be sent to the messagequeue of the calling program

– Send Completion Message (SNDCMPMSG)

• completion message to be sent to a calling

function

• 6 Message Functions

– Send Status Message (SNDSTSMSG)

• status message to be sent to a calling function


Message Functions




• 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 messagefile

– Execute Message (EXCMSG)

• specifies that a request message has to be executed

• What are Function Fields?

– Special types of fields that can be used in device designs


Function Fields




Special types of fields that can be used in device designsand action diagrams

– based on other fields

– processing can be specified for a function field

• Function field Usages

– Sum (SUM)

• contains sum of values of another field


Function Fields




• 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


– Maximum (MAX)

• contains the highest value of another field


Function Fields




contains the highest value of another field

• Input Parameter is the field whose maximum is to be calculated

• 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


– Derive (DRV)

• performs user-defined action to derive result


Function Fields




performs user defined action to derive result• action diagram is attached where processing can be specified

for deriving the result

• Multiple input Parameters can be specified

• One Resulting Parameter

– User (USR)

• reserved for work fields needed in device design or actiondiagram e.g. menu options, command string

• can be input-capable or output only

• What are Function Options?

– Function options control the features of functions

– Function Options for


Function Options




p• Database Changes

• Display Features

• Exit Control

• Commitment Control• Exception Routine

• Generation

• Environment

• Database Changes Function options

– determine if program allows add, change or delete capabilities or

a combination


Function Options




• 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



• Exit Control

– Determines execution characterstics of programs

– Closedown Program - whether program will terminate or


Function Options




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 program message queue of calling

program

• Commitment Control

– Determines commitment control regime for a program namelyMASTER SLAVE or NONE


Function Options




g p g yMASTER, SLAVE or NONE

– MASTER - program contains commit points and the program

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 commitment control

• Exception Routine

– Generate Exception Routine - specifies whether code forexception routine (*PSSR) should be generated


Function Options




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

• Generation Options

– Generate Help - specifies whether help is generatedScreen Text Constants


Function Options




– Screen Text Constants

L results in panel literals being hard coded in source

M results in panel literals to be stored in message file

D means model value to be used

• What are Function Parameters?

– Specifies the fields passed between functions

• Basic properties of function parameters


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 externalfunction

• Neither parameters

– No value passed or returned for a parameter

– Neither parameters are available for use as local variables withinthe function


Function Parameters




the function

• Default parameters of functions

Function default parameters usage

CHGOBJ all fields of update index I

CRTOBJ all fields of update index I

DLTOBJ key fields of update index I

RTVOBJ key fields of attached acc. Path I

SELRCD key fields of update index B

• Return Code Parameter

– Informs the calling program of the state under which calledprogram was exited


Function Parameters




p g

– All functions except EXCUSRPGM & EXCUSRSRC have

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

• Parameter Roles

– Specifies the use of parameter in function

– Following are the parameter roles


Function Parameters




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 withoutpassing a value

Restrictor Parameter - the parameter restricts the pupation of field by making it input only field

Positional Parameter - the parameter is used to position afunction to start reading records from a particular record

• Parameter Roles

Vary Parameter - the parameter can have a varying length.

Useful for interfacing with user-written functions• Defining Function Parameters


Function Parameters




• Defining Function Parameters

– in the Edit Functions panel, type P next to the selectedfunction

– 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

Op: XXXXXX QPADEV0012 11/02/06 7:52:36

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




Commodity Update index KEY

|

Values

FLD: One parameter per field

RCD: One parameter for all fields

KEY: One parameter for key fields only

SEL: Z-Details (field selection).

F3=Exit F5=Reload




Device Designs

• What are Device Designs?

– Specifies the layouts of fields and constants on the panels or

report designs for a function• Basic properties of Device Designs




• Basic properties of Device Designs

– Device Design Standard

• depends on the function type and associated standardheader/footer functions

– Device Design Format

• Formats are created from the fields of the based-on accesspath and their associated text


Device Designs

• Basic properties of Device Designs

– Device Design Field

• fields come from access path, function parameters andHeader/Footer




Header/Footer

• Editing Device Design

– in the Edit Functions panel, type S next to the selected functionto display the device design

– use function keys to edit the device design

• F1 moves the field 40 columns

• F3 exits the panel


Device Designs



• F4 move the field 40 columns to the right

• F5 edits device format details




• 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


Device Designs



• F13 fast exits the panel• F15 moves panel window to left margin




• 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


Device Designs



• F23 adds constant field to the device design




• F25 aligns all fields under the cursor position


Action Diagrams

• What are Action Diagrams?

– Action Diagrams record the basic constructs that make up a

procedure

th d l t li t f ti lik ll t




– the procedural steps encompass a list of actions like call 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


Action Diagrams

EDIT ACTION DIAGRAM Edit Y2MDLP25 Commodity

FIND=> 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=Prev block F5=User points F6=Cancel pending moves F23=More options

F7=Find F8=Bookmark F9=Parameters F24=More keys


Action Diagrams

User Points

COOL:2E/2 functions except EXCUSRSRC & EXCUSRPGM

have default action diagramsome portions of default action diagrams which depict essential




p g p

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 points for thefunction


Action Diagrams

EDIT ACTION DIAGRAM Edit Y2MDLP25 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 : <




. | .. : 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=Prev block F5=User points F6=Cancel pending moves F23=More options

F7=Find F8=Bookmark F9=Parameters F24=More keys


Action Diagrams

Action Diagram Constructs

Sequential - specify a list of actions or other constructs that are

executed in a sequential order. Denoted by brackets enclosingdotted lines




___

: ….

: ….

:___




Action Diagrams

Action Diagram Constructs

Iterative - represents repetitive logic. Denoted by REPEAT

WHILE and ENDWHILE statements




_ REPEAT WHILE

: ….

: ….

:_ ENDWHILE


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




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 likecondition etc.

System Contexts - instances of fields available from various

system values


Action Diagrams

Context

Function Contexts - instances of field available from function

attributes like parameterDatabase Contexts

DB1 fi ld i th fi t th l f t f th b d




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


Action Diagrams

Device Contexts

KEY - fields are from the key panel display in case of EDTRCD

or DSPRCD functionsDTL - 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


Action Diagrams

Device Contexts

CTL - fields are from the subfile control record format

RCD - fields are from the subfile record formatCUR - fields are from the current report format in PRTOBJ and




PRTFIL functions

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

and PRTFIL functions


Action Diagrams

Literal Contexts

CND - particular field condition is specified as a value

CON - constant context contains a literal value for non-statustype fields




System Contexts

JOB - contains system fields having execution time

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

PGM - contains system fields that control the execution like

*Program Mode, *Return Code


Action Diagrams

Function Contexts

PAR - parameter fields as field values

WRK - program variables not declared as any context as fieldvalues e.g. any field in data dictionary




Action Diagram Editor

allows modification of Action Diagram

line commands allow the modification


Action Diagrams


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




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 lineFF 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


Action Diagrams


Line Commands

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

I= Insert *MOVE built-in function

I=A Insert and Prompt *MOVE ALL built in function




p

I=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 conditionII Insert Iteration

IIF Insert and Prompt Iteration

IM Insert Message function

IMF Insert and Prompt Message function

IO Insert *OTHERWISE condition

IOF Insert and prompt *OTHERWISE condition



Generating Applications

COOL:2E Generator

Generation

Data Model is translated into either DDS sources or SQL

collectionsAccess Paths into Physical and Logical files

COOL:2E functions are translated into HLL programs -




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 filesCompilation of generated code is automatically submitted

Generating Applications

COOL:2E Generator

Generating Code

from the Services Menu, take option for displaying all access

paths or all functionsTake option J(batch) or G(online) for the item that has to be

generated




generated

COOL:2E/1E Utilities

Menus

COOL:2E/1E Menus

dynamic menu system

removes the need of individual OS/400 display file for eachapplication menu

Menus stored in special form and displayed using COOL:2E




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 withCOOL:2E/1E


Menus

COOL:2E/1E Menus

YCRTDSNF command can create a new design file

YADDDSNFM adds new member to design file2 types of COOL:2E menus

Single option




Single option

Multiple option


Menus




Thank you

COOL2E TRG ppt1

Documents

Transcript of COOL2E TRG ppt1