Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
print directory files cleared on next recurring job run
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Troy J
Past 24 Hours:
1
Prev. 24 Hours:
1
Overall:
5189
People Online:
Visitors:
280
Members:
0
Total:
280
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1351
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
print directory files cleared on next recurring job run
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Page 2 of 2
<<
<
1
2
Author
Messages
mikeP
Veteran Member
Posts: 151
4/13/2013 11:48 AM
Greg,
Thanks for your help with this issue, I will put that article away for future reference. I think I found a way to make this work without the need to copy the print files to all the users in the report's distribution list.
We have a batch job account (BATUSER) that runs recurring jobs, and those jobs output reports to distribution lists.
Testing in our current AS400 system shows that all the users in a report's distribution list can look at BATUSER's print files and see the files sent to the distribution list to which they belong, but not BATUSER's other print files.
The plan is to copies of the previous job's print files in a different folder as described earlier in this thread, and loadrpts them into BATUSER's print file list, where they should be visible to members of the report distribution list.
I'll need to test this on the future Windows system, if that behavior is the same, that will work for us.
jacob
New Member
Posts: 2
4/30/2013 1:24 PM
Greg's suggestion of a seperate archive directory is safer since under both Windows and UNIX, the job's print directory location is cleared, and additionally mutexes can lock a file on rewrite (get used to seeing 9 065 errors)
___________________________________
[url=http://www.diagnosticobd2.com/Supply-car-diagnostic-tool_c2]car diagnostic tool[/url][url=http://www.diagnosticobd2.com/carprog-full-v401_p79.html]CARPROG FULL V4.01[/url]
Cindy
New Member
Posts: 1
5/31/2013 5:07 PM
We ran into this problem because Auditors wanted to know if the user logged into AP161 was captured when the prt was generated to process a payment. Because multiple users have access to that form and the Auth code is Multi-select, and because the AP161.prt eats itself every time the job is run we customized the form to scrape the user who triggers the report and a process flow that goes out to the file in the user's print folder to grab it before commit and after just to be sure. it reads in the prt doc and takes the check number range, payment type, date, etc and saves that and the logged in user id to the workflow variables and from that we built a report to match the check to the check range and assign a user to the transaction.
When we contacted Lawson initially to see if they would consider closing this security hole they said it was very low priority and would most likely never be addressed. They said that the only security needed should be limiting access to the form that pays the invoices, but when a company is large and three people are needed to process payements at that stage to keep up, and auditors find something strange in the payments, all three employees are now on the hot seat. it's much better to be able to reliably isolate the one user who processed that check.
You are not authorized to post a reply.
Page 2 of 2
<<
<
1
2