Thanks for your reply. That's right. As you mention above, I used the
clean option in configaa datadvh.
Also, this auto reply error messages was related with
'MAXIMUM_UNASSIGNED_WORKUNITS=' option which default value was 10.
So, I change the default value to 100 and delete the LINK parameter
under DATAMOVE directory file and delete file 'PURGES PENDING'.
After update above configuration, I issue the PURGE command with
noclean option. then all error message was disappeared.

However, we still have problem when I used the purge command by maint,
it was not purged clearly that i think.
Because, after purged the guest,  it information was still exist in
directory file that was  appeared  by 'DIRM USER NOPASS'.

1. How can I purge the guest in perfectly by purge command?
2. That was related problem 'CLEAN' or 'NOCLEAN' option?

If this problem was related 'CLEAN' option in CONFIGAA DATADVH
configuration file, we have to another way to remove the guest.
Always, we have to shared the one storage by two z/VM. So, when we
make the guest in first, we define the directory and racf on both
systems.



thanks in advance.

best regards.



>If DIRMAINT didn't respond to your initial request, then there was something
>wrong with it at that point.  When you logged on and issued the DVHBEGIN
>command, you restarted DIRMAINT.  That is why your commands started to be
>processed.
>
>What you need to find out is the status of DIRMAINT before you logged in.
>Do you keep the console logs archived anywhere?  If you do, check the one
>from just before 16:23:45 and see what state DIRMAINT was in at that point.
>
>When you purge a guest, but default DIRMAINT tries to clean up any minidisks
>defined to that guest.  It does this by transferring them to the DATAMOVE
>virtual machine, which then does a format on the disks before giving them
>back to the system.  So, that is what the messages involving DATAMOVE are
>about.
>
>If this guest had a lot of minidisks, or they were very large ones, this
>process can take quite awhile.  So, that may have been part of the delay
>you were seeing (can't really tell without seeing the full console log).
>You can avoid the cleanup process if it isn't important to your situation.
>To avoid it, use the NOCLEAN option on the PURGE command, for example:
>
>dirm for xlnx2 purge noclean
>
>Then, DIRMAINT deletes the guest from the directory but does not format
>the disks.
>
>Martha McConaghy
>Marist College

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to