Thanks, Ken. That's alot of help.
[EMAIL PROTECTED] wrote:
My users have frequently done the same. Sometimes I have to clean up by
mostly following the "Dirmaint R5 DASD Management Cleanup" script. It's
somewhere off of the VM.IBM.... pages. Try google. I have seen no harm done
by just logging on to dirmaint to resolve these kind of problems. If you
hit enter twice the machine stops and you have access to all of the files
without trying to link to disks. If you want to see startup msgs. logoff
and logon.
Look at the history file. It will tell you what the first error was. Things
usually get stacked behind this or made worse by the system programmer.
If you can, which it sounds like you cant, cancel the outstanding
workunits. If dirmaint becomes responsive, fix the original problem.
The cleanup doc mentioned above will usually get you going again. I just do
all the tasks while logged on to Dirmaint. Since I know what I or the users
were trying to do, I usually just delete the old workunit files and lock
files I find. If you were moving mdisks make sure you know were the extents
were originally so you can re-add them back to the original user before you
try again. You just have to be careful. Some of my users have the same
problem all over again after dirmaint is working again. This is because
they fail to check the History file to fix the first problem.
The last problem I had with Dirmaint was a move mdisk to a new location
which was not formatted. In this problem there were no good error
descriptions. The space was previously OS I think. We manually added a
mdisk statement to get to this area and format it. The other thing is our
Dirmaint is pretty backlevel so our results may be different than yours.
Rich Smrcina
<[EMAIL PROTECTED]
om> To
[email protected]
Sent by: VM/ESA cc
and z/VM
Discussions Subject
<[EMAIL PROTECTED] DIRMAINT not accepting work
.UARK.EDU>
12/05/2005 10:49
AM
Please respond to
VM/ESA and z/VM
Discussions
<[EMAIL PROTECTED]
.UARK.EDU>
Somehow I have DIRMAINT in a state where it isn't accepting work. I get
this message:
DVHXMT1192E The DIRMAINT service machine is not accepting work. Your
DVHXMT1192E QUERY command has been rejected; RC= 1057. Please try again
DVHXMT1192E later. If the problem persists, notify your local support
DVHXMT1192E group.
I've looked up the 1192E and check the options there and they all look
good. But, what does the RC=1057 mean?
Thanks.
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006
