EOD&BOD

ADMINISTRATOR TRAINING MANUAL
EOD&BOD
www.infosysinbanking.com
Document number: VersionRev: 1.04
Authorized by: R N NAGARAJ Signature/Date:
Document revision list
Ver.Rev Date Author Description

1.00 02-06-2001 Balaji. S Original version
1.01 09-12-2003 Balaji. S Changes related to CSOLOP
1.02 10-01-2005 Saravanan Rudrakoti Updated to 7.1.2
1.03 05-01-2006 Saravanan Rudrakoti Updated to 9.0
1.04 24-01-2006 M.Vijayalakshmi Moved to 9.1
1.05 13-03-2006 Balaji. S Updated.
© 2006 Infosys Technologies Limited, Bangalore, India
All rights reserved by Infosys Technologies Limited,

Electronics City, Hosur Road
Bangalore – 560 100
India.
No part of this volume may be reproduced or transmitted in any form or by any

means electronic or mechanical including photocopying and recording or by any
information storage or retrieval system except as may be expressly permitted.
This Training manual has been written and produced by the FINACLE -USER
EDUCATION TEAM of Infosys Technologies Limited.
Infosys believes that the information in this publication is accurate as of its publication date.
This document could include typographical errors, omissions or technical inaccuracies.
Infosys reserves the right to revise the document and to make changes without notice.
Infosys acknowledges the proprietary rights in the trademarks and product names of other
companies mentioned in this document.
Infosys FINACLE – UET Finacle Training
Document
TABLE OF CONTENTS
1 OVERVIEW................................................................................................................1
2 SECTION OBJECTIVE...........................................................................................1
3 PROCESSES INVOLVED........................................................................................2
3.1 PROCESS DIAGRAM....................................................................................................2
3.2 TERMINOLOGY EXPLAINED...................................................................................3
3.2.1 NON BUSSINESS PARALLELISATION (NBP).......................................................................3
4 DBA RELATED ACTIVITIES.................................................................................4
4.1 INITIAL SET-UP- OPERATING SYSTEM LEVEL....................................................4
4.1.1 CUST_OPTIONS........................................................................................................................4
4.1.2 ENVIRONMENT VARIABLES.................................................................................................4
4.1.3 ENVIRONMENT VARIABLES FOR NBP................................................................................5
4.1.4 MISCELLANEOUS....................................................................................................................8
4.2 INITIAL SET-UP - APPLICATION LEVEL.................................................................8
4.2.1 EXCEPTIONS............................................................................................................................8
4.2.2 HSCFM SETUP........................................................................................................................10
4.2.3 SETTING UP OF SOL PRIORITY...........................................................................................10
4.2.4 SOL SUBMISSION FOR CLOSE SOL OPERATION.............................................................11
4.3 SETTING UP OF BATCH JOBS..................................................................................11
4.3.1 DATE MNEMONICS IN BATCH JOBS..................................................................................15
4.3.2 REPLICATION MODE OF HBJSTM:.....................................................................................16
4.3.3 MENU OPTION SOLVAL (SOL VALIDATION RUN REPORT)...........................................17
5 OPCONSOLE MESSAGING................................................................................20
6 SYSTEM USER ACTIVITIES...............................................................................20
6.1 SERVICE OUTLET STATUS.......................................................................................20
6.2 VALIDATIONS DONE FOR THE SERVICE OUTLETS.........................................22
6.2.1 MENU OPTION RESUBSOL (RESUBMIT SOL FOR CSOLOP).........................................26
6.3 RECONCILING ISO TRANSACTIONS....................................................................26
6.4 AFTER BUSINESS HOURS........................................................................................27
6.4.1 PRECONDITIONS FOR ABH..................................................................................................29
6.4.2 CHECKS DONE IN ABH.........................................................................................................30
6.4.3 LIST OF JOBS EXECUTED BY ABH.....................................................................................30
EOD & BOD Ver. Rev 1.04 Page i

Document
6.5 END OF THE DAY FOR THE SERVICE OUTLET..................................................30

6.5.1 PRECONDITIONS FOR CSOLOP..........................................................................................33
6.5.2 JOBS RUN IN CSOLOP:..........................................................................................................33
6.6 DATACENTER END OF THE DAY - CENTRAL EOD PROCESS.........................34
6.6.1 PRECONDITIONS...................................................................................................................35
6.6.2 CHECKS DONE IN CENTRAL EOD.....................................................................................35
6.6.3 EXCEPTIONS CHECKED DURING CENTRAL EOD.........................................................36
6.6.4 PROCESSES RUN DURING CENTRAL EOD.......................................................................36
6.7 DATACENTER BEGINNING OF THE DAY..............................................................36
6.7.1 PRECONDITIONS FOR CENTRAL BOD..............................................................................37
6.7.2 PROCESSES DONE IN CENTRAL BOD...............................................................................38
6.8 BEGINNING OF THE DAY FOR THE SERVICE OUTLET...................................39
6.8.1 PRECONDITIONS FOR ISOLOP...........................................................................................39
6.8.2 JOBS EXECUTED DURING BRANCH BOD.......................................................................40
6.9 OPENING TRANSFER TRANSACTIONS.................................................................40
6.10 OPENING OF CASH TRANSACTION...................................................................41
6.11 CLOSING OF TRANSFER TRANSACTION.........................................................41
6.12 CLOSING OF CASH TRANSACTION....................................................................42
6.13 REINITIATING TRANSFER OF HISTORY TRANSACTIONS..........................44
6.14 VERIFICATION OF PREVIOUS DAY’S TRANSACTIONS................................45
6.15 CHANGING USER’S CONTEXT SOL...................................................................46
6.16 TREATMENT OF UNPOSTED TRANSACTIONS DURING EOD.....................46
6.16.1 HDTE – DELETE TRANSACTION IN ENTERED STATUS............................................47
6.16.2 PPT – PROXY POST TRANSACTION IN ENTERED STATUS.......................................47
6.17 BACKGROUND QUEUE MAINTENANCE...........................................................49
7 RELATED MENU OPTIONS................................................................................50
8 RELATED TABLES................................................................................................51
9 BATCH JOBS..........................................................................................................51
10 MRTS/MRRS/SAMPLE REPORTS.....................................................................55
10.1 NON BUSINESS PARALLELISATION REPORTING..........................................56
11 flashback....................................................................................................................58
EOD & BOD Ver. Rev 1.04 Page ii

Document
OVERVIEW
End-of-day & begin-of-day are operations 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 next working day.
As part of a bank’s routine functions it is necessary that certain batch operations are carried
out at the start of every working day and certain others at the end of every working day.
These are commonly referred to as BOD (Beginning of Day) and EOD (End of Day) processes.
This document covers in detail the set of operations that need to be carried out by the
DBA/System operator at the end of the day and beginning of the day before start of normal
banking operations.
Finacle provides the flexibility for the bank to decide on the processes that can be initiated
either from the branch or all EOD operations from the Datacenter itself. It also provides the
flexibility on what operations need to be run during each of the processes.
SECTION OBJECTIVE
The Objective of this section is to introduce the user to operations related to the END-OF-DAY
(EOD) and BEGINNING-OF-DAY (BOD). This document discusses also the initial set-up needed
and covers even the additional operations that are to be done in case of a centralised
database (Multiple Service Outlets in Database).
EOD & BOD Ver. Rev 1.04 Page 1

Document
PROCESSES INVOLVED
1.1 PROCESS DIAGRAM
SOLSTAT
ABH
SOLVAL
CSOLOP
CEOD
CBOD
ISOLOP
Notes:
1. Solstat and SOLVAL are independent processes and can be run be run at any time
to know the status of various Sol's and the exceptions.

Document
1.2 TERMINOLOGY EXPLAINED
1.2.1 NON BUSSINESS PARALLELISATION (NBP)

Normally the accounts are not evenly distributed across branches. Some branches (SOLs)
may have large volume of transactions/accounts. During the execution of day end jobs, the
Sols which have a large volume would take much longer to complete its Day end activities
compared to other smaller SOLs. This results in unnecessary delay in the End of day
operations as all the smaller sols have to wait for the jobs for bigger sols to get over before
they can proceed to the next step in the EODBOD. To optimize the utilization of CPU and cut
down the Day end activity time required, Finacle has logic of Non Business Parallelization
(NBP) built into some of the Day end jobs.
With the feature of Non Business Parallelisation (NBP), parallelisation is possible within a sol.
Thus the batch jobs for the bigger sols will get over along with the ones for the smaller sols
and so the effective EOD/BOD time will be reduced considerably. Even though multiple
processes are running for a SOL, one consolidated report will be generated for all the
processes. NBP is just a feature to utilize the machine resources to the maximum. This will
have to be set at each of the sites depending on the customer data for a particular job.
The following critical jobs have been enabled for NBP:

Sl Name of the process Menu Option Exe Name
Num
1. System asset classification SASCL asor5002
2. Interest Calculation ACINT, ACBOOK, ACACCR. icbx4008
3. LA Create demand Run during ISOLOP labx4001
4. Loan Late fee assessment LALFAR labx4005
5. Delinquency Cycle Update DECUP babx4064
6. TDS Calculation TDSCALC txbx4001
7. Automatic Closure of TD Run during CSOLOP babx4008
8. Automatic Verification of TD Run during CSOLOP babx4008
9. Automatic renewal of TD Run during CSOLOP babx4008
10. Year end EIT/IST Updates Run from TRWASTE babx4065
11. ATO updates Run from ATOR or during babx4005
EODBOD
12. Batch Charge Calculation BCCALC babx4050

Document
DBA RELATED ACTIVITIES
INITIAL SET-UP- OPERATING SYSTEM LEVEL

