Re: RE:Command Restriction

["Clare Holtham" <Clare.Holtham@xxxxxxxxxxxxxx>]

Hi Chandra,

You put the special library above QSYS using the system value QSYSLIBL.
The reason for not keeping the changed command in QSYS is that if you do,
you will lose it when you upgrade OS/400.
Hope this helps,

Clare

Clare Holtham
Director, Small Blue Ltd - Archiving for BPCS
Web: www.smallblue.co.uk
IBM Certified AS/400 Systems Professional
E-Mail: Clare.Holtham@xxxxxxxxxxxxxx
Mobile: +44 (0)7960 665958
----- Original Message -----
From: "Chandra Sekhar Rath" <ChandraRS@xxxxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, August 05, 2003 1:03 PM
Subject: RE:Command Restriction


> Hi Clare,
>
> Thanks for the response.What i would like to do is
>
> 1)The original command be copied and put in a special library.Since only
> SECOFR can use CHGSYSLIBL  , and i would like to
> have it run from command line for SECOFR as well as *PGMR group, by doing
so
> i avoid using CHGSYSLIBL.
>
> 2)Change the command DLTF in QSYS , so that the end users use the changed
> command.
>
>
> Hence, can you please tell me how to i put the special library above QSYS
> above the system library list?
>
> Thanks and regards
> Chandra Sekhar
>
>
> The usual way is to put the changed commands in a special library that you
> put above QSYS in the System library list. So users will be using the
> changed commands anyway. Then programmers can use the CHGSYSLIBL command
to
> remove that special library, thus having access to the real commands. Or
> they can specifically invoke the real commands from QSYS. Remember that
> *Secofr is needed to do a CHGSYSLIBL. Current library is a red herring,
and
> in any case is not in the system library list (it doesn't work like on the
> System 36 with #library.) Hope this helps,
> Clare
> Clare Holtham Director,
> Small Blue Ltd - Archiving for BPCS
> Web: www.smallblue.co.uk IBM Certified AS/400 Systems Professional
>  E-Mail: Clare.Holtham@xxxxxxxxxxxxxx
> Mobile: +44 (0)7960 665958
>
>
>
>
>
>
> _______________________________________________
> 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.
>
>