Infosys

Finacle 10.x 24x7 EOD BOD

May 2016

INFOSYS LIMITED
Bangalore

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211

©2014 Infosys Limited, India 1

COPYRIGHT NOTICE

© 2014 Infosys Limited, Bangalore, India. All rights reserved. Infosys believes the information in this
document is accurate as of its publication date; such information is subject to change without notice. Infosys
acknowledges the proprietary rights of other companies to the trademarks, product names and such other
intellectual property rights mentioned in this document. Except as expressly permitted, neither this document
nor any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any
means, electronic, mechanical, printing, photocopying, recording or otherwise, without the prior permission of
Infosys Limited and/or any named intellectual property rights holders under this document.

Infosys Limited
Hosur Road
Electronic City, 3rd Cross
Bangalore 560 100
India.
Telephone: (91) (80)28520 261-270
Fax: (91) (80) 8520 362
Website: http://www.infosys.com

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211

©2013 Infosys Limited, India 2

Document Details
Author(s) : Arpan Roy

Date written : 26 May 2016

Project Details
· Project(s) involved : China Banking Corporation, Philippines
· H/W Platform : IBM AIX
· S/W Environment : Finacle 10x
· Application Type : Package Application
· Project Type : Package Implementation

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211

©2014 Infosys Limited, India 3

Document Details
Target readers
This document will be helpful for teams engaged in Development, Maintenance, Support, Testing and
Implementation of Finacle.

Keywords
Finacle EOD BOD, Sol Date Change, Bank Date Change, Batch Job Configuration

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211

©2013 Infosys Limited, India 4

Agenda
• Introduction
• Steps in Finacle 10.x 24x7 EOD BOD
SOL Level Operations
Bank Level Operations
• Checking of EOD/BOD status in each stage
• Set up For EOD/BOD
• Batch Job Maintenance & Other Configurations
• Sample Pre-EOD checklist
• Useful Menu Option & Table List

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Introduction

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Introduction
• The End of day/Beginning of Day operations (EOD/BOD) are performed in
Finacle to mark the logical end-of-day for a branch level operations as well as
the bank and mark the beginning of the next working day.

• Finacle ensures that the bank can function on a 24 X 7 X 365 basis from a
branch as well as delivery channels, and support all application-related
functionalities. Finacle solution supports transaction processing round the
clock. Delivery channels including branches can access Finacle services even
when the EOD is running.

• For the branches, the business date is the business date of the branch from
where the transaction is originating whereas as for channels, the business
date is the business date of the data center.
Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Key Challenges in Finacle 7.x EOD BOD
• A single business date for all SOLs of the Bank.
• End of Day operations for all SOLs should be completed before the End of Day
for the Bank (and business date changes) is initiated.
• Only one user (the EOD Operator) is allowed to login during CEOD and CBOD.
• Business date change process is tightly linked to user log-in, specific batch
jobs and transaction processing capabilities.
• EOD BOD Operations are to be manually initiated. Such operations cannot be
triggered using external schedulers.
• Certain functional batch jobs are tightly coupled with the EOD Stages ( e.g.
FFD is opened as part of ABH, SI Carry Forward Batch Job is executed as part
of CSOLOP).

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Finacle 10.x 24x7 EOD BOD
Key Benefits with 24x7 EOD BOD Model are as below.
• Every SOL has its own business date, different from the business
date of the Bank. Each SOL can operate on its own independent
business date.
• User Operations can continue during the EOD BOD window, thereby
permitting 24x7 availability.
• EOD BOD Operations can be initiated through external schedulers.
• Batch Jobs can be configured at any stage of the EOD BOD based on
business requirements.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Steps in 10x EOD/BOD

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Finacle 10.x 24x7 EOD BOD
SOL 1 SOL 1
SOL 1 Date
Closure Closure of
Change
Operations Last Day

SOL 2 SOL 2
SOL 2 Date
Closure Closure of
Change
Operations Last Day