The initial set-up done at the OS level are highlighted in this section
1.2.2 CUST_OPTIONS
1.2.3 ENVIRONMENT VARIABLES

 NBR_OF_PARALLEL_EODBODJOBS
The user can decide the number of streams that a EOD/BOD job should run in parallel. This
variable can be set just before running the CEOD/CBOD at command prompt or can be set in
“commonenv.com” available in “/etc/b2k/$B2K_INSTALL_ID/com directory. While running the
CEOD/CBOD processes, the relative “ceod.b2k” or “cbod.b2k” files will look for this value and
accordingly initiate multiple number of processes. If this is not defined then the default is 3
(for single sol it is always 1). This variable can be used to decrease the time taken for long
batch jobs like GL update (glbx4004), BJS jobs (babx4009) by running multiple streams in
parallel, one for each sol in the data center.
 BJS_NO_OF_PARALLEL_JOBS
It is possible to execute all the jobs running in same priority level in parallel. This is done so
that the CPU utilization can be maximized during end of day operations. Parallelisation of BJS
jobs in the same priority level can be achieved by setting the environment variable
BJS_NO_PARALLEL_JOBS to a number. In case this environment variable is not set, then the
jobs within the same priority are run one by one.
 TBA_TRACE_DIR
It is also possible to generate EOD execution logs in one place. If this environment variable is
defined then it will create all EOD execution logs at that place. Otherwise it will create all logs
in Users home directory. This is very helpful when different users either at Branch level or
Datacenter execute the EOD/BOD operations.
All the process status message logs will now be routed to the directory
$TBA_TRACE_DIR/message/<BODdate>/<SOLID>/(ABH/CSOLOP/CEOD/CBOD/ISOLOP).log.
if TBA_TRACE_DIR variable is not available, the logs will be created in HOME directory of the

Document
user who has initiated the process of ABH.
 EOD_BOD_LOGS_REQD
If this env variable is set then system will create the logs of all the op-console messages.
These logs will be created in
$TBA_TRACE_DIR/messages/<BOD date>/<Sol Id>
if TBA_TRACE_DIR is set else the logs will be created in the EODBOD user home directory.
1.2.4 ENVIRONMENT VARIABLES FOR NBP

Setting a few environment variables can enable NBP. These environment variables differ from
process to process (so that NBP can be achieved selectively). There are three parameters
that can be set.
One parameter to specify the minimum number of records for which a new process needs to
be run.
One parameter that governs the maximum number of such process that can be run at any
point of time.
One parameter that will generate a summary of what all process got run due to NBP.
Details about the environment variables are given below.
FORMAT OF THESE VARIABLES
These environment variables have the following format:
1. For enabling parallelisation of a job for a particular sol:
<exe_name>_<solId>_NUM_RECCOUNT
<exe_name>_<solId>_NUM_JOB
2. For enabling parallelisation for a particular job irrespective of the sol for which
it is being run
<exe_name>_ NUM_RECCOUNT
<exe_name>_ NUM_JOB
3. For enabling summary log for a job for a particular sol

Document
<exe_name>_<solId>_SUM_LOG
4. For enabling summary log for a particular sol irrespective of the sol for which
it is being run
<exe_name>_SUM_LOG
The exe_name varies from process to process. For example, for System Asset Classification,
it is ASOR5002 whereas for Interest Calculation it is ICBX4008.SolId is the sol for which job is
running.
e.g. So if the parallelisation has to enabled for the job System Asset Classification and for the
sol 282 , the following environment variables need to be set.
ASOR5002_282_NUM_RECCOUNT
ASOR5002_282_NUM_JOB
If the System Asset Classification has to be parallelised for all the sols then the following
environment variables need to be set.
ASOR5002_NUM_RECCOUNT
ASOR5002_NUM_JOB
VALUES OF THESE ENVIRONMENT VARIABLES
The main criterion that governs the NBP is the value of these environment variables. These
values of these variables decide the extent of the parallelisation.
e.g.
If System Asset Classification batch job is required to be parallelisation for sol 282 and one
wants to run a separate process for every 1000 records with maximum of 5 processes
running at any one time the following environment variable should be set,
ASOR5002_282_NUM_RECCOUNT=1000
ASOR5002_282_NUM_JOB =5
Suppose there are 7958 records are eligible for System Asset Classification, the number of
processes that will be run will be 7958/1000 = 8 (rounded to highest integer). First 7
processes will be processing 1000 records each and the 8th process will be processing 958

Document
record.
Each new process may not always be run for exactly NUM_RECCOUNT number of records. In
case there is a logical break required for a process, then the break will happen on the next
logical record.
e.g. In case of TDS calculation, one process should contain all the accounts of the customer.
In case 997 to 1005 account in the list belong to same customer, then the logical break will
happen only after 1005 records and not after 1000 records as specified by the
NUM_RECCOUNT variable. Thus NUM_RECCOUNT specifies minimum records that may be
required for each new child process.
As NUM_JOB is set to 5, only 5 process will be run initially. Only after one of the process
completes, another new instance of the same process will be run. Thus at any point of time,
only 5 instances of ASOR5002 for SOL 282 will be running.
Please note that if the second variable i.e. <exe_name>_solId_NUM_JOB is not set then the
system looks for the environment variable <exe_name>_NUM_JOB. In case even the variable
<exe_name>_NUM_JOB is not set, system automatically restricts the maximum number of
jobs to value of environment variable NBR_OF_PARALLEL_EODBODJOBS. This variable is
required for EOD processes. In case the variable NBR_OF_PARALLEL_EODBODJOBS is not set,
then maximum number of jobs is taken as 10.
SETTING UP OF THESE ENVIRONMENT VARIABLES
These environment variables can be set up in commonenv.com or in the script hooks

provided at various places. In case these variables are set in commonenv.com then even if a
user runs any of these batch jobs during daytime, it will do the NBP and hence lots of batch
processes can be running affecting the online response time. To avoid the same, in case of
BJS jobs, these environment variables should be set in BJS script hook
(B2K_PreJobExecCheck.scr) .
A script hook (A sample script B2K_BatchStart.sscr is being provided) has been provided
which can be used for setting any environment variable. For example we want to set the
following environment variables:
ASOR5002_282_NUM_JOB=1000
ASOR5002_ NUM_JOB=5

Document
In case the program is not a bjs enabled job, these variables can be set in script
B2K_BatchStart.scr. Here the db_stat_code from SOL table should be checked and in case
the db_stat_code is not ‘C’ (ISOLOP Completed), only then environment variables should be
set.
 SKIP_ON_LOCK_UNAVAILABLE
The following programs will 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.
(i.e. it has been locked by some other program)
ACINT
ACACCR
LADSP
LALIEN
If this variable is set to "Y”, the process will skip all the records for which processing is not
possible (put the list of such records in fatal_info.log) and proceed processing other records.
If it is set to "N" or left unset, a fatal error will occur 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 etc... the user has the option to enable the program not to terminate with a fatal
error. However the records which were busy will be left unprocessed (typically the number of
such records will be less).
 SLEEP_TIME_BEFORE_FORK
Depending upon the value set to this environment variable the system will sleep while
splitting jobs into multiple processes. This value is in seconds.
1.2.5 MISCELLANEOUS
All the EOD/BOD processes are enabled for execution of site specific unix shell scripts. These
scripts should be named as the “<menu option>.site”. e.g. “ABH.site”
INITIAL SET-UP - APPLICATION LEVEL

Document
1.2.6 EXCEPTIONS
The following are the exceptions that are set in the menu option SCFM for the datacenter and
SOL which are checked during EOD/BOD processes.
Exceptions set at Group level:
 Transaction Pending authorisation

 Transaction not Stopped
 Transaction not Verified
 Invt. tran not Posted
 SI Execution not Completed
 Unprinted DD's exist
 Unprinted TD's exist
 Unprinted Branch Advc exists
 Pending Anywhere Trans exist
 Sum of acct balances not zero
 Pending Purchase/Sale Excp
 Pending Profit/Loss Excp
 Unclosed inward clg zone
 Open/suspended out clg zone
 Bar gen not Regularised
 Unprinted Bars exist
 Undespatched ATM/Anywhere
 ISO Balance Check Excp
 Pending Business Trans Excp
 Pending VAT Approval Excp
 Swift Mesgs Transfer Pend Excp
 Bills Pending verification
 Exceptions set at SOL level:
 proxy not verified Excp code
 proxy outstanding Excp code
The following exceptions set at scheme level will also be looked into during EOD/BOD process

Document
 Exceptions set at GSPM – Currency details

 EOD minimum balance check
 EOD maximum balance check
1.2.7 HSCFM SETUP
MENU HSCFM: DATA CENTER DETAILS
O N R EGULARIZATION TOD , A PPLY INTEREST :

This field indicates if you want to apply interest calculation also to accounts on regularization
of TODs. This would only apply interest to those accounts under saving and current without
limits at account level.
1.2.8 SETTING UP OF SOL PRIORITY
The field Sol Priority in SOL details of SCFM specifies the priority level of the Sol during
EOD/BOD process. Sols with higher priority will be taken up for processing earlier compared
to the sols of lower priority.

Document
For example, a sol with a sol priority of ‘1’ will be processed before a sol with priority ‘2’.
1.2.9 SOL SUBMISSION FOR CLOSE SOL OPERATION
It can be set that for CSOLOP to be executed that submission of the SOL in SOLVAL menu
must be made mandatory.
If this flag is set to Y, then CSOLOP will pick up only those SOLS, for which submit to CSOLOP
is done in SOLVAL operation.
If this flag is set to N, then CSOLOP will pick all the SOLs for end-of-day operation.
This gives a control to the bank that SOLVAL operation is made mandatory before starting the
Close SOL operations.

