|
Okay - That is what I have observed. I would also like to know if this is 'working as designed' or is a bug. Maybe I'll fire off a note to George Farr... Thanks for all your input! -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of AGlauser@xxxxxxxxxxxx Sent: Tuesday, July 18, 2006 9:14 AM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Object authority issue Hmm ... good show Bill. I just tried this out, and you are on the money. I did a "RVKOBJAUT OBJ(mylib/QBNDSRC) OBJTYPE(*FILE) USER(myUserName) AUT(*EXECUTE), and while QBNDSRC still showed up in PDM, it disappeared from the list of objects in my library in RSE. When I did a GRTOBJAUT with the same parameters to get the authority back, it showed up in RSE again. So ... is this an "undocumented feature" in PDM or RSE? I would have expected a lack of *EXECUTE authority on a library to suppress listing of the objects in that library, but not *EXECUTE on a file. I guess that's my Unix permissions background speaking. Adam wdsci-l-bounces@xxxxxxxxxxxx wrote on 18/07/2006 08:54:08 AM:
It appears to me as if the lack of *EXECUTE rights is likely your
problem,
though I cannot explain why the lack of that would allow an object to
show
up in PDM, but not RSE. According to the Help text documentation in the GRTOBJAUT command: *EXECUTE Execute authority provides the authority needed to run a program or locate an object in a library. "Locate an object in a library" looks to be your culprit. Bill -----Original Message----- From: Terry Richardson [mailto:terry-sssc@xxxxxxxxxxxx] Sent: Tuesday, July 18, 2006 8:48 AM To: 'Websphere Development Studio Client for iSeries' Subject: Re: [WDSCI-L] Object authority issue I checked that, the filter strings do not specify any object types. In
that
dialog box, it selects all objects, all types and attributes. (*.*) The authority on the objects that DO show up in RSE is different: They
have
Operational and Management rights, and read and execute data rights. We are also using the Softlanding Turnover client plug-ins, so I called their tech support and asked if they had any ideas. They said that if
you
can see the object in PDM (or WRKOBJ), you should see it in RSE. -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On
Behalf Of AGlauser@xxxxxxxxxxxx Sent: Monday, July 17, 2006 3:00 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Object authority issue Hi Terry, Depending on the dialogue box, it may be limiting which files show up based on the object attribute text (for example, we have some PF38 files
which don't show up when one is looking for source files, RSE wants 'PF-SRC'). Hope this helps, Adam wdsci-l-bounces@xxxxxxxxxxxx wrote on 17/07/2006 02:30:24 PM:Good afternoon- I am having an issue with certain objects (object type *FILE) notappearingwhen drilling down into a library with RSE. These objects are visible
andusable from the green screen via PDM. The specific object authority
is
Operational and the data authority is Read. Is there a minimal level
of
authority required in order to see an object in RSE? -- This is the Websphere Development Studio Client for iSeries (WDSCI- L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
############################################################################
######### Attention: The above message and/or attachment(s) is private and confidential and
is
intended only for the people for which it is addressed. If you are not named in
the
address fields, ignore the contents and delete all the material. Thank you. Have
a
nice day. For more information on email virus scanning, security and content management, please contact administrator@xxxxxxxxxxxx
############################################################################
######### -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. -- This is the Websphere Development Studio Client for iSeries (WDSCI- L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
############################################################################ ######### Attention: The above message and/or attachment(s) is private and confidential and is intended only for the people for which it is addressed. If you are not named in the address fields, ignore the contents and delete all the material. Thank you. Have a nice day. For more information on email virus scanning, security and content management, please contact administrator@xxxxxxxxxxxx ############################################################################ #########
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.