Re: QAUDJRN track spool writer changes

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Individual spool files have some great audit entries.
Writers, not so much.  Can you tell when I restarted a writer?
 Sequence  Code  Type  Object      Library     Job         Time
171942825   T     ZC                           ROBHQ1      12:37:11
171942826   T     ZC                           PRTL023     12:37:11
171942827   T     ZC                           PRTL023     12:37:11
171942828   T     ZC                           PRTL023     12:37:11

Look about the time that the printer writer job started.

qaudlvl
Auditing
options
*DELETE
*OBJMGT
*SYSMGT
*CREATE
*SAVRST
*SECURITY
*PGMADP
*PRTDTA
*SPLFDTA
*NETSECURE

On Thu, May 22, 2025 at 12:06 PM Tim Adair <tadair@xxxxxxxxxxxxxxxx> wrote:

> We have a situation where a spool writer for a printer (PRT01) suddenly
> gets changed to point to someone's personal OutQ (QGPL/JSMITH).  No one
> seems to know how this is occurring, but it has happened multiple times.
>
> I want to use QAUDJRN to track down how this is happening.  This brings
> us to two questions...:
>
>
> 1. What parms do I set QAUDJRN with to gather the appropriate
> information to track this?
> These are my current settings:
> QAUDCTL(*AUDLVL *OBJAUD)
> QAUDLVL(*SPLFDTA *DELETE *SECURITY *SYSMGT *AUTFAIL)
>
>
> 2. When it occurs again, what parms do I use with DSPJRN to search for
> the cause?
>
>
> I've read that you cannot track changes to a spool writer with QAUDJRN.
> Is that true?
>
> Any guidance would be appreciated.
>
> ~TA~
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.