What is EB.API? Why we need this?

Dear All,
I have no idea about EB.API, but Every time I write a subroutine I had to create a EB.API . Would you people tell me what is the purpose of EB.API?

I believe EB.API is mainly used to declare if a subroutine is a BASIC or JAVA executable to let T24 know how to call the routine if attached somewhere (i.e. doing a CALL or CALLJ).

Usually in T24 when you write a Subroutine and want to attach it into your Version( Eg. Input / Authorisation / Validation ...) you had to create an entry for that subroutine in the PGM.FILE table. This is how T24 validated the name of the subroutine. In the newer releases of T24 when it supported Java code, the PGM.FILE did not have a field to tell if the Code written is a Java Code or a jBASE Basic Code. To cater to this they created this EB.API where they had a field to specify if the code written is a Basic / Java Code. It is now made mandatory that all subroutines written for VERSIONs in T24 to have an entry in EB.API table. This is one of the reason why we have a EB.API table