SOL 3 SOL 3
SOL 3 Date
Closure Closure of
Change
Operations Last Day

Bank Bank
Bank Date
Closure Closure of
Change
Operations Last Day
Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL Date Change Operations
Initiate SOL SOL SOL SOL SOL
Change of Change Of Change Of Closure Closure Of
Day Date Date Operations Last Day

Pre Date Post Date

Change Change

HISCOD HSCOD HSOLCOP HSCOLD

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Bank Date Change Operations

Bank Change Bank Change Bank Closure Bank Closure

Of Date Of Date Operations Of Last Day

Pre Date Post Date

Change Change

HBKOD HBKCOP HBKOLD

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
EOD/BOD Process
• There are 8 Steps (6 Mandatory and 2 Optional steps) in Finacle 10x for completion of
EOD/BOD Process.
They are as below:-

Sl. No Menu Option Menu Description Note

0 HISCOD Initiate Sol change operating Date Optional Step
1 HSCOD Sol Change of Date Mandatory
2 HBKOD Bank Change of Date Mandatory
3 HSOLCOP Sol Closure Operations Mandatory
4 HBKCOP Bank Closure Operations Mandatory
5 HSCOLD Sol Closure of Last Day Mandatory
6 HBKOLD Bank Closure of Last Day Mandatory
7 HBJE Batch Job Executioner Optional Step

The order of execution of above stages can be modified as per the requirements of the bank.
The different types of orders/sequences can be:-
1. HSCOD -> HSOLCOP -> HSCOLD -> HBKOD -> HBKCOP -> HBKOLD
2. HSCOD ->HBKOD -> HSOLCOP -> HSCOLD -> HBKCOP -> HBKOLD
3. HSCOD -> HBKOD -> HSOLCOP -> HBKCOP -> HSCOLD -> HBKOLD
Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Initiate SOL Date Change (HISCOD)
•Initiate SOL Change Operating Date.
•Send an alert to the users indicating the commencement of date
HISCOD change operations.
•This menu will not actually start the Date Change Operations but will
just alert the users about the start of operations in near future.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL Change of Date (HSCOD)
• Pre Date Change Batch Jobs (Job Group – PRSCD)

• Determine the Next Working Date

• Initiate ISO Reconciliation
• Execute Validations configured in HSVAM for SOL Date
Change

HSCOD
• Sack other Online Users Logged in the SOL
• Change SOL BOD Date

• Create User Entered Transaction Numbering Sequence

• Change SOL BOD Date of EOD Operator

• Post Date Change Batch Jobs (Job Group – PSSCD)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL Change of Date (HSCOD)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Bank Change of Date (HBKOD)

• Execute Pre Date Change Batch Jobs (Job Group – PRDCD)

• Determine the Next Working Date

• Initiate ISO Reconciliation
HBKOD
• Execute Validations configured in HSVAM for DC Date Change
• Change DC BOD Date

• Execute Post Date Change Batch Jobs (Job Group – PSDCD)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Bank Change of Date (HBKOD)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL Closure Operations (HSOLCOP)

HSOLCOP • Execute SOL Closure Operation Batch Jobs (Job Group –

SLCOP)

• Execution of batch jobs as on a previous date, after date change, allows the
batch job execution to be disassociated from the date change event.
• The most essential batch jobs can be executed before date change.
• Immediately after date change, business operations on the new date can be
started.
• The remaining batch jobs can later be executed as on a previous day as part of
HSOLCOP.
• These jobs are executed as of the previous working date because by this time,
date is already changed to new working date.
• Jobs configured to run in HSOLCOP should be configured in HPDBJM to enable
“Run as on previous day”. Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL Closure Operations (HSOLCOP)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Bank Closure Operations (HBKCOP)
• Login as on Previous Date (only in the current context)
• Execute Bank Closure Operation Batch Jobs (Job Group –
HBKCOP
BKCOP)
• Revert Login to the Current Date

