Re: QSYSOPR user profile and GO SAVE 21

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

Roberto;

What you say is true, and only QSECOFR can reset the QSECOFR DST 
password, but since the user profile in this case is one that was 
created called QSYSOPR, (IBM does not supply a QSYSOPR in DST) it cannot 
be reset except by an authorized DST user profile.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 6/13/2012 9:54 AM, Roberto José Etcheverry Romero wrote:
> To reset the DST/SST QSECOFR password to QSECOFR (mind the capitals) you do:
>
> CHGDSTPWD *DEFAULT but the only one that can do it is the real QSECOFR
> AFAIK not even a *secofr user can issue it.
>
> Best Regards,
>
>
>
> On Wed, Jun 13, 2012 at 11:19 AM, John McKee<jmmckee@xxxxxxxxxxxxxx>  wrote:
> > >  Thanks for the SST reference.  The sa never allowed me any SST access.
> > >    The only person here (sa has bigger fish to fry) knows little of the
> > >  innards.  Interesting that he is the one with QSECOFR access, and I
> > >  have to explain to him what to do.  Wonderful situation, isn't it?
> > >
> > >  John McKee
> > >
> > >  On Wed, Jun 13, 2012 at 9:03 AM, Jim Oberholtzer
> > >  <midrangel@xxxxxxxxxxxxxxxxx>  wrote:
> > > >>  That just tipped a thought off.  If this is a LAN console user profile,
> > > >>  that's different than the IBM i profile.  If you can get into SST,
> > > >>  option 8 and check the user profile there.
> > > >>
> > > >>  Jim Oberholtzer
> > > >>  Chief Technical Architect
> > > >>  Agile Technology Architects
> > > >>
> > > >>
> > > >>  On 6/13/2012 8:54 AM, Porterfield, Sean wrote:
> > > > >>>  If you don't know what it is... how about I5CONSOLE?  We called our machine an i5 for quite a while, so that's a reasonable console name.  Perhaps it's about the SST user QSYSOPR which is probably needed before the IBM i user QSYSOPR?
> > > > >>>
> > > > >>>  I'll leave the other question for someone else, but our QSYSOPR *USRPRF also shows an old save date from when we restored to a new system.
> > > > >>>  --
> > > > >>>  Sean Porterfield
> > > > >>>
> > > > >>>
> > > > >>>  -----Original Message-----
> > > > >>>  From:midrange-l-bounces@xxxxxxxxxxxx    [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
> > > > >>>  Sent: Wednesday, June 13, 2012 09:23
> > > > >>>  To: Midrange Systems Technical Discussion
> > > > >>>  Subject: QSYSOPR user profile and GO SAVE 21
> > > > >>>
> > > > >>>  Some time back, a switch was made to use Go SAVE 21 on the v5r4 system.  This morning, I received an email about an issue with QSYSOPR.
> > > > >>>
> > > > >>>  Profile is marked as enabled, yet message displayed when operator tries to connect to ISCONSOLE is "The user id QSYSOPR is disabled".
> > > > >>>
> > > > >>>  DSPOBJD shows object QSYSOPR *USRPRF was changed this morning at 04:05:52..  But, Save/Restore shows last save date/time of 8/13/06 00:25:31.
> > > > >>>
> > > > >>>  Guess I have two questions:
> > > > >>>
> > > > >>>  1) I thought a SAVE 21 saved everything.  Does that function not update the saved date/time for the user profile?
> > > > >>>
> > > > >>>  2) What is ISCONSOLE?  I don't see anything by that name.
> > > > >>>
> > > > >>>     v5r4 way behind on PTFs.
> > > > >>>
> > > > >>>  John McKee
> > > > >>>  --
> > > >>  --