Thanks to all you contributed. I have successfully enabled the storage
group.
link maint 193 193 rr
Ready; T=0.01/0.01 09:31:39
acc 193 g
DMSACP723I G (193) R/O
Ready; T=0.01/0.01 09:31:43
set filepool techsrv:
query filepool disable
Object Type Object ID Disabled Creator Mode Link Status
GROUP 2 YES SFSBKUP SHARE LINKED
Ready; T=0.01/0.01 09:32:45
filepool enable group 2 techsrv: ( for sfsbkup
DMSWFP3485I FILEPOOL processing begun at 09:33:08 on 6 May 2008.
DMSWFP3486I FILEPOOL processing ended at 09:33:08 on 6 May 2008.
Ready; T=0.01/0.01 09:33:08
query filepool disable
Object Type Object ID Disabled Creator Mode Link Status
FILESPACE PKSBP NO - - -
Ready; T=0.01/0.01 09:33:20
Thank you,
Scott R Wandschneider
Senior Systems Programmer
Infocrossing
Office 402.963.8905
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Monday, May 05, 2008 6:32 PM
To: [email protected]
Subject: Re: SFS Locked Directory
On Monday, 05/05/2008, "Wandschneider, Scott"
<[EMAIL PROTECTED]> wrote:
> Thanks Richard. I too have worked with SFS for, well since day one, a
long
> time now. I have never had this situation. I tried all the
suggestions, etc
> in HELP nothing worked. Any ideas?
Your output to QUERY FILEPOOL DISABLE showed:
> Object Type Object ID Disabled Creator Mode Link Status
> GROUP 2 YES SFSBKUP SHARE LINKED
> Ready; T=0.01/0.01 16:50:35
The user SFSBKUP has disabled storage group (SG) 2, not an individual
filespace. I think the contents of all filespaces with space on SG 2
will
appear to be locked (because the physical storage is locked). Did
SFSBKUP
fail? If so, you need to do some recovery actions (consult
documentation). This may require manually enabling the storage group.
Or you need to satisfy whatever SFSBKUP is waiting on so that it can do
whatever and release the locks.
Alan Altmark
z/VM Development
IBM Endicott