• Execution of batch jobs as on a previous date, after date change, allows

the batch job execution to be disassociated from the date change event.
• The most essential batch jobs can be executed before date change
• Immediately after date change, business operations on the new date can
be started
• The remaining batch jobs can later be executed as on a previous day as
part of HBKCOP
• HBKCOP process can be bypassed by setting up the PSDC1 batch job with
the parameters as D 7 Y ALL
Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Bank Closure Operations (HBKCOP)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL Closure for Last Day (HSCOLD)
• Execute Validations configured in HSVAM for SOL Closure

• Check for Online and Batch Logins as on Previous Date

• Close the SOL

HSCOLD • Execute SOL Closure of Last Day Batch Jobs (Job Group –
SCOLD)

• Please note that, unlike HSCOD and HSOLCOP, in HSCOLD,

first sol status and closure status changes and then jobs
configured in that stage starts to run.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL Closure for Last Day (HSCOLD)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Bank Closure for Last Day (HBKOLD)

• Validations of DC Status

• Update BOD Date, DC BOD Date and Operating Date of

HBKOLD Channel User Logins.

• Initiate ISO Reconciliation

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Bank Closure for Last Day (HBKOLD)
• Execute Validations configured in HSVAM for Bank Closure
• Check for logins as on previous date
• Update DC Stat Code to X

• Execute EAB and GST Build

• DTD to HTD Movement
HBKOLD • Drop DTD Sequence as on previous date
• Update DC Stat Code to Y (DC Closure Done)

• Execute Bank Closure of Last Day Batch Jobs (Job Group –

BKOLD )
•Please note that, unlike HBKOD and HBKCOP, in HBOKLD, first bank
status and closure status changes and then jobs configured in that
stage starts to run.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Bank Closure for Last Day (HBKOLD)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
HBJE (Batch Job Executioner)
• This is an optional stage.
• This stage runs the jobs where Job_Group is configured as
“RPT”.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
CHECKING OF EOD/BOD STATUS
IN DIFFERENT STAGES

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
 SOL LEVEL STATUS DURING VARIOUS STAGES OF EOD/BOD
In Database Level, Flags and Fields will be as below during various stages of EOD/BOD :-

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL LEVEL STATUS DURING VARIOUS STAGES OF EOD/BOD
In Front End, In HSSI Menu Option, Flags and Fields will be as below during various stages of EOD/BOD :-

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
BANK LEVEL STATUS DURING VARIOUS STAGES OF EOD/BOD
In Database Level, Flags and Fields will be as below during various stages of EOD/BOD :-

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
BANK LEVEL STATUS DURING VARIOUS STAGES OF EOD/BOD
In Front End, In HBSI Menu Option, Flags and Fields will be as below during various stages of EOD/BOD :-

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SET UP FOR EOD/BOD

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Previous Day Batch Job Maintenance (HPDBJM)

• System Batch Job BSOLSTATUPD/1 should be mandatorily configured

in this menu
• All other user defined batch jobs which are executed in menus
HSOLCOP and HBKCOP (as on previous day) should be defined in this
menu.
• Note :- Underlying batch job should be evaluated for working as on a
previous day.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Job Event Maintenance (HJEM)
• Closure Event IDs are pre defined in the system, indicating the various
stages of End of Day Operations.

• A Job Group (RRCDM Code) is tagged to each Closure Event ID.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Job Event Maintenance (HJEM)
Menu Event Closure Event Job Group
ID
HSCOD SOL Pre Date Change Event PRESCOD PRSCD
SOL Post Date Change Event POSTSCOD PSSCD
HSOLCOP SOL Closure Operation SOLCOP SLCOP
HSCOLD SOL Closure Of Last Day POSTSCOLD SCOLD
HBKOD Bank Pre Date Change Event PREBKOD PRBKD
Bank Post Date Change Event POSTBKOD PSBKD
HBKCOP Bank Closure Operation BKCOP BKCOP
HBKOLD Bank Closure Of Last Day POSTBKOLD BKOLD

