Forum
Keyword
× Discuss on Template programming, jBASE programming, Enquiries, No-File enquiry, Enquiry routines, Version, Version routines, Menus, Abbriviations, Creating local reference fields, Fast path enquiries, Creating charts and graphs, Generating Reports, Deal slips, Straight through processing, Multi Company and Multi Book setup, Tabbed screens, Composite Screens, T24 API, etc...

Recognize core or local component

  • richard
  • richard's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 123
  • Karma: 1
  • Thank you received: 1

richard created the topic: Recognize core or local component

Hi all,

Is there any way to identify the component/data record/element is core or local. As in every release there are some components available of older release as well for example: FUNDS.TRANSFER,AUDIT in R14 release shows in audit fields as below
PGM.NAME.VERSION.. FUNDS.TRANSFER,AUDIT
 ------------------------------------------------------------------------------
  67. 1 GB D Audit
  87. 1 ATTRIBUTES..... NO.HEADER.TAB
 103 CURR.NO........... 3
 [color=red]104. 1 INPUTTER....... 1_201111[/color]
 105. 1 DATE.TIME...... 28 MAR 14 13:28
 106 AUTHORISER........ 98220_INPUTTER_OFS_MB.OFS.AUTH

and in some records as
PGM.NAME.VERSION.. AA.ACCOUNT.CLOSURE.DETAILS,INPUT
 ------------------------------------------------------------------------------
  87. 1 ATTRIBUTES..... CUSTOM.VERSION.ALIGN
 103 CURR.NO........... 1
 [color=red]104. 1 INPUTTER....... 1_R12m[/color]
 105. 1 DATE.TIME...... 28 MAR 14 13:23

OLDER release records have been carry forward if we try to use this INPUTTER/AUTHORISER concept, is there any other way to list these.

Best Regards,

Think green – keep this on the screen
#21339

Please Log in or Create an account to join the conversation.

  • VK
  • VK's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • R13|TAFC|jBASE|windoze
  • Posts: 441
  • Karma: 7
  • Thank you received: 58

VK replied the topic: Recognize core or local component

Hi
Normally there's an agreement for how to name local developments. For example, if your bank abbreviation is XY, then you name the VERSIONs like:
FUNDS.TRANSFER,XY.AUDIT

If there's no such agreement, then you have to check INPUTTERs for all history records. Of course if you users use personal USER IDs and not INPUTTER/AUTHORISER etc.

Cheers
VK
#21340

Please Log in or Create an account to join the conversation.

  • richard
  • richard's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 123
  • Karma: 1
  • Thank you received: 1

richard replied the topic: Recognize core or local component

Hi VK,

Here I have to differentiate local verses core data records, I understood as you said we can check via the prefixes.
But here the implementation which has not done as per this standards.
Records were been created with no prefix, which is bit confusing to identify by name whether it is core or local.

Best Regards,

Think green – keep this on the screen
#21341

Please Log in or Create an account to join the conversation.

  • VK
  • VK's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • R13|TAFC|jBASE|windoze
  • Posts: 441
  • Karma: 7
  • Thank you received: 58

VK replied the topic: Recognize core or local component

You can try to take "Model Bank" (a demonstration one with fake customers and accounts) and compare it to your environment. If you don't have "Model Bank", request it from Temenos.

Cheers
VK
#21342

Please Log in or Create an account to join the conversation.

  • richard
  • richard's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 123
  • Karma: 1
  • Thank you received: 1

richard replied the topic: Recognize core or local component

Thanks VK, I believe you are asking to compare the individual records and figure out is it core or local that probably we can do it if the count of records are less.

But what if I have to check among the VERSION application where you have huge number of records as below
jsh r13 ~ -->SELECT F.VERSION

 9076 Records selected

>

Best Regards,

Think green – keep this on the screen
#21344

Please Log in or Create an account to join the conversation.

  • VK
  • VK's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • R13|TAFC|jBASE|windoze
  • Posts: 441
  • Karma: 7
  • Thank you received: 58

VK replied the topic: Recognize core or local component

Firstly just check @IDs - those which are absent in "Model bank" are most probably local ones.
Then you'll need to compare records that are common... I think a program should be written for that.

Cheers
VK
#21345

Please Log in or Create an account to join the conversation.

  • Posts: 8
  • Thank you received: 2

jshanmugasundaram replied the topic: Recognize core or local component

Hi,

Please check F.PGM.DATA.CONTROL & F.RELEASE.DATA
#21351

Please Log in or Create an account to join the conversation.

  • richard
  • richard's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 123
  • Karma: 1
  • Thank you received: 1

