|
View previous topic :: View next topic
|
| Author |
Message |
nggaikwad
New User
Joined: 04 Mar 2009
Posts: 7
Location: SA
|
|
|
|
Dear All,
Hi All,
I have been given to analyse the migration strategies for a large mainframe application currently under OS VS COBOL and VS cobol II to enterprise cobol.
The application has both online (TELON) and batch.
I have no idea how to start with it??
I would like to ask the techies what should be my initial investigation for any application to convert it from cobol II to enterprise cobol.
what are the key points to start with??
Could anybody provide any help??
Thanks!
Nits |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
nggaikwad
New User
Joined: 04 Mar 2009
Posts: 7
Location: SA
|
|
|
|
Thank you very much for the reference books. Actually, It will be great if somebody can share their experiences with me, which I can use and related with the challenges I am facing..... Cheers....
Regards,
Nits |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Perhaps this will help (OS/VS COBOL to COBOL II conversion/migration) considerations -
ibmmainframes.com/references/a10.html
You should be able to compile COBOL II programs using the Enterprise COBOL compiler, resulting in very few (if any) errors. COBOL Intrinsic Functions were introduced with COBOL/370 and some of your OS/VS Special Registers (IE: TIME-OF-DAY) can be replaced by (for example) FUNCTION CURRENT-DATE. However, IBM's Language Environment can be used in any COBOL environment and you need to check if LE Callable Service routines are present in both of these older versions of code as mixing Callable Date routines with COBOL Date Functions can result in apples and oranges, unless a special COBOL compile option is used (not recommended).
The main effort will be the conversion from OS/VS COBOL to a more modern version.
Years ago, IBM offered a migration tool which would produce a report of unsupported OS/VS COBOL syntax which would be invalid in COBOL II, but I believe it's been withdrawn from service.
Try Googling "IBM COBOL Migration" as an Exact Phrase.
Regards, |
|
| Back to top |
|
|
nggaikwad
New User
Joined: 04 Mar 2009
Posts: 7
Location: SA
|
|
|
|
Thank you very much Bill !!!.
I do have to convert
1) TELON Programs to Enterprise COBOL
2) Assembler Language prog to Enterprise COBOL
3) OS VS COBOL II to Enterprise COBOL
4) OS VS COBOL to Enterprise COBOL.
Please suggest,
Regards,
Nits |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
1-2) by hand - discover the logic and rewrite
3-4) see migration guidelines |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
nggaikwad said -
| Quote: |
I do have to convert
1) TELON Programs to Enterprise COBOL
2) Assembler Language prog to Enterprise COBOL
3) OS VS COBOL II to Enterprise COBOL
4) OS VS COBOL to Enterprise COBOL.
Please suggest,
Regards,
Nits |
I can't help with TELON as I've never had any exposure.
OS/VS COBOL II should be expressed as VS COBOL II as there is a huge difference between these COBOL versions and if you prefix OS/VS to its name, this may lead to confusion by others.
Do you have any OS/VS COBOL CICS programs which require conversion? They will take up the majority of your time. The last CICS version/release that supports OS/VS COBOL was CICS/TS 2.3. Any CICS/TS version 3 (and greater) will not support OS/VS COBOL.
What type of Assembler programs do you need to convert to Enterprise COBOL? Are they CICS as well as Batch? You could probably place them at the bottom of the list, because they'll execute regardless of the environment. Note that CICS Macro Assembler support was dropped with CICS/ESA 3.1.1, about 10 years ago.
Having said this, be aware of ALL programs (any language) which require below-the-line addressability (AMODE 24). OS/VS COBOL was inherently AMODE 24 with VS COBOL II programs having the default of being AMODE 31. You can't call an AMODE 24 sub-program from an AMODE 31 caller as you'll get an addresssibility error (high order byte of the registers are not addressable). Keep this in mind.
Try compiling your existing COBOL II programs (both Batch and CICS) with the Enterprise compiler as I believe that they should be compatible, requiring very little changes.
As I had mentioned, OS/VS COBOL will require the most effort, for both Batch and CICS, with CICS the more of a challenge.
If you already have clean VS COBOL II programs, then use their syntax as a foundation and compare with an existing OS/VS COBOL, noting the differences.
You should Google different phrases (as suggested) and check your site results.
Click on the following link to Mackinney Systems (Springfield, Missouri, USA). They offer (amongst others) a product which will allow OS/VS COBOL CICS programs to execute in a CICS/TS version 3 environment and greater. Mackinney products are proven and relatively inexpensive -
www.mackinney.com/products/other/vci.htm
I hope you can appreciate the fact that there's too much to consider and post on this board.
Regards, |
|
| Back to top |
|
|
nggaikwad
New User
Joined: 04 Mar 2009
Posts: 7
Location: SA
|
|
|
|
Dear Bill,
I appreciate your detailed information on the same. Just to inform you that there is no CICS programs in our enviornment. We use only IMS DC, it's actually a IMS shop. Do I need to take any special care in case of IMS as well?
Please suggest,
Regards,
Nits |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Perhaps another member can help as I don't have a background in IMS.
Regards, |
|
| Back to top |
|
|
|
|