Closure Event
EOD Menu Job Group Batch Job
ID
Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
System Controlling Batch Jobs
Pre SOL Date Post SOL Date SOL Closure SOL Closure
Change Change Operations of Last Day
(PRSCD) (PSSCD) (SLCOP) (SCOLD)

Status
Other Other
PRSL1 Change
Batch Jobs Batch Jobs
(Implicit)

Other
PSSL1 PSSL1 Batch Jobs
Batch Jobs

PRSL2

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
System Controlling Batch Jobs
Pre Bank Date Post Bank Bank Closure Bank Closure
Change Date Change Operations of Last Day
(PRDCD) (PSDCD) (DCCOP) (DCOLD)

Status
Other Other
PRDC1 Change
Batch Jobs Batch Jobs
(Implicit)

Other
PSDC1 DCCP1 Batch Jobs
Batch Jobs

PRDC2

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
System Controlling Batch Jobs

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
System Controlling Batch Jobs
Job Next
Job Job Job Parameter Job
Job ID Job Description Holiday Execution
Group Priority Area Frequency
Status Date

PRSL1 DB STAT CODE FROM Y TO I PRSCD 1 S 1 N <CS> D E 9-Feb-2014

PRSL2 DB STAT CODE FROM I TO P PRSCD 999 S 2 N <CS> D E 9-Feb-2014

PSSL1 DB STAT CODE FROM M TO N PSSCD 999 S 3 N <CS> D E 10-Feb-2014

SLCP1 DB STAT CODE FROM N TO B SLCOP 999 S 4 N <CS> D E 9-Feb-2014

PRDC1 DC STAT CODE FROM Y TO I PRBKD 1 D 5 N ALL D S 9-Feb-2014

PRDC2 DC STAT CODE FROM I TO P PRBKD 999 D 6 N ALL D S 9-Feb-2014

PSDC1 DC STAT CODE FROM M TO N PSBKD 999 D 7 N ALL D S 10-Feb-2014

DCCP1 DC STAT CODE FROM N TO B BKCOP 999 D 8 N ALL D S 9-Feb-2014

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Maintain SOL Validations (HSVAM)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Maintain SOL Validations (HSVAM)
• Business and System validations, required to be executed prior to certain
important EOD stages, can be configured in menu HSVAM.

• Examples :-
• All transactions should be posted before SOL Change of Date
• All table spaces should have adequate free space before DC Change of
Date
• SOL Caution Holidays for the next working day should assessed before
SOL Change of Date

• Validations can be of three types :- System, Bank Defined and Custom.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Maintain SOL Validations (HSVAM) (HSVALRPT)
• Validations can be configured for four execution modes :- SOL Date Change,
SOL Closure, Bank Date Change, Bank Closure

• Validations maintained in HSVAM are executed implicitly by the system during

the mentioned execution modes.

• Validations can be either Blocking or Non-Blocking. Blocking Validations will

be identified as an Error by the system for completion of the particular EOD
stage. All business events resulting in a Blocking Validation should be
completed suitably prior to the completion of the respective EOD stage.

• Validations can be manually executed by the user using report menu

HSVALRPT.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Maintain SOL Validations (HSVAM) (HSVALRPT)
• For a Blocking validation, in case of failure the system will not allow the EOD-
BOD process to pass that particular stage.
The User/admin has to find out the cause of the failure and resolve it so that during re-
execution of the event the validation will not fail.
• Some properties of validations:-
 System and Bank Defined validations are by default added into core.
 System validations are always BLOCKING. Only priority can be modified.
 Bank defined validations are by default blocking. But both priority and blocking flag
can be modified.
 Custom validation can be set by user in which all the fields are modifiable.
Custom validations require a script to be entered which is mandatory.
 Each validation is associated by a VAL_ID, the corresponding entry of which is stored in
SMVT table.
 When a validation is executed during any stage of EOD-BOD operations, the details of its
