View previous topic :: View next topic
|
Author |
Message |
Rabi2212
New User
Joined: 24 May 2011 Posts: 1 Location: india
|
|
|
|
Hi! This is your First post in our Forums! So please be sure to 1) Use meaningful and descriptive Topic Title 2) Try to post your query in the relevant forum category 3) Make sure your query is not already posted and solved in our forums, Use the Search facility and avoid Reposts! If you are following the above rules, delete this message and post your query here! |
|
Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008 Posts: 2501 Location: Atlanta, Georgia, USA
|
|
|
|
If your CICS/Assembler is pretty much "Vanilla", yes, they'll be some inconsistencies, but migration to CICS/COBOL should be straightforward.
To ensure proper migration, it would be wise that you engage personnel who are well versed in both CICS Assembler and COBOL. You may find some "opportunities" in the Assembler code that doesn't translate well to COBOL.
Hopefully, this is Command Level CICS/Assembler and not CICS Macro Assembler?
What version/release of CICS are you migrating from and what version/release are you migrating to?
What is your target COBOL version/release?
Bill |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
as I replied in another topic
the whole shebang for an Assembler to COBOL migration project
is not something people will be happy to share with You on a forum,
for two main reasons
the complexity of the task
the work done by each one of us to acquire that knowledge
and ...
defining such a plan is task suitable for an hefty consulting contract
and asking for a little help is allowed,
not so to ask be spoon fed with knowledge/experience we gained with many years of hard work |
|
Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006 Posts: 475
|
|
|
|
enrico,
well said and AMEN brother ! |
|
Back to top |
|
|
|