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
User's joblist query, with last run date?
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
65
Members:
0
Total:
65
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Infor / Lawson Platforms
S3 Systems Administration
User's joblist query, with last run date?
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
29 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
TBonney
Veteran Member
Posts: 281
New Poster
Congrats on posting!
9/2/2010 2:30 PM
Can anyone advise on what tables would need to be queried to determine user's joblists, with the dates they last ran each? Also, is there a utility that can be used to delete whichever jobs we identify as being obsolete?
We'd like to clean out user's joblists by deleting all obsolete jobs that they no longer use because we are finding that when they use drill/drop-down in Portal, it is taking longer to bring up the lists. We assume this may be partially attributable to the large volume of jobs they have, many of which are no longer even used.
Thank you.
EricS
Veteran Member
Posts: 80
9/2/2010 3:49 PM
Split
I use the command below in a shell script that watches for failed jobs. You should be able to modify it to get what you want. I don't see how this is going to work out good for you. The job of cleaning up thier own jobs belongs to the individual users. Having been down this road before, if you delete a job that a user only runs once every 5 years they'll sure as the world need it the day after you delete it. Then they're going to be mad at you and esclataing it to everyone's boss. My adivce would be to list the jobs, e-mail them to the user, and advise them to clean up their act. Maybe that's just me though. Would be interesting to see if anyone else agrees.
rngdbdump -t gen queuedjob -f jobnumber username jobname status
Please
login
to post a reply.