Hello,
Thanks very much from your information.
Here, wen don't have a lot of CMS users like this :
q users
56 USERS, 61 DIALED, 0 NET
Ready; T=0.01/0.01 16:20:45
But, how you said, the very good important point is about manage password
changes, that is a question that We will study here, and also ask your opinion .
Thanks again, and Best Regards,
Sergio
> Date: Fri, 1 Oct 2010 11:53:13 -0600
> From: ron.schmie...@gmail.com
> Subject: Re: How DIRMAINT Work ?
> To: IBMVM@LISTSERV.UARK.EDU
>
> Robert,
> DIRMAINT does come with a "wakeup" table of commands that includes a
> BACKUP command to backup your online directory into a source file. It
> runs daily and you always have a current backup on DIRMAINT 1DB. Look
> at DIRMAINT DATADVH
>
> Sergio,
> I've been using DIRMAINT since coming back to VM in 1999 and it has
> not been a problem using it. I do not miss editing the entire
> directory at all. One other "pro" is that it is an added tool to beat
> back the auditors when they come around asking silly questions like
> "how do you manage password changes"? DIRMAINT can tell you who hasn't
> changed their passwords and you can either send them gentle reminders
> or have DIRMAINT give them a new password.
>
> Ron
>
> On Fri, Oct 1, 2010 at 10:13 AM, RPN01 <nix.rob...@mayo.edu> wrote:
> > The benefits are far greater than the loss of directly editing your
> > directory. Have you ever edited your directory and put it online, only to
> > find out later that you’d managed to overlay a minidisk or important piece
> > of CP’s disk? It shouldn’t happen again if you correctly implement Dirmaint.
> > And you won’t have to hunt for space to add a user. You can just say “I need
> > a 200 cyl minidisk, and Dirmaint will find a place to put it. Have two
> > systems? Dirmaint can actually manage one common CP directory between the
> > two. There really isn’t a reason to hand-manage a CP directory that
> > outweighs using Dirmaint or some other directory management tool. The tool
> > is always a better choice.
> >
> > Now, a caveat. On some regular basis, use the command “Dirmaint user
> > withpass”, and save a copy of the old-style complete directory on maint’s,
> > or your 191 disk, just for emergency’s sake. Don’t get caught without a
> > fairly current source directory that you could put online yourself in an
> > emergency situation if something should happen and Dirmaint couldn’t run. I
> > don’t know what that situation might be, but I like the warm, fuzzy feeling
> > of being able to see that “user withpass” file on my 191 disk.
> >
> > --
> > Robert P. Nix Mayo Foundation .~.
> > RO-OC-1-18 200 First Street SW /V\
> > 507-284-0844 Rochester, MN 55905 /( )\
> > ----- ^^-^^
> > "In theory, theory and practice are the same, but
> > in practice, theory and practice are different."
> >
> >
> >
> > On 10/1/10 8:54 AM, "Sergio Lima" <sergiovm...@hotmail.com> wrote:
> >
> > Hello List,
> >
> > We need implement the DIRMAINT product here, but we have some doubts.
> >
> > Have a STEP there, when need migrate our VMUSERS DIRECT A to DIRMAINT
> > minidisk.
> >
> > After do this, We never more can edit our VMUSERS DIRECT, as we do today?
> >
> > We are very concerned about this implementation, which we should take
> > necessary precautions?
> >
> > We already have implemented this, in a test environment, apapparently had no
> > problems, but we need to make sure.
> >
> > Could someone give their opinion?
> >
> > Thanks very much
> >
> > Sergio Lima Costa
> > Sao Paulo - Brazil
> >
> >
> >
> >
