Re: SFS question
Ivica and others. Thank you for the help. Increasing the size of the control disk fixed the problem. Steve From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Ivica Brodaric Sent: Saturday, March 12, 2011 8:12 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS question Stephen, Do I understand the formula and definitions correctly? You do, but that's just to get you started. It really all depends on how many objects are going to be created in that file pool. So, take that formula as an attempt to predict the future. MAXUSERS determines the logical size of the catalog and that formula is MAXUSERS * 85 (and that's a real formula). Half of that goes to data blocks and half to index blocks. The physical size of the catalog (number of blocks in group 1) can initially be much smaller than that. That smaller space would again be divided equally to data and index blocks. It is much easier to add another minidisk to group 1 (when you hit physical limit) than to do regenerate file pool (when you hit logical limit). Therefore, allocate MAXUSERS generously, so that you don't have to do this again soon. In your case, you have 640 cylinders in group 1 (16 * 40 cyl), which equates to 115200 blocks. You may have over-allocated group 1, but to decrease that now would be a pain, so leave it. To be able to use all that space, the logical size of the catalog has to be at least that much, so MAXUSERS must be at least 1356, which is 115200 / 85, rounded up. I would suggest that you use at least 5000 if not 1 for MAXUSERS. Over-allocating MAXUSERS is not harmful, it just takes a bit of space in control minidisk. Size of control minidisk (or of the rest of it) determines the number of potentially addressable blocks in the file pool (maximum size to which the file pool can grow to). You can see that number if you do QUERY FILEPOOL OVERVIEW, but roughly, it is a bit less than one million addressable blocks for each control disk cylinder. There is no formula for this, because other things go to control disk as well (MAXDISKS has a hand in it too), but for example (roughly again), with a 50-cylinder control disk you will be left with at least 45 million potentially addressable blocks, which equates to around 75 3390 mod3's. That's the maximum size of disk space that you will ever be able to have in the file pool before having to regenerate it. While regenerating file pool, you will have to increase the size of the control disk. You have to do this to allow for the increase of MAXUSERS in order to maintain at least the same number of potentially addressable blocks. Increase it by 25-33% to be sure, but do *not* over-allocate control disk. Whenever the file pool server performs control data backup (and it does it automatically when log disks fill up more than 80%), the file pool will be unavailable to end users for the duration of the backup. You want that backup to be quick especially if your log disks are small and the backup is run often. Control data backup backs up *entire* control disk and *used* blocks in group 1 (catalog). Therefore, over-allocating group 1 is OK, but over-allocating control disk is not. Follow the procedure to regenerate a repository file pool to which you have been pointed to already and you'll be fine. One final word of advice though: before doing anything like this, make sure that you also have a reliable backup of the whole file pool (storage groups 2 and above) handy. Ivica Brodaric BNZ
Re: SFS question
Stephen, Do I understand the formula and definitions correctly? > > You do, but that's just to get you started. It really all depends on how many objects are going to be created in that file pool. So, take that formula as an attempt to predict the future. MAXUSERS determines the logical size of the catalog and that formula is MAXUSERS * 85 (and that's a real formula). Half of that goes to data blocks and half to index blocks. The physical size of the catalog (number of blocks in group 1) can initially be much smaller than that. That smaller space would again be divided equally to data and index blocks. It is much easier to add another minidisk to group 1 (when you hit physical limit) than to do regenerate file pool (when you hit logical limit). Therefore, allocate MAXUSERS generously, so that you don't have to do this again soon. In your case, you have 640 cylinders in group 1 (16 * 40 cyl), which equates to 115200 blocks. You may have over-allocated group 1, but to decrease that now would be a pain, so leave it. To be able to use all that space, the logical size of the catalog has to be at least that much, so MAXUSERS must be at least 1356, which is 115200 / 85, rounded up. I would suggest that you use at least 5000 if not 1 for MAXUSERS. Over-allocating MAXUSERS is not harmful, it just takes a bit of space in control minidisk. Size of control minidisk (or of the rest of it) determines the number of potentially addressable blocks in the file pool (maximum size to which the file pool can grow to). You can see that number if you do QUERY FILEPOOL OVERVIEW, but roughly, it is a bit less than one million addressable blocks for each control disk cylinder. There is no formula for this, because other things go to control disk as well (MAXDISKS has a hand in it too), but for example (roughly again), with a 50-cylinder control disk you will be left with at least 45 million potentially addressable blocks, which equates to around 75 3390 mod3's. That's the maximum size of disk space that you will ever be able to have in the file pool before having to regenerate it. While regenerating file pool, you will have to increase the size of the control disk. You have to do this to allow for the increase of MAXUSERS in order to maintain at least the same number of potentially addressable blocks. Increase it by 25-33% to be sure, but do *not* over-allocate control disk. Whenever the file pool server performs control data backup (and it does it automatically when log disks fill up more than 80%), the file pool will be unavailable to end users for the duration of the backup. You want that backup to be quick especially if your log disks are small and the backup is run often. Control data backup backs up *entire* control disk and *used* blocks in group 1 (catalog). Therefore, over-allocating group 1 is OK, but over-allocating control disk is not. Follow the procedure to regenerate a repository file pool to which you have been pointed to already and you'll be fine. One final word of advice though: before doing anything like this, make sure that you also have a reliable backup of the whole file pool (storage groups 2 and above) handy. Ivica Brodaric BNZ
Re: SFS question
Yup, that's correct, Steve.you need to set MAXUSERS to at least 1500. DJ On 03/11/2011 08:16 AM, Gentry, Stephen wrote: > So far, thanks to all who have replied. > I'm going over various numbers and need some clarification. In the CMS > Pool Planning guide, Estimate Max Pool Size, the formula is: maximum > enrolled users = 300 * (# system defined users / # system active users) > If I understand the definitions correctly #system defined users is > number of users in USER DIRECT file. For us that number is 750 (but to > CMA, I'm going round up to 1000), #system active users is the number of > users logged on. On an average we have about 200 users logged on. So, > plugging in the values to the formula above: > 1500= 300 * ( 1000 / 200 ) > So the MAXUSER statement should be 1500 ? > If so, I'm way low, currently 300. > Do I understand the formula and definitions correctly? > > Steve > > -Original Message- > From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On > Behalf Of Sue Farrell > Sent: Friday, March 11, 2011 8:56 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: SFS question > > Steve, > > You need to increase your MAXUSERS setting by doing a FILESERV > REGENERATE > > for the file pool. > > Although it's buried, the 51010 reason code is mentioned in Chapter 5 of > > > the CMS File Pool Planning, Administration, and Operation manual: > > What Happens When the Limit is Reached: Logical catalog space is > reserved > > during file pool generation. FILESERV GENERATE processing uses the > MAXUSERS value to estimate and set the maximum logical catalog space. > Whe > n > the server runs out of logical space, it displays a warning message on > it > s > console > and continues processing. Depending on their use of the file pool, users > > > may > receive error messages (DMS1146E) and error return codes (with reason > cod > es > 51010 or 51020). When the logical catalog space is exhausted, you need > to > > increase the MAXUSERS value for the file pool. Follow the instructions > in > > Chapter 11, "Regenerating a Repository File Pool," on page xxx. > > Thanks, > Sue > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: SFS question
So far, thanks to all who have replied. I'm going over various numbers and need some clarification. In the CMS Pool Planning guide, Estimate Max Pool Size, the formula is: maximum enrolled users = 300 * (# system defined users / # system active users) If I understand the definitions correctly #system defined users is number of users in USER DIRECT file. For us that number is 750 (but to CMA, I'm going round up to 1000), #system active users is the number of users logged on. On an average we have about 200 users logged on. So, plugging in the values to the formula above: 1500= 300 * ( 1000 / 200 ) So the MAXUSER statement should be 1500 ? If so, I'm way low, currently 300. Do I understand the formula and definitions correctly? Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Sue Farrell Sent: Friday, March 11, 2011 8:56 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS question Steve, You need to increase your MAXUSERS setting by doing a FILESERV REGENERATE for the file pool. Although it's buried, the 51010 reason code is mentioned in Chapter 5 of the CMS File Pool Planning, Administration, and Operation manual: What Happens When the Limit is Reached: Logical catalog space is reserved during file pool generation. FILESERV GENERATE processing uses the MAXUSERS value to estimate and set the maximum logical catalog space. Whe n the server runs out of logical space, it displays a warning message on it s console and continues processing. Depending on their use of the file pool, users may receive error messages (DMS1146E) and error return codes (with reason cod es 51010 or 51020). When the logical catalog space is exhausted, you need to increase the MAXUSERS value for the file pool. Follow the instructions in Chapter 11, "Regenerating a Repository File Pool," on page xxx. Thanks, Sue
Re: SFS question
Steve, You need to increase your MAXUSERS setting by doing a FILESERV REGENERATE for the file pool. Although it's buried, the 51010 reason code is mentioned in Chapter 5 of the CMS File Pool Planning, Administration, and Operation manual: What Happens When the Limit is Reached: Logical catalog space is reserved during file pool generation. FILESERV GENERATE processing uses the MAXUSERS value to estimate and set the maximum logical catalog space. Whe n the server runs out of logical space, it displays a warning message on it s console and continues processing. Depending on their use of the file pool, users may receive error messages (DMS1146E) and error return codes (with reason cod es 51010 or 51020). When the logical catalog space is exhausted, you need to increase the MAXUSERS value for the file pool. Follow the instructions in Chapter 11, “Regenerating a Repository File Pool,” on page xxx. Thanks, Sue
Re: SFS question
How large is the catalog? -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Dave Jones Sent: Thursday, March 10, 2011 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS question Hi, Steve. Yes, you need to expand your storage group 1 size by adding more DASD space DJ On 03/10/2011 03:33 PM, Gentry, Stephen wrote: > I'm getting the following error on a DMSCLOSE: > > 51010 - No space for data left in catalog space. > > I am writing a group of files, 733 of them, to an SFS pool > > Does the error message mean that I don't have enough room in storage > group 1? > > TIA > > Steve > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 == This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Re: SFS question
Do QUERY FILEPOOL CATALOG to see the amount of catalog data blocks and catalog index blocks used. Total number of catalog space blocks (data+index) is MAXUSERS*85. Maybe your MAXUSERS value is too small? Ivica Brodaric BNZ
Re: SFS question
Here is the results from the QUERY: q filepool storgrp vmsyse: VMSYSE File Pool Storage Groups Start-up Date 03/02/11 Query Date 03/10/11 Start-up Time 23:39:25 Query Time 16:57:49 STORAGE GROUP INFORMATION Storage4K Blocks 4K Blocks Group No.In-Use Free 1 17973 - 16% 96971 2 8712106 - 67%4278828 The total number of files is 733, occupying approx. 2022 4k blocks. So, I don't understand why I'm getting this error. I have defined storage group 1 with 40 cylinders (7184 - 4k blocks) across 16 3390 mod3's. To clarify, that's 40 cylinders on each mod3. I'm wondering if there isn't enough room on one of the mod3's and thus I get this message. Due to the nature of SFS, I assume it would spread the load across the 16 drives. Steve From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Kris Buelens Sent: Thursday, March 10, 2011 4:43 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS question Thta's what I'd conclude too. Try Q FILEPOOL STORGRP (or use SFSULIST, it shows the summary too) 2011/3/10 Gentry, Stephen I'm getting the following error on a DMSCLOSE: 51010 - No space for data left in catalog space. I am writing a group of files, 733 of them, to an SFS pool Does the error message mean that I don't have enough room in storage group 1? TIA Steve -- Kris Buelens, IBM Belgium, VM customer support
Re: SFS question
Yes. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Gentry, Stephen Sent: Thursday, March 10, 2011 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: SFS question I'm getting the following error on a DMSCLOSE: 51010 - No space for data left in catalog space. I am writing a group of files, 733 of them, to an SFS pool Does the error message mean that I don't have enough room in storage group 1? TIA Steve
Re: SFS question
Thta's what I'd conclude too. Try Q FILEPOOL STORGRP (or use SFSULIST, it shows the summary too) 2011/3/10 Gentry, Stephen > I’m getting the following error on a DMSCLOSE: > > 51010 - No space for data left in catalog space. > > I am writing a group of files, 733 of them, to an SFS pool > > Does the error message mean that I don’t have enough room in storage group > 1? > > TIA > > Steve > -- Kris Buelens, IBM Belgium, VM customer support
Re: SFS question
Hi, Steve. Yes, you need to expand your storage group 1 size by adding more DASD space DJ On 03/10/2011 03:33 PM, Gentry, Stephen wrote: > I’m getting the following error on a DMSCLOSE: > > 51010 - No space for data left in catalog space. > > I am writing a group of files, 733 of them, to an SFS pool > > Does the error message mean that I don’t have enough room in storage > group 1? > > TIA > > Steve > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
SFS question
I'm getting the following error on a DMSCLOSE: 51010 - No space for data left in catalog space. I am writing a group of files, 733 of them, to an SFS pool Does the error message mean that I don't have enough room in storage group 1? TIA Steve
Re: CMS SFS Question
I don't believe that I said DELETE USER RICHARD. I certainly did not intend to imply that, nor did I intend for someone to infer it. I should have stated it better. Regards, Richard Schuh > -Original Message- > From: The IBM z/VM Operating System > [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler > Sent: Tuesday, March 01, 2011 2:07 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CMS SFS Question > > That's NOT the scenario you gave in your original note! You > wrote about deleting Richard when you wrote: > > It is possible for one user to grant access to other users > >>>> who are not enrolled. DELETE USER does not clean up > these >>>> permissions. > > I don't see *any* indication that would trigger a DELETE USER > Les (using your scenario, which was reversed from mine, > further confusing the issue). > > Les > > Schuh, Richard wrote: > > It is permissions granted to users who are not enrolled > that is the issue. Here is the scenario: > > > > User Richard is enrolled > > User Les is not enrolled > > Richard grants Les some SFS authorities. > > DELETE USER LES is issued without enrolling LES (or no > DELETE USER is > > issued for LES) The authorities granted to LES by RICHARD > are left hanging and will be applied to any newly created LES > regardless of the identity of the owner. > > > > If LES is enrolled before the DELETE USER, those > authorities granted to LES by others are removed. By doing > the ENROLL for 0 blocks for any userid that is to be deleted, > no ghost authorities are given to new users. The userids are > unconditionally enrolled. If the user has already been > enrolled and owns a file space, the enroll will fail. Because > all I care about is that the user be enrolled, I ignore that failure. > > > > > > Regards, > > Richard Schuh > > > > > > > >> -Original Message- > >> From: The IBM z/VM Operating System > >> [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler > >> Sent: Tuesday, March 01, 2011 1:24 PM > >> To: IBMVM@LISTSERV.UARK.EDU > >> Subject: Re: CMS SFS Question > >> > >> I guess there's something implied there that I don't get. > >> Scenario, from your note: > >> > >> Your task is to delete LES, who is enrolled, from the SFS > system LES > >> has granted rights to RICHARD but RICHARD is not enrolled > >> > >> How does enrolling LES for 0 blocks do anything about the granted > >> rights that RICHARD has? > >> > >> Les > >> > >> Schuh, Richard wrote: > >>> I simply enroll any user to be deleted for 0 blocks. The > >> alternative is to scan the sfs directories and files > looking for such > >> users. It is much easier to attempt the enroll. If it fails, it is > >> because the user is already enrolled. > >>> Regards, > >>> Richard Schuh > >>> > >>> > >>> > >>>> -Original Message- > >>>> From: The IBM z/VM Operating System > >>>> [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler > >>>> Sent: Tuesday, March 01, 2011 12:22 PM > >>>> To: IBMVM@LISTSERV.UARK.EDU > >>>> Subject: Re: CMS SFS Question > >>>> > >>>> I'm curious: How do you find the user who is not enrolled, but > >>>> granted rights to the target user to be deleted? > >>>> > >>>> Les > >>>> > >>>> Schuh, Richard wrote: > >>>>> The Pipe is the easiest. > >>>>> > >>>>> PIPE < user list | spec /delete user/ 1 w1 nw | cms | > > >> delete log a > >>>>> Note, however, that if you have an SFS that has a lot of > >>>> files and permissions, each DELETE USER can take a long > >> time, so you > >>>> do not want to do this on an id that you might need soon > after you > >>>> enter the PIPE command. In our shop, an individual > DELETE USER can > >>>> take upwards of 10 minutes. > >>>>> Cleaning up SFS when a userid is deleted is important from > >>>> a security standpoint. If the same id should be given to a > >> different > >>>> person, it would automatically inherit permissions from > the prior > >>>> owner. You should be doing a DELETE USER every time that a > >> userid is > >&
Re: CMS SFS Question
That's NOT the scenario you gave in your original note! You wrote about deleting Richard when you wrote: It is possible for one user to grant access to other users >>>> who are not enrolled. DELETE USER does not clean up these >>>> permissions. I don't see *any* indication that would trigger a DELETE USER Les (using your scenario, which was reversed from mine, further confusing the issue). Les Schuh, Richard wrote: It is permissions granted to users who are not enrolled that is the issue. Here is the scenario: User Richard is enrolled User Les is not enrolled Richard grants Les some SFS authorities. DELETE USER LES is issued without enrolling LES (or no DELETE USER is issued for LES) The authorities granted to LES by RICHARD are left hanging and will be applied to any newly created LES regardless of the identity of the owner. If LES is enrolled before the DELETE USER, those authorities granted to LES by others are removed. By doing the ENROLL for 0 blocks for any userid that is to be deleted, no ghost authorities are given to new users. The userids are unconditionally enrolled. If the user has already been enrolled and owns a file space, the enroll will fail. Because all I care about is that the user be enrolled, I ignore that failure. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler Sent: Tuesday, March 01, 2011 1:24 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: CMS SFS Question I guess there's something implied there that I don't get. Scenario, from your note: Your task is to delete LES, who is enrolled, from the SFS system LES has granted rights to RICHARD but RICHARD is not enrolled How does enrolling LES for 0 blocks do anything about the granted rights that RICHARD has? Les Schuh, Richard wrote: I simply enroll any user to be deleted for 0 blocks. The alternative is to scan the sfs directories and files looking for such users. It is much easier to attempt the enroll. If it fails, it is because the user is already enrolled. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler Sent: Tuesday, March 01, 2011 12:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: CMS SFS Question I'm curious: How do you find the user who is not enrolled, but granted rights to the target user to be deleted? Les Schuh, Richard wrote: The Pipe is the easiest. PIPE < user list | spec /delete user/ 1 w1 nw | cms | > delete log a Note, however, that if you have an SFS that has a lot of files and permissions, each DELETE USER can take a long time, so you do not want to do this on an id that you might need soon after you enter the PIPE command. In our shop, an individual DELETE USER can take upwards of 10 minutes. Cleaning up SFS when a userid is deleted is important from a security standpoint. If the same id should be given to a different person, it would automatically inherit permissions from the prior owner. You should be doing a DELETE USER every time that a userid is deleted from the directory. It is possible for one user to grant access to other users who are not enrolled. DELETE USER does not clean up these permissions. To get rid of them, you have to first enroll the user in the pool even if it is for 0 blocks. To solve this in our automated process, each user to be deleted is enrolled for 0 blocks, ignoring the return code. We don't care if the user is already enrolled, the attempt does no harm. After the enroll, the deletion will clean out all permissions granted to or by the user being deleted. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Rick Troth Sent: Tuesday, March 01, 2011 10:54 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: CMS SFS Question Nahh ... even easier ... Pipes. I'm thinking two pipes. One to gather the Q ENROLL output then a second to actually perform the deletes. In between shove that Q ENROLL output into a file, manually edit for confirmation, then feed the selected content into DELETE USER. -- R; Rick Troth Velocity Software http://www.velocitysoftware.com/ On Tue, 1 Mar 2011, Rich Smrcina wrote: REXX? On 03/01/2011 12:35 PM, Wandschneider, Scott wrote: Is there a way to delete multiple users at once or create a "batch" job to delete multiple users that are enrolled in SFS? Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || Ë:847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly** Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprieta
Re: CMS SFS Question
It is permissions granted to users who are not enrolled that is the issue. Here is the scenario: User Richard is enrolled User Les is not enrolled Richard grants Les some SFS authorities. DELETE USER LES is issued without enrolling LES (or no DELETE USER is issued for LES) The authorities granted to LES by RICHARD are left hanging and will be applied to any newly created LES regardless of the identity of the owner. If LES is enrolled before the DELETE USER, those authorities granted to LES by others are removed. By doing the ENROLL for 0 blocks for any userid that is to be deleted, no ghost authorities are given to new users. The userids are unconditionally enrolled. If the user has already been enrolled and owns a file space, the enroll will fail. Because all I care about is that the user be enrolled, I ignore that failure. Regards, Richard Schuh > -Original Message- > From: The IBM z/VM Operating System > [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler > Sent: Tuesday, March 01, 2011 1:24 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CMS SFS Question > > I guess there's something implied there that I don't get. > Scenario, from your note: > > Your task is to delete LES, who is enrolled, from the SFS > system LES has granted rights to RICHARD but RICHARD is not enrolled > > How does enrolling LES for 0 blocks do anything about the > granted rights that RICHARD has? > > Les > > Schuh, Richard wrote: > > I simply enroll any user to be deleted for 0 blocks. The > alternative is to scan the sfs directories and files looking > for such users. It is much easier to attempt the enroll. If > it fails, it is because the user is already enrolled. > > > > Regards, > > Richard Schuh > > > > > > > >> -Original Message- > >> From: The IBM z/VM Operating System > >> [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler > >> Sent: Tuesday, March 01, 2011 12:22 PM > >> To: IBMVM@LISTSERV.UARK.EDU > >> Subject: Re: CMS SFS Question > >> > >> I'm curious: How do you find the user who is not enrolled, but > >> granted rights to the target user to be deleted? > >> > >> Les > >> > >> Schuh, Richard wrote: > >>> The Pipe is the easiest. > >>> > >>> PIPE < user list | spec /delete user/ 1 w1 nw | cms | > > delete log a > >>> > >>> Note, however, that if you have an SFS that has a lot of > >> files and permissions, each DELETE USER can take a long > time, so you > >> do not want to do this on an id that you might need soon after you > >> enter the PIPE command. In our shop, an individual DELETE USER can > >> take upwards of 10 minutes. > >>> Cleaning up SFS when a userid is deleted is important from > >> a security standpoint. If the same id should be given to a > different > >> person, it would automatically inherit permissions from the prior > >> owner. You should be doing a DELETE USER every time that a > userid is > >> deleted from the directory. > >>> It is possible for one user to grant access to other users > >> who are not enrolled. DELETE USER does not clean up these > >> permissions. To get rid of them, you have to first enroll > the user in > >> the pool even if it is for 0 blocks. To solve this in our > automated > >> process, each user to be deleted is enrolled for 0 blocks, > ignoring > >> the return code. We don't care if the user is already > enrolled, the > >> attempt does no harm. After the enroll, the deletion will > clean out > >> all permissions granted to or by the user being deleted. > >>> > >>> Regards, > >>> Richard Schuh > >>> > >>> > >>> > >>>> -Original Message- > >>>> From: The IBM z/VM Operating System > >>>> [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Rick Troth > >>>> Sent: Tuesday, March 01, 2011 10:54 AM > >>>> To: IBMVM@LISTSERV.UARK.EDU > >>>> Subject: Re: CMS SFS Question > >>>> > >>>> Nahh ... even easier ... Pipes. > >>>> I'm thinking two pipes. One to gather the Q ENROLL > output then a > >>>> second to actually perform the deletes. In between shove that Q > >>>> ENROLL output into a file, manually edit for confirmation, > >> then feed > >>>> the selected content into DELETE USER. > >>>> > >>>>
Re: CMS SFS Question
I guess there's something implied there that I don't get. Scenario, from your note: Your task is to delete LES, who is enrolled, from the SFS system LES has granted rights to RICHARD but RICHARD is not enrolled How does enrolling LES for 0 blocks do anything about the granted rights that RICHARD has? Les Schuh, Richard wrote: I simply enroll any user to be deleted for 0 blocks. The alternative is to scan the sfs directories and files looking for such users. It is much easier to attempt the enroll. If it fails, it is because the user is already enrolled. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler Sent: Tuesday, March 01, 2011 12:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: CMS SFS Question I'm curious: How do you find the user who is not enrolled, but granted rights to the target user to be deleted? Les Schuh, Richard wrote: The Pipe is the easiest. PIPE < user list | spec /delete user/ 1 w1 nw | cms | > delete log a Note, however, that if you have an SFS that has a lot of files and permissions, each DELETE USER can take a long time, so you do not want to do this on an id that you might need soon after you enter the PIPE command. In our shop, an individual DELETE USER can take upwards of 10 minutes. Cleaning up SFS when a userid is deleted is important from a security standpoint. If the same id should be given to a different person, it would automatically inherit permissions from the prior owner. You should be doing a DELETE USER every time that a userid is deleted from the directory. It is possible for one user to grant access to other users who are not enrolled. DELETE USER does not clean up these permissions. To get rid of them, you have to first enroll the user in the pool even if it is for 0 blocks. To solve this in our automated process, each user to be deleted is enrolled for 0 blocks, ignoring the return code. We don't care if the user is already enrolled, the attempt does no harm. After the enroll, the deletion will clean out all permissions granted to or by the user being deleted. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Rick Troth Sent: Tuesday, March 01, 2011 10:54 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: CMS SFS Question Nahh ... even easier ... Pipes. I'm thinking two pipes. One to gather the Q ENROLL output then a second to actually perform the deletes. In between shove that Q ENROLL output into a file, manually edit for confirmation, then feed the selected content into DELETE USER. -- R; Rick Troth Velocity Software http://www.velocitysoftware.com/ On Tue, 1 Mar 2011, Rich Smrcina wrote: REXX? On 03/01/2011 12:35 PM, Wandschneider, Scott wrote: Is there a way to delete multiple users at once or create a "batch" job to delete multiple users that are enrolled in SFS? Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || Ë:847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly** Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or "Protected Health Information," within the meaning of the regulations under the Health Insurance Portability& Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. -- Rich Smrcina Velocity Software, Inc. http://www.velocitysoftware.com Catch the WAVV! http://www.wavv.org WAVV 2011 - April 15-19, 2011 Colorado Springs, CO
Re: CMS SFS Question
I simply enroll any user to be deleted for 0 blocks. The alternative is to scan the sfs directories and files looking for such users. It is much easier to attempt the enroll. If it fails, it is because the user is already enrolled. Regards, Richard Schuh > -Original Message- > From: The IBM z/VM Operating System > [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler > Sent: Tuesday, March 01, 2011 12:22 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CMS SFS Question > > I'm curious: How do you find the user who is not enrolled, > but granted rights to the target user to be deleted? > > Les > > Schuh, Richard wrote: > > The Pipe is the easiest. > > > > PIPE < user list | spec /delete user/ 1 w1 nw | cms | > delete log a > > > > Note, however, that if you have an SFS that has a lot of > files and permissions, each DELETE USER can take a long time, > so you do not want to do this on an id that you might need > soon after you enter the PIPE command. In our shop, an > individual DELETE USER can take upwards of 10 minutes. > > > > Cleaning up SFS when a userid is deleted is important from > a security standpoint. If the same id should be given to a > different person, it would automatically inherit permissions > from the prior owner. You should be doing a DELETE USER every > time that a userid is deleted from the directory. > > > > It is possible for one user to grant access to other users > who are not enrolled. DELETE USER does not clean up these > permissions. To get rid of them, you have to first enroll the > user in the pool even if it is for 0 blocks. To solve this in > our automated process, each user to be deleted is enrolled > for 0 blocks, ignoring the return code. We don't care if the > user is already enrolled, the attempt does no harm. After the > enroll, the deletion will clean out all permissions granted > to or by the user being deleted. > > > > > > Regards, > > Richard Schuh > > > > > > > >> -Original Message----- > >> From: The IBM z/VM Operating System > >> [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Rick Troth > >> Sent: Tuesday, March 01, 2011 10:54 AM > >> To: IBMVM@LISTSERV.UARK.EDU > >> Subject: Re: CMS SFS Question > >> > >> Nahh ... even easier ... Pipes. > >> I'm thinking two pipes. One to gather the Q ENROLL output then a > >> second to actually perform the deletes. In between shove that Q > >> ENROLL output into a file, manually edit for confirmation, > then feed > >> the selected content into DELETE USER. > >> > >> -- R; > >> Rick Troth > >> Velocity Software > >> http://www.velocitysoftware.com/ > >> > >> > >> > >> On Tue, 1 Mar 2011, Rich Smrcina wrote: > >> > >>> REXX? > >>> > >>> On 03/01/2011 12:35 PM, Wandschneider, Scott wrote: > >>>> Is there a way to delete multiple users at once or create > >> a "batch" job to delete multiple users that are enrolled in SFS? > >>>> Thank you, > >>>> Scott R Wandschneider > >>>> Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 > >>>> Miracle Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || > >>>> Ë:847.849.7223 || : > >> scott.wandschnei...@infocrossing.com **Think > >>>> Green - Please print responsibly** > >>>> > >>>> > >>>> > >>>> Confidentiality Note: This e-mail, including any > >> attachment to it, may contain material that is confidential, > >> proprietary, privileged and/or "Protected Health > Information," within > >> the meaning of the regulations under the Health Insurance > >> Portability& Accountability Act as amended. > >> If it is not clear that you are the intended recipient, you are > >> hereby notified that you have received this transmittal in > error, and > >> any review, dissemination, distribution or copying of this e-mail, > >> including any attachment to it, is strictly prohibited. If > you have > >> received this e-mail in error, please immediately return it to the > >> sender and delete it from your system. Thank you. > >>> > >>> -- > >>> Rich Smrcina > >>> Velocity Software, Inc. > >>> http://www.velocitysoftware.com > >>> > >>> Catch the WAVV! http://www.wavv.org > >>> WAVV 2011 - April 15-19, 2011 Colorado Springs, CO > >>> > >>> >
Re: CMS SFS Question
I'm curious: How do you find the user who is not enrolled, but granted rights to the target user to be deleted? Les Schuh, Richard wrote: The Pipe is the easiest. PIPE < user list | spec /delete user/ 1 w1 nw | cms | > delete log a Note, however, that if you have an SFS that has a lot of files and permissions, each DELETE USER can take a long time, so you do not want to do this on an id that you might need soon after you enter the PIPE command. In our shop, an individual DELETE USER can take upwards of 10 minutes. Cleaning up SFS when a userid is deleted is important from a security standpoint. If the same id should be given to a different person, it would automatically inherit permissions from the prior owner. You should be doing a DELETE USER every time that a userid is deleted from the directory. It is possible for one user to grant access to other users who are not enrolled. DELETE USER does not clean up these permissions. To get rid of them, you have to first enroll the user in the pool even if it is for 0 blocks. To solve this in our automated process, each user to be deleted is enrolled for 0 blocks, ignoring the return code. We don't care if the user is already enrolled, the attempt does no harm. After the enroll, the deletion will clean out all permissions granted to or by the user being deleted. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Rick Troth Sent: Tuesday, March 01, 2011 10:54 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: CMS SFS Question Nahh ... even easier ... Pipes. I'm thinking two pipes. One to gather the Q ENROLL output then a second to actually perform the deletes. In between shove that Q ENROLL output into a file, manually edit for confirmation, then feed the selected content into DELETE USER. -- R; Rick Troth Velocity Software http://www.velocitysoftware.com/ On Tue, 1 Mar 2011, Rich Smrcina wrote: REXX? On 03/01/2011 12:35 PM, Wandschneider, Scott wrote: Is there a way to delete multiple users at once or create a "batch" job to delete multiple users that are enrolled in SFS? Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || Ë:847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly** Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or "Protected Health Information," within the meaning of the regulations under the Health Insurance Portability& Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. -- Rich Smrcina Velocity Software, Inc. http://www.velocitysoftware.com Catch the WAVV! http://www.wavv.org WAVV 2011 - April 15-19, 2011 Colorado Springs, CO
Re: CMS SFS Question
The Pipe is the easiest. PIPE < user list | spec /delete user/ 1 w1 nw | cms | > delete log a Note, however, that if you have an SFS that has a lot of files and permissions, each DELETE USER can take a long time, so you do not want to do this on an id that you might need soon after you enter the PIPE command. In our shop, an individual DELETE USER can take upwards of 10 minutes. Cleaning up SFS when a userid is deleted is important from a security standpoint. If the same id should be given to a different person, it would automatically inherit permissions from the prior owner. You should be doing a DELETE USER every time that a userid is deleted from the directory. It is possible for one user to grant access to other users who are not enrolled. DELETE USER does not clean up these permissions. To get rid of them, you have to first enroll the user in the pool even if it is for 0 blocks. To solve this in our automated process, each user to be deleted is enrolled for 0 blocks, ignoring the return code. We don't care if the user is already enrolled, the attempt does no harm. After the enroll, the deletion will clean out all permissions granted to or by the user being deleted. Regards, Richard Schuh > -Original Message- > From: The IBM z/VM Operating System > [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Rick Troth > Sent: Tuesday, March 01, 2011 10:54 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CMS SFS Question > > Nahh ... even easier ... Pipes. > I'm thinking two pipes. One to gather the Q ENROLL output > then a second to actually perform the deletes. In between > shove that Q ENROLL output into a file, manually edit for > confirmation, then feed the selected content into DELETE USER. > > -- R; > Rick Troth > Velocity Software > http://www.velocitysoftware.com/ > > > > On Tue, 1 Mar 2011, Rich Smrcina wrote: > > > REXX? > > > > On 03/01/2011 12:35 PM, Wandschneider, Scott wrote: > > > Is there a way to delete multiple users at once or create > a "batch" job to delete multiple users that are enrolled in SFS? > > > > > > Thank you, > > > Scott R Wandschneider > > > Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 > > > Miracle Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || > > > Ë:847.849.7223 || : > scott.wandschnei...@infocrossing.com **Think > > > Green - Please print responsibly** > > > > > > > > > > > > Confidentiality Note: This e-mail, including any > attachment to it, may contain material that is confidential, > proprietary, privileged and/or "Protected Health > Information," within the meaning of the regulations under the > Health Insurance Portability& Accountability Act as amended. > If it is not clear that you are the intended recipient, you > are hereby notified that you have received this transmittal > in error, and any review, dissemination, distribution or > copying of this e-mail, including any attachment to it, is > strictly prohibited. If you have received this e-mail in > error, please immediately return it to the sender and delete > it from your system. Thank you. > > > > > > -- > > Rich Smrcina > > Velocity Software, Inc. > > http://www.velocitysoftware.com > > > > Catch the WAVV! http://www.wavv.org > > WAVV 2011 - April 15-19, 2011 Colorado Springs, CO > > > > >
Re: CMS SFS Question
Nahh ... even easier ... Pipes. I'm thinking two pipes. One to gather the Q ENROLL output then a second to actually perform the deletes. In between shove that Q ENROLL output into a file, manually edit for confirmation, then feed the selected content into DELETE USER. -- R; Rick Troth Velocity Software http://www.velocitysoftware.com/ On Tue, 1 Mar 2011, Rich Smrcina wrote: > REXX? > > On 03/01/2011 12:35 PM, Wandschneider, Scott wrote: > > Is there a way to delete multiple users at once or create a "batch" job to > > delete multiple users that are enrolled in SFS? > > > > Thank you, > > Scott R Wandschneider > > Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills > > Drive, Omaha, NE, 68154-4457|| : 402.963.8905 || :847.849.7223 || : > > scott.wandschnei...@infocrossing.com **Think Green - Please print > > responsibly** > > > > > > > > Confidentiality Note: This e-mail, including any attachment to it, may > > contain material that is confidential, proprietary, privileged and/or > > "Protected Health Information," within the meaning of the regulations under > > the Health Insurance Portability& Accountability Act as amended. If it is > > not clear that you are the intended recipient, you are hereby notified that > > you have received this transmittal in error, and any review, dissemination, > > distribution or copying of this e-mail, including any attachment to it, is > > strictly prohibited. If you have received this e-mail in error, please > > immediately return it to the sender and delete it from your system. Thank > > you. > > > -- > Rich Smrcina > Velocity Software, Inc. > http://www.velocitysoftware.com > > Catch the WAVV! http://www.wavv.org > WAVV 2011 - April 15-19, 2011 Colorado Springs, CO > >
Re: CMS SFS Question
REXX? On 03/01/2011 12:35 PM, Wandschneider, Scott wrote: Is there a way to delete multiple users at once or create a "batch" job to delete multiple users that are enrolled in SFS? Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| : 402.963.8905 || :847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly** Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or "Protected Health Information," within the meaning of the regulations under the Health Insurance Portability& Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. -- Rich Smrcina Velocity Software, Inc. http://www.velocitysoftware.com Catch the WAVV! http://www.wavv.org WAVV 2011 - April 15-19, 2011 Colorado Springs, CO
CMS SFS Question
Is there a way to delete multiple users at once or create a "batch" job to delete multiple users that are enrolled in SFS? Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| : 402.963.8905 || :847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly**
Re: SFS question
Not really true Dave: the SFSULIST panel is complete when not being SFS admin. Only the Catalog stats are not available to non-admins (upper right corner). But, yes, using PF11 to start DIRLIST of the user pointed too will only list the subdirs one is authorized to. 2011/1/4 Dave Jones > Steve, note that your user id must be enrolled in the file pool as an > administrator for SFSULIST to return all of the menaingful results. > > DJ > > On 01/04/2011 08:25 AM, Gentry, Stephen wrote: > > Thanks Dave. I was sure there was something out there that would > > provide this info. I had SFSULIST already downloaded just didn't know > > that's what it would/could do. > > Steve > > > > -Original Message- > > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On > > Behalf Of Dave Jones > > Sent: Tuesday, January 04, 2011 9:20 AM > > To: IBMVM@LISTSERV.UARK.EDU > > Subject: Re: SFS question > > > > Steve, grab Kris Buelen's SFSULIST tool from the VM download page; it > > does exactly what you are looking for. > > > > Have a good one. > > > > On 01/04/2011 08:13 AM, Gentry, Stephen wrote: > >> How can I tell what users and/or what files are in a storage group? > > I'd > >> prefer to know users but can trace it back if I know what files. > >> > >> Thanks, > >> > >> Steve > >> > >> > > > > -- > Dave Jones > V/Soft Software > www.vsoft-software.com > Houston, TX > 281.578.7544 > -- Kris Buelens, IBM Belgium, VM customer support
Re: SFS question
Steve, note that your user id must be enrolled in the file pool as an administrator for SFSULIST to return all of the menaingful results. DJ On 01/04/2011 08:25 AM, Gentry, Stephen wrote: > Thanks Dave. I was sure there was something out there that would > provide this info. I had SFSULIST already downloaded just didn't know > that's what it would/could do. > Steve > > -Original Message- > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On > Behalf Of Dave Jones > Sent: Tuesday, January 04, 2011 9:20 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: SFS question > > Steve, grab Kris Buelen's SFSULIST tool from the VM download page; it > does exactly what you are looking for. > > Have a good one. > > On 01/04/2011 08:13 AM, Gentry, Stephen wrote: >> How can I tell what users and/or what files are in a storage group? > I'd >> prefer to know users but can trace it back if I know what files. >> >> Thanks, >> >> Steve >> >> > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: SFS question
SFSULIST is an interactive tool. If you need this information in a REXX exec: Q LIMITS is your friend. If you also need to know the files: after Q LIMITS, you use LISTDIR; ACCESS and LISTFILE... 2011/1/4 Gentry, Stephen > Thanks Dave. I was sure there was something out there that would > provide this info. I had SFSULIST already downloaded just didn't know > that's what it would/could do. > Steve > > -Original Message- > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On > Behalf Of Dave Jones > Sent: Tuesday, January 04, 2011 9:20 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: SFS question > > Steve, grab Kris Buelen's SFSULIST tool from the VM download page; it > does exactly what you are looking for. > > Have a good one. > > On 01/04/2011 08:13 AM, Gentry, Stephen wrote: > > How can I tell what users and/or what files are in a storage group? > I'd > > prefer to know users but can trace it back if I know what files. > > > > Thanks, > > > > Steve > > > > > > -- > Dave Jones > V/Soft Software > www.vsoft-software.com > Houston, TX > 281.578.7544 > -- Kris Buelens, IBM Belgium, VM customer support
Re: SFS question
Thanks Dave. I was sure there was something out there that would provide this info. I had SFSULIST already downloaded just didn't know that's what it would/could do. Steve -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dave Jones Sent: Tuesday, January 04, 2011 9:20 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS question Steve, grab Kris Buelen's SFSULIST tool from the VM download page; it does exactly what you are looking for. Have a good one. On 01/04/2011 08:13 AM, Gentry, Stephen wrote: > How can I tell what users and/or what files are in a storage group? I'd > prefer to know users but can trace it back if I know what files. > > Thanks, > > Steve > > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: SFS question
Steve, grab Kris Buelen's SFSULIST tool from the VM download page; it does exactly what you are looking for. Have a good one. On 01/04/2011 08:13 AM, Gentry, Stephen wrote: > How can I tell what users and/or what files are in a storage group? I'd > prefer to know users but can trace it back if I know what files. > > Thanks, > > Steve > > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
SFS question
How can I tell what users and/or what files are in a storage group? I'd prefer to know users but can trace it back if I know what files. Thanks, Steve
Re: SFS question (was: Q LIMITS question)
Apparently you are not running SAFESFS? If not, this becomes labor intensive. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Gentry, Stephen Sent: Wednesday, March 04, 2009 10:32 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS question (was: Q LIMITS question) Bruce, thanks for the reply. But not exactly what I wanted. I probably didn't ask the question correctly. I have a specific userid, for example MAINT, what SFS directories does MAINT have read and/or write access to? When I run Query AUTHority VMSYSU:xx. (or VMSYSU:x.y) I get a list of users who can read and/or write to the specified subdirectory. I want to specify a userid and get a list of SFS subdirectories that user has access to. We heavily use SFS in our production batch processing using different batch worker machines (VM:Batch) Some worker machines have access to common SFS subdirectories. I can write something using the brute force method but I was hoping for something a little more elegant. Steve -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Bruce Hayden Sent: Wednesday, March 04, 2009 10:00 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS question (was: Q LIMITS question) I've had ALLDIRS XEDIT around for quite awhile. You start DIRLIST against your own space in the filepool and then enter ALLDIRS on the command line. /* ALLDIRS XEDIT */ 'command top' 'command next' 'extract /curline' parse var curline.3 10 filepool ':' 'command bot' address command 'PIPE command QUERY LIMITS ALL' filepool':', '| drop 1', '| pick 52.2 /== " 0"', /* Ignore unused directories */ '| spec "LISTDIR' filepool':" 1 w1 next ". (XEDIT" next', '| command' 'SDIR' Exit On Wed, Mar 4, 2009 at 8:17 AM, Gentry, Stephen wrote: > Is there a command of some kind or has anyone written an EXEC (or PIPE, > etc.) that will provide a list of SFS directories that a user has access to? > > > > Steve -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY
Re: SFS question (was: Q LIMITS question)
Bruce, thanks for the reply. But not exactly what I wanted. I probably didn't ask the question correctly. I have a specific userid, for example MAINT, what SFS directories does MAINT have read and/or write access to? When I run Query AUTHority VMSYSU:xx. (or VMSYSU:x.y) I get a list of users who can read and/or write to the specified subdirectory. I want to specify a userid and get a list of SFS subdirectories that user has access to. We heavily use SFS in our production batch processing using different batch worker machines (VM:Batch) Some worker machines have access to common SFS subdirectories. I can write something using the brute force method but I was hoping for something a little more elegant. Steve -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Bruce Hayden Sent: Wednesday, March 04, 2009 10:00 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS question (was: Q LIMITS question) I've had ALLDIRS XEDIT around for quite awhile. You start DIRLIST against your own space in the filepool and then enter ALLDIRS on the command line. /* ALLDIRS XEDIT */ 'command top' 'command next' 'extract /curline' parse var curline.3 10 filepool ':' 'command bot' address command 'PIPE command QUERY LIMITS ALL' filepool':', '| drop 1', '| pick 52.2 /== " 0"', /* Ignore unused directories */ '| spec "LISTDIR' filepool':" 1 w1 next ". (XEDIT" next', '| command' 'SDIR' Exit On Wed, Mar 4, 2009 at 8:17 AM, Gentry, Stephen wrote: > Is there a command of some kind or has anyone written an EXEC (or PIPE, > etc.) that will provide a list of SFS directories that a user has access to? > > > > Steve -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY
Re: SFS question (was: Q LIMITS question)
I've had ALLDIRS XEDIT around for quite awhile. You start DIRLIST against your own space in the filepool and then enter ALLDIRS on the command line. /* ALLDIRS XEDIT */ 'command top' 'command next' 'extract /curline' parse var curline.3 10 filepool ':' 'command bot' address command 'PIPE command QUERY LIMITS ALL' filepool':', '| drop 1', '| pick 52.2 /== " 0"', /* Ignore unused directories */ '| spec "LISTDIR' filepool':" 1 w1 next ". (XEDIT" next', '| command' 'SDIR' Exit On Wed, Mar 4, 2009 at 8:17 AM, Gentry, Stephen wrote: > Is there a command of some kind or has anyone written an EXEC (or PIPE, > etc.) that will provide a list of SFS directories that a user has access to? > > > > Steve -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY
SFS question (was: Q LIMITS question)
Is there a command of some kind or has anyone written an EXEC (or PIPE, etc.) that will provide a list of SFS directories that a user has access to? Steve From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: Tuesday, March 03, 2009 1:37 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Q LIMITS question Have a look at my SFSULIST package. Basically it displays a combination of Q LIMITS, Q ENROLL AMDIN, Q FILEPOOL CONNECT and Q FILEPOOL STORGRP 2009/3/3 Gentry, Stephen Don't' put the period '.' after MAINT. I just tried it and it worked for me. Steve -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Shimon Lebowitz Sent: Tuesday, March 03, 2009 11:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Q LIMITS question Hi, I am a bit confused by a Q LIMITS situation. 1) I (XMSL) am an admin: q enroll admin vmsys NUMBER OF ADMINISTRATORS =18 MAINT XMSL RMSMASTR DGTSRV01 DGTSRV02 DGTSRV03 READY; T=0.01/0.01 19:37:54 2) I can query limits of ALL the users: q limits all vmsys USERIDSTORAGE GROUP 4K BLOCK LIMIT 4K BLOCKS COMMITTED THRESHOLD DFSMS 2450090-02% 90% MAINT 27000 3030-43% 90% READY; T=0.01/0.01 19:39:10 3) BUT... I canot query an individual user: q limits for maint. vmsys USERIDSTORAGE GROUP 4K BLOCK LIMIT 4K BLOCKS COMMITTED THRESHOLD MAINT.- - - - READY; T=0.01/0.01 19:40:13 Why not?? Thanks for any suggestions, Shimon -- Shimon Lebowitzmailto:shim...@iname.com VM System Programmer . Israel Police National HQ. Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308 -- Kris Buelens, IBM Belgium, VM customer support
Re: SFS Question
Another word of caution though: don't use COPYFILE to move, use DDR of DFSMS COPY. When using COPYFILE, the new minidisk will no longer be RESERVED, and SFS will refuse to work. 2007/11/19, Kris Buelens <[EMAIL PROTECTED]>: > > Minidisks can be moved any way you like: they must remain of the same > size. > > Note however that SFS takes into account on which physical volume its > minidisks are located, and it will only launch 1 IO per physical volume. > So, spreading over multiple volumes can improve IO concurrency. > > 2007/11/19, Schuh, Richard <[EMAIL PROTECTED]>: > > > > If I take a file pool server down and move some of its SG2 disks to > > other locations, both volume serial and location on the disk, will it cause > > problems? We have a small file pool that has some minidisks on physical > > disks > > that are going away. > > > > Regards, > > Richard Schuh > > > > > > -- Kris Buelens, IBM Belgium, VM customer support
Re: SFS Question
Minidisks can be moved any way you like: they must remain of the same size. Note however that SFS takes into account on which physical volume its minidisks are located, and it will only launch 1 IO per physical volume. So, spreading over multiple volumes can improve IO concurrency. 2007/11/19, Schuh, Richard <[EMAIL PROTECTED]>: > > If I take a file pool server down and move some of its SG2 disks to other > locations, both volume serial and location on the disk, will it cause > problems? We have a small file pool that has some minidisks on physical disks > that are going away. > > Regards, > Richard Schuh > > -- Kris Buelens, IBM Belgium, VM customer support
SFS Question
If I take a file pool server down and move some of its SG2 disks to other locations, both volume serial and location on the disk, will it cause problems? We have a small file pool that has some minidisks on physical disks that are going away. Regards, Richard Schuh
Re: SFS Question?
Here the two examples we keep in our "model" file. You can use both solutions, but, I'd say getting a new workunit seems better than commit the one that is open (who says you can commit something that another program opened?) TITLE:How to handle Workunit problems with SFS files] MODEL: /* PIPE STATE fn ft dirid | ... leaves workunit open if the file MODEL: | is found. This then results in: MODEL: |DMSQRQ1157E Work unit already active when atomic request... MODEL: | Solution: commit the workunit. Example MODEL: | 'PIPE LITERAL T T .|STATE ISODATE|CONS' MODEL: | call csl 'DMSCOMM RETC REAS'; say retc reas MODEL: | 'CMDCALL QUERY LIMITS *' /* Would fail without DMSCOMM*/ MODEL: */ MODEL: /* Similar, when a file is open and a workunit is active, some MODEL: | cmds give: DMSQRQ1157E Work unit already active when atomic.. MODEL: | Solution: get a new workunit. Example MODEL: | call csl 'DMSGETWU RETC REAS WID1' /* Get a workunit */ MODEL: | call csl 'DMSPUSWU RETC REAS WID1' /* Start using it */ MODEL: | 'CMDCALL QUERY LIMITS *' MODEL: | call csl 'DMSPOPWU RETC REAS' /* Use prev Wunit */ MODEL: | call csl 'DMSRETWU RETC REAS WID1' /* Delete new Wunit */ MODEL: */ Kris, IBM Belgium, VM customer support "Schuh, Richard" <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System 2006-06-29 21:25 Please respond to The IBM z/VM Operating System To IBMVM@LISTSERV.UARK.EDU cc Subject SFS Question? I have a service machine that is an administrator for one of our file pools. I am trying to get it to clean up the file pool when a userid is deleted from the system. My method is to first, enroll the userid for 0 blocks, then issue a delete user command. I can log on to this machine and enter the commands from the CMS command line and everything works as expected. When I try to do it from the driver EXEC for the machine, I am greeted with: enroll user JDOE sfsa (blocks 0 DMSJEN1157E Work unit already active when atomic request is issued for work unit 1 The delete user fails the same way (different message number, same information). How can I determine what is causing the work unit to be active when I try this? Alternatively, how can I insure that no work unit will be active? Regards, Richard Schuh
Re: SFS Question?
Works great. I made a REXX filter out of by taking out the procedure and end and put a 'short' following. Then I simply prefaced the input stream. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Aria Bamdad Sent: Thursday, June 29, 2006 12:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS Question? Richard, Some SFS commands are 'atomic requests'. There is more about this in the CMS Application Dev. Guide. Your EXEC (pipes) creates a default work unit that stays active during the execution of the exec. In order to call the SFS commands you have, you must first close that work unit, then call the command. Below is a sample Rexx procedure you can call to close the default work unit. Then issue the command. Hope this helps. Aria. RelWorkUnit: Procedure CSLRC = 0 CSLRESC = 0 WU = 0 CALL CSL 'DMSRETWU CSLRC CSLRESC WU' If (CSLRC ^= 0) | (CSLRESC ^= 0) then do Say 'Error calling DMSRELWU, RC='CSLRC 'ReasonCode='CSLRESC Say 'Error releasing default workunit.' End Return On Thu, 29 Jun 2006 12:25:00 -0700 Schuh, Richard said: >I have a service machine that is an administrator for one of our file = >pools. I am trying to get it to clean up the file pool when a userid is = >deleted from the system. My method is to first, enroll the userid for 0 = >blocks, then issue a delete user command. I can log on to this machine = >and enter the commands from the CMS command line and everything works as = >expected. When I try to do it from the driver EXEC for the machine, I am = >greeted with:=20 > >enroll user JDOE sfsa (blocks 0 = > =20 >DMSJEN1157E Work unit already active when atomic request is issued for = >work unit 1 > >The delete user fails the same way (different message number, same = >information).=20 > >How can I determine what is causing the work unit to be active when I = >try this? Alternatively, how can I insure that no work unit will be = >active?=20 > >Regards, >Richard Schuh >
Re: SFS Question?
Thanks, I will give it a try. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Aria Bamdad Sent: Thursday, June 29, 2006 12:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject:Re: SFS Question? Richard, Some SFS commands are 'atomic requests'. There is more about this in the CMS Application Dev. Guide. Your EXEC (pipes) creates a default work unit that stays active during the execution of the exec. In order to call the SFS commands you have, you must first close that work unit, then call the command. Below is a sample Rexx procedure you can call to close the default work unit. Then issue the command. Hope this helps. Aria. RelWorkUnit: Procedure CSLRC = 0 CSLRESC = 0 WU = 0 CALL CSL 'DMSRETWU CSLRC CSLRESC WU' If (CSLRC ^= 0) | (CSLRESC ^= 0) then do Say 'Error calling DMSRELWU, RC='CSLRC 'ReasonCode='CSLRESC Say 'Error releasing default workunit.' End Return On Thu, 29 Jun 2006 12:25:00 -0700 Schuh, Richard said: >I have a service machine that is an administrator for one of our file = >pools. I am trying to get it to clean up the file pool when a userid is = >deleted from the system. My method is to first, enroll the userid for 0 = >blocks, then issue a delete user command. I can log on to this machine = >and enter the commands from the CMS command line and everything works as = >expected. When I try to do it from the driver EXEC for the machine, I am = >greeted with:=20 > >enroll user JDOE sfsa (blocks 0 = > =20 >DMSJEN1157E Work unit already active when atomic request is issued for = >work unit 1 > >The delete user fails the same way (different message number, same = >information).=20 > >How can I determine what is causing the work unit to be active when I = >try this? Alternatively, how can I insure that no work unit will be = >active?=20 > >Regards, >Richard Schuh >
Re: SFS Question?
Richard, Some SFS commands are 'atomic requests'. There is more about this in the CMS Application Dev. Guide. Your EXEC (pipes) creates a default work unit that stays active during the execution of the exec. In order to call the SFS commands you have, you must first close that work unit, then call the command. Below is a sample Rexx procedure you can call to close the default work unit. Then issue the command. Hope this helps. Aria. RelWorkUnit: Procedure CSLRC = 0 CSLRESC = 0 WU = 0 CALL CSL 'DMSRETWU CSLRC CSLRESC WU' If (CSLRC ^= 0) | (CSLRESC ^= 0) then do Say 'Error calling DMSRELWU, RC='CSLRC 'ReasonCode='CSLRESC Say 'Error releasing default workunit.' End Return On Thu, 29 Jun 2006 12:25:00 -0700 Schuh, Richard said: >I have a service machine that is an administrator for one of our file = >pools. I am trying to get it to clean up the file pool when a userid is = >deleted from the system. My method is to first, enroll the userid for 0 = >blocks, then issue a delete user command. I can log on to this machine = >and enter the commands from the CMS command line and everything works as = >expected. When I try to do it from the driver EXEC for the machine, I am = >greeted with:=20 > >enroll user JDOE sfsa (blocks 0 = > =20 >DMSJEN1157E Work unit already active when atomic request is issued for = >work unit 1 > >The delete user fails the same way (different message number, same = >information).=20 > >How can I determine what is causing the work unit to be active when I = >try this? Alternatively, how can I insure that no work unit will be = >active?=20 > >Regards, >Richard Schuh >
SFS Question?
I have a service machine that is an administrator for one of our file pools. I am trying to get it to clean up the file pool when a userid is deleted from the system. My method is to first, enroll the userid for 0 blocks, then issue a delete user command. I can log on to this machine and enter the commands from the CMS command line and everything works as expected. When I try to do it from the driver EXEC for the machine, I am greeted with: enroll user JDOE sfsa (blocks 0 DMSJEN1157E Work unit already active when atomic request is issued for work unit 1 The delete user fails the same way (different message number, same information). How can I determine what is causing the work unit to be active when I try this? Alternatively, how can I insure that no work unit will be active? Regards, Richard Schuh
