ASG Technical Guide

Product Analysis and Customer Support
Application Specialist Group

Technical Guide
ASG Technical Guide
Table of Contents
Document History....................................................................................................................................... 4
1. Introduction......................................................................................................................................... 5
2. COB / EOD issues.............................................................................................................................. 5
2.1 Some basic points on COB / EOD.................................................................................................... 5
Single Threaded /Multi-threaded job................................................................................................... 5
PROCESS.STATUS or JOB.STATUS................................................................................................ 6
Flow chart of a multi-threaded job....................................................................................................... 7
2.2 Basic Information required in case of COB/EOD Crash...................................................................8
Irrespective of T24 release.................................................................................................................. 8
Information Specific to T24/Globus release:.......................................................................................8
3. LOCKS & Process information.......................................................................................................... 11
3.1 LOCKS..................................................................................................................................... 12
SHOW-ITEM-LOCKS........................................................................................................................ 12
jRLA.................................................................................................................................................. 12
jDLS.................................................................................................................................................. 15
LOCKS in UNIVERSE....................................................................................................................... 16
3.2 Process Information................................................................................................................. 16
WHERE............................................................................................................................................ 16
MW42 (My WHERE)......................................................................................................................... 17
ps -ef................................................................................................................................................. 18
PORT.STATUS.................................................................................................................................. 18
3.3 Unlock or kill a process................................................................................................................... 18
4. File corruption and Maintenance....................................................................................................... 19
4.1 File Corruption in Universe environment (fixtool)............................................................................19
4.2 File Resize in Universe environment (RESIZE)..............................................................................20
4.3 File Corruption in jBASE environment (jcheck)...............................................................................21
4.4 File Resize in jBASE environment (jRF).........................................................................................23
4.5 File corruption - JR files.................................................................................................................. 24
4.6 File corruption of Sensitive files – New file creation........................................................................25
Procedure to Create New file for STMT.ENTRY:...............................................................................26
2 Product Analysis and Customer Support

ASG Technical Guide
Procedure to create new file for CATEG.ENTRY:.............................................................................26

Procedure to create new file for RE.CONSOL.SPEC.ENTRY:..........................................................27
Procedure to create new file for DE.O.HANDOFF............................................................................27
4.7 File Distribution............................................................................................................................... 28
5. Correction Routines & Utilities.......................................................................................................... 28
6. Browser Issues................................................................................................................................. 32
6.1 Setup Files............................................................................................................................... 32
7. Oracle related................................................................................................................................... 32
7.1 Basics of Oracle....................................................................................................................... 32
7.2 Some commonly reported Oracle errors..................................................................................34
7.3 Procedure to increase oracle tablespace.................................................................................39
7.4 INITRANS................................................................................................................................. 40
8. OS related issues.............................................................................................................................. 41
8.1 Available memory exceeded in Universe..................................................................................41
8.2 Memory error in jBASE (Ulimit)....................................................................................................... 44
8.3 LDR_CNTRL for AIX Machine.................................................................................................. 45
8.4 OS Tools......................................................................................................................................... 46
9 Performance issues.......................................................................................................................... 48
9.1 SEAT.............................................................................................................................................. 48
9.2 TEC................................................................................................................................................ 48
10 Installation Procedure.................................................................................................................... 48
Procedure to Upgrade, install Service Pack, Patch, Product in lower release..................................48
Procedure to Upgrade, install Product in higher release...................................................................48
Procedure to install an Update.......................................................................................................... 49
11 Miscellaneous................................................................................................................................ 49
11.1 Release Information...................................................................................................................... 49
11.2 FTP commands........................................................................................................................ 51
11.3 DUMMY SELECT......................................................................................................................... 53
11.4 ERRMSG.................................................................................................................................. 54
11.5 Disk Space............................................................................................................................... 54
11.6 Steps to bypass & Rerun in lower release G13........................................................................54
11.7 Procedure for Single Sided DC................................................................................................ 55
11.8 JEDI_SHM_WORKFILE Corruption......................................................................................... 55

ASG Technical Guide
11.9 jBASE Printer setup and jspool corruption...............................................................................55

11.10 Procedure to Catalog Object Code.......................................................................................56
Procedure in jBASE.......................................................................................................................... 56
Procedure in Universe...................................................................................................................... 56
11.11 Segmentation Violation......................................................................................................... 56
11.12 Universe Commands............................................................................................................ 56
11.13 Server Restart...................................................................................................................... 56
11.14 Frequently used commands........................................................................................................ 57
12 Conclusion.......................................................................................................................................... 57

ASG Technical Guide
Document History
Change Description /
S.N0 Version Issue Date Issued By Approved By
Comments
1 1.0 14/10/2012 Initial Draft T. Aseel

ASG Technical Guide
1.Introduction
This document is a technical guide for ASG, contains the details on the procedure to be followed
in various scenario of handling the crashes/online issues.
ASG handles all production issues which cause a system down situation for the client. It mainly
consist of
1. Production COB / EOD issues

2. Online issues, which stops the bank from their daily operations – Like the whole system
is not available to user or the users not able to operate on a particular module. This also
includes File corruption, Online Performance issues or any Database or OS issues due to
which the system become inoperable
2.COB / EOD issues
2.1 Some basic points on COB / EOD
A COB / EOD consist of five batch stages:
Stage Description of Activities
1- APPLICATION Individual application processes (Forex, Funds Transfer etc.)
2- SYSTEM WIDE System wide processes (Interest & Charges, Revaluation etc.)
3- REPORTING Main system reports (trial balance, general ledgers, transaction

journal etc.)
4- START of DAY Change date (Standing orders, split month end events, cash flow
maintenance etc.)
5- ON-LINE Any non-critical reports and processes which can be run after the
system has returned to on-line mode.

ASG Technical Guide
The stage of a batch is determined based on the field BATCH.STAGE in the BATCH
record
Single Threaded /Multi-threaded job
A COB job may be single threaded or multi-threaded job. Most of the jobs in COBs
are now multi-threaded. A COB job can be identified as a single thread or Multi-threaded by
checking the PGM.FILE (field BATCH.JOB) of the job.
Multi-threaded
A multi-threaded job will either have the value @BATCH.JOB.CONTROL in the field
BATCH.JOB or contains blank.
PROGRAM IC.COB
------------------------------------------------------------------------------
1 TYPE.............. B
4. 1 BATCH.JOB...... @BATCH.JOB.CONTROL
5 PRODUCT........... IC
7. 1 DESCRIPTION.... Performs entire IC processing
7. 2 DESCRIPTION.... for single account from GROUP.
7. 3 DESCRIPTION.... ACCOUNT
Single threaded
A single-threaded job will have the value @JOB.NAME in the field BATCH.JOB as shown
below.
Model Bank PROGRAM FILE SEE

PROGRAM COB.CHECK.EB.EOD.ERROR
------------------------------------------------------------------------------
1 TYPE.............. B
2. 1 GB SCREEN.TITLE COB.CHECK.EB.EOD.ERROR
3 ADDITIONAL.INFO... .CRITICAL
4. 1 BATCH.JOB...... @COB.CHECK.EB.EOD.ERROR
5 PRODUCT........... EB

START
ASG Technical Guide
PROCESS.STATUS or JOB.STATUS LOAD routine –

Opens all related
files
Some common status values are:
0 - Ready
1 - Running
2 - Completed <>successfully
processing
3 - On hold or in error CONTROL.LIST
.SELECT =”processing”
Session not doing select
BATCH.BUILD.LIST
PROCESS.LIST
CONTROL.LIST = processing
Flow chart of a multi-threaded job

EXTRACT.PORTION
PROCESS.PORTION
PROCESS.RECORD
Calling record routine
No If Keys
processed
eq 0
CONTROL.LIST = processed STOP

ASG Technical Guide
2.2 Basic Information required in case of COB/EOD

Crash
Irrespective of T24 release
i. Total EOD/COB duration time

ii. T24 release & DB used (jbase / universe / oracle)
iii. BASIC.LISTING output. The routine to extract the BASIC.LISTING is attached below

ASG Technical Guide
BASIC.LISTING
iv. If BASIC.LISTING is not available then get the output of the below commands from
the client.
> LIST F.BATCH WITH BATCH.STAGE NE “” AND PROCESS.STATUS EQ 1 JOB.NAME

JOB.STATUS
JOB.STATUS
JOB.STATUS
The batch that had been crashed can be obtained from the above set of commands
where the PROCESS.STATUS is set to 3 or 4.
Information Specific to T24/Globus release:
For Globus releases below G13.2.07:
v. If the EOD is run from classic then fetch the full como of the batch where the EOD
had crashed. This can be obtained from the universe/jbase prompt:
CT BAT.<<Comp.mne>>_BATCH.NAME
Eg: BAT.BNK_LD.END.OF.DAY
vi. If the EOD is run in desktop check how many sessions are used. It can be obtained
from the field BATCH.SESSIONS in the SPF file.
27 HELD.RPT.RETENTION 5
28 CACHE.SIZE........ 500
30 PREVIOUS.RELEASE.. G11.1.02
32 BATCH.SESSIONS.... 10
35. 1 NON.2DEC.CCY... BEF

ASG Technical Guide
vii. If EOD is run in desktop then run MERGE.GUI.COMO from classic and send the
como. The como id will be in the format :
BAT.<<Comp.mne>>_BATCH.NAME (After running MERGE.GUI.COMO)

Eg: BAT.BNK_SYSTEM.END.OF.DAY3
If need to extract the thread como (desktop) then the id of the como will be in the
form BAT.X (Where X = 1 to Number of sessions)
For Globus releases G13.2.07 onwards:
viii. The above 7 steps hold good for Globus releases G13.2.07 onwards.
In addition to the above steps the following information are also required.
ix. F.BATCH.STATUS record for the crashed job. The id of the F.BATCH.STATUS record
will be of the format
BATCH.NAME-JOB.NAME-JOB.POSITION
Eg: BNK/SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1
>CT F.BATCH.STATUS SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1

SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1
0001 processed
>
The BATCH.STATUS of currently running job is obtained using the below command
LIST.ITEM F.BATCH.STATUS WITH F1 LIKE ...processing...
Sample BATCH.STATUS record for a job looks as below while the job is running
Example 1
This is a sample record while the job finishes the selection process and running in
record routine. This job does not have CONTROL.LIST

ASG Technical Guide
BNK/PM.EOD2-PM.ACTIVITY.ONITE-1
001ýprocessingý206
Example 2
This is a sample record for a CONTROL.LIST job. This job has
CONTROL.LIST. It has two CONTROL.LIST, 20061113 and
TO.CALL.LD.END.OF.DAY.8.
LD.END.OF.DAY-LD.END.OF.DAY.4-3
001 20061113]processing]202
002 TO.CALL.LD.END.OF.DAY.8
In this example “processing” is concatenated with the date.It means Control list is
built and the job is running for the control list 20061113
SHOULD NOT bypass the job at this stage as it has to process one more control list.
Example 3
Here the job is currently processing the control list “PROTOCOL”
>CT F.BATCH.STATUS BNK/FILE.TIDY.UP-EB.CLEAR.FILES-3

BNK/FILE.TIDY.UP-EB.CLEAR.FILES-3
001 PROTOCOL]processing]156]19119]4002
002 EXCEPTION.LOG.FILE
003 LOCK.STAT
004 ENQUIRY.LEVEL
005 LIMIT.REP.KEYS
The numeric values denotes

19119 – Total Records selected
4002 – Completed

ASG Technical Guide
156– Total No. of JOB.LIST ids
x. Check the job list the job is using. This info is maintained in the F.LOCKING with the
same id format of F.BATCH.STATUS,
BATCH.NAME-JOB.NAME-JOB.POSITION. The format of the job list file name is
F.JOB.LIST.Y( In lower release, the JOB.LIST file is a FIN type, it will be in the format
FXXX.JOB.LIST.Y where XXX is the company mnemonic.
>CT F.LOCKING SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1

SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1
0001 F.JOB.LIST.4
xi. The ERROR record in F.BATCH.STATUS.

Eg :
>CT F.BATCH.STATUS ERROR
ERROR
1 STMT.UPDATE*PRINT.ACCOUNT.STMT
This record exists in G13 release, when a job crashes. This has to be deleted before
proceeding with the job. No need to check this record in above R4 release
xii. The respective EB.EOD.ERROR details.
LIST F.EB.EOD.ERROR WITH @ID LIKE …<<date when the crash had occurred>>…
For T24 release R4 onwards:
xiii. The above steps hold good for T24 R4 onwards.

In addition to the above steps the following information are also required.
xiv. Number of agents (tSAs) used for running the COB.
xv. Full COMO of the crashed agent. This can be obtained from the file F.TSA.STATUS
in the field COMO.NAME

ASG Technical Guide
CURRENT.SERVICE. COB
NEXT.SERVICE.... STOP
LAST.MESSAGE.... _MTA/STARTUP_EB.PRINT_4_04 JUN 2005_12:37:30_Processing...1
COMO.NAME....... tSA_100_20120404_22-32-07
JOB.PROGRESS.... 3
Id format it tSA_100_20120404_22-32-07
100 – Agent Number
20120404 – Date
22-32-07- Time
xvi. The como can be fetched from the jbase prompt as:
Jsh liveJED &COMO& tSA_100_20120404_22-32-07
3.LOCKS & Process information

Locks and process information is vital information to analyse both online and COB
issues.
There are different utilities available to monitor the locks in the system. The utilities
can be used depends on the locking mechanism used by the client.
3.1 LOCKS
SHOW-ITEM-LOCKS
SHOW-ITEM-LOCKS is used to obtain the information on the locks in the system. This is
used for getting the locks information on a single application server. SIL should not be
requested for the clients running on multi-application server, instead we need to request for
jDLS –dVL output (as explained in the below section of this document). Otherwise, for a
multi-application server, we need to request the SHOW-ITEM-LOCKS from all the application
servers.
Below is a sample output of the SHOW-ITEM-LOCKS. The output will display the port id,
process id, file name and record which is locked.

ASG Technical Guide
The last column BY-PID, usually will not hold any value for a normal port which locked a
record. If there is a blocking situation, then It will hold the PID of the port which actually
locked the record. In this example, port 48700 is waiting to attain a lock on the record, which
was already locked by the pid 217540.
PORT PID FILENAME RECORD KEY LOCK# BY-PID

10000 152380 ../bnk.data/de/F.DE.PHANTOM DE.O.SELECT.NEXT.MESSAGE.ACTIVE
0x0CF61412,W ----
10001 35708 ../bnk.data/de/F.DE.PHANTOM DE.O.MAP.MESSAGES.ACTIVE
0x3335A0C6,W ----
10003 196300 ../bnk.data/de/F.DE.PHANTOM DE.CC.GENERIC-SWIFT.ACTIVE
0x2B50E14D,W ----
10004 217540 ../bnk.data/am/FBNK.BV.O000 SYSTEM*8 0x03148F2D,W ----
10004 217540 ../bnk.data/eb/FBNK.JOB.010 191 0x22F19A01,W ----
10004 217540 ../bnk.data/am/FBNK.BV.P003 SYSTEM 0x222792F1 105040
10005 209630 ../bnk.data/eb/FBNK.JOB.010 159 0x0B298645,W ----
10006 112818 ../bnk.data/eb/FBNK.JOB.010 73 0x11C8020A,W ----
10006 112818 ../bnk.data/am/FBNK.BV.O000 SYSTEM*3 0x03979132,W ----
10007 161224 ../bnk.data/eb/FBNK.JOB.010 131 0x118C1450,W ----
10007 161224 ../bnk.data/am/FBNK.BV.O000 SYSTEM*6 0x03B261AB,W ----
10009 48700 ../bnk.data/am/FBNK.BV.O000 SYSTEM*4 0x039BDA74,W ----
10009 48700 ../bnk.data/eb/FBNK.JOB.010 172 0x14A4E65A,W ----
10010 127872 ../bnk.data/eb/FBNK.JOB.010 107 0x06B73B40,W ----
10010 127872 ../bnk.data/am/FBNK.BV.O000 SYSTEM*1 0x0392A628,W ----
jRLA
jRLA is a component of jBASE which helps to control locks for T24. jRLA uses shared
memory locking model, all locks will be held in shared memory which can be accessed by
each T24/jBASE processes.
Procedure to stop and start the jRLA
To Stop:
jBTP -k
jPML -k
jRLA -k

ASG Technical Guide
To start :
jRLA -ibs13120,2640,30
jPML -ib
jBTP -ib
jrla locks can be monitored efficiently with jrla –dvL command
-->jRLA -dvl
jRLA: $Revision: 3.8.4.4 $
Program at pid: 1757
Program started: Sat Oct 11 23:31:43 2003
Time last ran: Tue Oct 21 10:00:09 2003
Time last tidied up: Tue Oct 21 09:55:57 2003
Lock retries: 130554
Tidy-up time: 5 minutes
Locking mechanism: Memory semaphores based on PROCESS id
Tidy-up operations: 15
Shared memory IDs: 2055 , 8
Semaphore IDs: 23, 24
Memory: 15000 bytes used , 49536 bytes jfree
CPU Usage: 36.95 usr , 50.14 sys
Binary locks: 610 locks maximum in 61 groups of 10 locks/group
0 locks currently in use
0 is max. locks found in one group
Record locks: 3020 locks maximum in 151 groups of 20 locks/group
Please follow the below steps to Increase jRLA locking parameters as follows
1) Logoff all jBASE userS from the server. No foreground and background the process
should be running.

ASG Technical Guide
2) Login as root and export the minimal environment variables required:
export JBCRELEASEDIR=/usr/jbc
export JBCGLOBALDIR=$JBCRELEASEDIR
export PATH=$JBCRELEASEDIR/bin:$PATH
export SHLIB_PATH=$JBCRELEASEDIR/lib:/usr/ccs/lib:/usr/lib
We assume jBASE is installed in '/usr/jbc', if not change the path accordingly.
3) Stop the jRLA daemon using the following command
jsh ->jRLA -K
(Note capital K)
4) Use the ipcs -a command to check whether the daemon has been properly shut down,
jsh->ipcs -a
In the output of the above command you can see lines similar to the ones given below:
T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS O

Shared Memory:
m 1573094 0x4a414310 --rw-rw-rw- root staff root staff 161 8
m 393437 0x4a414311 --rw-rw-rw- root staff root staff 160 8
Semaphores:
s 2 0x4a414310 --ra-ra-ra- root system root system 61 no-5
s 3 0x4a414311 --ra-ra-ra- root system root system 61 no-5
Please remove the ids starting with '0x4a' using the command
ipcrm -m <shared memory ID>

ASG Technical Guide
ipcrm -s <semaphore ID>
In above case it would be
ipcrm -m1573094
ipcrm -m393437
ipcrm -s2
ipcrm -s3
5) Start the jBASE demon in this order:

jRLA -ibs 30720,1830,30
6) After starting the daemon check the jRLA -dvl whether the new parameters gets into effect
jDLS
jDLS locking is used for Multi-Application server architecture.
For setting up the jDLS locking mechanism, export the below variable in .profile of all
the application servers except the jDLS server
export JDLS=SERVER=10.40.10.71
To stop the jDLS demon
jDLS -k [lower case 'k']
jDLS -K [Uppercase 'K']
To start jDLS use the below command from jDLS server
jDLS -ibs13000,50

