Re: CHGUSRPRF no longer fixes NetServer access

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

New issue surfaced a few weeks ago where remote user would lose access to
shared folder.  CA not installed.  True, an alternative is available to
allow user to fix, but capability was already in a command, so nothing had
to be created to fix the issue.  If this "fix" was imposed to actually fix
another issue, that would be nice to know.

John McKee


On Tue, Jun 4, 2013 at 6:30 AM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

> To re-eanble Netserver users using Ops Nav,
> Go To Network, Servers. TCP/IP and Right Click on Netserver. You wil see
> the option for Disables Users IDs
> Click and any disabled profiles are displayed and can be re-enabled
>
>
>
>
> On Tue, Jun 4, 2013 at 4:09 AM, <rob@xxxxxxxxx> wrote:
>
> > In my earlier post I snickered about 7.1.1.  However you really need to
> > read that link!
> >
> > Note: MF55661 removes the ability of the CHGUSRPRF command to reset, or
> > re-enable, a user that is disabled for NetServer access. You should refer
> > to APAR MA42015 for additional information. This is a Hiper PTF and is
> > included in the current Hiper Groups and in every Cumulative PTF package
> > since the 2279 level. This means that all NetServer users will eventually
> > encounter this change. Individual users can be re-enabled by using the GO
> > NETS menu, using IBM i Navigator, or by writing a program that makes use
> > of the QZLSCHSI API. All profiles are re-enabled for iSeries NetServer
> use
> > when iSeries NetServer is restarted from the iSeries Navigator screen or
> > by running the STRTCPSVR *NETSVR command. All profiles are also
> re-enabled
> > for iSeries NetServer use when the iSeries family system is IPLed.
> >
> >
> > Rob Berendt
> > --
> > IBM Certified System Administrator - IBM i 6.1
> > Group Dekko
> > Dept 1600
> > Mail to:  2505 Dekko Drive
> >           Garrett, IN 46738
> > Ship to:  Dock 108
> >           6928N 400E
> >           Kendallville, IN 46755
> > http://www.dekko.com
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
>
> --
> Kirk
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.