×
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.
Be very careful when deleting user profiles, particularly regarding objects
/owned/ by those profiles:
The OWNOBJOPT parameter of DLTUSRPRF allows you to either delete or transfer
the ownership of objects owned by the profile.
We had a situation where some necessary files disappeared from one of the
Q/A libraries on our development system.
By examining the entries in the system audit journal (QAUDJRN), I was able
to determine /who/ deleted the files in question, and that led back to the
actions taken by the security officer - it turned out that when he deleted a
user profile, he had specified OWNOPJOPT(*DLT) when he deleted it, thus
deleting all of the objects owned by that profile.
This also points out the fact that the 'best practice' when setting up new
user profiles is to make the user profiles members of a group profile, and
specify the group profile of any objects created by the users.
- sjl
Robert wrote:
As usual, I overlooked something staring me right in the face
(the *OUTFILE). I usually use DSP commands to do just that,
display on my screen. Thanks for the help, it's been a long day...
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
