If they are moving from Solaris then IBM used to have (and probably still has) a tool which you run against the customer's source code to identify areas that need attention when porting (e.g. use of Solaris threads v POSIX threads). It produces a nice report that makes the porting effort easier.
If you are looking at moving databases then it's a matter of unload/load. If they are different database managers then there's going to be more work (schema differences, different implementation of standards, procedural languages etc.). If they have executables but no source and there's no version of that package available for Linux on z then you will have to go through a process of determining functional equivalences and will probably have to compromise on features. In some instances, there may be no equivalent and your customer will have to make the decision about finding an alternative or leaving that package behind. Then there's the files the data used by those apps. are stored in. Is it a little endian system where you need to write a conversion or unload/load utility. Neale On 9/1/11 9:51 PM, "Lu GL Gao" <[email protected]> wrote: > We have some clients who have plan to migrate there applications running on > UNIX to z/Linux. We have not communicate with those clients yet, so I don't > have detail info. > Before that, I just seek if there are some general considerations about > migration, so that I can have good preparation for our first met with > clients. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