Document
SETTING UP OF BATCH JOBS

The application provides for automating certain tasks and also generating reports as a part of
the end-of-day/begin-of-day operations. These tasks/reports can be set-up as batch Jobs that
will be executed automatically during the EOD/BOD operations.
These batch jobs can be set-up during the various operations of the EOD/BOD. There is also a
facility to execute user-defined UNIX commands/Scripts and also SQL scripts as the part of
Batch jobs. Each of the batch jobs can also scheduled to be executed at different frequency of
dates. An example like certain reports needs to be generated daily while certain tasks need to
be executed monthly.
The Batch job can be set-up to be executed in the following operations

 B CENTRAL BOD PROCESS
 L SOL BOD PROCESS
 T SOL EOD PROCESS
 A AFTER BUSINESS HOURS
 E CENTRAL EOD PROCESS
 U User Invoked Process
Batch jobs in Finacle are classified as jobs
 FORM
These jobs have a parameter form and the parameter form needs to be visited to
provide additional details. These are basically menu option screens itself which can be
setup as batch process to be automatically invoked with the parameters specified
during EOD/BOD operations.
 BATCH
These jobs do not have any parameter form to be visited. In case any parameters are
needed as input, the same would be provided in the parameter field on the main screen
of general details itself.
 SCRIPT
For these type of batch jobs, user needs to specify the script name/file name in the
parameter field.

Document
MENU OPTION: HBJSTM
The above screen displays the set-up of a batch job interest accrual done on daily basis
during SOL end-of-Day. The Options available in the functional block are A-add/ C-copy/ D-
del/ I-inq/ L-list/ M-modify/ U-undel/ R-replication.
SUB-OPTION: P-PARAMETER DETAILS

Since this batch is of form type, the parameter icon next to the file name needs to be clicked
and screen shown as below which is the screen for interest accrual for account ( HACACCR
menu ) appears.

Document
The screen above is the same as the menu option (HACACCR) which is for accrual of interest.
 Not all batch jobs need the parameter details.

Refer to the section of batch jobs for list of batch jobs available.
Any job can be made inactive by marking the job active flag as N. Also you can set a job as
inactive and make the same as active automatically by specifying the grace period. System
would make the job active after the number of grace days.
B LOCKING J OB
This particular field decides if other batch jobs succeeding the current should continue or not
if this particular job fails.
An example is that TDS calculation process should be run only after calculation of interest.
Hence interest calculation batch job should be a blocking type.
J OB C ATEGORY

Document
All batch jobs get executed based on the priority setup for that job. Jobs of lower priority will
not be executed until jobs of higher priority are completed based on the value set for the
above field. This field will accept the following values
‘I’ - Independent jobs. These jobs will start latest in their own priority but can start earlier
also if they can find a slot. These jobs do not prevent jobs of lower priority to start even if
they have not finished execution.
‘B’ – Blocking jobs. These jobs will start in their own priority and will prevent jobs of
lower priority to start unless execution of these jobs is over.
‘N’ – Non-Blocking jobs. These jobs will start in their own priority and will not
prevent jobs of lower priority to start even if they have not finished execution.
This helps in optimising the slots available for execution of batch jobs. Hence
independent jobs can utilize the slots available while jobs of other priority are being
executed.
B ATCH J OB T YPE :
This would provide information like ‘Skip on Year End’ or ‘Skip on Quarter End’ etc. Addition
and maintenance of the Valid Job Type Codes can be done through the RRCDM menu option.
Certain batch needs the arguments that can be passed through the parameter field.
Certain batch jobs like the one shown need to set certain parameters specific to the job. So
there is a sub-option P- PARAMETER FORM that displays the details of the parameter form
specific to that particular batch job being set-up.
Menu BJSTI is used for inquiring details of the BJS job. It accepts Inquiry mode only .
1.2.10 DATE MNEMONICS IN BATCH JOBS
A provision to specify date mnemonics while setting up BJS jobs has been provided. Date
mnemonics are values that can be specified in the date fields of BJS parameter screens. This
mnemonics will be converted to actual dates when the job is actually taken up for execution.
The following mnemonics are provided.
Date Mnemonic Remarks

Document
<BOM> Beginning of (current) month

<EOM> End of (Current) month
<BOLM> Beginning of last month
<EOLM> End of Last month
The user has to give the date mnemonic as shown above in the date fields.
Date mnemonic is enabled for the following files in BJS.
asfe0010, bafe3029, bafe3032, bafe3033, bafe3034, bafe3035, bafe3037, bafe3039,

bafe3041, bafe3044, bafe3051, bafe3054, bafe3057, bafe3070, bafe3211, bafe3251,
bafe3253, bafe3254,
bgfe3001, bgfe3002, bgfe3003, bgfe3004, bgfe3005, bife3004, bife3005, bife3006, bife3007,

bife3008, bife3009, bife3010, bife3012, bife3015, bife3016, bife3020, bife3021, clfe3003,
clfe3012, clfe3029, ddfe3013, ddfe3022, fxfe4013, glfr5001, hcfe3006, hcfe3007, hcfe3009,
hcfe3010, hcfe3011, hcfe3013, infe3004, lafe3006, lafe3007, lafe3008, lafe3255, lafe3258,
rrfe3001, rrfe3002, rrfe3003, rrfe3004, rrfe3005, rrfe3006, rrfe3007, rrfe3008, rrfe3009,

rrfe3010, rrfe3011, rrfe3012, rrfe3013, rrfe3015, rrfe3016, rrfe3017, rrfe3020, rrfe3021,
rrfe3022, rrfe3023, tdfe3003, tdfe3005, icfe3008
1.2.11 REPLICATION MODE OF HBJSTM:
Replication of the BJS jobs can be done through HBJSTM menu option (function code ‘R’), for

Document
all Sol Ids in a Sol Set. Banks can set the job for only one Sol, & replicate for all Sol Ids in a
Sol Set.
If we want a particular job to be replicated across all sols,then in the parameter screen for
that job we have to specify the Sol Id/Set Id as <CS>(mnemonic for Context sol). During
execution of job this is replaced by Context Sol Id / Set Id.
Replication program will skip all jobs which do not have pneumonic ‘<CS>’ entered anywhere
in the parameter screen. The assumption made here is either, the Job does not require
Replication as there is no Sol Id in the job parameters or the parameter screen for the Job
has not been modified to accept context Sol Id (‘<CS>’).
A report TMP*.RPT, gets generated, giving Sol Id wise result of BJS replication.
1.2.12 MENU OPTION SOLVAL (SOL VALIDATION RUN

REPORT)
Indicate if only validation run only or S for Submission for SOL for CSOLOP. This depends on
the value set at SCFM level if SOLVAL completion and submission is mandatory for completion
of CSOLOP.
SOLVAL menu option can be used to show discrepancies before going ahead with CSOLOP.

Document
The following error checks will be done by system:
 Check if all transactions initiated by this sol are posted.
 Check if all transactions initiated by this SOL are balanced.
 Check if any Inter sol transactions initiated by this SOL are pending.
 Check if all Cash and transfer transactions have been closed.

Here, if the Cash and transfer transaction are not closed, system will close them.
 Check for DD number is less than the DD number warning level.
 Check for any transaction against un-verified accounts.
 EOD Date cannot go greater than SYSTEM (Calendar) Date.
Check if any Caution Holiday is marked for the SOL and also for Data Center.
Also, following discrepancies will be checked by system if corresponding exception is set at

SCFM level:
Validation Exception Literal Menu Option/Sub-

Option
Unverified Transaction not Verified HSCFM

Transactions Data Centre Details
Unposted inventory Invt. tran not Posted HSCFM
Transactions Data Centre Details
Outstanding Pending authorization HSCFM
Modifications Data Centre Details
Outstanding Bills Pending verification HCFM
verification of Bills Data Centre Details
Minimum EOD EOD Minimum Balance Excp GSPM
Balance Check Code
Maximum EOD EOD Maximum Balance Excp GSPM
Balance Check Code
No Inward clearing Unclosed inward clg zone HSCFM
zone in unclosed Data Centre Details
status
No Outward clearing Open/suspended out clg zone HSCFM
zone in open or Data Centre Details
suspended status
Bar generation not Bar gen not Regularised HSCFM

Document
regularised Data Centre Details

SI execution SI Execution not Completed HSCFM
pending DATA CENTRE DETAILS
Unprinted DD Unprinted DD's exist HSCFM
DATA CENTRE DETAILS
Unprinted TD Unprinted TD's exist HSCFM
DATA CENTRE DETAILS
Unprinted BAR Unprinted Bars exist HSCFM
DATA CENTRE DETAILS
unprinted branch Unprinted Branch Advc exists HSCFM
advices DATA CENTRE DETAILS
Non-complete Pending Anywhere Trans exist HSCFM
ANYWHERE DATA CENTRE DETAILS
transaction
Any non completed Pending Purchase/Sale Excp HSCFM
Purchase Sale Entry DATA CENTRE DETAILS
non completed Profit Pending Profit/Loss Excp HSCFM DATA CENTRE
and Loss Procedure DETAILS
Undespatched Undespatched ATM/Anywhere HSCFM DATA CENTRE
ANYWHERE/ATM DETAILS
transaction
Uncompleted Priority Pending Business Trans Excp HSCFM DATA CENTRE
Workflow DETAILS
transactions
Unapproved Pending VAT Approval Excp HSCFM DATA CENTRE
Verification Audit DETAILS
Records
Unapproved Pending VAT Approval Excp HSCFM DATA CENTRE
Verification Audit DETAILS
Records
Unverified Proxy proxy not verified Excp code HSCFM SOL Maintenance
transactions Details
SWIFT messages Swift Mesgs Transfer Pend Excp SCFM/G
yet to be transferred
to swift center
Outstanding Proxy proxy outstanding Excp code HSCFM SOL Maintenance
transactions Details
minimum number of DDN warn level excp HSCFM SOL Maintenance
DDS Details
External All Ext Trans Proc Excp HSCFM SOL Maintenance
transactions not Details
successfully
processed
In case bank wants to add a new validation check before ABH starts, it can be done in the
step 4 (General ABH script hook). This script can be used to include any additional validations
which a bank may want to execute at the time of SOLVAL/ABH/CSOLOP.
Following checks can be added , which can be included in the sample script provided:

