Re: JobLog Creation

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

After wondering if we could spare the space to hold all of the 
joblogs, we bit the bullet and changed our system default to save all 
joblogs as log(4 00 *seclvl) logclpgm(*YES).

We change the default JOBLOG output queue to a queue named for the 
day of the week (along with the default dump queues, etc.).  We clear 
the queues 2 days after they are used.

Although the space is sometimes impressive, it's usually due to a job 
that we'd want to see the joblog for anyway.

--Paul E Musselman

.

At 4:18 PM -0500 10/17/18, Jerry Adams wrote:
> Is there any way to force a joblog to be created?  I have our menus, which
> the users, well, use with a signoff option using the *LIST option, but
> somehow there are occasions, real and imagined, where the joblog is not
> created. 
>
>
>
> I don't want to change the SIGNOFF command's default.  I checked the user
> profiles and job descriptions but did not see any option in either place. 
>
>
>
> On the other hand I can see where a command to create a joblog at the end
> (or middle) of a user procedure would be acceptable in a few cases.
>
>
>
> Jerry C. Adams
>
> I want my food dead.  Not sick, not dying, dead. -Oscar Wilde
>
> IBM i Programmer/Analyst
>
> --
>
> NMM&D
>
> 615-832-2730