Work file paths

Sort:
You are not authorized to post a reply.
Author
Messages
NickM
Basic Member
Posts: 7
Basic Member

    I went from apps 8.0.3 to 9.0.0.4. We have work files from jobs that are not going to the correct product line for example, we are getting old product line instead of the new one as a relative path to the work files. Do to this, jobs have been going down. Does anyone have a suggestion?????

    Sam Simpson
    Veteran Member
    Posts: 239
    Veteran Member
      Dump the WRKFLOPTS from GEN into a csv file (dbdump), change the product line, re-upload the csv file (dbload) then recompile the affected programs.
      John Henley
      Senior Member
      Posts: 3348
      Senior Member
        Use rngdbdump / importdb not dbdump/dbload for CSV files.
        Thanks for using the LawsonGuru.com forums!
        John
        John Henley
        Senior Member
        Posts: 3348
        Senior Member
          Also, make sure that it's just the workfile that has an embedded product line name, and that the job step itself is pointing to your new product line.
          Thanks for using the LawsonGuru.com forums!
          John
          Sam Simpson
          Veteran Member
          Posts: 239
          Veteran Member
            Correction: Use rngdbdump instead of dbdump.
            NickM
            Basic Member
            Posts: 7
            Basic Member
              Thank you for your replies. It's hard sometimes to write exactly what is occuring. We tried the Dump the WRKFLOPTS from GEN But no where on the GEN tables were we missing the current product line.

              The example below:

              For a single program for example "PR160" we have multiple jobs setup to run it. one job the workfiles go to the correct product lines work directory "/lsf9/law/pl900" . For another job setup for the same program, that jobs work files go to the old product lines directory "/lsf9/law/pl803"

              We have deleted the job going to the wrong directory and readded job using the same name and it still goes to the wrong directory. If we create a job with a new name it goes the the correct directory and then need to make scheduling package changes.
              John Henley
              Senior Member
              Posts: 3348
              Senior Member
                Dump out the JOBSTEPWRK file from GEN and see if that's the problem.
                Thanks for using the LawsonGuru.com forums!
                John
                Eric Haugen
                Basic Member
                Posts: 13
                Basic Member
                  "We have deleted the job going to the wrong directory and readded job using the same name and it still goes to the wrong directory. If we create a job with a new name it goes the the correct directory and then need to make scheduling package changes."

                  Did you ever figure out how the file still went to the wrong directory even after deleting and re-adding the job with the same name? Think that's happening to us also.
                  Eric Haugen
                  Basic Member
                  Posts: 13
                  Basic Member
                    "We have deleted the job going to the wrong directory and readded job using the same name and it still goes to the wrong directory. If we create a job with a new name it goes the the correct directory and then need to make scheduling package changes."

                    Ever figure out why deleting and re-adding with the same job name did not work?
                    You are not authorized to post a reply.