Re: Weird Print Issue

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Well, "IF" you have audit journaling turned on this is possible.

Sequence  Code  Type   Why?
33571026   T     CD     DSPJOB OUTPUT(*PRINT)
33571027   T     ZC     OUTQ
33571028   T     SF     SPOOL FILE NAME, JOB NAME, ETC
33571082   T     CD    WRKJOB
33571746   T     CD     CHGSPLFA (Basically did a 4 from the wrkjob and
changed it to a real printer)
33571747   T     ZC     NEW OUTQ changed cause it got a file
33571748   T     ZC     NEW OUTQ  changed cause it chucked a file
33571749   T     SF     lots of info on the file just printed
33572878   T     CD     DSPJRN ...
33575574   T     CD      DSPJRN JRN(QAUDJRN) FROMTIME(062524 1326)
JOB(ROBHQ1)

We have just about everything turned on in QAUDLVL and QAUDLVL2
including *SPLFDTA
QAUDCTL has:
Auditing
control
*NOQTEMP
*OBJAUD
*AUDLVL

A simple explanation could be someone changed the attributes to SAVE(*YES),
printed it, and printed it again.

Now, this is when someone usually asks:  I don't want to turn on anything
effective, like auditing, journalling, etc.  Is there some other way to
find out what happened?


On Tue, Jun 25, 2024 at 1:19 PM Freeman, Greg <gfreeman@xxxxxxxxxx> wrote:

> I have a remote Outq with an IP address.  User printed an AS400 print file
> in the morning.
>
> That afternoon, it printed again on the same printer - never have I seen
> this?
>
> Question:  how do I look at the print history in perhaps QSYSPRT?
>
> Greg
> --
> 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.