[T24] EOD duration taking 5 hours

awr

unread,

Aug 27, 2008, 12:17:48 PM8/27/08

to jBASE

Hello all,

I am working with G13 and jBASE 4.0 since a month I am facing problem
with EOD duration it takes me 5 hours to completed could somebody
assist me in advicing what could be the problem as I am doing resizing
of the files on a weekly basis.

many thanks in advance.

Regards,
Wahid

Jim Idle

unread,

Aug 27, 2008, 12:25:43 PM8/27/08

to jB...@googlegroups.com

On Wed, 2008-08-27 at 09:17 -0700, awr wrote:

Hello all,

I am working with G13 and jBASE 4.0 since a month I am facing problem
with EOD duration it takes me 5 hours to completed could somebody
assist me in advicing what could be the problem as I am doing resizing
of the files on a weekly basis.

Are you sure this is 4.0 and G13? I believe that at the level there things wrong with dictionary items in Globus that caused select to slow down. You should use the jcover/jprof tools to find out what the system is doing, but I bet that it is a select somewhere. If you can, you should target getting on to jBASE 5 and T24.

Abdul Wahid

unread,

Aug 27, 2008, 12:34:34 PM8/27/08

to jB...@googlegroups.com

Thank you dear, for the prompt response but could you please further advice how to process the monitor with the mentioned tools as I am not too good with jBASE and if this would be a SELECT how to get it solved.

Thanks once again.

Regards,

Rasuli

ADENIYI KAREEM

unread,

Aug 27, 2008, 1:32:26 PM8/27/08

to jB...@googlegroups.com

Hi Abdul,

upgrade your jbase 4.0 to jbase 4.1 ... i bet it will increase performance .... especially on G13...

infact... u are suppose to be on jBase 4.1 especially if you are on APR or DEC SP of G13....

regards,

'Niyi Kareem

On Wed, Aug 27, 2008 at 5:34 PM, Abdul Wahid <wahid....@fmfb.com.af> wrote:

Thank you dear, for the prompt response but could you please further advice how to process the monitor with the mentioned tools as I am not too good with jBASE and if this would be a SELECT how to get it solved.

Thanks once again.

Regards,

Rasuli

From: jB...@googlegroups.com [mailto:jB...@googlegroups.com] On Behalf Of Jim Idle
Sent: Wednesday, August 27, 2008 9:26 PM
To: jB...@googlegroups.com
Subject: Re: [T24] EOD duration taking 5 hours

On Wed, 2008-08-27 at 09:17 -0700, awr wrote:

--
'Niyi Kareem
IT Consultant
P.O.Box 1006
Satellite Town,
Lagos,Nigeria
+2348023382844

Road Jogger

unread,

Aug 28, 2008, 9:06:54 AM8/28/08

to jB...@googlegroups.com

Wahid,

Run BATCH.TIMES & this will tell you the time taken by each batch job.... if not you can also use JOB.TIMES... but i dont remember exactly if JOB.TIMES is there in G13....

Narayan

Abdul Abdul

unread,

Aug 29, 2008, 12:41:37 AM8/29/08

to jB...@googlegroups.com

Hi Narayan,

I looked at the BATCH.TIMES there is 2 batch job taking 1 hour each (FMFB.R1PB.SOD, AC.STMT.UPDATE) I am attaching the BATCH.TIMES here kindly look at it and advice.

I have plan to migrate to jBASE 4.1 but later in the year.

many thanks in advance.

Regards,
Wahid

BATCH.TIMES 20080828.txt

Road Jogger

unread,

Aug 29, 2008, 3:36:04 AM8/29/08

to jB...@googlegroups.com

Wahid,

From your batch times, ypur overall eod time is 3+ hours... out of which AC.STMT.UPDATE & FMFB.R1PB.SOD take about an hour+ each...

1. Did you add any local jobs to AC.STMT.UPDATE???

2. FMFB.R1PB.SOD --> what exactly is this batch process doing??? Pls. explain.

Regards,

Narayan

BATCH.TIMES FMFB Tajikistan (Live) 29 AUG 08 Batch times report Page 1
Area Head Office No. 1000 Printed at 29 AUG 2008 09:24:41
To Dushanbe Dushanbe HO

------------------------------------------------------------------------------------------------------------------------------------

