CoolGen - Syntax

Satyam Computer Services Limited Satyam Computer Services Limited 11

COOL:Gen Syntax

• The statements in Cool:Gen can be broadly divided into the following categories:

• Sequential Actions• Conditional Actions• Repeated Actions• Control Actions• Entity Occurrence Actions• Pairing Actions


Sequential Actions

SET Statement

SET is an assignment action used to assign values to attributeviews.

The format of SET action statement is:

SET view-1 attribute-view-1 [ROUNDED] TO expression [SUBSCRIPT] [NOT ROUNDED] [LAST of group-view]


MOVE Statement

MOVE assigns the values of all attribute views for an entityviews at once. A MOVE is not required for each attribute valuein the view.

The format of MOVE action statement is:

MOVE view-1 TO view-2

view-1 and view-2 should be of the same entity type/work view.

Sequential Actions


Sequential Actions

NOTE Statement

Note allows you to add your own annotations and commentsanywhere in the action diagram.


Conditional Actions

IF/ELSEIF/ELSE Statement

IF specifies the condition under which process actions take place.Simple mutually exclusive conditions can be added to the IF condition. +-> IF condition-1 (AND/OR condition-2) | process statements.... | .......... +-ELSEIF | process statements.... | .......... +-ELSE | process statements.... +--


Conditional Actions

CASE OF/CASE Statement

CASE OF conditional action specifies actions that depend on thevalue of one of the items listed in the CASE statements.

+->CASE OF expression-1 +->CASE constant-1 | process statements.... +->CASE constant-1 | process statements.... +->OTHERWISE | process statements.... +--


Repeated Actions

FOR Statement

The FOR conditions causes an action or group of actions to be repeated according to the criteria you specify for a local numericattribute view or an explicitly indexed repeating group view.

Format 1 +->FOR local-view-1 FROM num-1 TO num-2 BY num-3 | process statements.... +--

Format 2 +->FOR SUBSCRIPT OF group-view-1 FROM num-1 TO | LAST OF group-view-1 | process statements.... +--


Repeated Actions

FOR EACH Statement

The FOR EACH repeating action repeats the action group for eachoccurrence of an implicitly indexed repeating group view

+->FOR EACH group-view-1 | TARGETING group-view-2 FROM THE BEGINNING | UNTIL FULL | process statements.... +--

TARGETING clause allows you to identify the repeating export or local group view to be populated.


Repeated Actions

WHILE Statement

Repeats an action or group of actions as long as the condition is true.

+->WHILE condition-1 | TARGETING group-view-2 FROM THE BEGINNING | UNTIL FULL | process statements.... +--

Can contain more than one TARGETING statements.

The test for the condition takes place first. If the condition is not met thenthere are no iterations.


Control Actions

EXIT STATE IS Statement

EXIT STATE IS sets the value of the special attribute, exit state.

EXIT STATE IS exit-state-value

• Can hold only one value at a time. •An ESCAPE statement usually follows the EXIT STATE statement.

• An EXIT STATE causes the transfer of control from one procedure step to another. A dialog flow takes place on the existence of one or more exit states.


EXIT STATE IS Statement - Example

EXIT STATE IS customer_not_found

Control Actions


Control Actions

USE Statement

USE statement references the logic in common action blocks.

The logic is common in that it can also be used in other processes, procedures, and action blocks(including external action blocks).

Format process statements....

USE action-block-1 WHICH IMPORTS:import-1,import-2... WHICH EXPORTS:export-1,export-2...

process statements....


Control Actions

USE Statement

• Match the views (of called and calling action block).• Matching is possible only between similar(entity/work) views. • After execution, the control returns to the statement after the USE statement.


Entity Occurrence Actions

CREATE Statement

• Stores information about entities. • Entity should be defined in the entity action view of the action diagram.

• SET statement to assign value to the attributed.

• If any attribute is not assigned value using SET statement then the attribute takes the default value defined.

• ASSOCIATE statement used to set the associations.


CREATE Statement

Format

+-> CREATE entity-view-1 | [SET attribute-view-1 TO expression ] | [ASSOCIATE WITH entity-view-2 WHICH | relationship IT] +-> WHEN SUCCESSFUL | processing statements... +-> WHEN ALREADY EXISTS | processing statements... +-> WHEN permitted value violation | processing statements... +--



READ Statement

• Retrieves a single occurrence of one or more entity types based on the selection criteria specified. • Format

+-> READ entity-view-1(,entity-view-2...) | [WHERE selection-condition] +-> WHEN SUCCESSFUL | processing statements... +-> WHEN NOT FOUND | processing statements... +--



READ Statement

• Example - 3

+-> READ loan_transaction | WHERE DESIRED loan_transaction contains SOME | loan | AND THAT loan num = import loan num | ........ +--



READ EACH Statement

• Retrieves multiple occurrence of one or more entity types based on the selection criteria specified.• One iteration occurs for each entity occurrence satisfying the selection criteria specified. • Format

+-> READ EACH entity-view-1(,entity-view-2...) | [TARGETING group-view-1 FROM THE BEGINNING | UNTIL FULL] | [WHERE selection-condition] | processing statements... +--



READ EACH Statement

• Example

+-> READ EACH loan_transaction | TARGETING export_group FROM THE BEGINNING | UNTIL FULL | WHERE DESIRED loan_transaction contains | CURRENT loan | ........ +--

