Re: GO NETS menu

[CRPence <CRPbottle@xxxxxxxxx>]

On 05 Jun 2013 05:44, Musselman, Paul wrote:
> The "Users" option (12) on the let's GO NETS menu is concerned with
> re-enabling someone whose NetServer permission has been disabled.

 :-) he-heh "let's go ..."

> Is there an option to -disable- someone's NetServer permissions
> without affecting their system user profile? Would there be any need
> or advantage to block their ability to access the system from a
> mapped network drive, but still allow them green-screen access??

  Apparently disabling is available only for too many "incorrect 
sign-on attempts when connecting to iSeries Support for Windows Network 
Neighborhood (iSeries NetServer)"; i.e. for what is diagnosed by the OS 
with the message CPIB682.

  Perhaps disabling the user is an extension, that could be requested 
for the Change Server Information (QZLSCHSI) API; e.g. via a new format 
for /disable/ beyond the already available format [ZLSS0200 Enable user 
information] that exists to /enable/ user(s):
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/apis/qzlschsi.htm

  That is, if the OS can disable [just the NetServer access], then 
perhaps there is a reason that someone might also have the desire to 
effect the same, and thus require the same capability to disable.  Just 
being able to mimic what the OS provides is sometimes all that is 
required, rather than articulating a specific /need/ [e.g. for enabling 
a 3rd party product], to get such an enhancement.  One likely example 
was the access eventually added for the message key on which a 
[non-writer] job was waiting, to mimic the 7="Display message" of 
WRKACTJOB; I do not believe the support was added for any particular 3rd 
party product, rather just because enough people wanted to be able to 
mimic what the OS already provided... although perhaps in their own 
WRKACTJOB-like feature.