INGENIUM Architecture II

Topics to be covered

P-steps
S-steps
MIR
HTML
Flow File
Standard INGENIUM Online Programs
Filter Programs

Topics to be covered
Contd..

Online Process Drivers

Batch Process Drivers
Function Drivers
Sub Function Drivers
Insurance Drivers
Common Insurance Worker
Specific Insurance Worker
Utility Programs

P and S Steps

Step1: S-Step
Get Client Number
from User
Step2: P-Step
Retrieve Client
Information from
database
Step3: S-Step
Display Client
Information

P and S Steps

The input data for the P-Step example above is the

key value of the business function: the client number.
The output of the P- step is the values for all the
fields of data contained in the client record.
The input to the client name S-Step is simply the
client name. The step's output is again the client
name, which may have been updated by the user

P and S Steps

An S-step talks to the Screen.

Remember S for Screen.
A P-step talks to the Process Driver or
the back end.
A Flow file controls the flow of the Psteps and S-steps.

P - Steps
Represents an interaction with INGENIUMs insurance
logic and contains a definition of the fields that are used
by an INGENIUM Business Function.
Step Declarations

P-STEP step id
{
Attributes
{
Mir Name = mirname ;
<attribute list>
}
<Step statements> }

Client Update
P-STEP BF1222-P
{
ATTRIBUTES
{
BusinessFunctionId = "1222";
BusinessFunctionName = "Client Record Update";
BusinessFunctionType = "Update";
MirName = "NCWM0130";
}
OUT LSIR-RETURN-CD;
OUT MIR-RETRN-CD;
INOUT MIR-AGT-ID
{
Length = "6";
DBTableName = "TAG";
SType = "Text";
Label = "Agent ID";
}

Client Update
OUT MIR-UW-USER-2-ID
{
Length = "8";
DBTableName = "TCLI";
SType = "Text";
Label = "2nd Underwriter Initials";
}
IN MIR-CLI-ID
{
Key;
Length = "10";
DBTableName = "TCLI";
DefaultSession = "MIR-CLI-ID";
SType = "Text";
Label = "Client Number";
}

S-Step
Interacts with the End User

Define the set of data that is presented to, and/or returned from, the
user.
Step Declarations:
S-STEP Step id
{
Attributes
{
MirName = mirname;
< attribute list >
}
<Step Statements> }

Client Update : Input S-Step

S-STEP BF1222-I
{
ATTRIBUTES
{
BusinessFunctionType = "Update";
Type = "Input";
FocusField = "MIR-CLI-INDV-TITL-TXT";
FocusFrame = "ContentFrame";
}
IN Title;
IN TitleBar;
IN TitleBarSize;
IN ButtonBar;
OUT action
{
SType = "Hidden";
}

Client Update : Input S-Step

INOUT MIR-CLI-INDV-GIV-NM-T[2]
{
Length = "25";
FieldGroup = "Table3";
SType = "Text";
Label = "First Name";
Index = "1";
}
IN MIR-DV-CLI-INDV-TITL-TXT-T[6]
{
DisplayOnly;
Length = "15";
FieldGroup = "Table1";
CodeSource = "EDIT";
CodeType = "TITLE";
SType = "Text";
Label = "Title (Previous)";
Index = "1";
}

Generating S- Steps

UIGEN generates two S-Step configuration files from

each P-Step used as input.
Users can use the S-Steps, together with the source
P-Step to construct a basic S-P-S process flow for a
Business Function.
One S-Step collects data from the user using an
HTML page and the other S-Step displays the
processing results to the user using another HTML
page.

Generating S- Steps
Contd..

UIGEN is a software tool used to generate HTML pages from SStep configuration files as well as S-Step configuration files from
P-Step configuration files
Run the "UIGENS-Steps.bat" batch file. Use the following
syntax:
UIGENS-Steps unit BFnnnn
UIGEN displays any errors online and logs them in the error log
file. This file is named uigen.txt and is located in the logs folder
of the PathFinder runtime directory

MIR

Message Interface Record carries the information from the

presentation layer to the back end.

Two Types:Presentation Layer MIR copybook and Server part

MIR copybook.

In the presentation layer MIR copybook, each business process

has a copybook that defines the layout of the MIR.This information
would be obtained from the user and passed on to the Server
through CICS transaction gateway.

In the Server layer MIR copybook, each process driver has a

copybook that defines the layout of the MIR, which receives the
information through the INGENIUM Control program XSOM0010.

MIR : NCWM0130
01 MIR-PARM-AREA.
05 MIR-CONTROL-AREA.
10 MIR-BUS-FCN-ID
PIC X(004).
10 MIR-LENGTH
PIC X(005).
10 MIR-RETRN-CD
PIC X(002).
88 MIR-RETRN-OK
VALUE '00'.
88 MIR-RETRN-EDIT-ERROR
VALUE '01'.
88 MIR-RETRN-RQST-FAILED VALUE '02'.
88 MIR-RETRN-TS-MISMATCH VALUE '05'.
88 MIR-RETRN-INVALD-RQST VALUE '99'.
05 MIR-INPUT-AREA.
10 FILLER
PIC X(01).
05 MIR-IO-AREA.
10 MIR-PRCES-INFO.
15 MIR-DV-UPDT-NM-IND
PIC X(01).
15 MIR-DV-UPDT-ADDR-IND
PIC X(01).
10 MIR-CLI-INFO.
15 MIR-CLI-ID
PIC X(10). .
05 MIR-OUTPUT-AREA.
10 FILLER
PIC X(01).

HTML

HTML pages are the front end

screens used by the end user to
enter data
UIGEN is used to generate HTML
pages using S-Steps.

Steps to generate HTML

Pages

Check out from PVCS the HTML page corresponding

to an S-Step configuration file. For example, if users
have changed BF0090-I.s, they will have to check out
BF0090-I.htm
Make sure the S-Step configuration file is valid
Run the "UIGENHtml.bat" batch file. Use the
following syntax:UIGENHtml unit BFnnnn-x
where nnnn is the Business Function number filled
with zeroes to the left and x is one of O or I.
For example:
UIGENHtml unit BF0090-I

Contd..

UIGEN will display any errors online and in the errors

log file, which is typically named uigen.txt and located
in the logs folder of the PathFinder runtime directory
UIGEN will display any errors online and in the errors
log file, which is typically named uigen.txt and located
in the logs folder of the PathFinder runtime directory

Flow File

Flow file manages the flow of the Processes.

A combination of P-Steps and S-Steps are
triggered in an order.

Client Update
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE

"BF1220-P.p";
"BF1220-I.s";
"BF9302-I.s";
"BF1220-O.s";
"BF9302-P.p";
"GenUpdate.f";

PROCESS BF1222Update
{
STEP Main
{
USES PROCESS "GenUpdate";
ATTRIBUTES
{
GetMessages = "NO";
}

Client Update
STRINGTABLE.IDS_TITLE_BF1222Update -> Title;
"BF1220-I" -> InputS;
"BF1220-P" -> RetrieveP;
"BF9302-I" -> EditS;
"BF9302-P" -> UpdateP;
"BF1220-O" -> OutputS;
}
IF DisplayInput == "FALSE"
EXIT;
IF action == "ACTION_BACK"
EXIT;
BRANCH Main;
}

Process Drivers

Executable module associated with a

transaction.
Does not contain Insurance Logic
Online Process Drivers and Batch Process
Drivers
Validates the format of the data entered at
the top of the screen.
Processes the tasks directly that need to
be done or indirectly by calling other
modules.

Process Drivers Contd..

Acts as the guide for the process

requested by the user and executes
simple logic control.
Reads and updates the policy and the
coverage, if applicable.
Verify whether the user has the authority
to execute the requested function.
Can only be called by the Server Control
Program.

Function Drivers

Accepts an input message and determines

or controls the correct sequence of tasks
necessary to process the request.
In case of Complex process passes control
to the sub modules.
Performs necessary validations required to
process the function.
Manages the linking logic for the function.
Performs I/O Tasks.

Sub- Function Drivers

Accepts an Input message and

determines or controls the Correct
Sequence of Insurance Tasks.
Manages the linking logic for its task by
calling at least one Insurance driver.
Performs I/O Tasks.

Insurance Drivers

Executable Module that does a complex

Insurance task that is not specific to a
product.
Manages the linking logic for its task by
calling at least one common insurance
worker.
Performs I/O Tasks.

Common Insurance
Workers

Executable module that does a basic

insurance task that is not specific to a
product.
Controls processing that are common to
many Insurance Products.
Performs I/O Tasks.

Specific Insurance Workers

Executable Module that does a

basic Insurance task that is specific
to one product or country.

Utilities

Executable Module that does a basic

task not related to Insurance
Processing.
Three Types of utilities are : TPI, NonTPI and Table Access
TPI : Date Validation, Character Field
Compressing, Numeric Alignment,
Uppercase Conversion, User ID
Validation

Utilities Contd...

Non-TPI: Address Printing Format,

Height and Weight Conversion and
Phonetic Coding
Table Access: Obtaining Information on
the Policy Owner, Coverage for the
Insured and Rate Look Up on RH/RL,UV,
and PR tables.

Examples
Process Drivers

CSOMXXXX

Function Drivers

CSLFXXXX

Sub-Function Drivers

CSLSXXXX

Insurance Drivers

CSRIXXXX

Common Insurance
Workers

CSLCXXXX

Specific Insurance Workers

CSLVXXXX

Utilities

CSDUXXXX

STD INGENIUM Online

Programs

The data entered by the end user is received

through MIR Copybooks and then passed
through the COMMAREA. This data is then
received from COMMAREA and passed through
the INGENIUM Online Control Program
XSOM0010.