User Exits and MSQ's and MSK's

[sdoughty]

Hi,
We're upgrading MIMS 4.3.1 to Ellipse 5.2.3, and carrying most user exits forward. We were only using terminal interface for MIMS, and so had not implemented any of the user exits at the object level. Where we were using BOC, we are embedding the user exit logic in the application that calls connector (which is not very efficient)

We will be using WinView, and some of the MSQ programs (eg MSQ620). This means that we need to implement the user exits. I can see 2 options
- modify the MSQ (ie inherit from it and modify where necessary), so all applications will end up with embedded business logic, or
- modify the MSK, so all applications see the user exits, but at the increased cost of ongoing upgrades.

How have other people done this?

Cheers,

Steve

 

[alphacoward]

The only way to go is to modify the MSK. That will provide consistency for all clients. As you have said you are forwarding all your current your user exits from 4312 to 523. What difference does a couple more user exits make

Inheriting the MSQs would add to extra support costs and would complicate future upgrades more than user exits.

So unfortunately you have to put your delphi skills away and use those old rusty cobol skills.