batch program using Users locale for workfile definition instead of jobstepwrk

 6 Replies
 0 Subscribed to this topic
 43 Subscribed to this forum
Sort:
Author
Messages
Barry Ghotra
Veteran Member Send Private Message
Posts: 63
Veteran Member

Not sure If I'm explaining it correctly, but I have a issue, where one out of all the users, is not able to run a batch program and doesn't like the CSV file  layout. The key difference I found with the user and the rest of the users is that this users examine log says:

"FILE OPTIONS WERE TAKEN FROM USERS LOCALE" for the ZR504-INV file, VS

"File options were taken from JOBSTEPWRK record".

I believe it has something to do with the settings?

Can anyone help me with how I can force the user to use the FILE OPTIONS from JOBSTEPWRK instead of Users Locale?

 

Thanks.

Deleted User
New Member Send Private Message
Posts: 0
New Member
<!-- insert your reply above this line -->

Barry;
Are you on LSF9 or LAUA?
 
"does not like the CSV file layout",  is it the file layout or not able to generate the file?
Barry Ghotra
Veteran Member Send Private Message
Posts: 63
Veteran Member
It actually does not like/understand the file layout of the CSV file and keeps saying "Not Found" for every field/data. I'm on LSF9. The program works fine in lawson8 as well as for other users in lawson9.
John Henley
Send Private Message
Posts: 3351
Was this a converted/migrated job? You might want to just delete and recreate the job and the CSV peculiarities for this job.
Thanks for using the LawsonGuru.com forums!
John
Barry Ghotra
Veteran Member Send Private Message
Posts: 63
Veteran Member
I did not migrate the job, but I defined it in jobdef. I recompiled everything in lsf9 and then created the jobs for the users in jobsched. My confusion is why it works for all other users but one?

Thanks.
Barry Ghotra
Veteran Member Send Private Message
Posts: 63
Veteran Member
I guess, what I'm trying to find out is what makes the jobs/uses pick the file options from work file options Vs. JOBSTEPWRK? That's the key
Barry Ghotra
Veteran Member Send Private Message
Posts: 63
Veteran Member
OK, got it working. I did not have the CSV definition option at the workdef level, so it was using the User locale defiinition which was messed up. So I had to delete the options being used by jobdef and then go back and define the options in the WORKDEF, and that fixed the issue.

thanks for everyone's help.