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



On our system, I'm not sure about the authority setting on the production 
source file, but I can not open code for update. If I try to open a source 
member WDSC tell me I cannot update this member would I like to browse. So 
file authority will work.



Jerry Adams <jerry@xxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces+broche=packagingcorp.com@xxxxxxxxxxxx
10/27/2006 09:38 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Protect programs in certain library's






I don't know of anything in WDSc that would provide this "protection," 
but wouldn't setting the authority on the source PF to *Public/UserId = 
Read do the trick?  Haven't tried it, but security should prevail.


                 * Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
                 615.995.7024
fax
                 615.995.1201
email
                 jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



DLee@xxxxxxxx wrote:

Morning all;

I'm looking for a way to specify that any programs I bring up with lpex 
will be in brouse mode only if displayed from a specified library.

I don't want to someday shoot myself in the foot by modifying a program 
from the production source library.

Any suggestions?

Darrell Lee
Information Technology




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.