Jobs for old cobol programmer - cobol
This is a discussion on Jobs for old cobol programmer - cobol ; Hi all
I originally got my start into programming back in '74 at Corp.
Allstate as an IBM 360 assembler programmer. Went to Corp Motorola
after a couple of years where started programming in cobol and after a
couple of ...
-
Jobs for old cobol programmer
Hi all
I originally got my start into programming back in '74 at Corp.
Allstate as an IBM 360 assembler programmer. Went to Corp Motorola
after a couple of years where started programming in cobol and after a
couple of years moved on to other companies coding cobol and was the
manager of an IMS/DBDC department. I still code cobol on an old Wang
Operating System running in a VM environment but since about 92 have
coded in Topspeed, Python, Ruby some VB ,Access. Still coding cobol
but have lost skills in jcl etc.
Any advice on looking for jobs to get back in the mainframe
environment.
Len Sumnler Jr
-
Re: Jobs for old cobol programmer
In article <71a0517b-4eb2-467c-9a18-40309cd8423a@m36g2000hse.googlegroups.com>,
len <lsumnler@gmail.com> wrote:
>Hi all
>
>I originally got my start into programming back in '74 at Corp.
>Allstate as an IBM 360 assembler programmer.
[snip]
>I still code cobol on an old Wang
>Operating System running in a VM environment but since about 92 have
>coded in Topspeed, Python, Ruby some VB ,Access.
I've no particular advice for you, Mr Sumnler, outside of The Usual...
http://www.indeed.com being, in my experience, the most wide-ranging of
search-sites. I wish you the best of luck in your hunting.
(if you are looking for a job because you want one, well and good... if
you are looking for a job because you need one then it is curious that
you're not able to find one in decade-and-a-half-old skills and are
falling back on three-decades-old skills)
DD
-
Re: Jobs for old cobol programmer
On Mon, 5 May 2008 12:59:53 -0700 (PDT), len <lsumnler@gmail.com> wrote:
>Hi all
>
>I originally got my start into programming back in '74 at Corp.
>Allstate as an IBM 360 assembler programmer. Went to Corp Motorola
>after a couple of years where started programming in cobol and after a
>couple of years moved on to other companies coding cobol and was the
>manager of an IMS/DBDC department. I still code cobol on an old Wang
>Operating System running in a VM environment but since about 92 have
>coded in Topspeed, Python, Ruby some VB ,Access. Still coding cobol
>but have lost skills in jcl etc.
>
>Any advice on looking for jobs to get back in the mainframe
>environment.
Search for keyword MVS. If they are still clinging to an operating system name that was
obsolete eight years ago, you know their clock stopped at least a decade ago.
Re-learn CICS and DB2.
Do not mention Python or Ruby on your resume nor in conversation. Mainframers think that's
the enemy.
In Chicagoland, Discover is always looking. Of course, there's a reason why.
-
Re: Jobs for old cobol programmer
Isn't Python just a script tool?
On Mon, 05 May 2008 23:00:47 -0500, Robert <no@e.mail> wrote:
>On Mon, 5 May 2008 12:59:53 -0700 (PDT), len <lsumnler@gmail.com> wrote:
>
>>Hi all
>>
>>I originally got my start into programming back in '74 at Corp.
>>Allstate as an IBM 360 assembler programmer. Went to Corp Motorola
>>after a couple of years where started programming in cobol and after a
>>couple of years moved on to other companies coding cobol and was the
>>manager of an IMS/DBDC department. I still code cobol on an old Wang
>>Operating System running in a VM environment but since about 92 have
>>coded in Topspeed, Python, Ruby some VB ,Access. Still coding cobol
>>but have lost skills in jcl etc.
>>
>>Any advice on looking for jobs to get back in the mainframe
>>environment.
>
>Search for keyword MVS. If they are still clinging to an operating system name that was
>obsolete eight years ago, you know their clock stopped at least a decade ago.
>
>Re-learn CICS and DB2.
>
>Do not mention Python or Ruby on your resume nor in conversation. Mainframers think that's
>the enemy.
>
>In Chicagoland, Discover is always looking. Of course, there's a reason why.
** Posted from http://www.teranews.com **
-
Re: Jobs for old cobol programmer
On Tue, 06 May 2008 22:09:07 -0400, Graham Hobbs <ghobbs@cdpwise.net> wrote:
>Isn't Python just a script tool?
It compiles to byte code, similar to Java and .NET (CIL). There has been some work on JIT
compilation and straight compilation via C++.
AcuCobol and R/M Cobol compile to byte code. I wouldn't call them 'just a script tool.'
>On Mon, 05 May 2008 23:00:47 -0500, Robert <no@e.mail> wrote:
>
>>On Mon, 5 May 2008 12:59:53 -0700 (PDT), len <lsumnler@gmail.com> wrote:
>>
>>>Hi all
>>>
>>>I originally got my start into programming back in '74 at Corp.
>>>Allstate as an IBM 360 assembler programmer. Went to Corp Motorola
>>>after a couple of years where started programming in cobol and after a
>>>couple of years moved on to other companies coding cobol and was the
>>>manager of an IMS/DBDC department. I still code cobol on an old Wang
>>>Operating System running in a VM environment but since about 92 have
>>>coded in Topspeed, Python, Ruby some VB ,Access. Still coding cobol
>>>but have lost skills in jcl etc.
>>>
>>>Any advice on looking for jobs to get back in the mainframe
>>>environment.
>>
>>Search for keyword MVS. If they are still clinging to an operating system name that was
>>obsolete eight years ago, you know their clock stopped at least a decade ago.
>>
>>Re-learn CICS and DB2.
>>
>>Do not mention Python or Ruby on your resume nor in conversation. Mainframers think that's
>>the enemy.
>>
>>In Chicagoland, Discover is always looking. Of course, there's a reason why.
>
>** Posted from http://www.teranews.com **
-
Re: Jobs for old cobol programmer
On May 7, 2:09 pm, Graham Hobbs <gho...@cdpwise.net> wrote:
> Isn't Python just a script tool?
It can be used as a scripting tool, but it scales very well and can be
used to develop serious applications. For example see Stoq
http://en.wikipedia.org/wiki/Stoq
http://www.stoq.com.br/index.php?lang=en