Document
 Check for any user logged on

 Check if all trans initiated by some other SOL on this SOL are pasted
 Check if all ISO trans initiated by some other SOL on this SOL are pending
2 OPCONSOLE MESSAGING
Infosys OpConsole service will be installed only on versions Windows-NT 4.0 or above. It
receives messages from various LIMO clients and LIMO servers and writes them in Window
Event Viewer. Messages logged in the Event viewer are of three kinds – Error Messages,
Warning Messages and Information Messages. All EOD/BOD Messages can be viewed NT
Event viewer. For details about OP Console please refer Web Concept document.
SYSTEM USER ACTIVITIES

The daily operations are to be executed by the System Operator (User categorised as “OP” in
the User Profile Maintenance) as a part of End of Day and Beginning of day.
End of day is done in the following order irrespective of the number of SOLs
Individual Service Outlets:
SOLVAL – Validations on the Service Out let
SOLSTAT – Check the status of Service Out let
ABH – After business hours
CSOLOP – Service outlet End of Day
Data center
CEOD – Central End of Day
CBOD – Central Beginning of Day
Individual Service Outlets:
ISOLOP – Service outlet Beginning of day
SOLVAL process is not a mandatory process to be invoked. With the help of this menu, user
will be able to know all pending jobs that needs to be carried out before starting the
EOD/BOD processes, so that it goes smooth.

Document
SERVICE OUTLET STATUS
System maintains the status of the database and the process that is going on during the
EOD/BOD process.
The Service Outlet status of any one, or all the Service Outlets will be displayed when the
SOLSTAT option is invoked.
MENU OPTION: SOLSTAT
Depending on the status of the service outlet, system allows certain functions/processes that
are to be carried out further. It also depends upon the menu options which are allowed to be
executed.
BOD Process maintains db_stat_code and db_int_stat_code in the SOL table as flags, using
which it decides what is the next job to be executed and updates it appropriately. Following
table gives the various states of the BOD process as indicated by the db_stat_code and
db_int_stat_code.
The different DB_STAT_CODE for different EOD/BOD processes are given below.

Document
PROCESS DB_STAT_CODE in SOL Table

During execution of ABH Process 'A'
After completion of ABH process 'B'
During execution of CSOLOP Process 'F'
After completion of CSOLOP Process 'G'
During execution of CENTRALEOD Process 'E'
After completion of CENTRALEOD Process 'H'
During execution of CENTRALBOD Process 'K'
After completion of CENTRALBOD Process 'L'
During execution of ISOLOP Process 'S'
During execution of ISOLOP Process 'C'
In the case of a holiday at a data center, there cannot be any transaction (financial/non-
financial) on that day for the whole data center. This is because the day will be automatically
skipped whenever the EOD for a day before the holiday is done. In case of SOL holiday,
ISOLOP and CSOLOP for that SOL will be skipped and the status of the SOL will be CSOLOP
completed, as soon as Central BOD for that day is completed. As CSOLOP for the day is over,
no user will be able to login to the SOL, which is on holiday, for any operations. However,
other SOLs can initiate transactions on accounts belonging to the SOL on holiday. Thus there
can be GL entries for a SOL even when it is on holiday.
 Note: Holidays for a SOL are set up in the CTM option and for a data center in the DCTM
option. Calendar Table Maintenance is covered as a part of Masterdata Maintenance
VALIDATIONS DONE FOR THE SERVICE OUTLETS
Service Outlet Validation is a process, which needs to be run by the user at Service Outlet
level before invoking EOD. It contains all the checks for the Service Outlet that is to be
ensured before invoking EOD.
A report can also be generated/printed with all the errors/exceptions that are raised.

Document
OPTION: SOLVAL
The options will carry out the following checks and will be for the set id entered
1 All entered Part Trans that are not ‘POSTED’

Document
2 Unbalanced transactions initiated by the service outlets for which validation is

being run.
3 Unverified Transactions that exist for the service outlets on which validation is
being run.
4 Unposted Transactions initiated By Other SOLS
5 Transactions against unverified accounts check. All the accounts that are not
verified but transactions have happened are given.
6 All inter sol transactions that are un reconciled. These are in respect of
transaction initiated by my service outlet and I have not run RIST for reconciling the
transactions.
7 This is in respect of all ISO transactions initiated by all other SOLs on my service
out let and they have not run RIST for reconciling those transactions.
8 The currency in which the sum of the ISO Account balances is not zero.
9 All Outward Clearing Zones for the Sol should be in “Closed” status, which are
less than or equal to BOD date. All outward clearing zones which have zone date
greater than BOD date should have been in “Suspended status” If any zone is there
with any other status then this will display all such zones.
10 All Inward Clearing Zones open for the Sol should be in “Closed” status. If any
zone is in any other status other than “Closed” status, then those zones will be
displayed.
11 All unverified inventory transactions are displayed.
12 SI execution pending for the SOL.
13 All transactions to a parking account where advice is not printed will be shown
14 All originating HO transactions where advice are not printed will be displayed
15 Exception for BAR generation not regularized. There are instances where the
clearing transaction happens to the debit of HO accounts. In that case, the advice
would have been despatched to the main clearing house without the balances being
released to credit of account. At that stage the status of the zone would be “B” –
Bar generated. Unless the balances are released into shadow balance, the end of
day should not be done. In order to check this, the user needs to know the status.
16 All bills that are pending verification are displayed.

Document
17 All DD transactions where it is not printed will be displayed
18 For all Term deposits opened, receipts should have been printed. If any un
printed TD receipts exists those will be shown.
19 If for any scheme, EOD minimum and EOD maximum balance exception is set
and not maintained then this will show those accounts.
20 All Pending AnyWhere Transactions which are not in completed status are
shown.
21 Pending workflow Transactions List
22 Pending Proxy Transactions List I.e., the proxy transactions which are yet to be
verified.
23 Outstanding Proxy Transactions List i.e., to check that no proxy posted part
transaction for reversal shall be outstanding for more than ‘N’ days, where ‘N’ is a
parameter setup in HSCFM at sol level. Exception code will be accepted at SOL level
in HSCFM. System will not consider holiday for this exception i.e., this exception will
be raised only if above said condition is true, irrespective of next day is working or
not.
24 Pending Purchase and Sale
25 Pending Profit and Loss
26 Unprocessed External Trans
This exception is raised whenever there are records in the EXTRN_ACCOUNTING_TABLE (EAT)
with processed status is not complete.
27 Currencies with Nonzero Balance
28 Pending Referral Transactions Others
29 Others
Under the Category OTHERS the following checks are done
 Any Pending Audit Records for verification

 Any Records that have to be despatched (ATM and ANYWHERE Module)
 Whether there are any pending BAR’s – Service outlets receive BARs from other
service outlets which needs to be responded. If any of the BAR received is not

Document
responded those will be shown.

 Any Workflow transactions that are needed to be authorised. Additional audit for
workflow where same user created and verified records that need to be authorised.
 Whether any SWIFT messages is not generated for the day.
2.1.1 MENU OPTION RESUBSOL (RESUBMIT SOL FOR

CSOLOP)
In case automatically fired CSOLOP job aborts for a particular SOL, operator can take
corrective measures and restart the job using RESUBSOL menu option to start the process
automatically again. The jobs will be restarted from the step where it was aborted in the
previous run.
This menu option is available only when SCFM level parameter “SOL submission mandatory

Document
for CSOLOP?” is set to ‘Y’.
User can also start ABH/CSOLOP manually without executing RESUBSOL option to carry out
the remaining jobs after taking corrective action.
If the process of ABH/CSOLOP was fired manually first time itself and was aborted, user will
have to execute ABH/CSOLOP manually again to restart the process after taking corrective
action.
RECONCILING ISO TRANSACTIONS
The Inter-SOL transactions, which have occurred for the day must be reconciled or squared
off before the End-of-Day operations are initiated. The menu option HRIST can be invoked to
Square off the pending Inter-SOL Transactions.
MENU OPTION: HRIST/ RIST
Reconciliation of ISO accounts process is called in CEOD processes automatically. Because of

the volume of ISO transactions and to avoid delay during EOD/BOD processes, if the user
wants to reconcile, he can invoke HRIST and reconcile the transactions even before running
ABH process.

Document
AFTER BUSINESS HOURS
Each Bank will have some transactions that need to be put as a part of end of day. Typically,
these jobs will perform some operation depending upon the customer account balances and
the account attributes like TOD granted on the account, transferring funds from FFD to
operative account etc. All these could be set as a batch job that gets executed during this
process. The transactions so created needs to be ensured that it is posted and in verified
status. If not, the user has to take care to see that it is posted and verified.
Before running this option, the user should be fully aware of the conditions and sure that the
after business jobs could be run.

Document
OPTION: ABH
ABH can be run in parallel for all the sols. User can give a set_id on the screen to run ABH for
all the sols in the set. All the sols with the db_stat_code as ISOLOPCOMPLETED are picked up
and ABH is run in parallel for all these eligible sols. In case ABH aborts for any one of the sols,
then another user is eligible to run ABH for that sol after correcting the errors.
Number of parallel sols field is populated with the value of env variable
NBR_OF_PARALLEL_EODBODJOBS. After <key-accept> is pressed on this screen, the
following screen comes up.

