Distribution Group

Sorry i have no suggestion...we are experiencing the same issues with distribution groups; were you able find a solution?

I am still waiting to hear from our Admin guy, but try the following: I recommend that you review #2 and #3 and get these in place. How to setup a Distribution Group for job distribution: 1) Create the Group in grpdef 2) Add the Group to a Distribution List in dstlstgrpdef 3) Add the Dist. Group to the users LAUA record 4) Assign the Dist. Group to the desired job in jobdef

I wonder if it's a security issue.    Can the users that cannot see the reports in their own print queue see them if the look at the print queue for the user that actually ran the job that created the report? If not, that might be a clue.  It might help to compare the security settings for the one user that can see the reports, and those that can't.

 Also, there are other settings that affect report distribution.  In addition to distribution groups, there are user groups (usergrpdef) and distribution list groups (dstlstgrpdef), and they all interact if IIRC.  I have a few pages of notes on how I untangled that web when we first started with Lawson several years ago.    I could email them to you if you like.

Please email it to jacobernfc10@hotmail.com. Thanks The users cannot see the reports in their own queue but I can see them in their queue. The program runs in recdef and has about 17 steps to run the repors for each of our users. None of them except for the purchase manager and myself can see the report. Our security Admin said that we only use default or all. But Lawson suggested we add the distribution group to LAUA.

Do the users have security for the batch job? Everyone that needs to see it needs at least Inquiry access to MA236 in LSA.

unfortunately I don't have access to lawson security but our Admin is saying that they do and everything is set up correctly. We have 2 scenarios 1) as mentioned above, reports are distributed to print managers but certain employees can not view. 2) reports are not being distributed - not found in anyone's print manager. The batch job was just transferred from 1 user to another; prior to the transfer it was working properly. My last resort will be recreate all jobs under the new user.

The missing piece to this puzzle is the user must have a UserGroup assigned to their RM record that contains all of the users that are in the distribution group defined in the job def as well.