powerh-l Digest, Vol 80, Issue 2

[krikor Gullekian]

Many of the concerns have already been said, here is my
advice:


The redefines can take time to fix, keep that in mind.



If you use  MPE commands within your
Powerhouse code they have to be translated.


All JCLs have to be translated and optimized, there are 3rd
party vendors with tools to automate Unix scripts, I don’t know about Linux.


My preference is to create subfiles with all ascii fields,
which means translating all numeric fields to ASCII, then use SQLoader to load
to Oracle. I never had issues using this methodology and I can create and
optimize the DB’s before having Powerhouse on the target machine. The caveat is
that it will take more time to do it.


Once the step above is completed and you have Powerhouse  take few of the most complex programs and test
them on the new platform.


 Some image calls, eg:
backward and forward chain reads,  can
not be duplicated and that’s why you need to create your DB efficiently.


KSAM is tricky, if they are big with multiple keys your best
bet would be creating tables.


In any case every single migration is unique with one thing
in common it will always take longer than expected and you don’t need someone
on site to help you, it can be done remotely.


Good luck with your migration.
Krikor

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20120224/7f20bf11/attachment.htm>