Document
After user presses the Key-Commit key, ABH jobs are started. ABH operations for all the sols
are done in parallel. The maximum number of Parallel sols that can be run at any instance
should be specified on the first screen.
All the messages will now be routed to the op console message with the service name as
[b2k_install_id]_ABH_[solid]_PROGRESS.
e.g.. In case b2k_install_id set as FIN and ABH is running for SOL 200, then the service name
will be FIN_ABH_200_PROGRESS. Message is sent to op console when each new job starts
executing. In case one of the ABH job aborts, then a Fatal error message will be send to OP
console. The service name for this message will be [b2k_install_id]_EODBOD_FATAL
2.1.2 PRECONDITIONS FOR ABH

Listed below are some of the error checks required before running After Business Hour jobs.
 EOD Date cannot be greater than system (Calendar) date.

 All part transactions entered by the Service Outlet should have been posted and all
transactions initiated by the Service Outlet should be balanced.
 All part transactions entered on the Service Outlet should have been posted and all
transactions initiated on the Service Outlet by some other Service Outlet should be balanced.

Document
2.1.3 CHECKS DONE IN ABH
1 Check whether the sol is eligible for running ABH. Otherwise discard the sol
2 Check whether some other user is running the ABH operation. If so discard the
sol
3 Check if there are any cautioned holidays for all the eligible sols
In case bank wants to add a new validation check before ABH starts, it can be done in
General ABH script hook. Any validation can be added to the script.
2.1.4 LIST OF JOBS EXECUTED BY ABH
1. Updating TOD information
2. Automatic FFD Account Opening.
3. Transfer Funds from FFD (Auto Regularization of TOD against FFD balances)
4. Executing User defined Batch Jobs
5. Executing Standing Instructions
6. Executing Site Specific Script. The script abh.site in the $TBA_COM directory.
The user can delete all the transactions which are not posted before end of
day or proxy post un posted transactions. Both the process will generate a
report .
All the jobs set up as priority one are fired in parallel. Number of parallel jobs
(degree) is set up as an environment variable BJS_NO_OF_PARALLEL_JOBS
from the user input in the first screen.
 Note: A script “WABH.scr” is provided, where by the user can carry out the following jobs
 Deletion of all un posted transactions calling menu HDTE

 Proxy post all un posted transactions calling menu PPT
 Run ABH for end of day process

Document
END OF THE DAY FOR THE SERVICE OUTLET
The Service Outlet EOD is the second step in EOD/BOD process run by the user at the Service
Outlet at the end of each working day. All the error/exception/warning that were present are
converted into information. When a operator invokes CSOLOP menu options, these conditions
are checked only if the corresponding exception is set. Each of the above condition is
validated for each eligible sol and in case it is not satisfied for any sol, a message is flashed
on the screen to the user. Information of for what sol the condition has failed will be logged
on the opconsole (or user can use SOLVAL menu option). If the user desires, he can proceed
with completion of CSOLOP operations by pressing <key-accept> on the screen.This menu
option closes the operations of the SOL. CSOLOP will execute ABH if the same is not
complete for the SOL.
One user can run CSOLOP for all the sols (the no. of the sols that can be run in parallel can be
specified by the user). This menu also has the feature of running ABH jobs if it has not been
run. The user specifies the set for which sol operations needs to be closed. A list of eligible
sols in the given set is formed and for all the sols, these jobs are run in parallel. . All the sols
with the db_stat_code as SOLBODCOMPLETED, ABHSTARTED, ABHCOMPLETED and
SOLEODSTARTED are picked up. Now for all the sols for which ABH jobs are not run, ABH jobs
will be run before CSOLOP batch jobs are run. Thus if a bank wants to run ABH/CSOLOP jobs
together, it can be done by only running CSOLOP menu option.
Default value for No. of Parallel jobs is picked from the environment variable
NBR_OF_PARALLEL_EODBODJOBS. In case the variable is not set, then a default value of 1 is
shown on the screen. When user presses Key-Accept, the following screen is displayed to the
user.

Document
After user presses the Key-Commit key, CSOLOP jobs are started. CSOLOP operations for all
the sols are done in parallel. The maximum number of Parallel sols that can be run at any
instance should be specified on the first screen.
All the messages will now be routed to the op console message with the service name as
[b2k_install_id]_CSOLOP_[solid]_PROGRESS.
e.g.. In case b2k_install_id set as FIN and CSOLOP is running for SOL 200, then the service
name will be FIN_CSOLOP_200_PROGRESS. Message is sent to op console when each new
job starts executing. In case one of the CSOLOP job aborts, then a Fatal error message will
be send to opconsole. The service name for this message will be
[b2k_install_id]_EODBOD_FATAL.
The validations that are done as a part of CSOLOP will be through the script
generalABHcheck.scr. These checks will be performed only when CSOLOP is invoked after
running ABH. If CSOLOP is performed without running ABH no exception checking is done and
a message "Exception Checking can be done only after ABH." will be displayed. In such case
system will go ahead with CSOLOP. Further the exception checking will be done only for a
SOL and not for SolSet. If a SolSet is entered on the screen then the system will display the
following message "Exception Checking can't be done for a SOLSET.” In such cases the

Document
system will go ahead with CSOLOP. The reason for this being is if in a SolSet there are 10 sols
and exceptions checks are failing only for one sol, EOD process of all the other 9 sols will be
stalled. So for exceptions checking to happen only sol Id has to be entered in CSOLOP menu
option.
2.1.5 PRECONDITIONS FOR CSOLOP
Listed below are some of the error checks required before running the CSOLOP option.
 EOD Date should not be greater than system (Calendar) date

 Check whether CSOLOP can be done
 Check for Caution Holidays
The script for csolop jobs is csolop.b2k and it is present in

$TBA_PROD_ROOT/cust/INFENG/com directory.
2.1.6 JOBS RUN IN CSOLOP:
1. Executing user defined batch job.
2. Generate Carryforward list for Standing Instructions.
3. Calculation of Standing Instruction’s Charges.
4. Execute particular SOL’s site specific jobs. (executes CSOLOP.site script)

Document
DATACENTER END OF THE DAY - CENTRAL EOD

PROCESS
The Central EOD is a process carried out at the end of each working day. Before initiating this
process, all the SOL in the data center should have completed their CSOLOP. The user at the
data center can initiate this process. Central EOD cannot be run on a Set, where at least one
Service Outlet has not completed its Service Outlet EOD. All Service Outlets should run on the
same BOD date. Central EOD will not increment the BOD date of any Service Outlet. It will
check for all financial exceptions, for after the Service Outlet EOD has been run, Inter-Service
Outlet transactions might happen. Once central EOD is started, Inter-Service Outlet and
financial transactions are not allowed. Jobs that create financial transactions are not allowed
in Central EOD. When Central EOD is being run, no users are allowed to login into the Service
Outlet Set except the user running Central EOD.
OPTION: CEOD
 This is a one-time process run by the central user or a SOL.

 This will be run for the whole data center
 CENTRAL EOD cannot be run even if one SOL has not completed CSOLOP.

Document
 CENTRAL EOD cannot be run on a set where SOLs are in different BOD dates.
 It will check for all financial exceptions for transactions done after CSOLOP at SOL
 Central EOD will not increment the BOD date of any SOL.
 No users are allowed to login in once CEOD process starts except the user running central
EOD process.
 Jobs that create financial transactions are not allowed in Central EOD.
2.1.7 PRECONDITIONS
Listed below are some of the error checks required before running the CEOD option.
 EOD Date cannot be greater than system (Calendar) date for any Service Outlet in the
Service Outlet Set.
 All the Service Outlets in the given set should run on same BOD dates. Otherwise, an error
message is displayed.
 Service Outlet EOD for Service Outlets under the Service Outlet Set should be completed.
 All entered transactions should have been posted and all transactions should be balanced.
 All Inter-Service Outlet transactions should have been squared off.
 No user should be logged on while invoking Central EOD in the Service Outlet Set other than
the one who invokes it.
2.1.8 CHECKS DONE IN CENTRAL EOD
1. All entered Part Trans should have been balanced and posted This is necessary in
Central EOD as some Inter-SOL Transactions may happen after SOL finishing its
CSOLOP.
2. InterSol transactions not squared off check.
3. No user should be logged in while invoking Central EOD in the SOL SET.
4. Check whether there are any hanging online LGIs.
5. Check for Caution Holidays in any of the sols
6. Check whether any batch jobs are running in background.
7. Check for system resources (Table space has at least 10% free space).

Document
2.1.9 EXCEPTIONS CHECKED DURING CENTRAL EOD
These are only the financial exceptions checked during Central EOD. Only financial
transactions might happen (like ISO transactions) after the SOL completes CSOLOP. Hence
only financial exceptions are checked and can be overridden if they are set as exceptions and
user has work class to override. All exceptions set as errors need to be corrected for Central
EOD to proceed further.
a) EOD balance check - This checks the EOD minimum and EOD maximum balance
exceptions that are set at scheme level for all the SOLs in the given data center.
b) Account Balance not zero exception - This checks for the net sum of all the
accounts in the SOLs for the data center should be zero.
2.1.10 PROCESSES RUN DURING CENTRAL EOD.
1. Proxy post any transactions that are unposted
2. Stop uniserver transactions
3. Handover to Central standin server.
4. Bring down uniserver
5. Inter SOL reconciliation
6. End of day account/GL balances Updates
7. Running user defined Batch Jobs
8. Executing Site Specific Script
DATACENTER BEGINNING OF THE DAY
Central BOD is a process carried out at the beginning of each working day. It can be run at
the Service Outlet or the data center level. After running Central BOD, the BOD dates of all