success/failure is recorded in a history table – SVHT. In case a validation gets executed,
the corresponding success/ failure entry will go in SVHT table.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Batch Job Maintenance (HBJSTM)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Batch Job Maintenance (HBJSTM)

Invoking Process Holiday Frequency

•SOL Level •Previous
•Bank Level •Next
•User Invoked •Skip
•Execute on a Holiday

Job Group Other Parameters

•Corresponding to the •Blocking Job (Y/N)
Invoking Process •Job Category
•Should be Blank for User (Independent/Block Lower
Invoked Batch Jobs Priority Job
execution/Allow Lower
Priority Job execution)

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Environment Variables
• Certain environment variables are available to control different aspects of
processing of the EOD BOD and Batch Job Execution.
• Path :- /etc/b2k/$FINACLE_INSTALL_ID/FINCORE/com/commonenv.com
Environment Variable Purpose of the Variable
NBR_OF_PARALLEL_EODBODJOBS This variable decides the number of streams of an EOD BOD
job which can be executed in parallel.

This value will be default populated as “No. Of Parallel Sols”

in HSCOD, HSOLCOP and HSCOLD. This can be over-ridden
in those menu options.
SLEEP_TIME_BEFORE_FORK Depending upon the value set for this environment variable
the system sleeps while splitting jobs into multiple processes.
This value is in seconds.

NBR_OF_PARALLEL_DTDHTDJOBS How many sol’s DTD records will move to HTD at a time

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
 Environment Variables
Environment Variable Purpose of the Variable

BJS_NO_OF_PARALLEL_JOBS This variable decides the number of streams of an EOD BOD job which can be
executed in parallel for the Bank Date Change Operations (HBKOD) or Bank Closure
Operations (HBKCOP) or Bank Beginning of Day operations (HBKOLD)

The value of NBR_OF_PARALLEL_EODBODJOBS parameter is getting set each time as

equal to BJS_NO_PARALLEL_JOBS_BANK whenever we are invoking HBKOD, HBKCOP
and HBKOLD. This is controlled by these scripts:-BKOLD_Validate.scr,
BKCOP_Validate.scr, BKOD_Validate.scr. (Location: - $TBA_SCRIPTS).

It is because If the field 'No. of Parallel SOLs' for which value is auto-populated from
commonenv (NBR_OF_PARALLEL_EODBODJOBS) is getting over-ridden by user in
either HSCOD or HSOLCOP or HSCOLD, changed value takes precedence over the
commonenv variable value during DC level EOD/BOD jobs.

Example :- If NBR_OF_PARALLEL_EODBODJOBS is set as 10, and during HSCOD for

last set id, the “No. Of Parallel Sols” is changed to 5, then if we run HBKOD
immediately after this, then HBKOD will start running as 5 parallel sols.(Not 10). Logic
is written in those 3 scripts, to take care of this.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Environment Variables
Environment Variable Purpose of the Variable

SKIP_ON_LOCK_UNAVAILABLE This variable is used by certain batch jobs to skip processing of the records for
(Y/N) which a lock could not be obtained for processing.

The other records are processed in this case, and the records which could not
be processed are dumped in the fatal_info.log file.

If the variable is not set, the system gives a fatal error if a lock could not be
obtained on any record for processing.

The following programs give fatal error depending upon the environment variable set, if
a resource (say, an account) is not available, even after waiting for a specified period of
time. In other words it has been locked by some other program :- ACINT, ACACCR,
LADSP
If this variable is set to Y, the process skips all the records for which processing is not
possible and proceeds processing other records.
If it is set to N or left unset, a fatal error occurs terminating the process after trying for
the number of times as set in the environmental variables.
This is introduced, so that if for any reason one particular record is busy because of a
hung process and so on., the user has the option to enable the program not to
terminate with a fatal error. However the records which were busy are left unprocessed.
Typically the number of such records are minimal.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Non Business Parallelization (NBP)
• Non Business Parallelization can be used for optimum utilization of server
resources by implementing parallel execution of a batch job.