| | | |
| START | END ELAPSED
| | | |
------------------------------------------------------------------------------------------------------------------------------------
| | | |
APPLICATION | | | |
| | | |
UNAUTH.PROCESSING 21:48:23 21:48:33 00:00:10
AC.CLOSED.ACCT.CONV 21:48:33 21:48:33 00:00:00
ACCT.RATE.CHANGE 21:48:33 21:48:34 00:00:01
CRF.SELF.BAL.UPD 21:48:34 21:48:34 00:00:00
EB.BROWSER.CLEAR.LOCKS 21:48:34 21:48:35 00:00:01
EB.LIMIT.TXNS.INSPECT 21:48:35 21:48:35 00:00:00
ST.EOD.GROUP.FIX 21:48:35 21:48:36 00:00:01
RE.BUILD.CONT.EXTRACT 21:48:36 21:48:36 00:00:00
PD.EOD.PRE.PROCESS 21:48:36 21:48:37 00:00:01
PM.SET.ONITE.ACTION 21:48:37 21:48:37 00:00:00
TT.END.OF.DAY 21:48:37 21:48:37 00:00:00
AC.CHG.REQ.EOD 21:48:38 21:48:38 00:00:00
BR.END.OF.DAY 21:48:38 21:48:38 00:00:00
EB.DUPLICATE.EOD 21:48:38 21:48:38 00:00:00
EB.UNAU.INSTL 21:48:38 21:48:39 00:00:01
EB.UNAU.OTHERS 21:48:39 21:48:39 00:00:00
EOD.DATA.CAPTURE 21:48:39 21:48:41 00:00:02
FT.END.OF.DAY 21:48:41 21:48:43 00:00:02
FX.END.OF.DAY 21:48:43 21:48:46 00:00:03
GIC.LD.STATIC.UPDATE 21:48:46 21:48:46 00:00:00
LD.END.OF.DAY 21:48:46 21:53:48 00:05:02
PL.MOVE.TO.AL 21:53:48 21:53:48 00:00:00
RMB.TT.BAL 21:53:49 21:53:49 00:00:00
STOCK.ARCHIVE 21:53:49 21:53:49 00:00:00
CHEQUE.COLLECTION 21:53:49 21:53:50 00:00:01
COLLATERAL 21:53:50 21:53:50 00:00:00
FX.EOD.UPDATE.STATIC 21:53:50 21:53:50 00:00:00
PD.END.OF.DAY 21:53:51 22:02:08 00:08:17
CARD.CHEQUE.EOD 22:02:08 22:02:09 00:00:01
EB.APPLICATION.TIDY.UP 22:02:09 22:02:10 00:00:01
EB.FREE.MESSAGE.CLEAR 22:02:10 22:02:10 00:00:00
REPORT.PRINT.APPLICATION 22:02:10 22:07:56 00:05:46

Total time for all processes in stage : APPLICATION = 00:19:30
Actual elapsed time for stage = 00:19:33

BATCH.TIMES FMFB Tajikistan (Live) 29 AUG 08 Batch times report Page 2
Area Head Office No. 1000 Printed at 29 AUG 2008 09:24:41
To Dushanbe Dushanbe HO

------------------------------------------------------------------------------------------------------------------------------------

| | | |
| START | END ELAPSED
| | | |
------------------------------------------------------------------------------------------------------------------------------------
| | | |
SYSTEM WIDE | | | |
| | | |
EOD.FT.TAPES 22:07:56 22:07:56 00:00:00
SYSTEM.END.OF.DAY1 22:07:56 22:08:02 00:00:06
SYSTEM.END.OF.DAY2 22:08:02 22:08:05 00:00:03
SYSTEM.LIMIT.EOD1 22:08:05 22:08:09 00:00:04
EOD.CUST.CHARGE 22:08:09 22:08:09 00:00:00
SYSTEM.END.OF.DAY3 22:08:09 22:11:15 00:03:06
GROUP.ACCRUAL.EOD 22:11:15 22:11:17 00:00:02
SYSTEM.COLLATERAL 22:11:17 22:11:17 00:00:00
SYSTEM.LIMIT.EOD 22:11:18 22:15:50 00:04:32
ACCOUNT.OVERDRAWN 22:15:50 22:15:54 00:00:04
PD.SYS.END.OF.DAY 22:15:54 22:15:55 00:00:01
SYSTEM.END.OF.DAY5 22:15:55 22:17:11 00:01:16
STMT2.FILE.UPDATE 22:17:12 22:17:12 00:00:00
TELLER.PASSBOOK.STMT 22:17:12 22:17:13 00:00:01
RE.CONTRACT.UPDATE 22:17:13 22:17:14 00:00:01
EOD.RE.BASE.CCY.CRF 22:17:14 22:17:14 00:00:00
PM.EOD2 22:17:15 22:17:15 00:00:00
AC.STMT.UPDATE 22:17:15 23:20:07 01:02:52
REINTEGRATE.POSITIONS 23:20:07 23:20:08 00:00:01
CUS.ALLOCATION.EOD 23:20:08 23:20:08 00:00:00
REPORT.PRINT.SYSTEM 23:20:08 23:20:50 00:00:42