ASG Technical Guide
Use the next prime number for the number of groups. so in this case the shared lock
table will be 13150 locks in 263 groups with 50 locks per group
jDLS locks can be monitored using jDLS –dvL command
jDLS -dVL
Lock monitor at pid: 4685 - Active
Lock listener at pid: 4686 - Active
Program started: Sat Dec 13 14:00:44 2008
Time last ran: Tue Jan 20 10:57:28 2009
Time last tidied up: Tue Jan 20 10:56:18 2009
Lock retries: 11769
Tidy-up time: 5 minutes
Locking mechanism: IPC semaphores based on THREAD id
Tidy-up operations: 14013
Semaphore IDs: 163841, 196610
Memory: 13760 bytes used , 121408 bytes free
CPU Usage: 0.13 usr , 0.16 sys
Record locks outstanding

Group value pid type port i-node device queued ipaddr key
0 0x5ac0ad2d 26751 WRITE 45109 5c952584 2bc5ee3e None 10.40.10.20
BATCH090204510939448.04 tid ac6453b0,
waitpid 14978
3 0x1722ac81 15702 WRITE 25020 79fff8c1 2bc5ee3e None 10.40.10.66 FT08359003842880 tid
aab1c0a0, waitpid
15381
7 0x5827d7f0 15557 WRITE 28253 18aadafb 2bc5ee3e None 0.0.0.0
FBNK.FUNDS.TRANSFER$NAU.FT09020786601006 tid aac6a3b0, waitpid 15730
12 0x6007e15f 15723 WRITE 28261 18aadafb 2bc5ee3e None 0.0.0.0
FBNK.LD.SCHEDULE.DEFINE$NAU.LD0902000105 tid aac6a3b0, waitpid 14980
17 0x3135b8fb 16258 WRITE 46009 79fff8c1 2bc5ee3e None 10.40.10.21 FT08364109419939 tid
aab1c0a0, waitpid
14979
Record locks: 13150 locks maximum in 263 groups of 50 locks/group


ASG Technical Guide
LOCKS in UNIVERSE
In Universe, the locks can be monitored using the below command
>LIST.READU EVERY
Active Record Locks:
Device.... Inode.... Netnode Userno Lmode Pid Login Id Item-ID.............
3014657 245891 0 29 20 RU 55182 dataop LD010720002220011920
3014657 508504 0 29 41 RU 55182 dataop 0760095044
3014657 245891 0 29 68 RU 55182 dataop LD002830000720012210
3014657 508504 0 29 73 RU 55182 dataop 0760100889
3014657 442505 0 29 82 RU 55182 dataop PDLD0018900011
3014657 508504 0 29 137 RU 55182 dataop 0760061751
3014657 172042 0 29 139 RU 55182 dataop B04/LD.END.OF.DAY
3014657 245891 0 29 140 RU 55182 dataop LD002510000920012190
3014657 245891 0 29 172 RU 55182 dataop LD011550000120012210
3014657 508504 0 29 185 RU 55182 dataop 0760007269
3.2 Process Information

WHERE
WHERE (V command is very useful to analyse / monitor a particular jBASE or T24 process.
WHERE gives useful information like what the processes is doing, what routine its executing,
what line the process is in, how many reads writes opens deletes it has done etc

ASG Technical Guide
Screen shot of WHERE (V portnumber output
MW42 (My WHERE)
mw42 gives lot of useful information regarding T24 processes.

Mw42 gives information like number of reads, writes, opens, deletes, executes, memory
utilised, CPU consumed etc
Mw42 uses memory mapped files to capture the data (each jbase processes will keep the
information in memory and mw42 reads that process memory and gets the information) so
performance won’t be impacted by using mw42 monitor.
213 vbalaji 999632 54 (50) 7 153 34747 4040 1487 4.74M 4.67 2 BLOCK tSA 3 (BATCH.JOB.CONTROL,1080)
245 vbalaji 405964 54 (49) 8 601 21370 3459 847 4.75M 3.18 2 tSA 3 (S.JOB.RUN,520) <BNK/TEC
262 vbalaji 590212 40 (37) 7 1 5667 7 99 4.76M 0.26 2 tSA 3 (S.JOB.RUN,407) <CO3/REP
269 vbalaji 946178 131 (118) 123 273 36925 2349 2154 5.88M 3.61 2 tSA 3 (BATCH.JOB.CONTROL,1207)
270 tskumar 581846 6 (4) 2 1 24 6 25 2.60M 0.00 1 E jsh -s jsh (jsh.b,111)
277 parthee 438716 7 (4) 8 1 27 3 20 2.97M 0.38 2 E /jbtemprel/R08.000.01.aix52.jbc505
The following options can be used with the mw42 command .

-a display application account instead of logged on user name
-f display Full listing, normally Command is truncated to screen size
-m split the memory into Free and Used sections
-n disable check for input (some platforms block when we do this)
-pPort restrict display to Port number

ASG Technical Guide
-pp1-p2 restrict display to Port range p1 to p2

-s display IO stats instead of iSeries JobId (Default on UNIX)
-t prefix each line with time stamp
-uuser restrict display to user
You can toggle most of the options at runtime by hitting the key for the option
q or 'Q' will exit
Mw42 also gives subroutine trace which shows which subroutine and which line of code is
currently been executed by jBASE, using this functionality performance issues can be easily
monitored and analysed
It is always advised to get the output using –f option as below, which will avoid truncating the
output
--->mw42 –f
The below command from unix prompt will save the output into a file mw42.out. This will be
helpful in case of analyzing performance issues.
$mw42 -e -f 300>mw42.out
ps -ef
ps –ef command is used from unix to identify the process running in the system.
Syntax:
$ps –ef
A selective display of process can be done using the below command. For example, if we want to
display all the process in which tSA are running, we can execute the below command from unix
prompt
$ps –ef | grep tSA

ASG Technical Guide
PORT.STATUS
In universe, the command PORT.STATUS is used to list out the process.
3.3 Unlock or kill a process
Below commands can be used to remove a lock or to logoff a process.
CLEAR-ITEM-LOCKS – Used to clear all the locks in jBASE

LOGOFF <Port Id> - Use to logoff the port supplied
kill -9 -1 – Use to kill all the session (Do not use this as it will kill all the process)
kill -9 <PID> - Use to kill the process for the PID supplied.
UNLOCK ALL – To unlock all the locks in an Universe environment

UNLOCK <USER <NO.> - In universe environment, to unlock the lock held by the userno
given
4.File corruption and Maintenance

VOC is a pointer in T24. For every T24 files, there will be a corresponding VOC, which
contains the actual name of the physical file.
A sample VOC
FBNK.ACCOUNT
001 F
002 ..\bnk.data\ac\FBNK_ACCOUNT
003 ..\bnk.dict\F_ACCOUNT]D
The T24 file name can be obtained from the physical file name using the below command on
VOC

ASG Technical Guide
>LIST VOC ONLY WITH F2 LIKE .../FBNK.ACCO018...
4.1 File Corruption in Universe environment (fixtool)
To find whether the file is healthy FILE.STAT command can be used.
>FILE.STAT F.ENQUIRY.LEVEL
WARNING: Internal file corruption detected during file open!

File must be repaired, possible truncation.
hsize: 2048
bsize: 2048
fsize: 538976312
Unable to open "../bnk.data/eb/F.ENQUIRY002" file
If the file is found to be corrupted, fixtool can be used to recover the file.
In order to run the fixtool following steps must be implemented.
a. First take the backup of corrupted file.
$ cd ../mbdemo.data/eb
$ cp F.ENQ000 F.ENQ000.BAK
b. Then run the following command from the Unix level.
$ fixtool - file ../bnk.data/eb/F.ENQUIRY002 -fix level9

ASG Technical Guide
4.2 File Resize in Universe environment (RESIZE)
The following procedure has to be adopted to resize any file.
1. Do a FILE.STAT for the file you want to resize and note down the following
a) Number of records (for ex R)
b) Average number of bytes per record (say A)
c) Separation (say S)
d) Type (say T)
>FILE.STAT <File.Name>
2. Formula to calculate Modulo
Number of records * Average number of bytes

N = -------------------------------------------------------------------
(Separation * 512) - 0.1 * (Separation * 512)
i.e. R*A
N = ----------------------------
(S*512) - 0.1* (S-512)
3. From Universe prompt do
>PRIME N
The output will give one highest and lowest Prime Number; now consider the Highest one let
that be P.
4. Now resize the file using the following command

>RESIZE <File.Name> <TYPE> <Higher Prime Number> <Separation>

ASG Technical Guide
i.e. >RESIZE filename T P S

This will resize the file accordingly
4.3 File Corruption in jBASE environment (jcheck)
For the file corruption in jBASE, we can use the jcheck utility to recover the file.
From jshell prompt issue:
--->jstat -v <file name>
say for example:
--->jstat -v F.JOURNAL
If the file is corrupt, the output of jstat command would display something similar to the
following:
jsh karthiks ~ -->jstat -v F.JOURNAL

File ../mbdemo.jnl/F.JOURNAL
Type=J4 , Hash method = 4
Create at Wed Jun 2 11:51:07 2004
Groups = 201 , Frame size = 4096 bytes , Secondary Record Size = 8192 bytes
Restore re-size parameters : (none)
File size = 827392 bytes , Inode = 2695232 , Device = Id 2752514
Last Accessed Wed Jun 9 14:18:06 2004 , Last Modified Wed Jun 9 14:18:06 2004
Backup = YES , Log = YES , Rollback = YES , Network = AUTO
F.JOURNAL: File is corrupt  The file is corrupt.
Record Count = 118 , Record Bytes = 62244

ASG Technical Guide
Bytes/Record = 527 , Bytes/Group = 309

Primary file space: Total Frames = 201 , Total Bytes = 62244
Secondary file space: Total Frames = 0 , Total Bytes = 0

jsh karthiks ~ -->
This indicates that the file is corrupt.
Follow the below steps to correct the file using jcheck utility.
1. jstat -v F.XYZ
It will tell you that the file is corrupted
jsh sysman ~ -->jstat –v F.JOURNAL

File ../bnk.jnl/F.JOURNAL
Type=J4 , Hash method = 4
Groups = 7501 , Frame size = 8192 bytes , Secondary Record Size = 16384 bytes
../bnk.jnl/F.JOURNAL: File is corrupt
Record Count = 5732 , Record Bytes = 25526577

