Prev
Next
Forums Integration / Customization S3 Customization/Development

work file def

 4 Replies
 1 Subscribed to this topic
 17 Subscribed to this forum
Sort:
Author
Messages
Chesca
Veteran Member
Posts: 490
Veteran Member
10/7/2015 1:05 PM

    Hello, we are in the process of upgrading from Lawson MSP 9.1 to MSP 9.11. We have some custom code that I need to put back in vendor's programs. I am having a problem when copying the code, it doesn't rename the work files so it keeps the vendor's work file name. So I have a program that has like 6 works file that I need to copy and it can be so tedious. Is there an easy way to copy the work file definitions? 

    Woozy
    Veteran Member
    Posts: 709
    Veteran Member
    10/7/2015 1:52 PM
      You might try metadumpwrk and metaloadwrk. Dump the files, use a text editor to update the dump file, then load it. It is still tedious, but at least you don't have to recreate it from scratch.

      There are several "metadumpxxx" programs - workfiles, messages, libraries, etc.
      Kelly Meade
      J. R. Simplot Company
      Boise, ID
      Chesca
      Veteran Member
      Posts: 490
      Veteran Member
      10/8/2015 6:52 PM
        Thanks for your prompted response, Woozy. What about the libraries? They weren't copied?
        Woozy
        Veteran Member
        Posts: 709
        Veteran Member
        10/8/2015 7:53 PM
          It depends what "libraries" you mean. Program code will copy fine, but external libraries shouldn't need to be copied, unless you are wanting to clone and modify them. That's the only reason I mentioned the metadumplib.

          By the way, you'll still have to modify the program logic to reference your new work files - but this will be obvious when you attempt to compile.

          Good luck!
          Kelly Meade
          J. R. Simplot Company
          Boise, ID
          jaherb
          Veteran Member
          Posts: 164
          Veteran Member
          10/9/2015 2:36 PM
            Bernfc10... I just responded to your other posting on this subject. I have always opted for the pgmdump / pgmload utilities since they will capture the work file definitions, unlike metadump / metaload. With the later utilities, you then must perform the metadump / metaload on each of the work files.