• For each iteration, the subscript of the group view will be incremented by 1.




READ EACH Statement - Options

• Distinct• Always generate cursor with Distinct.• Never generate cursor with Distinct.• Use default.

• Select clause isolation level• Repeatable• Cursor Stable• Uncommitted/Browse• Default


READ EACH Statement - Options

• Optimize for N rows.• Do not generate optimize clause• Use TARGETING value, when present• Use the value - 9999.




UPDATE Statement

• Can change the attribute value of an entity occurrence.

• Can update the relationships.

• Should be preceded by a READ/CREATE statement to identify the row to be updated.



DELETE Statement

• Removes an occurrence of an entity.• Should be preceded by a CREATE/READ statement to identify the row to be deleted.• Cascade deletion. (Cool:GEN level or Database level).

Format +-> READ entity-view-1 | WHERE [condition-1] +-> WHEN successful | DELETE entity-view-1 +-> WHEN not found | processing statements... +--



DELETE Statement

• Example

+-> READ loan | WHERE DESIRED loan loan_num = import loan | loan_num +-> WHEN SUCCESSFUL | DELETE loan +-> WHEN NOT FOUND | processing statements... +--


Pairing Actions

ASSOCIATE Statement

• Breaks a specific pairing along a specific relationship.• ASSOCIATE has to be used for mandatory relationships.• ASSOCIATE may be used for optional relationships.• Used with CREATE or UPDATE statement or as standalone statement.

• Format 1 - with CREATE/UPDATE

ASSOCIATE WITH entity-view-1 WHICH relation-1 IT • Format 2 - as stand alone statement ASSOCIATE entity-view-1 WITH entity-view-2 WHICH relation-1 IT


ASSOCIATE Statement

• Example 1

+-> CREATE loan_transaction | SET loan_transaction effective_date TO | 20020101 | SET loan_transaction updated_date TO ‘SATYAM’ | ASSOCIATE WITH loan WHICH identifies IT +--• Example 2

+->ASSOCIATE loan_transaction | WITH loan WHICH identifies IT +--

Pairing Actions


DISASSOCIATE Statement

• Establishes a pairing along a relationship between two entities.• DISASSOCIATE can be used only for optional relationships.• Used with UPDATE statement.

• Format 1 - With Update statement

DISASSOCIATE FROM entity-view-1 WHICH relation-1 IT

• Format 2 - With Update statement

DISASSOCIATE entity-view-1FROM entity-view-2 WHICH relation-1 IT

Pairing Actions


DISASSOCIATE Statement

• Example 1

+-> UPDATE loan_transaction | SET loan_transaction effective_date TO | 20020101 | SET loan_transaction updated_date TO ‘SATYAM’ | DISASSOCIATE FROM loan WHICH identifies IT +--• Example 2

+->DISASSOCIATE loan_transaction | FROM loan WHICH identifies IT +--

Pairing Actions


TRANSFER Statement

• Transfers the relationship between specific entity occurrences.• TRANSFER can be used only for relationships defined as transferable.• Used with CREATE/UPDATE statement or stand alone statement.

• Format 1 - With Create/Update statement

TRANSFER entity-view-1 WHICH relation-1 IT TO entity-view-2 WHICH relation-2 IT

• Format 2 - stand alone statement

TRANSFER FROM entity-view-1 WHICH relation-1 IT TO entity-view-2 WHICH relation-2 IT

Pairing Actions


Miscellaneous Actions

SUMMARIZE Statement

• Allows the aggregate functions COUNT, MAX, MIN, AVERAGE and SUM to be used.

• Similar to READ except that one or more PLACING clauses are required.

• PLACING clause assigns the value retrieved by the aggregate function to modifiable fields.

• One or more PLACING clauses can be used for a single SUMMARIZE.

• Can contain a WHERE clause to add the selection criteria.


SUMMARIZE Statement

• Format

+-> SUMMARIZE entity-view-1, entity-view-2,...| PLACING aggregate function-1 INTO attribute-1| PLACING aggregate function-2 INTO attribute-2| PLACING...+--

• Example

+-> SUMMARIZE loan| PLACING count(OCCURENCES) INTO local | ief_supplied count+--



SUMMARIZE EACH GROUP Statement

• Allows the aggregate functions COUNT, MAX, MIN, AVERAGE and SUM to be used.

• Divides into subgroups based on common attribute values.

• Similar to GROUP BY clause in SQL.

• WITH THE SAME clause used with SUMMARIZE EACH to designate the common attributes

• TARGETING clause can be used with SUMMARIZE EACH.

• Can contain a WHERE clause to add the selection criteria.




MAKE Statement

• Sets the video properties of screen fields from an action diagram.

• Can be used only in online procedures.

• Is active only in procedure step, will not be active in action diagrams.

• Example

MAKE export customer name Unprotected High Intensity Containing Cursor



COMMAND IS Statement

• Sets the value of the special attribute, command.

• Can hold only one value at a time.

• Used mainly to control flow within the procedure step.

• Format

COMMAND IS command_value

• Example

COMMAND IS ADD


Interface

Screen Design

• Visual Layout of the views imported to and exported from the procedure step.

• Screen can contain the following components.

• Fields.

• Literals.

• Prompts.

• Special Fields

CoolGen - Syntax

Documents

Transcript of CoolGen - Syntax