Forums
S3 Systems Administration
Copy System Code
Author
Messages
George Graham
Veteran Member
Posts: 201
4/10/2013 7:34 PM
Have a custom system code with programs defined. Trying to copy that entire system code to another server. No new elements involved. Have created the new blank system code on new server and have copied over the entire xxsrc folder. Also did pgmdump and pgmload as well as install few keys in skndef. Most of the programs are fine, but on a few getting error when trying to compile - and looks like its the scrgen causing the issue.
In program error file getting:
Warning: Errors found in CM71.1
Error: nScrs only 0
This is also all I get when I try to manually do scrgen on this program.
I know I'm missing something simple......just looking right past it.
John Henley
Senior Member
Posts: 3348
4/11/2013 12:55 PM
George, are you running sysdump on the old product line, and sysload on the new one?
Ideally, you should really be running metadumpxxx/metaloadxxx (e.g. metadumppgm/metaloadpgm, etc. ) to on source/target product lines to keep the metadata up-to-date; that is the Lawson-supported way of migrating product lines and metadata.
maalimsimo
Veteran Member
Posts: 49
5/12/2017 7:49 PM
This is an old thread but I do have some questions in the same regard. We are gearing for an upgrade from V9 to V10. We do have a handful of custom cobol code that we need to migrate that lives in 5 custom system codes, all zasrc, zbsrc, etc. Now, the recommended utilities metadumpxxx all seem seem to operate at Product line level, for example: metadumppgm productline programcode. How does that work if I need to dump custom programs within the custom source code only (and exclude the Lawson source code (e.g hrsrc) from the dump)?.
Jason Beard
Veteran Member
Posts: 124
6/15/2017 1:05 PM
Sadly you are correct... I normally still do a sysdump pline syscode with no issues. Alternatively you can generate a listing of programs and script the process of the metadump/loads.