Use of EB.ALTERNATE.KEY

What is the use of EB.ALTERNATE.KEY application??

Great power comes with great responsibilities.

EB.ALTERNATE.KEY

This is a seperate table which holds the details of the alternate key
for the regular @ID of the Globus table.



CONCAT.TYPE

This field decides if a concat file should be created for an alternate key.
If 'SYSTEM' is specified, the concat file is created.


ALT.KEY.FIELD

Valid field name on the Standard selection record for the application can be specified here.

The field specified must be defined as a SYS.FIELD.NAME or USR.FIELD.NAME on the STANDARD.SELECTION record for the APPLICATION.

The name of the file to which the alternate key or keys defined in the record are to be applied.


ACCESS METHOD

If READ is specified then the concat file maintained for the alternate key will be read to get the real key for an alternate key input.

If SELECT is specified, concat file will be selected if there is one for this alternate key.

The 'SELECT' option may have some performance implications.
It is recommended to use the 'READ' option for better performance.


If a routine is defined then it will be executed to get the real key.

BNK TESTBASE EB.ALTERNATE.KEY INPUT

APPLICATION....... ACCOUNT ACCOUNT

---

1 ALT.KEY.MAX.LENGTH 7
2. 1 ALT.KEY.FIELD.. ALT.ID.ACCT
3. 1 CONCAT.TYPE.... SYSTEM
4. 1 ACCESS.METHOD.. READ ((READ, SELECT or @ROUTINE allowed;
SELECT is allowed only if the field UNIQUE is set as ?SYSTEM? or ?? )
5. 1 UNIQUE.........
6. 1 ENQUIRY........
7. 1 BUILD.ROUTINE..
8. 1 VALIDATION.RTN.

The file will be created with the name APPLICATION NAME.ALTERNATE FIELD,for ex



if the alternate key field is ALT.ID.ACCT for Account then the file created is



F.ACCOUNT.ALT.ID.ACCT



EB.ALTERNATE.KEY is very helpfull at the time of data migration when the client switiches from different system to T24.




SharathNP

Think positive