Friday, June 14, 2013

JBase / T24 Administration

What are Basic Topics in T24:


 1. Jbase programming
2. T24 Architecture
3. Types of Files or Templates
4. Template programming
5. API development
6. OFS (Open Financial Service)
8. COB Management
9. Multi-threading of COB jobs
10. Secure Management System (User & Privileges)
11. Customer (T24 is customer centric)
12. Accounts
13. Accounting entries
14. Enquiry
15. Reporting

Detailed Content

        monitoring the COB
        Re-launching of a BATCH (COB) process after a crash
        Check a user activity on T24 or a phantom instance under Unix
        In which library has been compiled a program
        Show current locks
        Create a standard file under Jbase
        Search in an archived F.JOURNAL under Jbase
        Resize a table
COB Monitoring
For the monitoring of the COB there are some important tools.
        T24 desktop command ENQ AGENT.STATUS which shows the number of the agents running the COB and the relevant job that each agent runs.
        COB.MONITOR. This command given via mainline routine could provide a general overview of the % progress of the COB.
        nmon -s1 command given via jshell provides also an overview of the CPU and common bin usage.
        TOPAS again via jshell provides the most active Process ID and system I/O CPU usage and some more useful info about the current status of the system.

Re-launching of a BATCH (COB) process after a crash

After a job crash, selection lists may be still filled with keys. You have then to clear theses files, for EACH COMPANY:


Note that 4 is just an example here, it depends on the number of telnet sessions opened during the COB. (Cf field #32 BATCH.SESSIONS from SPF). If you get the following message: “BATCH.JOB.CONTROL -> Aborting” There’s a record ERROR in F.BATCH.STATUS to delete. When it is possible, you can re-run a job which has crashed. If the job is not re-runnable (as T24 tells it you) but you think it can be re-run anyway: Change the property of the job in PGM.FILE in the field 3 ADDITIONAL.INFO to set R (stands for re-runable batch job). Note that you must be 100% sure that this won’t corrupt your COB, for instance there’s not any dependencies with other jobs.

Check a user activity on T24 under Unix

        Check the Unix process ID (pid) in the UV column for the enquired user/activity.

Under Jbase: BKS (shell T24):

WHERE (V <pid>

The Command column contains full details.

        Check details about a phantom process

You can create a paragraph in your voc with:


  0001 PQN
  0002 IF # %2 MV #1 "ps -eaf|grep -E -i 'PHANTOM|catalog|xrlistener|jbase_agent'"
  0003 IF %2 MV #1 "ps -eaf|grep -E -i 'PHANTOM|catalog|xrlistener|jbase_agent'|grep -i '"%2"'"
  0004 PU

Example: CHECK.PHANTOM SWIFT will show you all instances of phantom’s names containing SWIFT under your server.

  In which library has been compiled a program

ED VOC <prog_name>  or  jshow -c <prog_name>

Show current locks

show-item-locks or jrla -d V or LIST.READU

Create a standard file under Jbase

create.file FILENAME TYPE=UD

Search in an archived  F.JOURNAL under Jbase


with LIST.JS is an entry in the VOC declared like this (depending on your history files directory)

  0001 PQN
  0002 IF # %2 XArgument missing. Usage: LIST.JS YYYYMMDD or list.js YYYYMMDD
  0003 MV #1 "LIST ../bnk.arc/F.JOURNAL.SAVE/"*%2*" USING DICT F.JOURNAL " %3,*
  0004 P

Resize a table

        Let Jbase analysing a table automatically:


        Let Jbase applying its analyse:


        Force a resize with a different modulo/separator (m) (2 notions were distinct under Universe, now same under Jbase):


jABSE performance increasing 

Periodically You may run following Command get performance

CREATE-INDEX     Define and create indexes.
DELETE-INDEX     Delete existing index definitions.
LIST-INDEX     Display index definitions.
QUERY-INDEX     Using and index for inquiry.
KEY-SELECT     Using and index for inquiry.
REBUILD-INDEX     Rebuild indexes.
VERIFY-INDEX     Verify index integrity.