add new job - update print distribution

 4 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
My process flow will create a new job and submit it with no problems - but I would like to have the report output distributed; usually that is done in jobdef after the job is created.

Is there a way to update this information through a syscmd or some other method via PF?

TIA,
Karen
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
You should be able to use a WebRun to push your report out. I don't know if you can push out to a distribution group - this is how you send it to a particular user.

Web Program: cgi-lawson/jobrun.exe
Post String: FUNC=run&USER=dwilliams&JOB=LOADRPTS&OUT=text
David Williams
SP
Veteran Member Send Private Message
Posts: 122
Veteran Member
In theory, you could update GEN directly with an SQL node.

On Wed, Jul 11, 2012 at 10:08 AM, wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> Lawson
> ProcessFlow Forum Notification A message was posted to a thread you are
> tracking. *add new job - update print distribution* Posted by: *Karen
> Schuette*
> 07/11/2012 08:55 AM My process flow will create a new job and submit it
> with no problems - but I would like to have the report output distributed;
> usually that is done in jobdef after the job is created.
>
> Is there a way to update this information through a syscmd or some other
> method via PF?
>
> TIA,
> Karen
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...-print-distribution/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

SP
Veteran Member Send Private Message
Posts: 122
Veteran Member
Karen,

Try running an SQL update node against GEN after the job has been created,
but before it is submitted. The example below is for a Windows username =
'NT00000003', Jobname = '1GL290', and distributes the four reports to a
distribution group = 'TSTGRP'

UPDATE JOBSTEPRPT
SET DSTGRP='TSTGRP'
WHERE USERNAME='NT00000003'
AND JOBNAME='1GL290'
AND PRTFILENAME IN ('GL290.prt', 'currency1', 'currency2', 'error-rpt')

I have not actually done this, but I see no reason it would not work,
presuming the values are valid.

Start off by testing just one of the report files.

HTH,
-Shane

On Wed, Jul 11, 2012 at 10:08 AM, wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> Lawson
> ProcessFlow Forum Notification A message was posted to a thread you are
> tracking. *add new job - update print distribution* Posted by: *Karen
> Schuette*
> 07/11/2012 08:55 AM My process flow will create a new job and submit it
> with no problems - but I would like to have the report output distributed;
> usually that is done in jobdef after the job is created.
>
> Is there a way to update this information through a syscmd or some other
> method via PF?
>
> TIA,
> Karen
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...-print-distribution/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
Shane,
I'd rather not update any tables directly, if I can avoid it. I did find a command line utilitiy called loadrpts. I don't think it will do what I want unless I copy the print files to a directory under the "receiving" users' id which has lots of pit falls since I anticipate 500 or more reports to be run within this 3 week or so period (merit). We are using a generic batch Unix id to run the jobs. Maybe I simply need to run the job under the user id of the user in the compensation department.
Still thinking,
Karen