Hello Dave,

 

Help a lot, for us, was very good understand this.

 

Thanks again, and Best Regards,

 

Sergio


 
> Date: Fri, 1 Oct 2010 09:21:19 -0500
> From: d...@vsoft-software.com
> Subject: Re: How DIRMAINT Work ?
> To: IBMVM@LISTSERV.UARK.EDU
> 
> Hi, Sergio.
> 
> On 10/1/2010 8:54 AM, Sergio Lima 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?
> >
> Yes, once you give DIRMAINT control over your VMUSERS DIRECT file, you 
> can no longer edit it youself.....all changes to the user dirctory mut 
> be done by DIRMAINT.
> 
> However, it is very easy to switch bak to managing the VMUSERS DIRECT 
> file yourself, jut as you are doing now. Here ar the steps required:
> 
> 1) First tell DIRAMINT to send you a copy of the current (source) user 
> directory file:
> DIRM USER WITHPASS
> 2) receive the sent file onto your A (191) minidisk
> RECEIVE <spoolid> VMUSERS DIRECT A
> 3) Stop DIRMAINT processing:
> FORCE DIRMAINT
> 4) begin making changes to the user directory file by editing it and 
> then bringing it online:
> XEDIT VMUSRES DIRECT
> (make changes)
> DIRECTXA VMUSERS
> 
> That's all there is to taking back control of the user directory file 
> from DIRMAINT.
> 
> If you want DIRMAINT to (again) manage your user directoy, all you have 
> to do is rename the current user directory file USER INPUT to USER INPUT 
> and put it on DIRAMINT's 1DF minidisk, are restart the DIRMAINT virtual 
> machine.
> > 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?
> >
> 
> I've found DIRMAINT to be a useful and stable tool, especially where 
> managing DASD space is concerned. The olnly poblems I have ever 
> encountered are stalled workunits by the DATAMOVE virtual machine.
> 
> Hope this helps some.
> > Thanks very much
> >
> > Sergio Lima Costa Sao Paulo - Brazil
> >
> >
                                          

Reply via email to