Infor v10 Upgrade - Customs

I may have asked this question before, and been sent to the stake! If so, please disregard, and call me names

We are prepping for the large v10 upgrade (from 901.13), and the request we have is:

"For follow-up with the technical team, the requirement that all Lawson COBOL programs be “in” the Application Management Toolkit (AMT). So our custom programs for Lawson need to be added if not already."

Based on this request - it is to essentially make sure that we are capturing all of our Custom code, and if it is possibly, somehow, to get custom code "in" AMT? Does this make sense to anyone? Or, are there ways to make sure customs are captured?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

acollins

Are you trying to use AMT for version control and/or deployment management?

I have used other tools for version control like subversion or ClearCase for custom code. We put only the custom code in the version control tool.

For deployment management, one organization where I worked used a custom script because the typical deployment was either Java, ear file deployments, or mainframe COBOL. We did not fit any typical deployment type of the organization. We were trying to package everything up and get as close to pushing a button to deploy code from ClearCase. The challenge was deploying COBOL, sr/or files, configurations, tables, etc using staff who did not know a thing about Lawson and many times did not even know the OS of the system.

unknown

well, to simplify it - I think so? I just want to be able to successfully capture ALL code we currently have in our 901x environment, and promote to the new 10x environment. Someone, thought AMT was where that can be defined, but I don't see how the set tools in AMT can be tweaked to capture custom

unknown

When it comes to custom Cobol code version 10 isn't any different than version 9. As far as I know the only way to include the custom code would be to apply it after you have performed the upgrade which is a manual process for us. I don't think there is a way to use AMT to include it.

unknown

What does warrant a discussion about with code in 10x versus 9x appears that the settings on the PROGRAM options (such as "In Production" or 4GL) do matter Under the 9x and LID the program level options appeared not be an issue but the LSO and PORTAL execution do - so it depends what type of UI you came from versus the 10x UI's Sync the metadata so Lawson knows about custom objects

unknown

Hey Brushy Bill, can we chat more? I'd like to pick your brain more about this work to get metadata sync, and customs recognized.

bszczesny

What we've done with most of our custom code is create new system codes that start with a 'z' (ZN=>BN, ZH=HR, etc.). This way we can keep our custom separate from the Lawson delivered. We do have some Lawson delivered with custom code and those are much harder to upgrade. When we went to v10 we brought over the custom systems, compiled and dealt with any compile errors, then our users went through their testing scripts. Just another thought.

Copyright © 2025 Infor. All rights reserved.