Total time for all processes in stage : SYSTEM WIDE = 01:12:51
Actual elapsed time for stage = 01:12:54

BATCH.TIMES FMFB Tajikistan (Live) 29 AUG 08 Batch times report Page 3
Area Head Office No. 1000 Printed at 29 AUG 2008 09:24:41
To Dushanbe Dushanbe HO

------------------------------------------------------------------------------------------------------------------------------------

| | | |
| START | END ELAPSED
| | | |
------------------------------------------------------------------------------------------------------------------------------------
| | | |
REPORTING | | | |
| | | |
AC.REPORTS 23:20:50 23:20:50 00:00:00
EB.ACCT.TRIAL.BAL 23:20:50 23:20:50 00:00:00
EB.RE.BALANCE.PRINT 23:20:50 23:20:51 00:00:01
COLLATERAL.COMPENSATION 23:20:51 23:20:51 00:00:00
EB.PRINT.TRIAL.BALANCE 23:20:51 23:20:51 00:00:00
EB.CONSOL.PRINT 23:20:51 23:20:51 00:00:00
EB.PRINT 23:20:51 23:20:51 00:00:00
EB.REC.PRINT 23:20:51 23:20:51 00:00:00
EB.STAT.PRINT 23:20:52 23:20:52 00:00:00
JOURNAL.PRINT 23:20:52 23:20:52 00:00:00
LIMIT.COLLATERAL.REPORTS 23:20:52 23:20:52 00:00:00
RE.STAT.MISMATCH 23:20:52 23:20:52 00:00:00
USER.CUSTOMISED.REPORTS 23:20:52 23:20:52 00:00:00
RE.PRINT.DEAL.RPT 23:20:52 23:20:53 00:00:01
FX.JOURNAL 23:20:53 23:20:53 00:00:00
REGEN.CRF.ACCOUNT 23:20:53 23:20:53 00:00:00
REGEN.CRF.AL 23:20:53 23:20:53 00:00:00
REGEN.CRF.ALL 23:20:53 23:20:53 00:00:00
REGEN.CRF.ASST.LIAB 23:20:53 23:20:53 00:00:00
REGEN.CRF.FOREX 23:20:54 23:20:54 00:00:00
REGEN.CRF.LD 23:20:54 23:20:54 00:00:00
REGEN.CRF.MG 23:20:54 23:20:54 00:00:00
REGEN.CRF.MM 23:20:54 23:20:54 00:00:00
REGEN.CRF.PD 23:20:54 23:20:54 00:00:00
REGEN.CRF.PRFT.LOSS 23:20:54 23:20:54 00:00:00
REGEN.CRF.SC 23:20:55 23:20:55 00:00:00
REGEN.CRF.RVL.PRT 23:20:55 23:20:55 00:00:00
RE.CRB.EXPORT 23:20:55 23:20:55 00:00:00
RE.UPD.LINE.BAL.MVMT 23:20:55 23:21:59 00:01:04
EM.B.F2.REPORT 23:21:59 23:23:08 00:01:09
FIN.CYCLE.DATA 23:23:08 23:23:09 00:00:01
RE.EM.E.F3.REP 23:23:09 23:23:17 00:00:08
PM.CYCLE.DATA 23:23:17 23:23:17 00:00:00
CCY.CYCLE.DATA 23:23:18 23:23:19 00:00:01
RE.REPRINT.DEAL.RPT 23:23:19 23:23:19 00:00:00
SYSTEM.REPORTS 23:23:19 23:23:19 00:00:00
REPORT.PRINT.REPORTING 23:23:19 23:24:30 00:01:11

Total time for all processes in stage : REPORTING = 00:03:36
Actual elapsed time for stage = 00:03:40

BATCH.TIMES FMFB Tajikistan (Live) 29 AUG 08 Batch times report Page 4
Area Head Office No. 1000 Printed at 29 AUG 2008 09:24:41
To Dushanbe Dushanbe HO

------------------------------------------------------------------------------------------------------------------------------------

