May 31 2006, 05:54 PM
QUOTE(cks2k2 @ May 31 2006, 07:45 AM)
I have to disagree on some of your points:
1. COBOL is still pretty much used in the banking industry, there's even a .net version of it
i second that...1. COBOL is still pretty much used in the banking industry, there's even a .net version of it
QUOTE(strongbaby @ May 31 2006, 10:30 AM)
If there is some banks still using COBOL, you have to tell me which bank,
i will tackle that bank as vendor.
yeah, i might be wrong by pointing out only the good ones and cast away the bad ones.
some language might be in good use for certain criteria, some not.
The reason is, the thread starter were asking for his future in job, thats why only
the good ones will be shown here for his best of luck.
SAP, all you need is 1 year to learn up, you're starting to feel many people are trying to get in, that's right. as said, msia facing shortage of SAP fellas.
COBOL is still pretty much needed in banking system. The company i'm working in right now, is a Credit card solution provider.....and our backbone is written in COBOL.i will tackle that bank as vendor.
yeah, i might be wrong by pointing out only the good ones and cast away the bad ones.
some language might be in good use for certain criteria, some not.
The reason is, the thread starter were asking for his future in job, thats why only
the good ones will be shown here for his best of luck.
SAP, all you need is 1 year to learn up, you're starting to feel many people are trying to get in, that's right. as said, msia facing shortage of SAP fellas.
As far as i'm concern, til now, Citibank are still using lotsa cobol programmer, not sure for it's core banking system though.
and SAP, everybody is getting their heads into this...ABAP, MM, PP....not tryna say your point is incorrect but mayb the thread-starter can use some lil perspectives here.
Quote
0.0139sec
0.41
6 queries
GZIP Disabled