|
midrange.com
Duhhh... That will teach me to read the screen and try all of the options.
I knew that it was probably saved somewhere. Thanks Charles.
Dave
CWilt@xxxxxxxxxxx
m To:
midrange-l@xxxxxxxxxxxx@SMTP@CTB
cc:
05/13/2004 11:47 Subject: RE: Restrict
CLROUTQ--A good use for an exit
AM program?
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
David,
Hit F10=Display only entry details
HTH,
Charles
> -----Original Message-----
> From: David A Parnin [mailto:daparnin@xxxxxxxxxxxxxxxxxx]
> Sent: Thursday, May 13, 2004 12:26 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: Restrict CLROUTQ--A good use for an exit program?
>
>
>
> Vern / everybody,
>
> I'm still going to look into the exit program option but I
> did do as you
> suggested and turned on object auditing for the CLROUTQ
> command to log when
> it gets used. I did a test and it seemed to capture the
> job/workstation
> and command but I don't see the user-id anywhere. Am I missing it or
> doesn't that get saved? I'm new to journaling and am still stumbling
> around with the commands.
>
> To test it I did a CLROUTQ DPTEST/DPTEST2 and got the
> following entry when
> I did a DSPJRN JRN(QAUDJRN)
>
> 34448161 T CD DAVEPS7 10:50:53
>
> When I typed a "5" next to it to display the entry I got the
> following:
> Display Journal Entry
>
> Object . . . . . . . : Library . . . . . . :
> Member . . . . . . . :
> Incomplete data . . : No Minimized entry data : No
> Sequence . . . . . . : 34448161
> Code . . . . . . . . : T - Audit trail entry
> Type . . . . . . . . : CD - Command string
>
> Entry specific data
> Column *...+....1....+....2....+....3....+....4....+....5
> 00001 'CCLROUTQ QSYS *CMD NCLROUTQ OUTQ(DPTEST/'
> 00051 'DPTEST2)'
>
>
> Any ideas?
>
> Dave Parnin
> Nishikawa Standard Company
> Topeka, IN 46571
> daparnin@xxxxxxxxxxxxxxxxxx
>
>
>
>
>
> Vern Hamberg
>
> <vhamberg@centerfieldtech To:
> Midrange Systems Technical Discussion
> nology.com>
> <midrange-l@xxxxxxxxxxxx>@SMTP@CTB
> cc:
>
> 05/10/2004 03:27 PM
> Subject: Re: Restrict CLROUTQ--A good use for an exit
> Please respond to
> program?
> Midrange Systems
>
> Technical Discussion
>
> <midrange-l@xxxxxxxxxxxx>
>
>
>
>
>
>
>
>
> Hey, Dave, I'm with you. Why take the easy way? And there's always
> something new!
>
> I made a mistake - OBJAUD should be *ALL - *USRPRF means you
> also need to
> set up auditing in the user profile.
>
> When set to *ALL, at least according to the help text, it
> says that READs
> and CHANGEs will have an entry added to the journal. This
> suggests to me
> that failed attempts to use the command (a READ, correct?)
> will be logged.
> But I've not verified this.
>
> Good luck, whatever new thing you try!
> Vern
>
> At 02:36 PM 5/10/2004, you wrote:
>
> >Vern,
> >
> >People may have called me "simple" in the past but I haven't
> always been
> >known for doing things the easy way. :) I think that I'm
> still inclined
> >to go the exit program route mostly because it would get me
> started with
> >exit programs. I am curious--If you turn on auditing for the CLROUTQ
> >command does it log attempts to use the command by users who aren't
> >authorized it or does it only log when it was successfully
> used? As you
> >can probably tell I also haven't used auditing or journaling before.
> >Either way I guess I get to learn something new!
> >
> >Dave Parnin
> >Nishikawa Standard Company
> >Topeka, IN 46571
> >daparnin@xxxxxxxxxxxxxxxxxx
> >
> >
> >
> >
> >
> > Vern
> > Hamberg
> >
> > <vhamberg@centerfieldtech To:
> Midrange
> > Systems Technical Discussion
> > nology.com>
> > <midrange-l@xxxxxxxxxxxx>@SMTP@CTB
> > cc:
> >
> > 05/10/2004 02:14 PM Subject: Re:
> > Restrict CLROUTQ--A good use for an exit
> > Please respond
> > to program?
> >
> > Midrange
> > Systems
> >
> > Technical
> > Discussion
> >
> > <midrange-l@xxxxxxxxxxxx>
> >
> >
> >
> >
> >
> >
> >
> >
> >Dave, the simplest way is to turn on auditing for the command. Use
> >
> >CHGOBJAUD OBJ(CLROUTQ) OBJTYPE(*CMD) OBJAUD(*USRPRF)
> >
> >You might want to do the same with the CHGOBJAUD command! ;-)
> >
> >And be sure to know which users have *AUDIT special
> authority - they can
> >change auditing even if they do not have authority to an
> object, according
> >to the help text.
> >
> >Then you need to have a journal called QAUDJRN. And set system value
> >QAUDCTL. The easiest way is to GO SECTOOLS and use option
> 10. For this
> >purpose, all you need is object auditing (*OBJAUD).
> >
> >HTH
> >Vern
> >
> >At 11:27 AM 5/10/2004, you wrote:
> > >Good morning all,
> > >
> > >We have a situation where someone appears to be clearing
> an outq for a
> > >printer used by many people. There's no real need for any
> user to be
> >using
> > >the CLROUTQ command or choosing option 14 from WRKOUTQ.
> What we would
> >like
> > >to do is to log the user-id of people trying to do this and give an
> error
> > >message to any non-MIS people.
> > >
> > >My boss initially suggested creating a modified CLROUTQ
> command that was
> > >higher in the library list than the system command. Over
> the weekend I
> > >started wondering if an exit program could do the job. I've never
> > >attempted an exit program before but wouldn't mind
> learning. I've seen
> > >examples for FTP and Telnet in the archives but can they
> be added for
> any
> > >command?
> > >
> > >I would appreciate any advice. Thanks.
> > >
> > >Dave Parnin
> > >Nishikawa Standard Company
> > >Topeka, IN 46571
> > >daparnin@xxxxxxxxxxxxxxxxxx
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
