|
View previous topic :: View next topic
|
| Author |
Message |
chinnielr
New User
Joined: 11 Jul 2005
Posts: 87
|
|
|
|
We have a requirement to migrate the batch jobs (DB2 using QMF) running in mainframe to Micro Focus (MF) environment.
The idea behind this exercise to save the MIPS cost in mainframe.
Can you pls. provide some more information on this migration on how it can be done, it's intricacies, savings details etc.
Is MF environment is really cost effective when compared to mainframe environment?
Your information will be really helpful in implementing this excercise.
Regards,
Chinni. |
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Without knowing an enormous amount about your system, this is impossible for us to answer.
It does entirely depend on your system, but I'd worry that the task your company is embarking on is akin to pushing water uphill.
You need people on site, timing, proving, evaluation of development/testing strategies for the migration and for future development, etc, etc, etc, etc.
Find a good consultancy. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
since this is a forum devoted to mainfraimes,
it seems INAPPROPRIATE(*) to ask how to get rid of them 
(*) substitute any MUCH STRONGER adjective for it
I really feel that it should be moved to the off topics, locked and later deleted ! |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Is this question about running MicroFocus on the mainframe or moving to some other platform?
If this is about moving away from the mainframe, it does not belong here. . . |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
Our shop develops on Microfocus, then migrates code to the mainframe for final testing and implementation.
It saves a LOT of wear and tear on the test environments. Everybody gets their own mainframe 'emulator' that can run COBOL/IMS programs. They have their own databases, with their own test cases in them.
We don't do DB2 on it, but it's an option. We don't have it because our DB2 stuff is currently "low maintenance" and not enough people are working on it to cause contention.
I kind of have the same question as the others though. Are you saying your shop wants to take DB2 stuff that is currently running on the mainframe, and port it to run on a Microfocus platform server/PC. Then run your production jobs from Microfocus? If so, would the DB2 servers still be on the mainframe? |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| Ed Goodman wrote: |
Our shop develops on Microfocus, then migrates code to the mainframe for final testing and implementation.
It saves a LOT of wear and tear on the test environments. Everybody gets their own mainframe 'emulator' that can run COBOL/IMS programs. They have their own databases, with their own test cases in them. |
My company did likewise about sixteen years ago, on the last project where I wrote any COBOL. As I recall, we developers put up with this for about two weeks, and then demanded connectivity to an actual mainframe, because of the non-trivial differences between Microficus and IBM COBOL.
That was, as I said, sixteen years ago; things have undoubtedly changed in the interval. It would be well, though, to verify that the savings in development won't be eaten up by the cost of porting the code back and forth. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
To repeat. . . .
| Quote: |
Is this question about running MicroFocus on the mainframe or moving to some other platform?
If this is about moving away from the mainframe, it does not belong here. . . |
MicroFocus now has this:
| Quote: |
Mainframe Express Enterprise Edition delivers a complete mainframe development environment on Windows. Organizations benefit from significantly increased developer performance and productivity.
Improve developer productivityDeveloper productivity can increase by over 35% by off-loading the development environment of a mainframe application to Windows. This is achieved by giving developers access to far greater processing power than is usually available to development processes in mainframe environments. These productivity improvements deliver additional business benefits: Time-to-market can be reduced, development costs are reduced and resources can be freed for more innovative developments which increase competitiveness. |
From what i've heard (no client is usng this on things i work with) the mainframe compatability is quite good now. It is also possible to run a virtual mainframe on the win-based systems to relieve the pain of moving source back and forth. |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
That's what we have, MFE.
We use it for IMS development and it's been good for us.
If I could change anything, it would be to have it emulate randomized IMS databases. Now, it treats them all as HIDAM. That causes trouble when a developer codes an SSA asking for the next segment "greater than the last one". It work great on MFE, fails on mainframe.
It's really nice for prototyping things. You can take an entire system and mess with it, break it, put it back together, test it with real data and demonstrate it from one PC. And none of it affects any other users. |
|
| Back to top |
|
|
|
|