Document
the Service Outlets in the Set will be incremented. While the process is being run, no user is
allowed to login to the Service Outlet Set except the user who is running Central BOD.
OPTION: CBOD
After running Central EOD, the BOD dates of all the SOLS in the SET will be incremented.
1. All the BOD jobs that operate on SET will be run in central BOD.
2. No users are allowed to login in the SOL set during this process except the user
who is running central BOD.
2.1.11 PRECONDITIONS FOR CENTRAL BOD
1. Central EOD of all Service Outlets in the Set should be over (there are occasions
where CEOD process is terminated/abandoned abruptly/intentionally. In those
cases it has to be restarted to complete CEOD for all the service outlets. Only
when the status is CEOD completed for all SOLs in the data center, then only
CBOD process can be initiated.

Document
2. All the Service Outlets in the Set should be running on the same BOD date. If the
Service Outlets are running on different BOD dates, then Central BOD cannot be
done for the Service Outlet Set.
2.1.12 PROCESSES DONE IN CENTRAL BOD
1. Creation of Financial daily transaction number sequence.
2. Running of user defined batch jobs
3. Execute site specific CBOD jobs
4. Change the BOD dates of all the SOLS to the next working date depending upon
the Calendar setup of each SOL.
5. Do BOD GST update for the SOLS that have marked holidays between EOD date
and the next working date. BOD GST updates will be done for those SOLS that
have marked been holidays before the next working date. This will insert records
into GST for the holidays.
6. Move records from Daily tables to Cumulative tables for the SOLS in the SOLSET.
Move future records to daily records for the next working date.
7. Send BOD message to CSIS
8. Bring up uniserver
9. Change Oracle passwords

Document
BEGINNING OF THE DAY FOR THE SERVICE OUTLET

The Service Outlet BOD is a process run by the user at a Service Outlet at the start of each
working day. No user is allowed to start transactions, financial or non-financial, before
ISOLOP is done. All the batch jobs specific to a Service Outlet should run during this process.
MENU OPTION: ISOLOP
1. Before branch BOD is done no users are allowed to start transactions, financial or
non-financial.
2. All the batch jobs specific to a SOL are run during this process.

Document
2.1.13 PRECONDITIONS FOR ISOLOP
1. Central BOD of the datacenter should be over.
2.1.14 JOBS EXECUTED DURING BRANCH BOD
1. Executing User Defined Batch Jobs
2. Enhancing TOD limits of accounts
3. Executing Standing Instructions
4. Running LA Create Demand
5. Executing site specific ISOLOP.site script
OPENING TRANSFER TRANSACTIONS

MENU OPTION: HOXFT

Document
Enter the sol id of the sol for which transfer transactions should be opened and commit
OPENING OF CASH TRANSACTION

MENU OPTION: HOCST
Enter the sol id of the sol for which cash transaction should be opened and commit.

Document
CLOSING OF TRANSFER TRANSACTION
MENU OPTION: HCXFT
Close the transfer transactions for the sol by entering the sol id and commit.
CLOSING OF CASH TRANSACTION
MENU OPTION: HCCST
Close the cash transactions of the sol by entering the sol id and commit.

Document
6.13 BATCH JOB EXECUTIONER (BJE MENU OPTION) &

USER DEFINED BJS JOBS:

Document
MENU OPTION: HBJE
The User Invoked BJS jobs can be run through the HBJE menu option. H BJE is the menu
option, which accepts Set Id (mandatory), From Job Id & To Job Id. This would help in
running User Invoked BJS jobs which may not be required to be run necessarily in EOD, BOD
or ABH & can be run anytime, thus helping in reduction of EOD / BOD / ABH time.
HBJE also accepts number of parallel jobs (default 10 jobs), which should be fired.
Benefit of this is, say, at a bank, if there are three nodes. Then three Sol Sets can be set up
& each Sol Set should have Sols proportional to the number of CPUs of the app-server. The
same job can be fired from three different nodes with different Set Id. A report
SOLID*******.OUT gets generated for each Sol Id.
For a BJS job, Invoking Process (exec_db_stat_code) can be set as ‘U’ (User Invoked) in
HBJSTM. This can be added with a new record, as well as modified in existing record.

Document
2.2 REINITIATING TRANSFER OF HISTORY

TRANSACTIONS
MENU: METOH
As a part of the begin of Day process, transactions records are moved from the daily
transaction table to the history Transaction table.
The movement process works as follows:

1) Drop CTD and CTH views
2) Drop ETD and ETH tables
3) Rename DTD to ETD and DTH to ETH
4) Recreate view CTD and CTH
4) Recreate DTD and DTH tables
5) Recreate indexes on DTD and DTH tables
6) Initiate transfer of records from
ETD to HTD and ETH to HTH in background
A table EST, which gets updated upon completion of each step to provide re-
startability.
The movement will be initiated in background and control will come to the
program immediately so that end of day operations can continue. The movement is
sol parallelized. To check the return status of the process, a script
“ETDtoHTDFailureCapture.scr” has been provided. This script internally calls a com

Document
script “ETDToHTDUserDefined.com” which can be used for customized action on

return of movement process. By default, this com script calls “mail” command to
send mail to concerned persons.
The menu option METOH has also been provided to reinitiate this transfer in
case it fails due to any reason. The menu option does not take any user input and
processes for all the sol ids. This menu needs to be invoked only if the process of
moving the history transaction during the Begin of Day is not completed.
2.3 VERIFICATION OF PREVIOUS DAY’S

TRANSACTIONS
MENU: PTV
Using the above menu, user can verify transactions of the previous period since TV will list
only transactions of the current day.

Document
2.4 CHANGING USER’S CONTEXT SOL

MENU: HCCS
During the End-of-day operations, sometimes it is required for the system operator to switch
SOLs to clear some transaction records. Using the menu option HCCS, user can change to
another SOL temporarily and work as if he/she is a user of that particular SOL.
This menu can be invoked only if the user tenor is Free at HUPM.
Also and script event has been provided to customize this menu to restrict user’s from
changing SOL depending upon various requirements. The script name is
HasBranchEODBODEnded.scr
2.5 TREATMENT OF UNPOSTED TRANSACTIONS

DURING EOD
During ABH and CSOLOP, if all the transactions are not posted, system gives the following
error, if appropriate exception is set in SCFM. :

Document
 ‘A LL TRANSACTIONS I NITIATED BY THE S ERVICE O UTLET ARE NOT POSTED ’
There are two menu options, one to delete all the unposted transaction (all legs in entered
status) and another to proxy post the partly posted transaction prior to ABH and CSOLOP.
2.5.1 HDTE – DELETE TRANSACTION IN ENTERED STATUS

This menu option is used to delete all the transactions in entered status. All the transactions
deleted will be reported in a separate report.
MENU OPTION: HDTE
This menu option will list all the transactions, which are eligible for deletion for a given SOL Id
(all records will be default selected). A script (ValidateTranForDelete.scr) is provided, where
user can decide/ filter out the records, which are not to be deleted. This script will be invoked
prior to listing of transaction.
 System can not distinguish between manually created transaction and system created
transaction. Hence all Transaction will be considered for deletion by default. However to avoid
deletion of system generated transaction make sure the ValidateTranForDelete.scr exist in script
directory.
2.5.2 PPT – PROXY POST TRANSACTION IN ENTERED STATUS

This menu option will proxy post all the transaction in entered status.

Document
MENU OPTION: HPPT
User can enter ‘Proxy Post Mode’ as ‘P’ – Normal post only(normal posting – similar to TM), 'Y'
for Proxy post only or 'B' for Both. All the transaction proxy posted will be reported in a
separate report. When the function is P, if any exceptions are there for posting a parttran
they remain in Entered status only.
A sample script (WABH.sscr) is provided to execute the following menu option in sequence.
1 HDTE – Delete Transaction In Entered Status
2 HPPT – Proxy Post Transaction In Entered Status
3 ABH – After Business Hours

Document
2.6 BACKGROUND QUEUE MAINTENANCE

MENU OPTION: BGJQM
Each user can fire any number of jobs in background during the normal operations. In this
case, the performance of online operations can be badly hit if lots of batch jobs starts running
during the same time.
The bank can control the number of batch jobs that can be fired in background during the
normal operation. This can be controlled using the feature called Background Queue. A new
table BG_QUEUE_TABLE has been defined that will contain a set of records for a defined
background queue. The number of records for a queue name is the number of concurrent
processes that can be run concurrently when the background jobs are executed via that
queue. A queue can also be assigned a value specifying the minimum user work class of the
user who can execute jobs in that queue. A new menu option BGJQM is the Maintenance
menu option for this table. The print parameter acceptance form has been modified to accept
a queue name when background execution is requested. By default the queue name
displayed is the value of the environment variable BGJ_QUEUE_NAME.
Whenever a batch job is fired in background, a dummy batch program bauu9500 is called
before execution of the actual batch program. It will check for a free queue record in

Document
BGJ_QUE table for the queue. Only after queue is obtained, it will proceed with execution of
the job in background. If bauu9500 cannot get a free BGJ_QUE record in 60 minutes, it gives
up the waiting, sends a message to Op Console and continues the execution of the job
without waiting for a free queue record. Also, the logout program (bauu9021) has been
enhanced to free the locked queue record in case of background execution. If a script called
BGJComplete.scr exists then it is executed with input (field name =”RetCode”) as the return
code of the background job. This script can be used to send a message to the user that the
batch job is complete.
Menu option BGJQM has been added to maintain BG_QUEUE_TABLE. The valid function codes
for this menu option are ‘A’ –Add, ‘L’ – List, ‘M’ – Modify ‘I’ – Inquire, ‘D’ – Delete and ‘U’ –
Unlock. Every queue has a header record with serial number ‘0000’. For example, if for a
queue, the number of records is 3, then there will be 3 records with the serial numbers ‘0000’
, ‘0001’ and ‘0002’ .
 In ADD mode, the fields to be entered are ‘Number of Streams’ which specifies the number