• Multiple threads of the same batch job can be executed in parallel, thereby
ensuring better performance in terms of execution time

• For enabling NBP, specific Environment variables are to be exported.

NBP for a SOL NBP for the Entire Bank

<exe_name>_<solid>_NUM_RECCOUNT <exe_name>_ NUM_RECCOUNT

<exe_name>_<solid>_NUM_JOB <exe_name>_ NUM_JOB

<exe_name>_<solid>_SUM_LOG <exe_name>_SUM_LOG

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Non Business Parallelization (NBP)
• NUM_RECCOUNT variable specifies the maximum number of records which
are to be processed in a single process.

• NUM_JOB variable specifies the maximum number of processes which

should be created for a job at time.

• SUM_LOG variable specifies whether a summary log for the NBP execution
should be created.

Example

ICBX4008_NUM_RECCOUNT=1000 ; export ICBX4008_NUM_RECCOUNT

ICBX4008_NUM_JOB=5 ; export ICBX4008_NUM_JOB

ICBX4008_SUM_LOG=Y ; export ICBX4008_SUM_LOG

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Non Business Parallelization (NBP)
Imp Notes :-
• Only some exe can be set for NBP. NBP cannot be enabled
for all batches.
• Heavy Parallelisation is not recommended. It can impact
resource management. (CPU Usage/ Memory Usage). It
should be set to some optimum value.
• NBP is applicable for only product exe. Customization
batches cannot be parallelised using these environment
variables.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SOL and DC Restartability
• A mechanism is available to monitor and prevent the simultaneous
execution of a SOL Date Change Operation or a Bank Date Change
Operation.
• This is managed by two flags – one at SOL level and one at Bank Level
SOL Restartability Flag Bank Restartability Flag

D SCOD Running D BKOD Running

L SOLCOP Running L BKCOP Running
C SCOLD Running C BKOLD Running
N/Null EOD Operation Not Running N/Null EOD Operation Not Running

• Scripts eod_sol_restartability.scr and eod_dc_restartability.scr are