Bytes/Record = 4453 , Bytes/Group = 3403
Primary file space: Total Frames = 5926 , Total Bytes = 20575030
Secondary file space: Total Frames = 734 , Total Bytes = 4951547
2. FInd out the path of F.XYZ using jshow -c

It will give you the path like (../bnk.data/eb/F.XYZ)
jsh sysman ~ -->jshow -c F.JOURNAL

File: ../bnk.jnl/F.JOURNAL

ASG Technical Guide
3.Go to this directory take a backup of this file.
jsh sysman ~ -->pwd

/globus/hbl/bnk/bnk.run
jsh sysman ~ -->sh
$ pwd
/globus/hbl/bnk/bnk.run
$ cd ..
$ cd bnk.jnl
$ pwd
/globus/hbl/bnk/bnk.jnl
$ ls -l F.JOURNAL
-rw-rw-rw- 1 sysman globus 104669184 Mar 19 19:20 F.JOURNAL
$cp F.JOURNAL F.JOURNAL.BAK
$ exit
4.From run directory,
Jsh---->jcheck -S ../bnk.data/eb/F.XYZ
It will say " Salvaged n records."
jsh sysman ~ -->jcheck -S ../bnk.jnl/F.JOURNAL

Checking file ../bnk.jnl/F.JOURNAL
ERROR! Group 5507 Invalid link detected at 05c32000
ERROR! Group 5507 Invalid Basefid detected at 05c32000
ERROR! Group 5507 InGroup Reclen exceeds available, skipping rest of group
Salvaged 8546 records
5. Go to the ../bnk.data/eb/F.XYZ path there you can see the file SLVG_F.XYZ
drwxrwxrwx 2 hbl globus 512 Mar 19 14:24 F.EBS.REM000

-rw-rw-rw- 1 sysman globus 104669184 Mar 19 19:20 F.JOURNAL
-rw-rw-rw- 1 sysman globus 101761024 Mar 19 20:45 SLVG_F.JOURNAL
-rwxrwxrwx 1 hbl globus 16384 Jul 15 2003 SLVG_F.JOURNAL]D

ASG Technical Guide
-rwxrwxrwx 1 hbl globus 18 Jun 3 2003 test
6. Move the file using,
mv SVLG_F.XYZ F.XYZ
$ mv SLVG_F.JOURNAL F.JOURNAL
4.4 File Resize in jBASE environment (jRF)
There is a utility in jBASE by name jrf which can be used to resize a J4 file. Follow the below
steps to resize a J4 file
1.) You can use jstat to find the physical file path of a file (from jshell prompt):
-->jstat <File name>
for example:
jsh-->jstat FBNK.ACCOUNT
File ../mbdemo.data/ac/FBNK.ACCOUNT
2.) Use jrf with -R option to check if a file needs resizing. '-R' option will only report and will
not resize the file.
for example:
jsh-->jrf -Rv ../mbdemo.data/ac/FBNK.ACCOUNT
If the output shows something like this:

Downsizing skipped from modulo xx to xx.
where 'xx' is a numeric value.

ASG Technical Guide
Then do:
jsh-->jrf -Dv ../mbdemo.data/ac/FBNK.ACCOUNT

This will downsize the file. This can be checked with a subsequent jrf -RV.
3.) But if jrf -Rv shows something like 'Resize from xx to nn.
where 'xx' and 'nn' are numeric value.
Then do:
jsh-->jrf -Snnv ../mbdemo.data/ac/FBNK.ACCOUNT

where 'nn' is the target modulo as given by the output of jrf -Rv.
This will resize the file. This can be checked with a subsequent jrf -RV.
Try jrf -h for more details.
4.5 File corruption - JR files
JR files may corrupt if there is a corruption to the header of the file. If the header get
corrupts, the file will not be recognized as a JR file and so the SELECT or COUNT will
display as below for the corrupted file.
r11 ~ -->SELECT FBNK.ACCOUNT

No file name could be found for your query
To correct the header of a JR file, we have a c program. The program should be executed on
the corrupted file, by following the below steps

ASG Technical Guide
1. Copy the below contents to a file named test.c. The program should be copied to the
path where the file is corrupted. <filename> should be replaced with actual file name
as below
f d=open64("./FBNK.STMT008.20120405",O_WRONLY,0);
The program is as below.
JED test.c
#include<stdio.h>
#include<fcntl.h>
int main(void)
{
int fd=0,rc=0;
char buffer[]="JBC__HSR";
fd=open64("./filename",O_WRONLY,0);
rc=pwrite(fd,buffer,sizeof(buffer),0);
close(fd);
2. Compile the program as below
cc -O test test.c
Note that it is Caps ’O’ and not zero.
3. After compilation, execute it as
$./test
4.6 File corruption of Sensitive files – New file

creation
For sensitive files, like STMT.ENTRY, CATEG.ENTRY, RE.CONSOL.SPEC.ENTRY etc, we

should not run jcheck or fixtool in the event of corruption of those files.

ASG Technical Guide
We have to create a new file and copy the relevant records to it from the corrupted file.
jcheck or fixtool can apply to those file only in case the files couldn’t recover from the backup
file, that is when it fails to copy the records from the corrupted file.
Each file has its own procedure to create and copy the records.
Procedure to Create New file for STMT.ENTRY:
Using Program:
This program can be used both in jBASE and Universe environment. This program
will create a new file and copy the relevant records for processing the system for the day.
Always give priority to run the routine to correct the file. Follow the manual steps only if there
is any issues in running the routine.
CORRECT.STMT.ENT
RY
Manual Steps to create new file in jBASE environment:
Please follow the steps in the attached document to create the new file and copy the relevant
records in the event of corruption of the file in jBASE environment
STMT.ENTRY FILE CREATION STEPS IN JBASE
Manual Steps to create new file in Universe environment:
records in the event of corruption of the file in Universe environment

ASG Technical Guide
STMT.ENTRY FILE CREATION STEPS IN UNIVERSE
Procedure to create new file for CATEG.ENTRY:
Using Program CREATE.NEW.CATEG.ENTRY:
This program can be used both in jBASE and Universe environment. This program
will create a new file and copy the relevant records for processing the system for the day.
Always give priority to run the routine to correct the file. Follow the manual steps only if there
is any issues in running the routine.
CREATE.NEW.CATE
G.ENTRY.txt
CATEG ENTRY file

creation steps in jbase.doc

ASG Technical Guide
Categ_Entry_File_Cr
eation_Universe.doc
Procedure to create new file for RE.CONSOL.SPEC.ENTRY:
RE.CONSOL.SPEC.E
NTRY CORRUPTION PROCEDURE.doc
Procedure to create new file for DE.O.HANDOFF
PROCEDURE FOR DE.O.HANDOFF NEW FILE CREATION IN JBASE

ASG Technical Guide
PROCEDURE FOR DE.O.HANDOFF NEW FILE CREATION IN UNIVERSE
4.7 File Distribution
Please find attached the procedure for distributing files automatically.

Please download the attached routines
CSHD.DISTRIBUTE.JBASE40
DIST.ALGO.31
DIST.ALGO.STMT.ENTRY.32
And compile.
Choose the distribution algorithm as required (details given in the attached document) and
distribute the current FBNK.STMT.ENTRY file.
After doing so, please also copy the contents of the original FBNK.STMT.ENTRY.BAK into
the new file.
DISTRIB.zip
5.Correction Routines & Utilities
Below are some of the routines or utilities required frequently while handling issues in ASG
Sl.
No. Name Description Routine
For correcting BATCH records in
the event of crash due “Snap shot
PACS.BATCH.CORR.GEN
1 PACS.BATCH.CORR.GEN too old error”

ASG Technical Guide
To complete the COB if the COB

crashed while resetting the batch
records in S.PROCESS.RESET. Run
the routine, which will complete
2 RESET.BATCH the COB RESET.BATCH.txt
This routine is used to split / bulk
a JOB.LIST file. To split a JOB.LIST,
3 PACS.JL.BULKING Input the Bulking No. as 1 PACS.JL.BULKING
Routine to delete
EB.AVAILABLE.FUNDS.WORK for
CHECK.AVF.WORK.UPDAT which ACCOUNT doesn’t exists in
4 E the system CHECK.AVF.WORK.UPDATE
This Program will check T24
related Files from the VOC
and report the Following
1. Missing Files
2. Corrupted Files
3. Badly Sized Files
5 CHECK.T24.FILES 4. Files reaching 2 GB CHECK.T24.FILES
PROGRAM TO CHECK IF THE
CONSOL KEY IN THE
RE.STAT.LINE.CONT
EXISTS IN THE
CONSOLIDATE.ASST.LIAB TABLE
IF NOT, DELETES THE MULTI-
CONT.CHECK.ASSET.AND.L VALUE SET OF THE
6 IAB.KEYS RE.STAT.LINE.CONT RECORD CONT.CHECK.ASSET.AND.LIAB.KEYS
This is a correction program, for
missing GROUP.DATE records.
It will select
GROUP.DEBIT.INT/GROUP.CREDIT.I
NT records, loop
through each record and call
MAINT.ACC.INT.DATES.
MAINT.ACC.INT.DATES gets called
by GCI/GDI to update
7 CORR.GRP.DATE GROUP.DATE file CORR.GRP.DATE
To display the account ids in
CROSS.CHECK.GROUP.DAT JOB.LIST file, which doesn’t
8 E contains the GROUP.DATE CROSS.CHECK.GROUP.DATE

ASG Technical Guide
EXISTS IN THE
CONSOLIDATE.PRFT.LOSS TABLE
IF NOT, DELETES THE MULTI-
VALUE SET OF THE
9 CORRECT.CONT.PFT.KEYS RE.STAT.LINE.CONT RECORD CORRECT.CONT.PFT.KEYS
Routine to update DATE.RESOLVED

10 DT.CHG.EOD.ERR field in EB.EOD.ERROR record DT.CHG.EOD.ERR
correction routines to clear the
Concat files
ACCT.ENT.FWD,ACCT.TRANS.FWD,T
RANS.FWD for the entries that are
11 FENTRY ROUTINE.zip not present in the STMT.ENTRY FENTRY ROUTINE.zip
To split the Account ID's in the

12 BREAK.IC.ACCRUAL.WORK IC.ACCRUAL.WORK by 2 i.e total/2 BREAK.IC.ACCRUAL.WORK.txt
JT.ANALYSE should be run after
completion of COB to refer time
taken by each COB job. This will
help
in understanding the performance
of every job and help in fine tuning
13 JT.ANALYSE.R9U the job. JOB_TIMES.zip
JOURNAL CORRUPTION.txt
Subroutine to rebuild the journal

14 REBUILD.JNL file. REBUILD.JNL
A trace in JOURNAL.UPDATE.JBASE
for finding out the corrupted file.
This is a sample trace in R08
release. The same has to be
applied in client routine. The trace
is included between the keyword
“PACS Trace Start” and “PACS
15 Tracer for file corruption Trace End” JOURNAL.UPDATE
Routine to delete the expired

16 CLEAR.EXPIRED.LOCKS RECORD.LOCK CLEAR.EXPIRED.LOCKS.txt
Routine to clear the unused and

17 CLEAR.EXPIRED.TOKENS expired tokens CLEAR.EXPIRED.TOKENS

ASG Technical Guide
Sometimes it is difficult to find the

locking port using mw42, SHOW-
ITEM-LOCKS and WHERE (V *
This small routine helps to find the
active invisible locks in the system
*
Then we can log off the ports
18 FIND.LOCK.TEC manually . * FIND.LOCK.TEC
PACS.TRACE.SUBROUTINE
Procedure.doc
19 PACS.TRACE.SUBROUTINE Routine to generate the jimi tracer
This routine is written to update
the field PRINT.STMT of the
ACCOUNT.STATEMENT.CO ACCOUNT.STATEMENT record to
20 RR 'NO' ACCOUNT.STATEMENT.CORR
To generate SEAT.RESULTS from

21 PREPARE.SEAT.RESULTS jimi log PREPARE.SEAT.RESULTS
Routine to delete UNAUTH

22 DEL.UNAUTH.POSITION position from POSITION file DEL.UNAUTH.POSITION.txt
GET.UNPROCESSED.SCHE To correct LMM.SCHEDULE.DATES

23 DULES of an LD contract GET.UNPROCESSED.SCHEDULES.txt
To check if the given files are

24 PACS.CHECK.FILE corrupted PACS.CHECK.FILE
Program to rebuild
REBUILD.CATEG.ENT.TODA CATEG.ENT.TODAY ( for a particular
25 Y date/day ) from CATEG.ENTRY REBUILD.CATEG.ENT.TODAY.txt
REBUILD FXXX.CATEG.MONTH
BASED ON BOOKING.DATE &
26 REBUILD.CATEG.MONTH CATEGORY OF CATEG.ENTRY REBUILD.CATEG.MONTH.txt
TO DELETE NULL STMT.ENTRY.NO
FROM STMT.PRINTED
REMOVE.INVALID.STMT.E ALSO DISPLAY THE ID'S THAT ARE
27 NTRY NOT PRESENT IN STMT.ENTRY FILE REMOVE.INVALID.STMT.ENTRY.txt

ASG Technical Guide
To rebuild RE.STAT.LINE.CONT
28 Y.REBUILD.CONT from the backup corrupted file Y.REBUILD.CONT.txt
This routine will select the ids
saved under the &SAVEDLISTS&
record name 'INCORR.ID' and
delete from the problematic job
list.
It will also delete the ids from the
29 JOB.LIST.DELETION bulk job list file. JOB.LIST.DELETION
6.Browser Issues
Attached the document briefly explain how to analyse Browser issues. It contains
procedure to enable relevant logs. The document also contains some frequently
occurring issues and their solution.
A GUIDE FOR
ANALYZING GENERIC BROWSER ERRORS.doc
6.1 Setup Files

The below configuration files should be requested from Client system for checking the
setup
1. t24-ds.xml – Available in JBoss Install Directory] \server\default\deploy
2. t24-destinations-service.xml (to check request and reply queues of
batchfile configured.)
Available under jboss-4.2.3.GA\server\default\deploy
3. browserParameters.xml
4. weblogic.xml
7.Oracle related.
7.1 Basics of Oracle

ASG Technical Guide
1. Oracle errors will be logged in ORA / XMLdriver.log. We can tail the driver.log using
the below command to identify the latest error logged.
>tail –500f ORAdriver.log (The log name varies based on the database, This is upto R09
release)
>tail –500f XMLdriver.log (From R10, the name of the log is generalized as
XMLdriver.log)
2. We can have either Stubfile and Stubless Architecture. In both, the VOC will differ.
Stubfiles are in bnk.data. bnk.data and VOC should be NFS mounted to all application
server.
‘Stub’ are pointers file that hold the following details
jEDI Driver that need to be initiated/used (XMLORACLEInit /XMLDB2Init /XMLMSSQLInit
/jediInitRemote)
TABLE Name
TABLE Type (CLOB or BLOB)
VOC in Stubfile
0001 F
0002 ../bnk.data/ac/FBNK.ACCOUNT
0003 ../bnk.dict/F.ACCOUNT]D
In Stubless, VOC can be as a Table, placed in DB. Both VOC and bnk.data no
longer exists in App server.
In a ‘Stubless’ architecture, the ‘stub’ file details are moved to VOC and hence this
eliminates the NFS mount of ‘bnk.data’. Also the VOC is to table and the data resides
in DB.
VOC in Stubless
FBNK.ACCOUNT

