× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2004

RE: Restrict CLROUTQ--A good use for an exit program?

My opinion?

User this problem as the excuse to remove *SPLCTL - no report on the
system is secure from a *SPLCTL user.

jte

--
John Earl | Chief Technology Officer
The PowerTech Group
19426 68th Ave. S
Seattle, WA 98032
(253) 872-7788 ext. 302
john.earl@xxxxxxxxxxxxx
www.powertech.com 
 

 
This email message and any attachments are intended only for the use of
the intended recipients and may contain information that is privileged
and confidential. If you are not the intended recipient, any
dissemination, distribution, or copying is strictly prohibited. If you
received this email message in error, please immediately notify the
sender by replying to this email message, or by telephone, and delete
the message from your email system.
--

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of David A Parnin
> Sent: Monday, May 10, 2004 2:16 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: RE: Restrict CLROUTQ--A good use for an exit
> program?
> 
> 
> Actually, virtually all users have *SPLCTL (yea, I know...
> what's with
> that?).  That was a product of a former employee and
> nobody has made the
> push to do anything about it.  I did look at removing
> *SPLCTL from
> everybody which would solve the problem of clearing the
> outq's but it still
> wouldn't leave any "footprints in the butter" of who the
> responsible party
> was.  I would also have to change the outq's too to allow
> people to see
> other people's spool files (where needed).  Still, we have
> a number of jobs
> scheduled in Robot under group profiles like SSA or
> KRONOS.  Who would be
> able to delete those spool files?
> 
> Ultimately, *SPLCTL should probably go away.  Maybe now is
> the time...?
> 
> Dave Parnin
> Nishikawa Standard Company
> Topeka, IN  46571
> daparnin@xxxxxxxxxxxxxxxxxx
> 
> 
> 
> 
> 
>                       John Earl
>                       <john.earl@powert        To:
> Midrange Systems Technical Discussion
>                       ech.com>                  <midrange-
> l@xxxxxxxxxxxx>@SMTP@CTB
>                                                cc:
>                       05/10/2004 04:05         Subject:
> RE: Restrict CLROUTQ--A good use for an exit
>                       PM                        program?
>                       Please respond to
>                       Midrange Systems
>                       Technical
>                       Discussion
>                       <midrange-l@midra
>                       nge.com>
> 
> 
> 
> 
> 
> As much as I am a proponent of exit programs, this seems
> like a good
> place to secure the outq itself.  Any chance that this
> user has *JOBCTL
> (or *SPLCTL) special authority?
> If they do, then consider removing the Special Authority
> from the user.
> 
> Another option is to change the AUTCHK parameter on the
> out queue to
> (*OWNER), so as to prevent the user from deleting entries
> that they
> don't own.  Either of these approaches would be easier
> than writing an
> exit program.
> 
> jte
> 
> --
> John Earl | Chief Technology Officer
> The PowerTech Group
> 19426 68th Ave. S
> Seattle, WA 98032
> (253) 872-7788 ext. 302
> john.earl@xxxxxxxxxxxxx
> www.powertech.com
> 
> 
> 
> This email message and any attachments are intended only
> for the use of
> the intended recipients and may contain information that
> is privileged
> and confidential. If you are not the intended recipient,
> any
> dissemination, distribution, or copying is strictly
> prohibited. If you
> received this email message in error, please immediately
> notify the
> sender by replying to this email message, or by telephone,
> and delete
> the message from your email system.
> --
> 
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-
> l-
> > bounces@xxxxxxxxxxxx] On Behalf Of David A Parnin
> > Sent: Monday, May 10, 2004 9:28 AM
> > To: midrange-l@xxxxxxxxxxxx
> > Subject: Restrict CLROUTQ--A good use for an exit
> program?
> >
> > 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 thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.