| | | |
| START | END ELAPSED
| | | |
------------------------------------------------------------------------------------------------------------------------------------
| | | |
START OF DAY | | | |
| | | |
DATE.CHANGE 23:24:30 23:24:32 00:00:02
SYS.FILE.TIDY.UP 23:24:32 23:24:34 00:00:02
CUS.FILE.TIDY.UP 23:24:34 23:24:35 00:00:01
FILE.TIDY.UP 23:24:35 23:45:28 00:20:53
EB.CHG.COM.SOD 23:45:28 23:45:29 00:00:01
SYSTEM.LIMIT.SOD 23:45:29 23:45:30 00:00:01
LD.START.OF.DAY 23:45:30 23:45:43 00:00:13
SA.START.OF.DAY 23:45:43 23:45:43 00:00:00
CUST.AGE.UPD 23:45:43 23:45:44 00:00:01
GIC.CUST.AGE.UPD 23:45:44 23:45:45 00:00:01
BUILD.POSITION.TABLE 23:45:45 23:45:45 00:00:00
ACSW.START.OF.DAY 23:45:45 23:45:46 00:00:01
FT.START.OF.DAY 23:45:46 23:45:52 00:00:06
FX.START.OF.DAY 23:45:52 23:45:55 00:00:03
TU.TC.SOD 23:45:55 23:45:55 00:00:00
MM.START.OF.DAY 23:45:55 23:45:55 00:00:00
PD.START.OF.DAY 23:45:55 23:49:24 00:03:29
FMFB.R1PB.SOD 23:49:24 00:46:23 00:56:59
AC.START.OF.DAY 00:46:24 00:46:26 00:00:02
PS.STOP 00:46:26 00:46:26 00:00:00
PURGE.HOLD.RPTS 00:46:26 00:46:27 00:00:01
PH.LOG.EOD 00:46:27 00:46:27 00:00:00
PM.BATCH.START 00:46:27 00:46:27 00:00:00
EOD.PM.REPORTS 00:46:27 00:46:27 00:00:00
SYSTEM.START.OF.DAY 00:46:27 00:46:28 00:00:01
EB.CLEAN.COMOS 00:46:28 00:46:28 00:00:00
STARTUP 00:46:28 00:46:29 00:00:01
REPORT.PRINT.SOD 00:46:29 01:03:36 00:17:07

Total time for all processes in stage : START OF DAY = 01:39:05
Actual elapsed time for stage = 01:39:06

BATCH.TIMES FMFB Tajikistan (Live) 29 AUG 08 Batch times report Page 5
Area Head Office No. 1000 Printed at 29 AUG 2008 09:24:41
To Dushanbe Dushanbe HO

------------------------------------------------------------------------------------------------------------------------------------

| | | |
| START | END ELAPSED
| | | |
------------------------------------------------------------------------------------------------------------------------------------
| | | |
ONLINE | | | |
| | | |
ONLINE 01:19:18 01:19:24 00:00:06
CO.ONLINE 01:19:24 01:19:24 00:00:00
DE.ONLINE 01:19:24 01:19:24 00:00:00
REPORT.PRINT.ONLINE 01:19:25 01:19:25 00:00:00

Total time for all processes in stage : ONLINE = 00:00:06
Actual elapsed time for stage = 00:00:07

BATCH.TIMES FMFB Tajikistan (Live) 29 AUG 08 Batch times report Page 6
Area Head Office No. 1000 Printed at 29 AUG 2008 09:24:41
To Dushanbe Dushanbe HO

------------------------------------------------------------------------------------------------------------------------------------

***************************************
* *
* TOTAL PROCESS EOD TIME = 03:15:08 *
* *
* TOTAL ELAPSED EOD TIME = 03:15:20 *
* *
* TOTAL PROCESS O/L TIME = 00:00:00 *
* *
* TOTAL ELAPSED O/L TIME = 00:00:00 *
* *
***************************************

Abdul Abdul

unread,

Aug 30, 2008, 2:19:02 PM8/30/08

to jB...@googlegroups.com

Hi Narayan,

No we did not add any local jobs to AC.STMT.UPDATE and under this BATCH JOB the below are mapped with frequency to run on daily basis.

AC.BAL.REFER

PRINT.ACCOUNT.STMT

DELETE.CLOSED.ACCOUNTS

DELETE.CLOSED.ACCOUNTS.POST

EOD.AC.VIOLATIONS

ACCT.STMT.MT942.RESET (This job runs at the end of the year 31^st Dec 08)

As for the FMFB.R1PB.SOD please see the below which I took copy during the EOD, when the EOD is reaching at this stage then its taking more than an hour for selecting of the followings;