ASG Technical Guide
001 TABLE
002 XMLORACLEInit
003 D_FBNK.ACC001
004 ACFBNK_ACC001
3. Jstat output on a filename will gives the underlying table name corresponds to the
file.
jstat -v F.JOB.LIST.1
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
File = default_F_JOB_LIST_1
Type = XMLORACLE, Version R09.1.91658, Table = F_JOB_LIST_1
Schema = COREORA1, Tablespace = COREORA1DATA
NLS Characterset = AL32UTF8
From sql prompt, we can execute the DESC command to check the
existence of the table in Oracle
>DESC F_JOB_LIST_1;
4. For performance improvement, we can advise indexing.

Index can be created using the below command from jbase
>CREATE-EXTINDEX FBNK.ACCOUNT CUSTOMER
By the above command, index will be created for the file FBNK.ACCOUNT for
the field CUSTOMER.
We can use the below command to check if index exists for a table
> LIST-EXTINDEX FBNK.ACCOUNT
We can delete an index using the below command

ASG Technical Guide
> DELETE-INDEX FBNK.ACCOUNT
5. config-XMLORACLE
Using this utility, we can see the user setting , database connection etc
jsh  config-XMLORACLE
** Version 3.3.0.60149 *
* Main menu
*
*
*
****************************************************************
1. Database settings.
2. User settings.
3. Test connection
4. XDB Setup
5. Save and exit.
9. Exit without saving.
7.2 Some commonly reported Oracle errors

ASG Technical Guide
ORA-00942 – Table or View doesn’t Exist
eg: A package SQL will be run before using the Oracle database if it is not run then this error might
occur and if the user who is trying to access the view does not have the permission.
** Oracle Error **: ORA-00942: table or view does not exist
ORA-01400 – Cannot insert NULL values eg: this error occurs when a record is written to a file
without the ID part.
389338 - 2.0.10.3b - Sun Feb 10 04:31:44 -
** Oracle Error **: ORA-01400: cannot insert NULL into

("NBFT24CORE"."DEF_EMAIL_F007"."RECID")
ORA-01658: unable to create INITIAL extent for segment in tablespace T24DATA eg: if a data file is
not created with an AUTOEXTEND option
Error - ORA-01658: unable to create INITIAL extent for segment in tablespace T24DATA
ORA-22924: snapshot too old
3.2.3.56077 - 19683 - (select.b,7) - Wed Mar 26 18:03:05 - F.BATCH - EBF_BATCH - ** Error ** READ:
Record key: SYSTEM.END.OF.DAY1.UBSSNÀü0
3.2.3.56077 - 19722 - (select.b,7) - Wed Mar 26 18:03:05 - F.BATCH - EBF_BATCH - ** Error **
readLob(): Unable to read LOB descriptor
3.2.3.56077 - 19722 - (select.b,7) - Wed Mar 26 18:03:05 - ** Oracle Error **: ORA-01555: snapshot
too old: rollback segment number with name "" too small
ORA-0955: name is already used by an existing OBJECT eg: If you are trying to use an object name
which was used previously but deleted and it exists in the recycle bin, then this error occurs.

ASG Technical Guide
ORA-00001-Unique constraints violated
3.2.3.156450 - 229874 - (BATCH.JOB.CONTROL,437) - Thu Jun 19 13:00:15 - ** Oracle Error **: ORA-
00001: unique constraint (T24USR.F_JOB_LIST_1_PK) violated
3.2.3.156450 - 262448 - (BATCH.JOB.CONTROL,437) - Thu Jun 19 13:29:50 - F.JOB.LIST.1 -
F_JOB_LIST_1 - ** Error ** writeRecordAsBLOB: Unable to write key 1 record SingleThread
3.2.3.156450 - 262448 - (BATCH.JOB.CONTROL,437) - Thu Jun 19 13:29:50 - ** Oracle Error **: ORA-
00001: unique constraint (T24USR.F_JOB_LIST_1_PK) violated
Annotation:The above problem ORA-00001: seems to be accuring since the JOB.LIST files accesing
the single data file. Multiple process tries to write into same file with same id (No locks before
write)
ORA-00060-Dead lock detected
3.2.3.156450 - 209078 - (S.JOB.RUN,535) - Thu Jun 19 20:48:35 - ** Oracle Error **: ORA-00060:
deadlock detected while waiting for resource
Annotation:We presume that the deadlock error is related to ORA-00001 problem.Also please send
us the Alertlog files for this problem.
ORA-01013-User requested to cancel the current operation
3.2.3.156450 - 270590 - (jql_listcolumnar.b,115) - Sat Jun 21 14:49:26 - ** Oracle Error **: ORA-
01013: user requested cancel of current operation
3.2.3.156450 - 270590 - (jql_listcolumnar.b,115) - Sat Jun 21 14:49:26 - FAHO.STMT.ENTRY -
FAHO_STMT_ENTRY - ** Error ** READ: Record key: 147810300111740.05000164101
Annotation:This problem is due to occurs when the user try to terminate the process using "Control
+ C" Or serious network failure problems.

