Hmm. The mapping from user profile name to user ID number is buried in
the bowels of DSPUSRPRF output. <plug>And I can get a listing of that
mapping by directing it to an outfile, then displaying that outfile in
QuestView (tm), and hiding the fields that are of no interest.
And it looks like the IBM-supplied user profiles have ID numbers that
are constant across systems. e.g.:
QSECOFR = 0, QUSER = 4294770692, QSYS = 101, QDFTOWN = 102 . . .
Tell me, just out of morbid curiosity, does anybody know if anything bad
happens (whether bad as in "may cause a mild headache" or bad as in
"don't cross the streams") if an IFS object's ownership is transferred
to QDFTOWN? Or to QSYS?
Hmm. This could be a problem: it apparently needs "add" authority to the
user profile to which the object's ownership is being transferred. They
make it easy enough for unwary system administrators to screw things up;
why must they make it so hard to make things unscrewable?
--
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.