Re: Deleted a VM ID and now trying to restore it

[Jim Bohnsack]

I have an ongoing problem like that with DIRMAINT.  I like to put mdisks where I want them to go rather than letting DIRMAINT find the space, so I always get the DVH3297 msg.  My "solution" is to add the userid with no mdisks and then add the disks where I want them using a DIRM FOR userid LOCK and then DIRM FOR userid REP with the mdisk(s) added in. 

As a word to the wise, however, always check for an overlap when you manually allocate a mdisk.  I use the CMS DIRMAP tool, rather than what comes with DIRMAINT.  Always do a DIRM USER BACKUP and then run DIRMAP against the fresh copy of USER BACKUP.

Jim

At 01:33 PM 11/9/2005, you wrote:

I deleted an ID that hasn't been signed in for over a year.  This was done
just a couple of days ago.  Just today I found out that there are some IDs
that link to the deleted VM ID mdisk.

Since I have a copy of the old USER WITHPASS, I extracted the VM ID that
was deleted and try to add it issuing DIRM ADD and get the following
errors:
DVHALC3297E No gap of sufficient size found in candidate area(s).
DVHAMD3298E DASD allocation attempt failed.                     

I also notice that there are some IDs still link to the delete VM ID.  I
guess the IDs that are still link to the mdisk hasn't signed off. 

Is this the reason I can't add the VM ID again and getting the no gap
error?

TIA,
Al  

Jim Bohnsack
Cornell Univ.
(607) 255-1760