DB2 Upgrade V8 to V10 & PL/I Upgrade from V1.1 to V4.2

sundarkudos · New User Joined: 16 Oct 2008 Posts: 39 Location: Chennai

Hello All,

In my mainframe project, in order to upgrade DB2 from V8 to V10, IBM is planning to perform prerequisite PL/I upgrade from V1.1 to Enterprise PL/I V4.2 for DB2 compatibility. Initial study has been done and approach has been finalized for PL/I upgrade and it will be upgraded application wise, Phase wise in order to reduce the risk i.e., we have different applications such as finance, marketing etc. which will be upgraded one by one.

And, the problem here is, one of the application is plan to decommission sometime next year, so client has requested us not to touch that application. This application 'A' is tightly coupled with other application 'B' (that is, 'A' is calling few DB2/IMS subroutines of 'B') which is participating in PL/I. So, once the upgrade is done, application 'A' runs in PL/I V1.1 and application 'B' runs in Enterprise PL/I V4.2. When 'A' calls 'B' DB2 subroutine, definitely there would be runtime exception because of version incompatibility.

One solution I can think of is,

Copying B subroutine(to V1.1 and rename the DB2 subroutine and use in calling program of 'A')before we upgrade to V4.2. If this is the case, when application A uses DB2 table with v8 and application B uses DB2 table with v10, when DB2 is upgraded for this application, will this really possible and works?

or is there any other way we can achieve this?

Please let me know if any additional information is required.

Thanks in Advance,
Sundar Rajan S

dick scherrer · Posted: Thu Jun 13, 2013 7:01 pm

Hello,

As all of the system software is from IBM, i'd ask IBM for guidance and alternatives.

enrico-sorichetti · Posted: Thu Jun 13, 2013 7:18 pm

sundarkudos · New User Joined: 16 Oct 2008 Posts: 39 Location: Chennai

Hi,

IBM has requested us to come up with our own suggestions and the better one will be taken into the account for finalizing approach/method.

Need your help on this.

Thanks in Advance,
Sundar Rajan S

sundarkudos · New User Joined: 16 Oct 2008 Posts: 39 Location: Chennai

Thanks dick.

Awaiting for your valuable inputs.

Thanks in Advance,
Sundar Rajan S

dick scherrer · Posted: Thu Jun 13, 2013 8:42 pm

Hello,

If the application is to be decommissioned soon and it heavily integrated with other processes, what is to replace the decommissioned application?

I believe i've confused myself . . .

d

sundarkudos · New User Joined: 16 Oct 2008 Posts: 39 Location: Chennai

Hello Dick,

I should have written the other way.

The application which is planned to decommission will be replaced by a another product which runs outside mainframe and interacts with Mainframe application to pull out the required data's.

Thanks,
Sundar.

sundarkudos · New User Joined: 16 Oct 2008 Posts: 39 Location: Chennai

Hello,

Anyone here to help me out?

Thanks,
Sundar.

sushanth bobby · Posted: Mon Jun 17, 2013 12:52 pm

Sundar,

sundarkudos · New User Joined: 16 Oct 2008 Posts: 39 Location: Chennai

Yes Sushanth. Both DB2 tables are in different subsystems.

sundarkudos · New User Joined: 16 Oct 2008 Posts: 39 Location: Chennai

One more thing is,

After the upgrades(Enterprise PL/I V4.2 & DB2 V10),

The DB2 table of application B(Enterprise PLI V4.2 & DB2 V10) has to be called (via subroutine) in application A(PLI V1.1 & DB2 V8), in order to retrieve few critical data's every few seconds.

Since application A with V1.1 cannot call DB2 V10, is there any other way, we can make it possible without changing the architecture?

Thanks,
Sundar.

sushanth bobby · Posted: Tue Jun 18, 2013 10:55 am

Sundar,

What are the suggestions that IBM is giving ?

Regards,
Sushanth

sundarkudos · New User Joined: 16 Oct 2008 Posts: 39 Location: Chennai

Sushanth,

IBM has requested us to come up with our own suggestions. Scratching my head now.

Thanks,
Sundar.

dick scherrer · Posted: Tue Jun 18, 2013 8:52 pm

Hello,

I suspect that if IBM has been unwilling or unable to provide what you want, it will probably not be anything simple/straight forward.

One approach (though probably not desired) is to run as-is until that app has been decommissioned . . .