Beruflich Dokumente
Kultur Dokumente
CLOSE OF BUSINESS
• Introduction to COB
• Stages in COB
• Features in COB
• Configuring COB
INTRODUCTION
Execution of jobs in
A-S-R-D order
SEP0010001 14th July 2008 15th July 2008 13th July 2008
SEP0010001-COB 13th July 2008 14th July 2008 12th July 2008
Dates Record during COB process
• TSA.SERVICE
• TSA.WORKLOAD.PROFILE
• TSA.PARAMETER
• TSA.STATUS
TSA.WORKLOAD.PROFILE
ID - Anything
AGENTS.REQUIRED - Number of tSAs to dedicate 0-N
TSA.WORKLOAD.PROFILE
The maximum number of agents that will be supported is
mentioned in the SPF
TSA.WORKLOAD.PROFILE
The number of tSA to be dedicated would be specified in
AGENTS.REQUIRED field
TSA.PARAMETER
This file enables the tSM to monitor the tSAs at fixed intervals of time
This is done by two important fields
• REVIEW.TIME
Specifies the number of seconds the tSM will sleep before reviewing
the tSA.SERVICEs,
• DEATH.WATCH
Specifies the maximum number of seconds allowed for an agent to
report to the tSM.
TSA.PARAMETER
TSA.SERVICE
To initiate a COB, record ‘TSM’ in TSA.SERVICE needs to be
started
TSA.SERVICE
To initiate the COB service, the record ‘COB’ in
TSA.SERVICE has to be marked for Starting.
TSA.SERVICE
• After marking service control as ‘START’ for TSM and TSA , open
necessary sessions.
• Every job during the Close Of Business uses a LIST file for
storing and sharing the records for processing between
different agents.
• Name of the List file have format like this
F<company mnmonic>.JOB.LIST.<agent no>
Example:
FBNK.JOB.LIST.1
COMO
• It gives the details for each job (Start time, End time, Records
processed and Records selected and time taken for processing
each record)
COB.MONITOR (use Reflection)
• COB.PROGRESS.DISPLAY
• ================================================================================
• ==========
• TIME : 12:22:27 08 MAR 2010 COB-DATE :
• COB Running in
• ================================================================================
• ==========
• STAGE PROGRESS PROCESSED TOTAL %
• COMPLETED
• ================================================================================
• ==========
• APPLICATION [ ] 0 65
• 0.00
• SYSTEM WIDE [ ] 0 32
• 0.00
• REPORTING [ ] 0 52
• 0.00
• START OF DAY [ ] 0 43
• 0.00
• ONLINE [ ] 0 28
• 0.00
• ================================================================================
• ==========
• COB [ ] 0 220
• 0.00
ERROR HANDLING
• In case of less severe errors, updates the record for the current
batch run and the current company on the EB.EOD.ERROR
file and continues.
ERROR HANDLING
EB.EOD.ERROR
EB.EOD.ERROR.DETAIL
SUMMARY
• OBJECTIVES
To Understand the Multi Threading Concept.
It’s a core Globus subroutine that actually writes the list of ids
on to the LIST file. It takes in 2 parameters, the name of the
LIST file and the variable that holds the ids.
SUBROUTINE MULTI.RTN.SELECT
$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_MULTI.RTN.COMMON
SEL.CMD=“SELECT “:FN.CUSTOMER
CALL EB.READLIST(SEL.CMD,SEL.LIST,’’,NO.OF.REC.SEL.ERR)
CALL BATCH.BUILD.LIST(‘ ’,SEL.LIST)
RETURN
END
STEP 5
Write a routine MULTI.RTN that will process all the ids
selected.
• Now run the COB and Check whether the Multi threaded
routine gets invoked and the code is working or not.
Summary
When a single process can be executed by more than one
processor, the process is said to be multi-threaded.
BATCH.JOB.CONTROL is the Globus subroutine that
makes multi threading possible in Globus.
The xxx.SELECT routine will form a key only file containing
all the ids which need to be processed by this job.
THANK YOU…