× 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.


  • Subject: RE: Preventing users from RUNQRY Interactively
  • From: "Graziano, Marie" <mgraziano@xxxxxxxxxxxxxxx>
  • Date: Wed, 19 May 1999 11:03:40 -0500

If all you want to do is eliminate RUNQRY interactive for ALL.  Then do a
change on the command and  under the parameter where allowed to run, REMOVE
interactive.

                -----Original Message-----
                From:   John Cirocco [mailto:JCirocco@gw.ctg.com]
                Sent:   Wednesday, May 19, 1999 9:57 AM
                To:     MIDRANGE-L@midrange.com
                Subject:        Re: Preventing users from RUNQRY
Interactively

                How about CHGSYSLIBL?

                                  Change System Library List - Help

        

                The Change System Library List (CHGSYSLIBL) command changes
the      
                system portion of the library list for the job in which the
command  
                is entered.  You can specify if the library is added to the

                beginning of the system portion of the library list, or
removed from 
                that list.  The library QSYS cannot be added to or removed
from the  
                system portion of the library list.


                >>> Shane Bill <bshane@video.astral.com> 05/19 8:34 AM >>>
                >Unfortunately, this Appendix D does not mention the
problems involved in
                >putting another library in front of QSYS.
                >Many, if not most, AS/400's have QSYS defined as part of
the system value
                >QSYSLIBL.  That's good, since users cannot use EDTLIBL to
change this
                >portion of their job's library list - if they could, they
might
                >inadvertently remove QSYS, thereby killing their access to
any system
                >command.
                 
                >The "rub" here is that you can't add a library in front of
any library in
                >the SYS portion of your library list.

                You can change the system value QSYSLIBL so that your new
library appears
                above QSYS in the system library list.

                I have done that so as to have exit programs on commands for
secutity
                purposes and not changed the commands in QSYS.

                It also will run the customised versions of the commands
after an upgrade,
                although I have a CL to run that will recreate the commands
from QSYS.  

                Bill Shane
                Manager ERP systems
                Astral Video
                b_shane@bigfoot.com 

        
!
        

                +---
                | This is the Midrange System Mailing List!
                | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
                | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
                | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
                | Questions should be directed to the list owner/operator:
david@midrange.com
                +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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.