Re: QRPLOBJ Authority

Rudolph,
 
>> >I do not think that using QRplObj is a very good idea.
>> 
>>  Why?
>
>Because it is a "system library" owned and used by OS/400
>for a very special purpose.
>I "do not know" or "am not supposed to care about"
>- what OS/400 does with the objects in this library

>- when objects are created and destroyed in this library

 You should know, since the contents of this library can be used for
recovery in some cases (i.e. if you moved a pgm to production a "little too
soon".)

>- if creating my own objects there cause naming conflicts

 With what?  During normal operations, QRPLOBJ behaves like a normal
library, w/ the same rules.

>.. so it is IMO a good idea to leave this library to the system.

 While it is a "system" library, its function and behavior is fairly well
defined.  As such, the only objection I can see is the one Charlie
mentioned regarding security.

 As an aside, do you define your device descriptions in a user created
library or do you use QUSRSYS (which is a system library) like most shops?

 -mark

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *