Rene, you are a skilled Programmer. You shouldn't have to retire (especially
if you don't want to...)
Here are a couple of suggestions:
1. Can you peddle your COBOL skill on the Internet? If you offer a fixed
price (rather than an hourly rate) you may get some companies interested.
Guarantee the work (money back), be prepared to work from an outline of
their requirement (go through it carefully and make sure you clarify any
dodgy areas) and give them a time and a price. Make your initial prices very
competitive (but don't work for nothing :-)) Once you can establish some
credibility, look to expand your base. What's the worst that can happen? You
spend some time building a Web Site (and from what I've seen you are very
good at this) and you don't get a response. OK, you are no worse off and it
has only cost you time.
Don't get into details of what their COBOL environment or platform is and
whether you have experience with it. Focus on the functionality they need
and offering them a solution for a fixed price in a known timeframe. (If
they are running some version of COBOL on a platform you haven't worked
with, don't be intimidated. It is COBOL. There is a forum right here where
you can request advice for anything esoteric or unusal; focus on getting
them a solution.)
If you need some help or advice with any aspects of this, I'll be glad to
help you. (And I'm sure there are still others here who will too...)
2. Seriously consider leveraging your existing skills and be prepared to
learn the New Technology. I know that's what I always say, and have been
saying for around 25 years now, but I say it because it's true. There ISN'T
a living in standard COBOL anymore, except in a very limited marketplace,
for a very small percentage of programmers. Languages like VB.Net, C# and
Java, are NOT hard to pick up (you should see some of the idiots who have
done it...self included... :-)), and these are marketable skills.
Now, I'm not sure what the situation is in the Phillipines, but there is
another thing that is WELL worth remembering:
DON"T just do what you CAN do. (Whether it is COBOL or something else).
Instead, FIND OUT what is NEEDED and WANTED, then acquire the skills to
provide that.
Survey local in-house IT departments and ask them if they are interested in
reducing workload by LOCAL outsourcing, with a guaranteed price and
delivery. Don't get dejected if there isn't a raging response right away; it
takes a little time. Offer a problem solution; NOT a contract COBOL
programming service. You can start with COBOL but be prepared to look at
other things too. Maybe they need some web development support, maybe they
have some tedious JCL processes that they would like to have improved. Be
prepared to go and see people, make contacts, and LISTEN. Don't rule out
anything; if you can't do it yourself, maybe you know someone who
can...Become a "solutions guy". Be prepared to sub-contract if you pick up
something like a complete sub-system. Amateurs rush in and try to do
everything on day one, professionals pace themselves and plan their
workloads. You haven't achieved anything if you work yourself into a nervous
breakdown by long hours and overly ambitious deadlines. PLan everything
before you even think about pricing. Recognize where the risks are by
identifying what you have control over and what you don't.
(The very first contract job I ever undertook (in the late 1960s) was
writing some COBOL for an NCR 315 (a machine I had never even seen). The
applications weren't difficult and I got the programs written in pretty fast
time but I needed Job Control to run them and so on. I had no idea, so I
went and had a beer with one of the programmers in their data centre and
asked if he would write me what I needed. He was happy to and I paid him
cash (it was less than 5% of the contract and worth every penny.) I COULD
have sat down with the manual and taught myself what I needed but it was
much better to have it provided by someone who knew what they were doing...
and it wasn't going to be a key skill I would need for the future.)
The question of whether you retire or not is really down to you. If you feel
a bit stalled by COBOL, go round it.
You can be very certain that nobody is going to come to you with money
unless you raise your profile and show them you can add value to what they
are doing..
Best of luck and every good wish,