• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization S3 Customization/Development

Best practice of copying a program

 3 Replies
 0 Subscribed to this topic
 17 Subscribed to this forum
Sort:
Author
Messages
Vijay S
Veteran Member Send Private Message
Posts: 174
Veteran Member
4/29/2016 11:17 AM

Dear All,

I have to copy a standard program having around 10 workfiles. We all know that Lawson doesn't change the name of workfile and WS-Field ID in work file definition while copying , It changes the same in PD (like wherever I am using WH130, it will change it to ZZ130 in PD/WS, The workfile name starting from WH130 doesn't change). It seems like I have to manually go into PD and change the name of all the Workfiles and other field. I had done it earlier also where there were like couple of instances of workfile. Was wondering is there a shorter way ?

Thanks,

- Vijay 

jaherb
Veteran Member Send Private Message
Posts: 164
Veteran Member
5/2/2016 2:21 PM
Vjay.... what you say is true... the copy process does not change the workfile names. However there is an easy way of doing this... you can use the cwf command at the command prompt... The syntax is Usage: To change work file names in the Environment database. Syntax: cwf ProductLine SystemCode ProgramCode OldWorkFile NewWorkFile I too use to do what you are doing or go in and manually enter each of the work files to match the program name. This is one item I do dislike in Lawson and usually take the time after I create a program to go in and generically rename each work file... so that in the event of copying the new program, this is not an issue. Jim
Vijay S
Veteran Member Send Private Message
Posts: 174
Veteran Member
5/12/2016 2:52 AM
Thanks Jim ...that helped !
jaherb
Veteran Member Send Private Message
Posts: 164
Veteran Member
5/12/2016 1:53 PM
No problem VJ. That is about the easiest way I have found to do that....