Time 21:56:59

21:56:59 RMB.ACCOUNT.LIST.SOD @RMB.ACCOUNT.LIST.ACCOUNT

Time 21:56:59 SELECT FBNK.CURRENCY

Time 21:56:59

Time 21:57:00 SELECT FBNK.RMB.ACCOUNT.LIST.TURN

Time 21:57:16

Time 21:57:24 SELECT FBNK.ACCT.ENT.LWORK.DAY

Time 21:57:24

Time 21:58:32 SELECT FBNK.CATEG.ENT.LWORK.DAY

Time 21:58:33

Time 22:47:36 SELECT FBNK.CONSOL.ENT.LWORK.DAY

Time 22:47:36

Thanks alot for you kind advice on this matter.

Regards,
Wahid

Luis Lascano

unread,

Sep 18, 2008, 9:21:56 AM9/18/08

to jB...@googlegroups.com

Wahid,

On AC.STMT.UPDATE BATCH, heaviest job is PRINT.ACCOUNT.STMT so you have to verify volumes on account statements generated on a daily basis. It could be the case that you have a high transactional Globus environment (+ 1000 txns per day per account) that makes that job slow.

If that is not the case then you could have a problem with jBase files in terms of access time as consequence of bad resizing parameters or similar.

On you local batch FMFB.R1PB.SOD by reviewing the COMO, selections are made fast but after FBNK.CATEG.ENT.LWORK.DAY selection there is a considerable time taken by process and probably is related with data manipulation done inside program. For this case you should check what is program actually doing and if possible, to put some print flags that makes you figure out where is the bottleneck.

Regards,

Luis

skype: llascano

From: jB...@googlegroups.com [mailto:jB...@googlegroups.com] On Behalf Of Abdul Abdul
Sent: Saturday, 30 August, 2008 1:19 PM
To: jB...@googlegroups.com
Subject: Re: [T24] EOD duration taking 5 hours

Hi Narayan,

concern shoko

unread,

Sep 19, 2008, 6:16:24 AM9/19/08

to jB...@googlegroups.com

Hi Wahid,

I recently had a problem with AC.STMT.UPDATE on G12 and Universe. It
turned out that my Inter-company Settlements Suspense Accounts were
taking almost 2 Hrs to generate statements. I just flagged the
accounts not to generate the statements (did i really need them?!). So
check if there are no suspense accounts generating "un-wanted"
statements.

Regards
Concern
+263-912 271 566

On 9/18/08, Luis Lascano <luisl...@gmail.com> wrote:
> Wahid,
>
>
>
> On AC.STMT.UPDATE BATCH, heaviest job is PRINT.ACCOUNT.STMT so you have to
> verify volumes on account statements generated on a daily basis. It could be
> the case that you have a high transactional Globus environment (+ 1000 txns
> per day per account) that makes that job slow.
>
> If that is not the case then you could have a problem with jBase files in
> terms of access time as consequence of bad resizing parameters or similar.
>
>
>
> On you local batch FMFB.R1PB.SOD by reviewing the COMO, selections are made
> fast but after FBNK.CATEG.ENT.LWORK.DAY selection there is a considerable
> time taken by process and probably is related with data manipulation done
> inside program. For this case you should check what is program actually
> doing and if possible, to put some print flags that makes you figure out
> where is the bottleneck.
>
>
>
> Regards,
>
>
>
> Luis
>
> skype: llascano
>
>
>
> _____
>

> PL.MOVE.TO.AL <http://pl.move.to.al/> 21:53:48

> REGEN.CRF.AL <http://regen.crf.al/> 23:20:53

> 23:20:53 00:00:00
> REGEN.CRF.ALL 23:20:53 23:20:53 00:00:00
> REGEN.CRF.ASST.LIAB 23:20:53 23:20:53 00:00:00
> REGEN.CRF.FOREX 23:20:54 23:20:54 00:00:00
> REGEN.CRF.LD 23:20:54 23:20:54 00:00:00

> REGEN.CRF.MG <http://regen.crf.mg/> 23:20:54

> 23:20:54 00:00:00

> REGEN.CRF.MM <http://regen.crf.mm/> 23:20:54

> 23:20:54 00:00:00
> REGEN.CRF.PD 23:20:54 23:20:54 00:00:00
> REGEN.CRF.PRFT.LOSS 23:20:54 23:20:54 00:00:00

> REGEN.CRF.SC <http://regen.crf.sc/> 23:20:55

Reply all

Reply to author

Forward