EB.COMPILE ON R10

Just want to find out how compilation of programs are done on R10

the compilation on r10 is dependent on the type of license of r10 given to your bank. at r10 temenos expect no compilation of programs however this feature could be granted by temenos upon your organisation request or the vendor that implement your r10.

however, confirm this procedure from your end.

1.0 BASIC xxx.bp program-name
if successful, then do this;
2.0 CATALOG xxx.bp program-name

xxx.bp is the folder/directory created and where your program(s) is/are located

Note if step 1.0 above is not successful step 2.0 cannot be carry out.

thk u.

rgds

raf

Raf,
Thanks for your reply and the information.I will try it out and revert. Just a quick one do you know of any client that was granted the EB.COMPLIE. I understand it has to be done with alot of persuasion since Temenos wont budge if the request is made.

Nana,
I must say that uptill now i did not know of any site that Temenos has given EB.COMPILE.

Your bank might not be able to get it even if alot of persuation is employed.

Just talk to the vendor that handled your implementation or upgrade to handle the issue for better communication/persuation.

thank you.
rgds

Raf,
Thanks for your response.We tried the BASIC and CATALOGUE and it worked fine.
We having some coversation with our Account Manager on the way forward and will keep you posted on developments.
Do have a blessed day.

Hi,

Since R10 Temenos has launched a new concept around local developments using TAMS. Any bank wishing to develope local Versions or Enquiries is encouraged to use Tams where it can be documented.

This will allow for smoother upgrade paths with any and all local developments being documented and will also permit banks to benefit from local changes, i.e. a bank that developes a version that is relevant to that country can be packaged and distrbuted to all local banks.

Adam Norrington

Adam,

This is a very short sighted, revenue enhancing way of making your customers very irate. One of the key reasons banks choose T24 is it's flexibility and it's ability to be enhanced or amended in a timely and efficient manner by the bank itself. Yes upgrades are more complicated because of the local code but if managed correctly by experienced staff they can be limited to a normal task required every two years and not the heartache that some people seem to think it is.

This is a method employed by Flexcube and from experience and talking to other consultants, is that it is a very time consuming and expensive to get anything developed by Flexcube which has served many of its customers to regret buying the system in the first place !

I appreciate where you coming from here, especially with respect to other sites. The main point behind it though is that, if properly managed, it will significantly benefit banks in the long run.

In most cases the community that has made the most extensive use of EB.COMPILE has been MFI's. Most of them follow a strict 2 release upgrade which has allowed them to forgo a lot of the stress involved. Others however, have remained on a release for well over 10 years. This is where the problem lies, these clients have waited for so long and developed so much that an upgrade is no longer viable, but instead a re-implementation is needed. This is what we are now trying to avoid, by documenting local developments we can future proof the system allowing all our clients to upgrade at their own pace.

In some cases we are already talking with clients about back-working the local developments (devs) they have by a means of, identifying devs that have been hard coded into new releases or documenting the others. As well as receiving the devs from clients allowing Temenos to document them.

This will not work without the support of our clients and that, ultimately is what Temenos wants to achieve. Whenever a bank decides to choose a vendor for their Core Banking, historically it is seen as just a contract. We need to be partners in the sense that the Technology only evolves as the industry does, without the banks influencing us in what to change and how to change it the technology would stand still.

This isn't a quick fix solution, it is a long term investment and with the support of our clients we can continue to reduce the cost of ownership and provide a market leading solution.

Regards,

Adam Norrington

Hi Adam,

I worked with Globus and now have to use T24. Without Local Developement, especially Version Routines, NoFile Enquiries, Build Routines etc. you are lost as a bank.
its not easy to make TAM understand what you want and for 10 lines of code starting the "new process" and wait for months? I dont believe that this will ever work...
And I dont want to give my good ideas to Temenos and pay for it :-)

Lars wrote: wrote:

Hi Adam,

I worked with Globus and now have to use T24. Without Local Developement, especially Version Routines, NoFile Enquiries, Build Routines etc. you are lost as a bank.
its not easy to make TAM understand what you want and for 10 lines of code starting the "new process" and wait for months? I dont believe that this will ever work...
And I dont want to give my good ideas to Temenos and pay for it :-)

Lars, you just read my mind !

Hi Lars,
I agree wholeheartedly with what you are saying. Not wishing to give Temenos ideas, but why takeaway EB.COMPILE and leave BASIC/CATALOG? Equally you could argue that custom Enquiries and Local Ref fields are bank specific and would also need checking on each upgrade. Will these be locked down as well in future? It is because the development we get back from TAM is sometimes not what was asked for that we have to take to local development.

A better policy would be for Temenos to offer their clients the choice and if they do go down the local development route, explain to them how to better organise their code and the necessary testing procedures when an upgrade is due.

I don't understand how restricting EB.COMPILE and letting BASIC/CATALOGUE would actually restrict people from making local developments. Is there any difference between the two commands?

EB.COMPILE is stopped to give to clients.

Use below

BASIC -IGLOBUS.BP LOCAL.BP ROUTINE NAME
CATALOG LOCAL.BP ROUTINE NAME

TAM's future?? a very dark one... either TEMENOS will end up opening a lot of TAMs all over the world to be able to handle local developments or will release EB.COMPILE routines for the banks to do it themselves... i give it a year at most.

Check your Bank's Contract it should be specified there if your Bank has the right to use it.

assuming basic and catalog works, what about all the old inserts like i_common i_equate and so on, would any of the old ways of doing local devs also change, enquiry routines, new applications, nofile enquiries and etc?

I was not able to insert I_COMMON and I_EQUATE in R10 environment for local developments. I guess they wont be available for local developments henceforth.

Thanks for the Info jpb. Will do this.

And a little trick will be to create a VOC entry
for GLOBUS.BP to point at T24.BP ( or T24_BP)..