HP3000-L Archives

May 2008, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Wed, 7 May 2008 14:00:16 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (73 lines)
I am currently working on a Cobol/View/Image 3K migration to HPUX using 
AcuCobol, SP2 thinclient, and Eloquence.

I personally would prefer Linux/Fujitsu Cobol/SP2/Eloquence with 
supporting/optional technologies like "C", Java, PHP, Perl, and MySQL

Migration choices really depend on your current HP3000 environment, like 
"Cobol/View/Image" being a very common HP-3000 environment, as well as 
environments that mostly consist of purchased/canned software. More 
variant in-house development environments may require trans-pilers to 
convert MPE only languages like SPL, HP basic or Transact, to something 
like Cobol "C" or Java.

You could benefit from waiting to migrate if you are not dependent on a 
Application Software Vendor and all is running well, using 3rd party 
Hardware & OS Software support . Some argue that by saying; "The longer 
you wait the less likely it will be to find the expertise to do your 
migration." I think there will be less expensive solutions available 
down the road, "Independent Contractors" like myself will most likely be 
able to do things with less overhead, and maybe even develop user 
friendly inexpensive software that will do most of the migration for 
you. I've already developed some of these tools for my own tool bag (aka 
Flash Memory), they're just not user friendly right now.

Migration plans should include applications built on technology that 
will run on any hardware, operating system, database, and one that will 
be available for decades to come.  Look at technology that stands on it 
own, technology that can't be taken out by one choice from one company.

   1. Posix/Unix type Operating systems (linux).
   2. Hardware that is high quality and generic enough to be updated
      easily without needing to repurchase the entire machine.
   3. Database's like Postgres, MySQL,  Oracale, Eloquence, that will
      run on most anything.
   4. Compilers/Languages:  "C" will be around forever, but NOT a first
      choice for application coding. For applications Cobol still fits
      into the "Run on any Hardware, and will not be taken out"
      category, Java also is a great choice for new development. I would
      not rely on any of the "Visual" languages because they seem to tie
      you to one IDE.
   5. Development Environment (IDE) should also be Language independent
      and OS independent.


-- 
Michael Anderson,
J3k Solutions
Sr.Systems Programmer/Analyst
832.515.3868





Ron Seybold wrote:
> Hello Friends,
>
> I am writing a story for our May issue about the progress and choices 
> you've made in migrating off your HP 3000. Can you tell me where you 
> have taken the 3000's computing? What's your schedule?
>
> If you can include a note or two about why, or how the migration is 
> going -- like if you plan to finish by the end of this year -- I'd 
> really appreciate it.
>
> Thanks for the help. Even an answer of "HP-UX" or "Windows" or another 
> environment will really tell me a lot.
>
> Best of luck to all of you,

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2