richard replied the topic: Recognize core or local component

Thank you, this resolved my problem

Best Regards,

Think green – keep this on the screen
#21352

Please Log in or Create an account to join the conversation.

  • VK
  • VK's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • R13|TAFC|jBASE|windoze
  • Posts: 441
  • Karma: 7
  • Thank you received: 58

VK replied the topic: Recognize core or local component

Hi
I'm not sure we can trust these tables much - after 5 minutes of trying I found a core record that isn't there:
F.AUTO.ID.START>CUSTOMER

Given more time (that alas I don't have) more records might be found.

Also, you need to keep in mind that very often the local developers amend core records...

Cheers
VK
#21353

Please Log in or Create an account to join the conversation.

  • richard
  • richard's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 123
  • Karma: 1
  • Thank you received: 1

richard replied the topic: Recognize core or local component

Okay VK, will have a check around this too.

Best Regards,

Think green – keep this on the screen
#21354

Please Log in or Create an account to join the conversation.

  • Posts: 8
  • Thank you received: 2

jshanmugasundaram replied the topic: Recognize core or local component

Hi,

AUTO.ID.START>CUSTOMER is not a core component but AUTO.ID.START of STANDARD.SELECTION is a core component and you can find the same.

@ID......... F.STANDARD.SELECTION>AUTO.ID.START
@ID......... F.STANDARD.SELECTION>AUTO.ID.START
PGM.DATA.ID. F.STANDARD.SELECTION>AUTO.ID.START
PRODUCT..... EB
SUB.PRODUCT.
OBSOLETE....
SOURCE.REQ.. Y
COMPONENT... EB_SystemTables
#21367

Please Log in or Create an account to join the conversation.

  • VK
  • VK's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • R13|TAFC|jBASE|windoze
  • Posts: 441
  • Karma: 7
  • Thank you received: 58

VK replied the topic: Recognize core or local component

Hi

AUTO.ID.START>CUSTOMER is not a core component


Really? Looks like core to me. What I think is that before certain point in time core components were not listed in that table...
     KEY............... CUSTOMER
 ------------------------------------------------------------------------------
   1. 1 DESCRIPTION.... CUSTOMER NUMBERS
   2. 1 APPL CUSTOMER
   3. 1 ID.START....... 100000
  18 CURR.NO........... 1
  19. 1 INPUTTER....... 66_J.LORD
  19. 2 INPUTTER....... 27_CONV.AUTO.ID.START.G11.0.01
  20. 1 DATE.TIME...... 05 DEC 94 14:44
  21 AUTHORISER........ 66_J.LORD
  22 CO.CODE........... xx-001-0001
  23 DEPT.CODE......... 200       

Cheers
VK
#21370

Please Log in or Create an account to join the conversation.

  • Posts: 8
  • Thank you received: 2

jshanmugasundaram replied the topic: Recognize core or local component

I hope nothing can be confirmed in G series "05 DEC 94" since we are in current generation of R13. :-)
#21376

Please Log in or Create an account to join the conversation.

  • VK
  • VK's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • R13|TAFC|jBASE|windoze
  • Posts: 441
  • Karma: 7
  • Thank you received: 58

VK replied the topic: Recognize core or local component

Hi

I hope nothing can be confirmed in G series "05 DEC 94" since we are in current generation of R13. :-)


"G" series and "R" series are the same product, not different ones.

I checked VERSION records that were introduced in "G" time. They are definitely core but they are not in the F.RELEASE.DATA. Try:
SELECT F.VERSION SAVING EVAL "'F.VERSION>':@ID"
SAVE.LIST VER
GET.LIST VER
SELECT F.RELEASE.DATA

You'll see about 2000 errors "not in file".

For you "core" is "introduced in R series". For topic starter "core" is "supplied by Temenos".
So I afraid your advice to use F.RELEASE.DATA is not very useful :))

Cheers
VK
#21377

Please Log in or Create an account to join the conversation.

  • Posts: 8
  • Thank you received: 2

jshanmugasundaram replied the topic: Recognize core or local component

I hope it was helpful for RICHARD and some people.
#21383
The following user(s) said Thank You: VK

Please Log in or Create an account to join the conversation.

  • VK
  • VK's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • R13|TAFC|jBASE|windoze
  • Posts: 441
  • Karma: 7
  • Thank you received: 58

VK replied the topic: Recognize core or local component

Hi
Thanks anyway because I never stumbled upon these tables before :)))

Cheers
VK
#21384

Please Log in or Create an account to join the conversation.

Time to create page: 0.176 seconds