×
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.
In order to guard against damnfool admins doing a DLTUSRPRF with
OWNOBJOPT(*DLT) on former employees (thereby wiping out IFS objects they
created), our CRM product, when it creates IFS objects, attempts to
reassign ownership of them to the user's primary group profile.
But that leaves us high and dry in attempting to track down the origin
of defective IFS objects, since options 8 and 9 in WRKLNK show the
owner, but not the creator.
QSYS objects, of course, don't have that problem, since they have
separate OWNER and CREATOR attributes. Indeed, that's why, when we
create QSYS objects to be shipped, we have separate "creator" user
profiles, so that the objects we ship all have IBM-supplied user
profiles as OWNER, and some generic name like QVCREATOR or WTCREATOR as
CREATOR.
Is there someplace where IFS objects keep track of a CREATOR, separately
from the OWNER? Someplace that doesn't show up in WRKLNK Options 8 and
9, but does show up someplace else?
--
JHHL
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
