Re: How to personalize System Request Menu?

The "authority fix" method that I proposed would survive release upgrades.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                    "John Earl"
                    <johnearl@powertech       To:     <midrange-l@midrange.com>
                    group.com>                cc:
                    Sent by:                  Subject:     Re: How to 
personalize System Request Menu?
                    midrange-l-admin@mi
                    drange.com


                    12/27/01 04:41 PM
                    Please respond to
                    midrange-l






Oh yes - and be prepared to re-apply this change after every OS
upgrade.

jte

--
John Earl
johnearl@powertechgroup.com
The Powertech Group          www.powertechgroup.com
Seattle, Washington, USA    +1 253-872-7788


----- Original Message -----
From: John Earl <johnearl@powertechgroup.com>
To: <midrange-l@midrange.com>
Sent: Thursday, December 27, 2001 01:28 PM
Subject: Re: How to personalize System Request Menu?


> Dimitri,
>
> Message description QSYS/QCPFMSG CPX2313 contains the commands
> that are executed by the System Request menu.  If you were
> replace the "SNDMSG" and "DSCJOB" strings with a string such as
> "NULLCMD" and then create a command called NULLCMD that does
> nothing, this would prevent all users from using the System
> request menu to run these commands.
>
> If you really want to limit just one group of users, you could
> try to (Warning! - I haven't actually done this myself - so
test
> first.) replace the string "SNDMSG" with "SNDMSGX" and "DSCJOB"
> with "DSCJOBX", and then write shells for the "X" commands that
> called the real OS/400 commands.  You could then give your
teller
> group *EXCLUDE authority tot he DSCJOBX and SNDMSGX commands.
> This allows the users to run these commands within their
regular
> applications, but prevents access from the System Request menu.
>
> HTH, I could go into more detail if this explanation is too
> cryptic.
>
> jte
>
> --
> John Earl
> johnearl@powertechgroup.com
> The Powertech Group          www.powertechgroup.com
> Seattle, Washington, USA    +1 253-872-7788
>
>
> ----- Original Message -----
> From: Dimitri Efimov <defimov@wiese.com.pe>
> To: <midrange-l@midrange.com>
> Sent: Thursday, December 27, 2001 12:52 PM
> Subject: RE: How to personalize System Request Menu?
>
>
> > To be more precise, we need to disable part:
> >  "Send Message" (5)
> >  "Disconnect job" (80)
> >
> > But just for the tellers profile users. Another problem: we
> cannot just
> > change the authorization for SNDMSG command, because this
> command is to be
> > called from teller application module.
> >
> > Thanks a lot
> >
> > Dmitri Efimov
> > Banco Wiese Sudameris
> >
> > DE
> >
> > -----Mensaje original-----
> > De: Norbut, Jim [mailto:Jim.Norbut@Grubb-Ellis.com]
> > Enviado el: Jueves, 27 de Diciembre de 2001 03:45 p.m.
> > Para: 'midrange-l@midrange.com'
> > Asunto: RE: How to personalize System Request Menu?
> >
> >
> > If you need to disable a person from accessing the menu
> >
> > I think changing the LMTCPB variable in a person's user
profile
> to *YES will
> > do this.
> > Any other ideas ?
> >
> > Or do you need to disable only "parts" of the menu and if
> so.....which parts
> > ?
> >  -----Original Message-----
> > From: Dimitri Efimov [mailto:defimov@wiese.com.pe]
> > Sent: Thursday, December 27, 2001 2:35 PM
> > To: midrange-l@midrange.com
> > Subject: How to personalize System Request Menu?
> >
> >
> > We need to eliminate (or just make disable) some of System
> Request Menu (is
> > the one U can get pressing Shift/Esc) functionality's for one
> group of
> > users.
> >
> > Is there possibility to do that?
> >
> > Will appreciate for advise
> >
> > Dmitri Efimov
> > Banco Wiese Sudameris
> >
> > DE
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion
(MIDRANGE-L)
> mailing list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> 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@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.