of records in the given
RELATED MENU OPTIONS

MENU OPTION DESCRIPTION
ABH Initiate After Business Hours Process
BGJQM Background Job Queue Maintenance
BJE Batch Job Executioner
BJSINQ Query on BJS table
BJSTI BJS Table Inquiry
HBJSTM BJS Table Maintenance
CBOD Initiate BOD Central Process
HCCS Change Context Service Outlet
HCCST Close Cash Transactions
CEOD Initiate EOD Central Process
CSOLOP Initiate SOL EOD Process
HCXFT Close Transfer Transactions
HDTE Delete Transaction In Entered Status
ISOLOP Initiate Service Outlet BOD Process
METOH Transaction record movement
HOCST Open Cash Transactions
HOXFT Open Transfer Transactions
HPPT Proxy Post Transaction In Entered Status
PTV Previous Day Transaction Verification
HRIST Reconcile Inter Service Outlet transactions

Document
SOLSTAT Check status of all the SOLs

SOLVAL Validations on a SOL before initiating the EOD/BOD related jobs
3 RELATED TABLES
There are no tables separately for End of day / Begin of Day data.
TABLE ABBR TABLE NAME

GCT SOL_GROUP_CONTROL_TABLE
SOL SERVICE_OUTLET_TABLE
BJS BATCH_JOB_SCHEDULER_TABLE
EST EOD_STATUS_TABLE
BATCH JOBS
All the Batch jobs are listed in the table below
# FILE NAME TYPE DESCRIPTION SR Create

NO Tran
1 asff0006 FORM Parameters For Asset Provisioning 1 Y
2 asfe3002 FORM System Asset Classification 1 N
3 asfe2007 FORM Asset Classification Report 1 N
4 babx4006 BATCH Update Account Dormancy Status 1 N
5 babx4025 BATCH Transfer to Overdue Deposits 1 Y
6 bafe3006 FORM Report Generation 1 N
7 bafe3027 FORM Cheque Book Report 1 N
8 bafe3029 FORM Stop Payment Report 1 N
9 bafe3032 FORM Batch Charges Calculation 1 Y
10 bafe3253 FORM Deferred Charges Calculation 2 Y
11 bafe3033 FORM Office Account Ledger Print 1 N
12 bafe3034 FORM Charges Register Print 1 N
13 bafe3035 FORM MS Transactions Ledger Print 1 N
14 bafe3037 FORM Pending Contra Transactions Report 1 N
15 bafe3039 FORM Income/Expenditure Register Print 1 N
16 bafe3041 FORM MS Outstanding Items Report 1 N
17 bafe3042 FORM Customer Master Register Print 1 N
18 bafe3044 FORM Account Master Print 1 N
19 bafe3048 FORM Deposits Account Balances List 1 N
20 bafe3048 FORM Deposits Account Details List 2 N
21 bafe3049 FORM Schemewise Distribution of Deposits 1 N
22 bafe3049 FORM Ratewise Distribution of Deposits 2 N
23 bafe3049 FORM Ratewise Distribution of Interest Paid 3 N
24 bafe3049 FORM Maturity Period Wise Distribution of 4 N

Document

NO Tran
Deposits
25 bafe3051 FORM Commission Accounts List 1 N
26 bafe3054 FORM TODs Register Printing 1 N
27 bafe3055 FORM Pass Sheet Print 1 N
28 bafe3057 FORM Resume Of Accounts 1 N
29 bafe3066 FORM Accounts Below Minimum Balance 1 N
30 bafe3070 FORM DAYBOOK Report Generation 1 N
31 bafe3211 FORM Customer Account Ledger Print 1 N
32 bafe3215 FORM Purchase Sale Entry 1 N
33 bafe3251 FORM Customer Becoming Major 1 N
34 bafe3254 FORM Deletion of User Defined Expired Liens 1 N
35 bafe3263 FORM Shortfall Recovery Process 1 Y
36 bafi2030 FORM Report on Partition A/cs 1 N
37 bafi2030 FORM Report on Partition A/cs History 2 N
38 baor5020 BATCH Accounts Opened During the Day 1 N
39 baor5021 BATCH Accounts Closed During the Day 1 N
40 baor5022 BATCH Mark Paid Cheques as Returned 1 N
41 baos3010.com SCRIPT Execute an O.S Command Procedure 1 N
42 bwaytran.com SCRIPT BankAway! Transaction Download 1 N
43 bwaydepo.com SCRIPT BankAway! Deposit Download 1 N
44 bwayloan.com SCRIPT BankAway! Loan Download 1 N
45 bwayschm.com SCRIPT BankAway! Scheme Download 1 N
46 bgfe3001 FORM PRR11A Quarterly Statement of 1 N
Guarantees
47 bgfe3002 FORM PRR11B Monitoring of Guarantees 1 N
48 bgfe3003 FORM PRR11C Statement of Guarantees 1 N
49 bgfe3004 FORM Guarantees Issued cum Liability Register 1 N
50 bgfe3005 FORM Deferred Payment Guarantee Register 1 N
51 bife3003 FORM Interest Calculation - Non Bill by Bill 1 Y
52 bife3004 FORM Balancing Report - Collection 1 N
53 bife3005 FORM Bills Register Report - Bills Purchased 1 N
54 bife3006 FORM Usance Bills Discounted 1 N
55 bife3007 FORM Balancing Report Bills Purchased 1 N
56 bife3008 FORM Co-accepted Bills 1 N
57 bife3009 FORM Interest Payed on Delayed Collection 1 N
58 bife3010 FORM Bills Dishonoured 1 N
59 bife3012 FORM Statistical Report on Bills 1 N
60 bife3013 FORM Large Amt Chqs Disc. - Daily Reporting 1 N
61 bife3014 FORM Bills Due Today But Unpaid 1 N
62 bife3015 FORM Bills Interest Collected Report 1 N
63 bife3016 FORM Advance Interest Collected Report 1 N
64 bife3020 FORM Large Amt Chqs Disc. - Monthly 1 N
Reporting
65 bife3021 FORM Bills Register Report - Collection 1 N
66 clfe3003 FORM Outward Clearing Schedule Print 1 N
67 clfe3003 FORM Outward Clearing Waste Print 2 N
68 clfe3012 FORM Inward Clearing Waste Print 1 N
69 clfe3012 FORM Inward Clearing Schedule Print 2 N

Document

NO Tran
70 clfe3029 FORM Outward Clearing Valuedate Report 1 N
71 csfe3004 FORM Shroff Cash Report 1 N
72 csfe3004 FORM Shroff Cash Report - All 2 N
73 csfe3005 FORM Cash Balance Report 1 N
74 dcfe5071 FORM Statement of Documentary Credit 1 N
75 fxfe3002 FORM Forward Contract Register 1 N
76 fxfe3004 FORM F/C Liability Register 1 N
77 fxfe4013 FORM Foreign Bills Export Claim Report 1 N
78 glfr5001 FORM Balancing Report Print 1 N
79 hcfe3007 FORM HO Summary Reports 1 N
80 hcfe3006 FORM Bar Inward Outward Register Print 1 N
81 hcfe3009 FORM HO Schedules Print 1 N
82 hcfe3010 FORM ABSOT Schedules Print 1 N
83 hcfe3011 FORM AGCL Schedules Print 1 N
84 hcfe3013 FORM Unresponded Transactions Report 1 N
85 ibbx4000 BATCH Create file to send to IBR center 1 N
86 tdfe3005 FORM Irregular Recurring Deposits Report 1 N
87 infe3003 FORM Inventory Status Report - All 1 N
88 infe3004 FORM Inventory Movement Report Print 1 N
89 lafe3006 FORM Agricultural Loans Master Sheet Print 1 N
90 lafe3007 FORM PSR29 - Agricultural Loans Return 1 N
91 lafe3008 FORM EI (Equated Instalments) Reports 1 N
92 lafe3254 FORM Batch Rephasement of EI Loans 1 N
93 lafe3255 FORM Loan Demands Overdue Reminder 1 N
94 lafe3258 FORM Loans Collection and Position Report 1 N
95 sife3001 FORM Standing Instructions Register 1 N
96 sife3002 FORM SIs Tried Today Report 1 N
97 sife3004 FORM advices for standing instruction 1 N
98 sife3005 FORM standing instructions covering letter 1 N
99 srfe3001 FORM System Substitution of Securities 1 N
100 tba_sql.com SCRIPT Run an SQL Script 1 N
101 rrfe3001 FORM PRR 2 : Monthly review of Irregular A/cs 1 N
102 rrfe3002 FORM PRR 25 : Report Of Rejected Cheques 1 N
103 rrfe3003 FORM PSR 49 : Quarterly statement on interest 1 N
A/c
104 rrfe3004 FORM PRR 38 : EOD Balance Report 1 N
105 rrfe3005 FORM PRR 12 : (OLD PR-12) Certificate 1 N
106 rrfe3006 FORM PSR 3/4 : Basic Statistical Returns I 1 N
107 rrfe3007 FORM PSR 11: Groupwise Advances 1 N
108 rrfe3008 FORM PSR 2 : Statement Of Deployment Of 1 N
Funds
109 rrfe3009 FORM PSR 32: Sanction Limits For Accounts 1 N
110 rrfe3010 FORM PSR 7 Advances Granted to Spec Commu 1 N
111 rrfe3011 FORM BSR 3: Advances to Selected Securities 1 N
112 rrfe3012 FORM PRR 8 : Credit And Review Programme 1 N
113 rrfe3013 FORM STR 19 :Insurence Covered Guarantee 1 N
Report
114 rrfe3015 FORM PRR 4B: Review of Deferred Payment 1 N
Guarantee

