Pdraebel
865 pts. | Nov 12 2009 8:46AM GMT
Assuming a job log is produced (normally if settings are correct a failing job would produce a joblog) you have several commands to check for the joblog. First would be WRKJOBLOG.
You may not be authorised to view the joblog of users that have *ALLOBJ authority and your profile has not. This joblogs can be viewed but you’ll have to use WRKFCNUSG to allow your profile to view those joblogs.
Splat
1040 pts. | Nov 12 2009 3:23PM GMT
If you don’t know the job name but do know the user name, try WRKUSRJOB USER(user name) to locate the job.
CarterC19
170 pts. | Nov 12 2009 3:26PM GMT
Actually, there is a user profile setting, accessible only via Navigator, that will allow a user who does *not* have *ALLOBJ authority to view the joblog of a user that *does* have *ALLOBJ authority. Right-clicking the profile to get Properties, click the Applications tab, change the drop down to Host applications, and under the I5/OS / All object subcategory you will see a checkbox to ‘Access joblog of *ALLOBJ job’. Check that and you’re good to go.
True, you gotta go well out of your way to do it, but I imagine in the security world that’s how it should be.