ASG Technical Guide
ORA-12545:Connect failed because target host or object does not exist.
‘ORA-01012: not logged on’

No connection between application server and database.
ORA-12537: TNS:connection closed
ORA-03114: not connected to ORACLE
3.2.3.156450 - 242060 - (tSA,117) - Sun Jun 22 13:37:40 - ** Oracle Error **: ORA-12545: Connect
failed because target host or object does not exist
- 242060 - (tSA,117) - Sun Jun 22 13:37:40 - ** Error ** OPEN: Unable to initialise driver data
Annotation : This problem due to appears whenever there is a database down and the users tries to
enter into T24.
ORA-25408: can not safely replay call. Cause: The connection was lost while doing this call. It may
not be safe to replay it after failover
3.2.3.156450 - 168256 - (MBU.SWIFT.FTP.MESSAGE,41) - Mon Jun 23 01:38:19 - F.EB.PHANTOM -

F_EB_PHANTOM - ** Error ** READ: Unable to execute statement. Key = SWIFT.PH
3.2.3.156450 - 168256 - (MBU.SWIFT.FTP.MESSAGE,41) - Mon Jun 23 01:38:19 - ** Oracle Error **:
ORA-25408: can not safely replay call
Annotation:It seems when the oracle was shutdown abruptly EB.PHANTOM was not able to replay
to the RDBMS.However please open a new cshd request if you want a further investigation on this.

ASG Technical Guide
ORA-01756: quoted string not properly terminated. Cause: A quoted string must be terminated with
a single quote mark ('). ...
3.2.3.156450 - 168230 - (select.b,7) - Fri Jun 27 02:30:45 - ** Oracle Error **: ORA-01756: quoted
string not properly terminated
3.2.3.156450 - 168230 - (select.b,7) - Fri Jun 27 02:30:45 - F.BATCH - F_BATCH - ** Error ** SELECT:
Unable to allocate statement handle
3.2.3.156450 - 168230 - (select.b,7) - Fri Jun 27 02:30:45 - ** Oracle Error **: ORA-01756: quoted
string not properly terminated
3.2.3.156450 - 168230 - (select.b,7) - Fri Jun 27 02:30:45 - F.BATCH - F_BATCH - ** Error **
SCANFILE: Failed to process statement SELECT t.RECID FROM F_BATCH t WHERE RECID LIKE
'SYSTEM.END.OF.DAY1.UB'%'
Annotations:This problem appears whenever a wild character pattern did not meet the standard
selection pattern when LIKE involved.
442516 - 2.0.9 - Wed Feb 6 09:43:47 - LMFBNK_LMM_023 - ** Error ** READ: Key =

LD072500332500. Unable to convert XML record into jBASE record
This error may occur if the record is corrupted.Above error message suggests that the record
LD072500332500 is corrupted on the file LMM.ACCOUNT.BALANCES.
** Error ** READ: Record key with length 563 exceeds maximum of 255 bytes
ORA-03106: fatal two-task communication protocol error

ORA-03113: end-of-file on communication channel
connection break or oracle memory crash
ORA-01461: can bind a LONG value only for insert into a LONG column
column alignment for Non English characters are exceeded Or not in a sync.
Non English Character and Internationalisation variable not set.

ASG Technical Guide
**Oracle Error** Unknown OCI status code 1013
Due to timeout because of long running select. Solution is to index the fields.
ORA-01000: maximum open cursors exceeded
Need to increase the open curser at Oracle

open_cursors
ORA-01653 merely denotes that whenever the tablespace is unable to extend <Failed to allocate an
extent for table segment in tablespace> Or there is not enough space left in a datafiles.
7.3 Procedure to increase oracle tablespace
ORA-01653 merely denotes that whenever the tablespace is unable to extend <Failed to
allocate an extent for table segment in tablespace> Or there is not enough space left in
a datafiles.
To increase the table space, please follow the below steps
1. Login to oracle as 'sys as sysdba' previlege.
2. You'll have to check the size of the datafiles attached to the tablespace and check
whether they can autoextend or not..
SQL>select file_name, bytes, autoextensible, maxbytesfrom dba_data_fileswhere
tablespace_name='TABLESPACE_NAME'
Either add more datafiles to the tablespace, set the autoextensible flag or enlarge the
datafile(s).
A.)To add more space to a file issue following command:
alter database datafile 'C:\ORACLE\ORADATA\TOOLS01.DBF' resize 1000m;

ASG Technical Guide
B.)To turn on the autoextend feature on a datafile use following command:

alter database datafile 'C:\ORACLE\ORADATA\TOOLS01.DBF' autoextend on next
100m maxsize 2000m;
C.)To add a new datafile to the tablespace use following command:

alter tablespace TOOLS add datafile 'C:\ORACLE\ORADATA\TOOLS02.DBF' autoextend
on next 100m maxsize 2000m;
Replace the 'C:\ORACLE\ORADATA\TOOLS01.DBF' with your actual datafile location.

Please contact your dba for more help.
Make sure that you have enough disk space to do this.
7.4 INITRANS
In oracle, we can increase the initrans value of some frequently used tables to
improve the system performance. The tables that is advised to increase the initrans
are
F.OS.TOKEN
F.OS.TOKEN.USE
PROTOCOL
ENQUIRY.LEVEL
OS.XML.CACHE
TSA.STATUS
The advised value of initrans for the frequently used table is 100
Follow the below steps to increase the initrans value
1. Check the table name from jstat output

ASG Technical Guide
>jstat -v F.OS.TOKEN.USE
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
File = ../bnk.data/eb/F_OS_TOKEN
Type = XMLORACLE, Version 3.4.1.72556, Table = F_OS_TOKEN
Schema = MBLT24LIVE, Tablespace = MBLT24LIVEDATAXML
NLS Characterset = AL32UTF8
Partitioned = NO
jsh mblt24 ~ -->
2. Check the output of below command:
SQL>select ini_trans, max_trans from user_tables where table_name =

'F_OS_TOKEN'
INI_TRANS MAX_TRANS
-------- ----------
1 255
If the INIT_TRANS value is set to 1 the ask the client to increase it to 100.
Execute the below command to increase the value:
SQL>alter table F_OS_TOKEN initrans 100;
3. The changes can be verified again using the same command

SQL>select ini_trans, max_trans from user_tables where table_name =
'F_OS_TOKEN'
INI_TRANS MAX_TRANS
-------- ----------
100 255
8.OS related issues

ASG Technical Guide
8.1 Available memory exceeded in Universe
In Universe if the memory error occurs as below
"Available memory exceeded"
Then Increase the SELBUF value which can be get from the CONFIG ALL value.
SELBUF: Specifies the amount of local cache.
Below is the sample output of CONFIG ALL.
>CONFIG ALL
Configuration data for license number 406005:
User limit = 100
Expiry date= 1/1/2500
-UCI package is installed.
User limit = 100. Expiry date = 1/1/2500
-UVADM package is installed.
User limit = 100. Expiry date = 1/1/2500
Current tunable parameter settings:
MFILES = 52
T30FILE = 200
OPENCHK = 1
WIDE0 = 0x3eb00000
UVSPOOL = /usr/spool/uv
UVTEMP = /tmp
SCRMIN = 3
SCRMAX = 5
SCRSIZE = 512
QDEPTH = 16

ASG Technical Guide
HISTSTK = 99
QSRUNSZ = 2000
QSBRNCH = 4
QSDEPTH = 8
QSMXKEY = 32
LOGSYCNT = 0
LOGSYINT = 0
TXMEM = 32
OPTMEM = 64
SELBUF = 4
ULIMIT = 128000
FSEMNUM = 23
GSEMNUM = 97
PSEMNUM = 64
FLTABSZ = 11
GLTABSZ = 75
RLTABSZ = 75
RLOWNER = 300
PAKTIME = 300
NETTIME = 5
QBREAK = 1
VDIVDEF = 1
UVSYNC = 1
BLKMAX = 8192
PICKNULL = 0
SYNCALOC = 1
MAXRLOCK = 100
ISOMODE = 1
PKRJUST = 0
PROCACMD = 0
PROCRCMD = 0

ASG Technical Guide
PROCPRMT = 0
ALLOWNFS = 1
CSHDISPATCH = /usr/bin/csh
SHDISPATCH = /usr/bin/sh
DOSDISPATCH = NOT_SUPPORTED
LAYERSEL = 0
OCVDATE = 0
MODFPTRS = 1
THDR512 = 0
UDRMODE = 0
UDRBLKS = 0
MAXERRLOGENT = 100
JOINBUF = 4095
64BIT_FILES = 0
TSTIMEOUT = 60
To do the changes
 Take a backup of the UVCONFIG file of UNIVERSE present in the UNIVERSE home
directory.
From Unix:
1. cd UniVerse Home Directory i.e. cd /usr/uv
2. ls –la .uvconfig To test that you are in the correct directory
3. cp .uvconfig .uvconfig.orig Copy the .uvconfig file
4. cp uvconfig uvconfig.orig Copy the uvconfig file

ASG Technical Guide
 Change the values of the following parameters in the UVCONFIG file to the ones
