Rob,
We had this same issue and determined a few users were using the WRKPRTSTS command to attach BPCSOUTQ to a writer. WRKPRTSTS is an option on the WRKOUTQ and WRKSPLF panels (9=Work with printing status). These users believed they were only changing their own spoolfiles but were actually attaching BPCSOUTQ to a writer. We changed the authority to the WRKPRTSTS command to PUBLIC *EXCLUDE and instructed users on how to move spoolfiles. We have had no further occurences since. This took some detective work to track down...... :)
-----Original Message-----
From: bpcs-l-bounces+christopherwynn=abmauri.us@xxxxxxxxxxxx [mailto:bpcs-l-bounces+christopherwynn=abmauri.us@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, January 25, 2010 10:23 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] CHGWTR
As a default most of our printed output goes to BPCSOUTQ. This is not
attached to any active printer. When they want to print something they
move it to their printer. Well, someone changed a writer to start
processing BPCSOUTQ. So people from several states/countries/etc had
their stuff sent to this writer. To top it all off the writer was for
Infoprint server and all this stuff went out as email. Default (luckily
enough) is to send it to whomever generated it.
Standard 4.0.5CD menu option
F14=Services
2 Work with Output Queue
F20=Writers
Helps if you change your assistance level from basic to intermediate.
And the bear is that this is not logged in any of the following:
- QAUDJRN (of course - no object was changed)
- DSPLOG
- DSPMSG QSYSOPR
- Any of the jobs associated with that writer.
The only possible way to catch it is to look at all interactive jobs
(providing they are still signed on). But who wants to pour through these
jobs individual joblog?
Users:
Signed on . . . . . . . . . . . . . . . . . . . . . . . : 448
Temporarily signed off . . . . . . . . . . . . . . . . . : 0
Suspended by system request or group jobs . . . . . . . : 1
Signed off with printer output waiting to print . . . . : 6111
DSPSYSSTS ASTLVL(*BASIC)
Plan C is to add a Command Exit point on CHGWTR and see if we can pin the
individual down the next time. We could also say that if the writer they
are trying to change is our infoprint server to not allow them to attach
it to BPCSOUTQ.
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apis/xcachg.htm
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/bpcs-l.
Delivered-To: christopherwynn@xxxxxxxxxx
The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged, confidential and exempt from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender or the AB Mauri/Ohly Help Desk at Tel: 314-392-0800 x 1881 immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer. Thank you.
midrange.com
