Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Copy System Code
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
52
Members:
0
Total:
52
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Infor / Lawson Platforms
S3 Systems Administration
Copy System Code
Please
login
to post a reply.
3 Replies
2
Subscribed to this topic
29 Subscribed to this forum
Sort:
Oldest First
Most Recent First
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
Posts: 3366
New Poster
Congrats on posting!
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader art thou!
4/11/2013 12:55 PM
Split
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
New Poster
Congrats on posting!
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader art thou!
5/12/2017 7:49 PM
Split
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: 125
New Poster
Congrats on posting!
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader art thou!
6/15/2017 1:05 PM
Split
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.
Please
login
to post a reply.