specified below.
From Unix:
1. use either VI or ED to edit the uvconfig ascii file.
 cd /usr/uv - From UniVerse home directory
 ls –l uvconfig - To check that the correct file exists.
 vi uvconfig - Edit the uvconfig file.
2. Change SELBUF parameter appropriately.<< Change it to 512>

3. Change MFILES parameter to approximately <<change it to 60>
4. change FSEMNUM parameter to approximately <<change it to 40>
5. Save and exit the file.
6. Run the command /UniVerse Home Dir/bin/uvregen to update the .uvconfig binary
file.
i.e /usr/uv/bin/uvregen
5. Run the command /UniVerse Home Dir/bin/DBsetup to regenerate the shared
memory segments.
i.e. /usr/uv/bin/DBsetup
8.2 Memory error in jBASE (Ulimit)
Ulimit values must be changed when we encounter the following type of Memory errors.
i) “Error, errno 12 - 'Not enough space'

** Error [ NO_PRINTER ] **”
ii ) “jBASE: Fatal memory signal seen on process id 108760

jBASE: Because of this, there may be file corruption on file /prod/live/bnk/bnk.run/VOC”

ASG Technical Guide
iii) jBASE: Unable to allocate 147697225 bytes, errno = 12 at

jlibBStore.c,347(RE.UPDT.STAT.LINE.CONT,34) “
On UNIX systems, the ulimit command controls the limits on system resource, such as
process data size, process virtual memory, and process file size.
Each user can either inherit resource limits from the root user or have specific limits defined.
On Solaris systems, by default, the root user has unlimited access to these resources (for
example, unlimited).
On AIX, some limits might apply to the root user.
In order to find out the current values of the ulimit,following command must be executed.
jsh nrtsup1 ~ -->ulimit -a

time(seconds) unlimited
file(blocks) 8285924
data(kbytes) 5214566
stack(kbytes) 4194304
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited
Ulimit values can be optimised by referring the 'ulimit -Ha' values.
jsh nrtsup1 ~ -->ulimit -Ha

time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 4194304
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited

ASG Technical Guide
Values can be changed to "unlimited" by including the following lines in the .profile as below.
ulimit -d unlimited
8.3 LDR_CNTRL for AIX Machine
This is applicable only for AIX systems.

There is a provision for the, extended memory model for performing high memory utilizing
processes. This can be turned on when there is a memory error.
For example if we encounter error message as below:
“ Process ID 20952 – Memory error

Program source name CommandInit.b , line 228 “
Export the value LDR_CNTRL depending upon situations as follows.
jsh->export LDR_CNTRL=MAXDATA=0x40000000
8.4 OS Tools
OS tools are a valuable tool in determining the type of limitation that is being applied, and
from there
The main tool for AIX is nmon. Before a test is run the following command should be run:
nmon -r <<testname>> -t -F <<filename>> -s<<timeslice>> -c<<duration>>

ASG Technical Guide
e.g.
nmon -r eod1 -t -F /tmp/eod1_nmon_file -s30 -c300
The above command would create a file in /tmp call eod1_nmon_file and would give the test
a title of eod1. This command would record stats every 30 seconds for 300 minutes. Once
the test is complete (you do not have to wait for the time period to finish) the output needs
sorting. Still in AIX use the following command:
Sort –A infile > outfile
e.g. sort –A /tmp/eod1_nmon_file > /tmp/eod1_nmon_file.csv
This command sorts the data into a .csv file. This file should then be ftp’d to a windows
machine, and the “nmon analyzer” spreadsheet used to analyse the data.
NB the “nmon analyzer” is an IBM tool, though it is unsupported. The T & R department can
supply copies of this spreadsheet if required.
Below are some examples of the data that is presented by this tool:
CPU usage:

ASG Technical Guide
Disk activity:
Network utilisation:

ASG Technical Guide
9 Performance issues
9.1 SEAT
The below document briefs on how to analyse performance issues using SEAT
SEAT Analysis.doc
9.2 TEC
The below document details on how to make use of TEC to analyse performance
issues.
T24EnterpriseConsol
e.doc
10 Installation Procedure
Procedure to Upgrade, install Service Pack, Patch, Product in lower

release
T24 Upgrades.pdf
Procedure to Upgrade, install Product in higher release
T24 Upgrades User

Guide.pdf

ASG Technical Guide
Procedure to install an Update
11 Miscellaneous
11.1 Release Information
T24 release can be obtained from SPF
SYSTEM SPEC....... SYSTEM

------------------------------------------------------------------------------
1 RUN.DATE.......... 30 MAR 2011
2 SITE.NAME......... R11 Model Bank
3 OP.MODE........... O
5. 1 MAIN.ACCOUNT... ../bnk.data
8 CURRENT.RELEASE... R11.000
jBASE / TAFC release can be obtained from jdiag output
jdiag –dv
jdiag - jBASE diagnostic '$Revision: 1.12 $'

System Information
==================
System : AIX globus 2.5 005CB33A4C00
OS Release : 5.2.0.0
UNIX User : kicdev (uid 208, euid 208)
Tty name : /dev/pts/3
jBASE User (JBCLOGNAME) : Not Set

ASG Technical Guide
Time : Tue Dec 9 08:03:33 2003

WARNING: License information can only be displayed by an administrative user
Environment
===========
JBCCONNECT : 'CONNECT*31*819288'
JBCPORTNO : Not Set
Connect Port : '31'
JBCRELEASEDIR : '/usr/jbc/jbase4.1'
JBCGLOBALDIR : '/usr/jbc/jbase4.1'
HOME : '/globus/dev/bnk/bnk.run'
JEDIFILEPATH : '/globus/dev/bnk/bnk.run'
JEDIFILENAME_MD : 'VOC'
JEDIFILENAME_SYSTEM : '/usr/jbc/jbase4.1/src/SYSTEM'
SYSTEM File is (DICT) : '/usr/jbc/jbase4.1/src/SYSTEM]D'
JBCBASETMP : '/globus/dev/bnk/bnk.run/jBASEWORK/tmp_3'
JBCNOINTERNAL : Not Set
JEDI_NOSHMEM : Not Set
RELEASE Information : Major 4.0 , Minor 4 , Patch 0206
Spooler dir (JBCSPOOLERDIR) : '/usr/jspooler_dev'
WARNING: Cannot access Spooler directory '/usr/jspooler_dev', error 13
JBCEMULATE : 'prime'
Emulation Config file '/usr/jbc/jbase4.1/config/Config_EMULATE' OK
JBCEMULATE Label 'prime' found in file '/usr/jbc/jbase4.1/config/Config_EMULATE'
Executable search Path:
/usr/vac/bin:/usr/jbc/jbase4.1/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java131/jre/bin:/usr/java131/bin:.:/us
r/local/bin:/globus/dev/bnk/bnk.run/bin:/globus/dev/bnk/bnk.run/globuspatchbin:/globus/dev/bnk/bnk.run/globusbin:/usr/ccs
/bin:/usr/ucb
WARNING: Cannot access Executable path '/globus/dev/bnk/bnk.run/globuspatchbin', error 2
Shared Object search path: LIBPATH=/usr/jbc/jbase4.1/lib:/oracle9i/lib32:/usr/ccs/lib:/usr/lib
Found : '/usr/jbc/jbase4.1/lib/libjbase.so'
Found : '/usr/jbc/jbase4.1/lib/libjbaseutil.so'
Found : '/usr/jbc/jbase4.1/lib/libjcon.so'
Found : '/usr/jbc/jbase4.1/lib/libjsub.so'
Found : '/usr/jbc/jbase4.1/lib/libjlic.so'
Object path (JBCOBJECTLIST) :
'/globus/dev/bnk/bnk.run/globuspatchlib:/globus/dev/bnk/bnk.run/globuslib:/globus/dev/bnk/bnk.run/lib'
WARNING: Cannot access Object path '/globus/dev/bnk/bnk.run/globuspatchlib', error 2
Program dir (JBCDEV_BIN) : '/globus/dev/bnk/bnk.run/bin'

ASG Technical Guide
Program Path '/globus/dev/bnk/bnk.run/bin' is in your PATH

Subroutine dir (JBCDEV_LIB) : '/globus/dev/bnk/bnk.run/lib'
Subroutine path '/globus/dev/bnk/bnk.run/lib' is in JBCOBJECTLIST
Universe release can be obtained from RELLEVEL output

>.L RELLEVEL
RELLEVEL
001 X
002 9.4.1.3
003 INFORMATION
004 INFORMATION.FORMAT
005 9.4.1.3H
Driver release can be obtained from ORA/XMLdriver.log
R11.95548 - 9502740 - (EBS.TERMINAL.SELECT,73) - Mon May 7 10:30:42 - - -

Error - ORA-12537: TNS:connection closed
11.2 FTP commands

Below are some of the useful ftp commands, which can be used to transfer files to the
system.
Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.
U:\>c:
C:\>ftp

ASG Technical Guide
ftp> open 10.92.5.6

Connected to 10.92.5.6.
220 lclass FTP server (Version 1.1.214.8 Fri Apr 20 07:27:42 GMT 2001) ready.
User (10.92.5.6:(none)): intstu1
331 Password required for intstu1.
Password:
230 User intstu1 logged in.
ftp> pwd
257 "/globus2/HDareas/INfareas/intstu1/mbdemo/mbdemo.run" is current directory.
ftp> cd ..
250 CWD command successful.
ftp> cd mbdemo.jnl
ftp> bi
200 Type set to I.
ftp> get F.JOURNAL
200 PORT command successful.
150 Opening BINARY mode data connection for F.JOURNAL (2187264 bytes).
226 Transfer complete.
ftp: 2187264 bytes received in 0.19Seconds 11634.38Kbytes/sec.
ftp> cd mbdemo.dict
550 mbdemo.dict: No such file or directory.
ftp> cd ..
ftp> cd mbdemo.dict
ftp> get D_F.JOURNAL
150 Opening BINARY mode data connection for D_F.JOURNAL (4096 bytes).
ftp: 4096 bytes received in 0.00Seconds 4096000.00Kbytes/sec.