available to reset the EOD Status to EOD Operation Not Running, in case
the EOD BOD operations are aborted due to any reason.
Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
SAMPLE CHECKLIST FOR
EOD/BOD

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Sample Pre EOD/BOD Run Checklist
1. EOD Batch Job setup should be done for all active SOL Ids.
2. Holiday Calendar should be in sync for all working Sol ids.
3. Check in HCTM and HBCTM whether the next BOD you want is holiday. It
shouldn’t be a holiday, if it is a holiday, the date will be changed to the next
working day.
4. Previous Day’s EOD/BOD logs are to be procedurally moved to other safe
directory before starting each day’s EOD/BOD operations.
5. Data backup needs to be taken before EOD/BOD start. This is to ensure
prevention of data corruption in case of errors in EOD/BOD.
6. There should not be any unbalanced transaction.
7. There should not be any unposted cash transaction.
8. There should not be any sol id which is not part of ALL set.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Sample Pre EOD/BOD Run Checklist
9. There should not be any sol id which is not part of these Set ids :-
EODDEP1
EODDEP2
EODDEP3
EODWLN1
EODWLN2
10. All the relevant finacle services should be up and running :-
Finlistval in both node
Cores session in both nodes
Finrpt in both nodes
WAS in both nodes
11. CDCI directory should have sufficient space to generate logs inside the
directory. For 1 Day Run, Approximately 15-20 GB of free space is recommended.
12. Database level locks are to be checked. If it is there, needs to be released.
13. Next_Exec_Date (TBAADM.BJS) of all EOD/BOD jobs (Where job group is null)
should be correct and in sync. (Both system jobs and other jobs )

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Sample Pre EOD/BOD Run Checklist
14. In HSSI Menu Option, For Each Sol id the status will be like this before
EOD/BOD Starts :-
SOL Status: SOL Closure Done
Closure Date: Previous Working Date of that Sol Id
BOD Date: Present Working Date of that Sol id
Closure: Closed
EOD Event Status: EOD event not in progress
Sol Batch operating date: - Should have a valid date equal to or less
that the current BOD Date
Example: - If Present working Date is 31-Jul-2015 and Last Working Date was 31
Jul 2015

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Sample Pre EOD/BOD Run Checklist
Example: - If Present working Date is 31-Jul-2015 and Last Working Date was 30
Jul 2015

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Sample Pre EOD/BOD Run Checklist
15. In HBSI Menu Option, For Each bank id the status will be like this before
EOD/BOD Starts :-
Status: Bank Closure Done
Bank Closure Date: Previous Working Date of Bank
Bank BOD Date: Present Working Date of Bank
Bank Closure: Bank Closure Done
EOD Event Status: EOD event not in progress
Bank Batch operating date: - Should have a valid date equal to or less
that the current BOD Date
Example: - If Present working Date is 31-Jul-2015 and Last Working Date was 31
Jul 2015

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Sample Pre EOD/BOD Run Checklist
Example: - If Present working Date is 31-Jul-2015 and Last Working Date was 30
Jul 2015

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Sample Pre EOD/BOD Run Checklist
Example: - If Present working Date is 31-Jul-2015 and Last Working Date was 30
Jul 2015

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Useful Menu Options & Tables
For EOD/BOD

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Useful Menu Options List
Sl.No Menu Id Description
1 HSCOD Sol Change of Date
2 HSOLCOP Sol Closure Operations
3 HSCOLD Sol Closure of Last Day
4 HBKOD Bank change of Date
5 HBKCOP Bank Closure Operations
6 HBKOLD Bank Closure of Last Day
7 HBSI To Check Bank Status during EOD/BOD
8 HSSI To Check Sol Status during EOD/BOD
9 HBJMON To Check Batch Job Running Status
10 HBJSINQ TO Check Batch Job List for a given criteria
11 HBJSTI Inquire of Batch Job Set Up
12 HBJE To Invoke any batch job manually
13 HCCS To Change context Sol
14 HFTI To Inquire Financial Transaction
15 HTI To Inquire Financial Transaction
16 HSVALRPT To generate Sol Validation Report
17 HPR TO view generated report
18 HRRCDI To view HRRCDM parameters
19 HPDBJINQ To Check Previous Day Run enabled or not
20 HPDBJM Make Batch job enabled to run as on previous day
21 HPDBJDEL Delete Batch job from list of enabled to run as on previous day
22 HBJSTM Batch Job Set up Configuration
23 HSCOFF Mark SOL not to run EOD/BOD
24 HSVAM EOD/BOD validation Maintenance
25 HCTI Sol Level Calendar Table inquiry
26 HBCTM Bank Level Calendar Table Inquiry
27 HPPT Post/ Proxy Post Entered Transactions
Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
Summary of Tables
Table Name Purpose

JEM Job Event Maintenance Table

PBJ Previous Day Batch Job Maintenance Table

BJS Batch Job Maintenance Table

SMVT SOL Validation Maintenance Table

SVHT Sol Validation History Table

BJM Batch Job Monitor and Inquiry

SOL

GCT

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211
 THANK YOU
www.infosys.com
The contents of this document are proprietary and confidential to Infosys Limited and may not be disclosed in
whole or in part at any time, to any third party without the prior written consent of Infosys Limited.
© 2014 Infosys Limited. All rights reserved. Copyright in the whole and any part of this document belongs to
Infosys Limited. This work may not be used, sold, transferred, adapted, abridged, copied or reproduced in
whole or in part, in any manner or form, or in any media, without the prior written consent of Infosys Limited.

Username: Rajasekhar_B, Hostname: 10.232.20.211, Date:Tue Jun 28 15:59:54 IST 2016, IP Address:10.232.20.211

©2014 Infosys Limited, India