Hi Pawel, The 'new' branches are introduced ( generally ) when there is a 'major' change in functionality provided, eg :
A brief ( simplified ) history : jBASE 4.0 ( the first Temenos release ) was based on jBASE 3.4 ( as used by jBASE International customers ) [ written in purest C ] jBASE 4.1 ( for both Temenos ( jBASE 4.1.5 ) and jBASE International customers ( jBASE 4.1.6 ) ) : removed the 'jPML' daemon, used in jBASE 4.0 and jBASE 3.4 allowed jBASE processes to be 'EXECUTE'd as threads ( within the current process ) new licensing mechanism introduced 64bit platforms ( eg HPUX Itanium ) added some C++ code ;-) etc jBASE 5 ( jBASE 5.0 for Temenos customers, jBASE 5.2 for jBASE International ) 64 bit ( only ) platforms new licensing mechanism R09 / R10 ( Temenos customers only ) 'naming change' to align with the Temenos T24 application 'naming' The currently supported 'branches' are kept 'in sync', regarding fixes for issues where appropriate ( and yes this is an additional complication for the support team ;-(, but I don't believe this as incurred additional costs to the customers ;-) ) Generally there have not been any occasions where there was something special for 'R09' that is not propagated into R10 and other subsequent releases Pat. On 18 Aug, 23:15, "Pawel (privately)" <[email protected]> wrote: > Hi Pat, > > I though I am reading about branches in SVN :) > > Excuse me for stupid question - but what was a reason for introducing > branches of major (jBASE 4 & jBASE 5) releases? I understand that you > have branches of major releases and you must (or should) keep them > somehow in sync (or will you not?). Will you require to do anything > special for R09, but not for R10? > I fully understand that jBASE 4 & jBASE 5 are having different codebase > (rumours say that jBASE 5 is partially written in C++ - not sure of > that). > Maintenance of branches will introduce you extra cost if I am not > mistaken. Support will (likely) not be cheaper. I do not understand what > was the reason behing changing versioning - except clear marketing (but > that does not count :)). > Clear marketing means - you use R09 - your TAFC is R09. I think that > users will not be able to compare easily installations :) > > Kind regards > Pawel > > Dnia 18-08-2010 o godz. 22:57 pat napisa (a): > > > Re the jBASE / TAFC release and Change number ( shown in the 'jdiag' > > output ) : > > > RELEASE Information : Major 09.0 , Minor 0.6 , Patch (Change > > 86864) > > > is TAFC R09 SP6 > > > RELEASE Information : Major 5.0 , Minor 22 , Patch 0373 > > (Change 87455) > > > is jBASE 5.0.22 patch release > > > The Change number(s ) shown, is the last change incorporated in said > > release > > The change numbering is 'global' across all releases, so for a change > > in any branch, beit jBASE 4.1.5, jBASE 5.0, TAFC R09, TAFC R10 etc, > > the ( global ) change number is incremented > > > So the change numbers above, (Change 86864) and (Change 87455), > > simply show that R09 SP6 was produced ( at change number 86864 ) > > before jBASE 5.0.22 was produced ( at change number 87455 ) > > > But as the change numbers are independent of the 'branch' ( R09 or > > jBASE 5.0 say), then these change numbers do NOT imply that jBASE > > 5.0.22 contains additional functionality, features or fixes over and > > above R09 SP6 > > > Pat. > > > On 18 Aug, 07:30, "FaktoriyeL !" <[email protected]> wrote: > > > Hi; > > > > Log size issue is very interesting for us. let me explain; > > > > we have two banks in different country that using T24.As I said The first > > > bank uses T24 R09 and TAFC. The other bank uses T24 R07 and jbase > > 4.1.5.11. > > > First bank creates 4 Million records and log size is 11 GB approx for each > > > day. The other bank creates 4 million records and log size is 3 GB > > approx > > > for each day. I think this is weird. Because record count is almost same. > > > > And yes we closed some files logging attirube. the files like following. > > > > (and I cannot analyze our log files. because all command (like SELECT > > LIST) > > > get this error) > > > > F.EB.PHANTOM > > > F.ACTIVITY > > > F.PROTOCOL > > > F.DE.SYSLOG > > > F.OS.TOKEN > > > F.OS.TOKEN.USE > > > F.DE.PHANTOM.LOG > > > F.TERMINAL > > > F.ENQUIRY.SELECT > > > F.ENQUIRY.LEVEL > > > F.OS.XML.CACHE > > > F.TSA.SERVICE > > > F.TSA.SERVICE$HIS > > > F.TSA.STATUS > > > F.BATCH.STATUS > > > F.JOB.TIMES > > > F.OFS.MSG.UNIQUE.REF > > > F.OFS.REQUEST.DETAIL > > > > and of course $JBCDIR/jbc/jspooler/* > > > > when we used old version of T24 (R06 and jbase 4.1.5) we did not get any > > > error message. we upgraded t24 version and jbase version (same time) and > > > this issue occurred. > > > > Thank you, Best Regards > > > > 2010/8/18 Pawel (privately) <[email protected]> > > > > > Hi, > > > > > So you should really stress out to CSHD that it is important issue and > > > > you really require assistance (you pay for it I belive!). I am sure they > > > > will help you - your Support and Account Managers are first escalation > > > > points. > > > > > Logsets 10 GB large from a whole business day is not anything uncommon. > > > > You should however check what you store to logsets. I hope you do not > > > > save unnecessary information like F.TSA.STATUS, F.TSA.SERVICE, > > > > F.EB.PHANTOM tables. These files you can safely exclude (jchmod -T if I > > > > remember well). > > > > Analyse logsets also to check which tables are most popular - perhaps > > > > you will find something that you do not need to keep. > > > > > Release information did not tell me much (Major 09.0 , Minor 0.6 , Patch > > > > (Change 86864)). > > > > I think that rebranding jBASE to TAFC and hiding (real?) version number > > > > will only introduce people's confusion. TAFC 9.06 is equal to jBASE 5, > > > > right? (which minor release by the way?) :| > > > > > Last thing (just comment): I see that you use gcc as compiler. Is this > > > > new default? We (and Temenos I think) are normally using xLC, which is > > > > shipped together with AIX. > > > > > I am afraid that I can not help you much. Does issue happen since you > > > > upgraded to R09? Has not it been adressed before upgrade? > > > > > Kind regards > > > > Pawel > > > > > Dnia 17-08-2010 o godz. 9:33 cengizhan napisa (a): > > > > > Firstly thank you very much for all your answers. > > > > > > We already have gone to Temenos Support. They wanted our TJ Log files > > > > > but the log file size is about 10 GB and log counts are about 4 > > > > > Million. Is this normal? Anyway I sent the files them but they have > > > > > not responded yet. we have been waiting for two months. > > > > > > And the other information. We had used jbase4 before jbase5. There was > > > > > no error. We upgraded our DBMS. And we got these errors. > > > > > > And I am so sorry for your rules. This is first post in this group and > > > > > I didn't know the rules. after that I will be more careful. > > > > > > jdiag - jBASE diagnostic '$Revision: 1.15 $' > > > > > > System Information > > > > > ================== > > > > > > System : AIX trkshaix 3.5 000CC802D900 > > > > > OS Release : 5.3.9.0 > > > > > UNIX User : bulent (uid 204, euid 204) > > > > > Tty name : /dev/pts/76 > > > > > Time : Tue Aug 17 10:22:58 2010 > > > > > > Environment > > > > > =========== > > > > > > JBCPORTNO : Not Set > > > > > JBCRELEASEDIR : '/opt/TAFC/R09' > > > > > JBCGLOBALDIR : '/opt/TAFC/R09' > > > > > WARNING: JBCDATADIR is not set, Default '/opt/TAFC/R09/jbase_data' > > > > > WARNING: JBCDATADIR is subdirectory of JBCGLOBALDIR > > > > > HOME : > > '/opt/globus/TBASLIV/bnk/bnk.run' > > > > > JEDIFILEPATH : '/opt/globus/TBASLIV/bnk/bnk.run' > > > > > JEDIFILENAME_MD : '/opt/globus/TBASLIV/bnk/bnk.run/VOC' > > > > > JEDIFILENAME_SYSTEM : '/opt/TAFC/R09/src/SYSTEM' > > > > > RELEASE Information : Major 09.0 , Minor 0.6 , Patch (Change > > > > > 86864) > > > > > Spooler dir (JBCSPOOLERDIR) : '/opt/globus/TBASLIV/bnk/bnk.run/ > > > > > jspooler' > > > > > JBCEMULATE : 'prime' > > > > > WARNING: Cannot access Executable path '/usr/vac/bin', error 2 > > > > > WARNING: Cannot access Executable path '/usr/local/bin', error 2 > > > > > WARNING: Cannot access Executable path '/opt/globus/TBASLIV/bnk/ > > > > > bnk.run/globuspatchbin', error 2 > > > > > WARNING: Cannot access Library path '/usr/java5/jre/lib/platform', > > > > > error 2 > > > > > Object path (JBCOBJECTLIST) : > > > > > '/opt/globus/TBASLIV/bnk/bnk.run/t24lib:/ > > > > > opt/globus/TBASLIV/bnk/bnk.run/gdGR0100040lib:/opt/globus/TBASLIV/bnk/ > > > > > bnk.run/globuspatchlib:/opt/globus/TBASLIV/bnk/bnk.run/lib:/opt/globus/ > > > > > TBASLIV/bnk/bnk.run/GR0300108lib:/opt/TAFC/R09/lib' > > > > > WARNING: Cannot access Object path '/opt/globus/TBASLIV/bnk/bnk.run/ > > > > > gdGR0100040lib', error 2 > > > > > WARNING: Cannot access Object path '/opt/globus/TBASLIV/bnk/bnk.run/ > > > > > globuspatchlib', error 2 > > > > > jBASE Compiler Run-time : '/opt/TAFC/R09/config/system.properties' > > > > > jcompile.ccjbc : 'gcc' > > > > > jcompile.ccjbc.options : '-fPIC -w -maix64' > > > > > jcompile.cc : 'gcc' > > > > > jcompile.cc.options : '-fPIC -w -maix64' > > > > > jcompile.cpp : 'g++' > > > > > jcompile.cpp.options : '-fPIC -w -maix64' > > > > > jcompile.ccslib : 'gcc' > > > > > jcompile.ccslib.options : '-shared -Wl,-brtl' > > > > > jcompile.ccexe : 'gcc' > > > > > jcompile.ccexe.options : '-shared -Wl,-brtl' > > > > > jcompile.output.file : '-maix64 -o' > > > > > jcompile.debug : '-g' > > > > > jcompile.optimise : '-O2' > > > > > jcompile.obj.extension : '.o' > > > > > Program dir (JBCDEV_BIN) : '/opt/globus/TBASLIV/bnk/bnk.run/bin' > > > > > Subroutine dir (JBCDEV_LIB) : '/opt/globus/TBASLIV/bnk/bnk.run/lib' > > > > > Max open files : 65534 > > > > > > Thank You.. > > > > > > On Aug 17, 12:48 am, "Pawel (privately)" <[email protected]> wrote: > > > > > > Hi, > > > > > > > Not sure about jBASE 5, but in 4.1.5.29 jBASE guys did a lot of > > > > > > updates > > > > > > to Transaction Journaling processes. We have reported only 1 serious > > > > (in > > > > > > our opinion) thing - "DB-PAUSE -art" seemed to not stop db activity > > > > > > properly. We suspect that problem is coming from older 4.1 release > > > > > > (did > > > > > > not test to be honest). There is a (little?) change that we also did > > > > not > > > > > > do everything properly (I am in doubts with problem reported)... > > > > > > > Get change logs for jBASE 5 - perhaps it is worth upgrading to newer > > > > > > minor release. Guys are really fixing issues and it is worth to read > > > > > > changelogs - to convince people to upgrade :) > > > > > > > Segmentation Violation problems are rather serious problems. Is in > > > > > > not > > > > > > that one related to your setup / OS (version)? Anything special? > > > > > > > Kind regards > > > > > > Pawel > > > > > > > Dnia 16-08-2010 o godz. 11:36 cengizhan napisa (a): > > > > > > > > Hi All; > > > > > > > > We are testing Transaction Journaling on our systems. The > > ... > > read more » -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
