Move batch jobs to a new Lawson ID

One of my colleagues just got married and her name, and Lawson NT user id, changed as a result. She would like to have all the batch jobs she created in the past available under her new Lawson NT user ID. I understand that the jobs are stored in our LAWGENPROD database in the QUEUEDJOB, JOB, JOBSTEP, and JOBSTEPRPT tables, and I know her old NT user id was NT000000b2 and is now NT000000fe, but I don't know the best way to assign all her past batch jobs to the new user ID.

Is there an existing function to get this done? If not, does anyone have a recommendation as to how I can accomplish the request? Can I insert new records in the table copying the old data and assigning the new NT user ID?

Thanks!

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

ujobdump ujobload should help to get her pre-defined jobdefs migrated. Existing print files in print manager will be a little bit harder.

moellerg

I have a different procedure for moving jobs between systems/environments that should work as well.

Is there a way to add attachments here?

moellerg

To transfer jobs between systems/environments

On the system where the jobs already exist - I’m using the interface user of the domain called Domain

jobdump -d -o Job -v UserName Domainintrface|tee d: mpjobdump.intrface.all.dmp

Modifying the UserName to whichever user you are dealing with at the moment. In my case it was the ‘intrface’ user.

Transfer the /tmp file over to the system where you would like the jobs to be imported at.

Run the following command:

jobload -m LawDir "$LAWDIR" $LAWDIR /tmp/jobdump.intrface.all.dmp

Producing the following:

Validation mode.

Job UserName=intrface JobName=ANSOS

Job AP520-ALON: ProductLine "LPROD" does not exist.

Job UserName=intrface JobName=AP520-ALON did not pass validation.

Job UserName=intrface JobName=APIED

Job UserName=intrface JobName=APITH

Job GH180: ProductLine "LPROD" does not exist.

Job UserName=intrface JobName=GH180 did not pass validation.

Job UserName=intrface JobName=GLDJE

Job HR310: ProductLine "LPROD" does not exist.

Job UserName=intrface JobName=HR310 did not pass validation.

Job IC500: ProductLine "LPROD" does not exist.

Job UserName=intrface JobName=IC500 did not pass validation.

Job IC500C: ProductLine "LPROD" does not exist.

Job UserName=intrface JobName=IC500C did not pass validation.

Job UserName=intrface JobName=IC500CRUN

Job IC500I: ProductLine "LPROD" does not exist.

Job UserName=intrface JobName=IC500I did not pass validation.

Job IC500ILH: ProductLine "LPROD" does not exist.

Job UserName=intrface JobName=IC500ILH did not pass validation.

Job UserName=intrface JobName=IC500IRUN

Job UserName=intrface JobName=IC500LRUN

Job UserName=intrface JobName=IC500RUN

Repeat above command until no errors come back on the screen. Replacing values as they come up and adding –m options as they are needed.

I needed to add a –m ProductLine option to my command and run it again.

jobload -m LawDir "$LAWDIR" $LAWDIR -m ProductLine "LPROD" LDEV /tmp/jobdump.intrface.all.dmp

Producing the following:

Added Job UserName=intrface JobName=ANSOS

Added Job UserName=intrface JobName=AP520-ALON

Added Job UserName=intrface JobName=APIED

Added Job UserName=intrface JobName=APITH

Added Job UserName=intrface JobName=GH180

...

Then I need to repeat the command one more time, this time adding a –c to commit the changes to the database table and have the jobs available.

jobload –c -m LawDir "$LAWDIR" $LAWDIR -m ProductLine "LPROD" LDEV d: mpjobdump.intrface.all.dmp

unknown

Thank you both Greg and alexwolff. I'll start experimenting with your recommendations now.

unknown

Assuming you're on Lawson v10, here's how you would migrate jobs with a name change.

Old Name: Jane Smith - jsmith

New Name: Jane Johnson - jjohnson

1. Dump the user's jobs replacing the name in the process.

- jobdump -d -o Job -v UserName domainjjohnson -m Username domainjsmith domainjjohnson > jane.dmp

2. note the UID of the old user in their environment identity.

3. create a new user with the new name, assuming the user's name has been changed in AD, the UID should be the same once you add the new person.

4. delete the environment identity under jsmith

5. Run listusermap -n

6. Run delusers and make sure the UID is the same with the new user

7. Load the users jobs from step 1

- jobload -c -o Job jane.dmp

8. rename the users xml file to the new name located in lawdirpersistdatalawsonportaldatausers

9. Rename the user's print directory to the new name and delete all the print files

10. delete the old user

11. user signs in and deletes their old job history.

CSF SM Project Generation, Invoicing and Collection

unknown

My thanks to you too Pres29. Using your feedback (with alexwolff's and Greg's) I was able to move the jobs to the new user name. I was moving them to the same environment so, for reference, my command's parameters ending up as:

MOVING user "browns" JOBS OVER TO user "brownpralls":

jobdump -d -o Job -v UserName {Domain}rowns -m UserName {Domain}rowns {Domain}rownpralls > sb.dmp

jobload -c -m UserName {Domain}rowns {Domain}rownpralls sb.dmp

My target user had already re-added some jobs by hand prior to this transfer so I hand-deleted them out of the sb.dmp file after the jobdump job finished and before performing the jobload. I of course ran the jobload without the -c (commit) parameter until I confirmed the command would be successful.

Thanks again guys. I really appreciate your help! ...Lance

Copyright © 2025 Infor. All rights reserved.