10.0 MSP#8

Are there any clients that have installed 10.0 MSP#8? If so, can you give me any feedback on the update as far as stability? Also, did you upgrade RQC as well with the MSP?

Find more posts tagged with

Comments

Legacy Contributor

So far we haven't been able to get RQC to work properly on MSP 8. We started with RQC 10.0.6, then installed MSP 8. RQC is doubling all Req line entries and pops up spurious error messages whenever we try to release an unreleased Req, stating that its already been released (which it hasn't). Tried upgrading RQC to 10.0.7 and rechecked the 106 JT's needed, and still have the same problems. Have a case open with Lawson for about a week now.

Legacy Contributor

We upgraded to MSP10.0.8 (from 10.0.7), and RQC to 10.0.6.40 (from 10.0.6.22) in our DEV system in June; then go-live on 8/3. All is working fine for us.

Hans Mueller

Hi all -

I don't mean to throw confusion into the mix, but I want to make sure that everyone (truly) understands how the AMT (patching engine of Lawson Cobol applications) works. An MSP is just a large collection of CTPs, all bundled together - hundreds and hundreds of CTPs. But when you install an MSP on your system, it doesn't lay down all the same code for every customer - same as if you install a single CTP on your system.

In Lawson Cobol applications, every patch that is delivered bundles together all of the needed code libraries for that patch to compile - all the way back to base 10.0.0 being installed on your system. The AMT (Application Maintenance Toolkit) then parses all those delivered code libraries and compares them to what you already have installed on your system. If the delivered individual library is older on your system, and newer in the patch - then the newer one is laid down. If the delivered individual library is newer on your system already (or the same), then it is skipped. And this is done for every one of the libraries delivered within an individual CTP (hundreds of them are delivered with each individual CTP). This is how we can deliver the same CTP to hundreds of customers regardless of what MSP they are on or what other CTPs they may have been taken. So what gets ultimately updated on your system is different between customer A, customer B, and customer C - depending on what those customers have already taken for patches. All the CTP does is make sure that ALL of the individual libraries that make up the CTP are raised to a common minimum level to solve the problem. So the baseline is raised, but it doesn't make everyone the same.

Now apply the same logic to an MSP, which contains hundreds and hundreds of CTPs. It does that same individual library compare against what is already installed on your system. It raises the baseline of ALL libraries to MSP 8, but components can be higher than that baseline due to other patches you have already taken. So again - three customers apply MSP 8, they all will have different individual libraries updated based on what patches they already have installed on their system.

Hopefully that makes sense. So asking these kind of questions - while I agree provides some level of value that people are having problems or not (trendlines)- but it can't provide a true gauge to your own experience because it will be different than almost every other customer out there.

Hans

Legacy Contributor

Hans - that's correct for COBOL. But, doesn't RQC run off of Landmark? Which is based on Java techology?

Hans Mueller

I don't believe it runs off Landmark, but it doesn't run on Cobol and yes, it is patched differently. But RQC interacts/integrates with the core applications and the thrust of this thread was the two pieces working together after the update. And so I was outlining why two customers on the same version of RQC and seemingly the same version of MSP would have different experiences - as I am willing to bet they are not on the same versions of underlying application code for the specific integration points on the cobol side.

bhillz

Actually RQC is not Landmark based, but it is Java and runs in a JVM. So when you install RQC you need compatible versions of RQC and your LSF version. The Compatibility Guide is a good place to start, but then read the RQC Install Guide for more refinements/clarification/requirements.

Copyright © 2025 Infor. All rights reserved.