ASG Technical Guide
ftp> exit
Invalid command.
ftp> quit
221 Goodbye.
C:\>ftp
ftp> open 10.92.5.5
Connected to 10.92.5.5.
220 ibmrs6000 FTP server (Version 4.1 Fri Apr 6 03:07:22 CDT 2001) ready.
User (10.92.5.5:(none)): intstj1
331 Password required for intstj1.
Password:
230 User intstj1 logged in.
ftp> cd RICK.BP
ftp> BI
200 Type set to I.
ftp> put F.JOURNAL
150 Opening data connection for F.JOURNAL.
ftp: 2187264 bytes sent in 0.28Seconds 7783.86Kbytes/sec.
ftp> put D_F.JOURNAL
150 Opening data connection for D_F.JOURNAL.
ftp: 4096 bytes sent in 0.00Seconds 4096000.00Kbytes/sec.
ftp> QUIT
221 Goodbye.

ASG Technical Guide
11.3 DUMMY SELECT
In G130 & G131 release, to rerun a job, we need to insert a dummy select for the job. The
procedure for dummy select is a below. Please make sure to decatalog the dummy select
immediately after completing the job.
In Universe environment
a) Check the VOC for the program AC.STATIC.UPDATE.SELECT
> CT VOC AC.STATIC.UPDATE.SELECT
b) Create a dummy program as shown below:
> ED BP AC.STATIC.UPDATE.SELECT
------:I
0001 : SUBROUTINE AC.STATIC.UPDATE.SELECT
0002 : RETURN
0003 : END
------ : FI
>
c) Compile the program

> EB.COMPILE BP AC.STATIC.UPDATE.SELECT
d) Catalog the program AC.STATIC.UPDATE.SELECT back to its original voc before continuing the next process.
> CATALOG GLOBUS.BP AC.STATIC.UPDATE.SELECT LOCAL
In JBase environment:

ASG Technical Guide
1. Check the jshow

jsh patch ~ -->jshow -c AC.STATIC.UPDATE.SELECT
Subroutine: E:\emergedbs\patch\bnk\bnk.run\globuslib\lib23.dll
jBC AC.STATIC.UPDATE.SELECT version 4.0 Fri Jun 04 17:05:27 2004
jBC AC.STATIC.UPDATE.SELECT source file S:storage1globus.sourcespg131064
2. Create the dummy select in TEST.BP

--->JED TEST.BP AC.STATIC.UPDATE.SELECT
SUBROUTINE AC.STATIC.UPDATE.SELECT
RETURN
END
3. Compile the routine

jsh jbase ~ -->BASIC TEST.BP AC.STATIC.UPDATE.SELECT
jsh jbase ~ -->CATALOG TEST.BP AC.STATIC.UPDATE.SELECT
OR
jsh jbase ~ -->EB.COMPILE TEST.BP AC.STATIC.UPDATE.SELECT
4. Decatalog the routine from the directory after completing the job
jsh patch ~ --> DECATALOG TEST.BP AC.STATIC.UPDATE.SELECT
11.4 ERRMSG
The command can be used to identify the description of the error number
Example :
jsh r11 ~ -->ERRMSG 5

WIN32 API Error (5) - Access is denied.
The error number varies based on the OS, so it is always advisable to get the output
from the client system where the error happened.

ASG Technical Guide
11.5 Disk Space

Issues may happen due to lack of space in the disk. Disk space can be
monitored using the below command from unix
$df -k
11.6 Steps to bypass & Rerun in lower release

G13
The attached document contains the below procedure
How to bypass the job in G13.2.07
How to rerun the job in G13.2.07
Tips_ByPass_Rerun_
G13.doc
11.7 Procedure for Single Sided DC
The attached document contains how to input a single sided Data Capture to
Balance a system in case of imbalance in the system
DC.BATCH.CONTRO
L.doc
11.8 JEDI_SHM_WORKFILE Corruption
The 'JEDI_SHM_WORKFILE' is located in the jBASE release "tmp"

subdirectory. This file is used by jBASE programs to store shareable
information, such as current number of reads or writes, etc, which can then
be displayed via various utilities, e.g. SHOW-ITEM-LOCKS and WHERE \(V.
So if this file is corrupt we cannot get the correct output of commands like
SHOW-ITEM-LOCKS,mw42,WHERE etc.

ASG Technical Guide
The environment variable JEDI_NOSHMEM can be set to disable this feature

if required.The jshmem command can be used to interrogate the
JEDI_SHM_WORKFILE.
If the file 'JEDI_SHM_WORKFILE' is corrupt you can either do:
1) As root used, when no users (i.e., when no foreground and background

process are running)
jshmem -r
which will rebuild the table.
(or)
2) Remove the corrupt 'JEDI_SHM_WORKFILE' file, when no foreground

and background process are running. This file will get created during the next
login.
11.9 jBASE Printer setup and jspool corruption

The attached document contains the procedure to create a new jspool_log
file in case of corruption of the file and the procedure to assign the
formqueue.
If the file size of jspool_log is less (say less than 1GB), then it is advised to
run jcheck on the jspool_log file.
JBASE printer setup

document.doc
11.10 Procedure to Catalog Object Code
Procedure in jBASE
Catalog
_object_code_Jbase.doc

ASG Technical Guide
Procedure in Universe
Catalaog_Object
Code_Universe.doc
11.11 Segmentation Violation

This write up aims at helping the reader understanding and analyzing ‘jBASE:
Segmentation Violation’ issues from Application perspective. The document
contains some example errors and its solution.
Segmentation Violation.zip
11.12 Universe Commands
The document contains some basic useful Universe Commands
Univ_Cmds.doc
11.13 Server Restart

Restarting a Production Server should be in the below order.
Order for Shutdown
1. Stop tcserver / Webserver / jBOSS / jbase agent

2. Stop TSM
3. Shutdown the Application Server
4. Shutdown the Database server
Order in which the system should bring up

ASG Technical Guide
1. Start the Database Server

2. Start the application server
3. Start TSM
5. Start tcserver / Webserver / jBOSS / jbase agent
11.14 Frequently used commands
>LIST F.DATES TODAY NEXT.WORKING.DAY LAST.WORKING.DAY

CO.BATCH.STATUS
>LIST F.COMPANY MNEMONIC FINANCIAL.MNE
>LIST F.BATCH BATCH.STAGE PROCESS.STATUS JOB.NAME JOB.STATUS

FREQUENCY NEXT.RUN.DATE LAST.RUN.DATE BY BATCH.STAGE
>LIST F.TSA.STATUS WITH CURRENT.SERVICE EQ 'COB' AND WITH

AGENT.STATUS EQ 'RUNNING'
>chmod –R 777 ../bnk.data/ac/FBNK_ACCOUNT
12 Conclusion
We had included most of the procedures and routines in this document which can be used
as a guide to handle critical issues in ASG.. Please contact the ASG team Lead for any queries
or suggestions related to document.

ASG Technical Guide

ASG Technical Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ASG Technical Guide

Uploaded by

Copyright:

Available Formats

Product Analysis and Customer Support

Application Specialist Group

2 Product Analysis and Customer Support

Procedure to create new file for CATEG.ENTRY:.............................................................................26

3 Product Analysis and Customer Support

11.9 jBASE Printer setup and jspool corruption...............................................................................55

4 Product Analysis and Customer Support

1 1.0 14/10/2012 Initial Draft T. Aseel

5 Product Analysis and Customer Support

1. Production COB / EOD issues

2.COB / EOD issues

2.1 Some basic points on COB / EOD

A COB / EOD consist of five batch stages:

Stage Description of Activities

1- APPLICATION Individual application processes (Forex, Funds Transfer etc.)

3- REPORTING Main system reports (trial balance, general ledgers, transaction

6 Product Analysis and Customer Support

Single Threaded /Multi-threaded job

Model Bank PROGRAM FILE SEE

7 Product Analysis and Customer Support

PROCESS.STATUS or JOB.STATUS LOAD routine –

Session not doing select

Flow chart of a multi-threaded job

8 Product Analysis and Customer Support

CONTROL.LIST = processed STOP

2.2 Basic Information required in case of COB/EOD

i. Total EOD/COB duration time

9 Product Analysis and Customer Support

> LIST F.BATCH WITH BATCH.STAGE NE “” AND PROCESS.STATUS EQ 1 JOB.NAME

Information Specific to T24/Globus release:

For Globus releases below G13.2.07:

10 Product Analysis and Customer Support

BAT.<<Comp.mne>>_BATCH.NAME (After running MERGE.GUI.COMO)

For Globus releases G13.2.07 onwards:

>CT F.BATCH.STATUS SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1

11 Product Analysis and Customer Support

>CT F.BATCH.STATUS BNK/FILE.TIDY.UP-EB.CLEAR.FILES-3

The numeric values denotes

12 Product Analysis and Customer Support

156– Total No. of JOB.LIST ids

>CT F.LOCKING SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1

xi. The ERROR record in F.BATCH.STATUS.

xii. The respective EB.EOD.ERROR details.

For T24 release R4 onwards:

xiii. The above steps hold good for T24 R4 onwards.

xiv. Number of agents (tSAs) used for running the COB.

13 Product Analysis and Customer Support

3.LOCKS & Process information

14 Product Analysis and Customer Support

PORT PID FILENAME RECORD KEY LOCK# BY-PID

Procedure to stop and start the jRLA

15 Product Analysis and Customer Support

jrla locks can be monitored efficiently with jrla –dvL command

16 Product Analysis and Customer Support

2) Login as root and export the minimal environment variables required:

We assume jBASE is installed in '/usr/jbc', if not change the path accordingly.

3) Stop the jRLA daemon using the following command

T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS O

ipcrm -m <shared memory ID>

17 Product Analysis and Customer Support

ipcrm -s <semaphore ID>

In above case it would be

5) Start the jBASE demon in this order:

To stop the jDLS demon