|
View previous topic :: View next topic
|
| Author |
Message |
Adam
New User
Joined: 17 Jun 2005
Posts: 7
|
|
|
|
What are possible migration paths from the following environment:
z/OS, DB2, VAGen 3.0, COBOL, CICS, MQ to z/OS.e.
Most of the programs are VAGen generated COBOL/DB2/MQ/CICS ones.
The typical program is triggered by MQ in CICS and then write some data to DB2.
All opinions are welcome.
Regards
Adam |
|
| Back to top |
|
 |
reardons
New User
Joined: 08 Jun 2006
Posts: 5
|
|
|
|
Adam,
If you folks are looking to cut costs, keep your current legacy apps, and save even more money, I'd recommend migrationg to the iSeries. Same security, better performance. I can explain further if you'd like.
Regards,
Ben |
|
| Back to top |
|
|
reardons
New User
Joined: 08 Jun 2006
Posts: 5
|
|
| Back to top |
|
|
Adam
New User
Joined: 17 Jun 2005
Posts: 7
|
|
|
|
Thanks for the reply, Ben.
Sorry but migration to iSeries is not possible. It must be true Mainframe - even z9BC. I have some ideas but I want to know other people opinion too.
PS. I read article you mention -very interesting. |
|
| Back to top |
|
|
sasman
New User
Joined: 18 Jul 2006
Posts: 5
|
|
|
|
We run a z800 with 5 lpars, 2 of which are zOSe lpars and the migration from the legacy lpars was not hard at all. Since we didn't need to run any CICS or COBOL programs on the zOSe lpars, everything was relatively easy to move. One thing to consider when migrating may be to run multiple lpars. . . one for the legacy CICS/COBOL stuff and a zOSe lpar for the DB2/MQ things. Third party software will normally run unless it uses COBOL which means it will only run on the legacy lpar. Doing this will give you a price break since you will not be licensing CICS and COBOL on the entire machine but only on part of the machine. Third party software though is still licensed on the entire machine which can be very costly. The only things that need to be done to use the zose lpar is of course the lpar name and then making some parmlib changes which are very minor.
The price breaks on the operating system software were, in our case, enough to justify us splitting the box into the legacy lpars (CICS and COBOL) and the zOSe lpars. Good luck!! And I don't think you'll have any problems except for CICS/COBOL. |
|
| Back to top |
|
|
Adam
New User
Joined: 17 Jun 2005
Posts: 7
|
|
|
|
Splitting the box is considered but main aim is eliminating CICS/COBOL part of processing. It is possible in many ways. One example:
-upgrade VAGen to EGL
-generate Java code
-use (or not) WAS |
|
| Back to top |
|
|
|
|