Document

NO Tran
115 rrfe3016 FORM PSR 16: Ratewise Dist. of 1 N
Dep./Adv./FCNR A/c
116 rrfe3017 FORM PRR 15: Sectorwise Advances to 1 N
Companies
117 rrfe3020 FORM STR 8 : List of Secured and Unsecured 1 N
Advances
118 rrfe3021 FORM STR 14: Advances to Companies 1 N
119 rrfe3022 FORM STR 11: RBI Statement 1 N
120 rrfe3023 FORM PSR 1: FLASH report 1 N
121 babx4008 BATCH Auto Renewal of Deposits 1 Y
122 asfe0010 FORM Credit Transaction Report For An Account 1 N
123 clor5016 BATCH Auto Regularization of Shadow Balance 1 Y
124 tdfe3003 FORM Flow Amt-wise Distribution of Deposits 1 N
125 bafe3072 FORM Sparrow Balance Downloading 1 N
126 bafe3072 FORM Sparrow Card Downloading 2 N
127 bafe3072 FORM Sparrow Card Status Downloading 3
128 bafe3072 FORM Sparrow Mini Statement Downloading 4 N
129 babx4043 BATCH Exchange Profit/Loss Calculation 1 Y
130 icbx4005 BATCH Batch Review Of Pegged Accounts 1 N
131 swbx0001 BATCH Transfer of SWIFT Messages 1 N
132 icfe3007 FORM Customer Interest Preferential and Peg 1 N
Report
133 prfe3004 FORM System Pointing Transactions Reversal 1 Y
134 icfe3008 FORM Interest Accrual for Accounts 1 N
135 icfe3008 FORM Interest Booking for Accounts 2 Y
136 icfe3008 FORM Interest Run for Accounts 3 Y
137 txfe3402 FORM TDS Calculation 1 Y
138 txfe3402 FORM TDS upload - Phase 1 2 N
139 bafe3267 FORM Deposit Flow Regeneration 1 N
140 ddfe3022 FORM Demand Draft Reports 1 N
141 ddfe3013 FORM Demand Draft Reports 1 N
142 mcbx4020 BATCH Bancs Remote - Download of tables 1 N
143 lafe3257 FORM Lien Processing for Loans 1 N
144 lafe3257 FORM Loans Demand Satisfaction Process 2 Y
145 babx4055 BATCH Auto Post Of Transactions 1 N
146 bafi2031 FORM Past Due Accounts Details Report 1 N

Document
MRTS/MRRS/SAMPLE REPORTS
ISTR - Inter Sol Transaction Report Inter Sol Transaction Report

Document
ISAR - INTER SOL AUDIT REPORT

Document
3.1 NON BUSINESS PARALLELISATION

REPORTING
A summary of how many records have been processed by each of the child processes can
also be obtained by setting an environment variable. The report will look like
SUMMARY LOG FOR EXE[ICBX4008] AND SOL[282]
BJS JOB ID [SBINT]
+---------------------------------------------------------------------------------+
|Process Id |Start Rec |End Num | Start time | End Time |
+---------------------------------------------------------------------------------+
| 90506| 1| 232| 05-09-2001 18:15:04| 05-09-2001 18:15:28|
+---------------------------------------------------------------------------------+
|Records Processed: 232 |
|STATUS: SUCCESSFUL. |
+---------------------------------------------------------------------------------+
| 91103| 233| 439| 05-09-2001 18:15:04| 05-09-2001 18:15:27|
+---------------------------------------------------------------------------------+
+---------------------------------------------------------------------------------+
| 89818| 440| 656| 05-09-2001 18:15:05| 05-09-2001 18:15:30|
+---------------------------------------------------------------------------------+
+---------------------------------------------------------------------------------+
| 81296| 657| 859| 05-09-2001 18:15:05| 05-09-2001 18:15:17|
+---------------------------------------------------------------------------------+
+---------------------------------------------------------------------------------+
| 90993| 860| 1061| 05-09-2001 18:15:05| 05-09-2001 18:15:24|
+---------------------------------------------------------------------------------+
+---------------------------------------------------------------------------------+
| 89701| 1062| 1106| 05-09-2001 18:15:05| 05-09-2001 18:15:06|
+---------------------------------------------------------------------------------+
|STATUS: ABORTED. |
|Following abort files have been generated: |
|ABRT.SUCAAAabM_4a00001.LST |
|ABRT.FAIAAAabM_4a00001.LST |
|ABRT.INTAAAabM_4a00001.LST |
+---------------------------------------------------------------------------------+
The order of the report is the order in which the child process is started. The report prints
details of when the process started and when it ended with number of records processed with
each of the child process. In case one of the child process aborts (with a fatal error or any
abnormal condition), it is listed in the summary file as aborted process with details about
the .LST files for that process.

Document
The Summary file gets generated for the entire program in case one of the child process
aborts abnormally.
At the end of all the processes, one consolidated report will be generated for all those
processes that have ended successfully i.e. have not given any fatal error. For all the
processes that have given fatal error, following file will remain in the working directory
ABRT*LST
The records that appear in these aborted files will not be there in the report indicating that
the process failed for these records. So if at the end, any such file appears in the working
directory, this means that a child process has given fatal error. This information will also be
present in the status file.

Document
4 FLASHBACK
As a part of daily operations there are certain operations that need to be carried out during
the beginning of day and End of Day. These are termed as EOD/BOD operations.
The EOD processes are executed as under:
ABH – After business hours

CSOLOP – Service out let end of day
CEOD – Central end of day
CBOD – Central beginning of day
ISOLOP – Service out let beginning of day
ABH is a not a mandatory option. CSOLOP will complete ABH before proceeding.
Batch jobs can be set, which can be executed during each of these operations. Batch jobs
are setup through HBJSTM menu option.
Exceptions can be set up in the HSCFM and GSPM menu options to warn the user about
incomplete processes before initiating the End of day operations.
*****{}*****

EOD&amp;BOD

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

EOD&amp;BOD

Încărcat de

Drepturi de autor:

Formate disponibile

ADMINISTRATOR TRAINING MANUAL

Document revision list

Ver.Rev Date Author Description

© 2006 Infosys Technologies Limited, Bangalore, India

All rights reserved by Infosys Technologies Limited,

No part of this volume may be reproduced or transmitted in any form or by any

EOD & BOD Ver. Rev 1.04 Page i

6.5 END OF THE DAY FOR THE SERVICE OUTLET..................................................30

EOD & BOD Ver. Rev 1.04 Page ii

EOD & BOD Ver. Rev 1.04 Page 1

1.1 PROCESS DIAGRAM

EOD & BOD Ver. Rev 1.04 Page 2

1.2 TERMINOLOGY EXPLAINED

1.2.1 NON BUSSINESS PARALLELISATION (NBP)

The following critical jobs have been enabled for NBP:

EOD & BOD Ver. Rev 1.04 Page 3

DBA RELATED ACTIVITIES

INITIAL SET-UP- OPERATING SYSTEM LEVEL

1.2.3 ENVIRONMENT VARIABLES

EOD & BOD Ver. Rev 1.04 Page 4

user who has initiated the process of ABH.

$TBA_TRACE_DIR/messages/<BOD date>/<Sol Id>

1.2.4 ENVIRONMENT VARIABLES FOR NBP

Details about the environment variables are given below.

FORMAT OF THESE VARIABLES

These environment variables have the following format:

1. For enabling parallelisation of a job for a particular sol:

3. For enabling summary log for a job for a particular sol

EOD & BOD Ver. Rev 1.04 Page 5

VALUES OF THESE ENVIRONMENT VARIABLES

EOD & BOD Ver. Rev 1.04 Page 6

SETTING UP OF THESE ENVIRONMENT VARIABLES

These environment variables can be set up in commonenv.com or in the script hooks

EOD & BOD Ver. Rev 1.04 Page 7

INITIAL SET-UP - APPLICATION LEVEL

EOD & BOD Ver. Rev 1.04 Page 8

Exceptions set at Group level:

 Transaction Pending authorisation

EOD & BOD Ver. Rev 1.04 Page 9

 Exceptions set at GSPM – Currency details

1.2.7 HSCFM SETUP

MENU HSCFM: DATA CENTER DETAILS

O N R EGULARIZATION TOD , A PPLY INTEREST :

1.2.8 SETTING UP OF SOL PRIORITY

EOD & BOD Ver. Rev 1.04 Page 10

1.2.9 SOL SUBMISSION FOR CLOSE SOL OPERATION

EOD & BOD Ver. Rev 1.04 Page 11

SETTING UP OF BATCH JOBS

The Batch job can be set-up to be executed in the following operations

 L SOL BOD PROCESS

 T SOL EOD PROCESS

 A AFTER BUSINESS HOURS

 E CENTRAL EOD PROCESS

 U User Invoked Process

Batch jobs in Finacle are classified as jobs

EOD & BOD Ver. Rev 1.04 Page 12

MENU OPTION: HBJSTM

SUB-OPTION: P-PARAMETER DETAILS

EOD & BOD Ver. Rev 1.04 Page 13

 Not all batch jobs need the parameter details.

EOD & BOD Ver. Rev 1.04 Page 14

1.2.10 DATE MNEMONICS IN BATCH JOBS

The following mnemonics are provided.

Date Mnemonic Remarks

EOD&BOD

EOD&BOD