plda.cfg

 1 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
hsuhsen
Basic Member
Posts: 23
Basic Member
    Hi,

    I am copying a productline on my Development server.  The PL I am copying from also resides on my DEV server, but was originally copied from our production server prior to my becoming sys admin.

    I am at the point in my copy productline procedures where I run the pldbsetup and editda commands.  I was surprised and concerned when the pldbsetup prompts contained information from my production database.  I did some further searching and found multiple plda.cfg files in various productlines  in %LAWDIR% on DEV that pointed to our production DB.  I reviewed the copy PL instructions and don't see any instructions to delete those files or exclude them from the PL copy. 

    I'm not a DB expert by anymeans and while I feel very comfortable with most admin tasks, I am always concerned that I will delete or overwrite the production DB which would be problematic. 

    My question is this:  Should the editda and the plda.cfg files be deleted prior to running pldbsetup?  Did I miss a step in the instructions that would have directed me to delete the files that point to our Production DB?  If I run the pldbsetup, will the existing plda.cfg and editda files get overwritten?

    Thanks!

    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
      If you are creating a new prodline from an existing prodline, any standard lawson delivered files in the ToPL root folder can be deleted.

      ie: editdafile, plda, MICRSOFT, ORACLE etc.

      then you can run the editda, blddbdict, dbcreate etc.