View previous topic :: View next topic |
Author |
Message |
WHITE Beginner
Joined: 03 Sep 2004 Posts: 8 Topics: 4
|
Posted: Fri Sep 03, 2004 7:22 pm Post subject: Migration From CSP TO COBOL/CICS |
|
|
I have put the same question in MVSHELP forum but I am still waiting for the response. I would like to know the responses from this forum also.
Hi,
We have a client who has got a system built-in CSP Technology. As some of you aware that CSP is no longer supported by IBM. So the Client wanted to migrate this system from CSP to COBOL/CICS.
I know both CSP and COBOL/CICS in terms of development (More at low-level rather than at High-level)
But I am not very sure or I am not able to prepare a check list that needs to be considered for this migration (At the Highlevel).
All this is required
1)To Come up with Better Estimations
2)To foresee the Risks involved
3)To Identify the Complex activites
4)To Prioritize the Tasks
5)To Find out the Pre-requisites
6)To Set the time-lines
7)To Identify the Check-points
Your suggestions on this Issue would be very helpful for this project.
Thanks
White. |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
|
|
Back to top |
|
|
WHITE Beginner
Joined: 03 Sep 2004 Posts: 8 Topics: 4
|
Posted: Mon Sep 06, 2004 5:35 pm Post subject: |
|
|
Hi Kolusu,
Thanks for this Information. In fact, I know about these third parties but the Client somehow not willing to go with them.
Then second about the IBM link, that is actuaaly taking about Converting CSP 3.3 , not CSP 4.0.
And one more problem is that, this is not one step process. First they will convert CSP to VA and them to CObol/CICS.
In fact, what we are looking at, if we convert directly from CSP to COBOL how much time it takes and what are the things we need to take care. The following is the list of the things I think we need to do it at this point of time.
At system level:
1. TCT and all PPT enties
2. File definition in the Region (FCT entires)
At the Development Level:
1. Redesign the Screens using BMS software
2. All the CSP records will be converted to Cobol Copybooks
3. All the CSP global Processes are converted Procedure Division Copybooks
4. All the CSP local processes are converted to Paragraphs of the Cobol Modules
5. All the CSP SQL Objects are Converted to COBOL Embedded SQL statements
6. The Inherent logic of CSP Converse and Display to throw the Maps need to be handled by the CICS send and Receive Map commands.
7. Each CSP application is converted to one COBOL module. They contain all the above 6 Items.
If I again Categorize the above items in terms of Complexity, I think the 5 and 6 items comes first.
I would appreciate if some one can add more suggestion in this direction.
Thanks for your efforts on this one
White. |
|
Back to top |
|
|
|
|