Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
W dniu 2015-10-01 o 16:24, Longabaugh, Robert E pisze: SMS VSAM is handled through Media Manager, so even if you bypass or shut down an allocation manager product, Media Manager consolidates the extents, which gets in the way of VSAM running out of space. IMHO it is not true for allocation (1,0), that means no secondary extents. The feature you described regards secondary extent consolidation. But secondary extents have to exist, so secondary allocation has to be nonzero. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2015 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.840.228 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
SMS VSAM is handled through Media Manager, so even if you bypass or shut down an allocation manager product, Media Manager consolidates the extents, which gets in the way of VSAM running out of space. The easiest way to deal with this is to truly fill the volumes you are allocating to, with dummy data sets that either cause fragmentation or only leave a couple of tracks on the volume. Where I work, we have a set of mini-disks of 15 cylinders to use for this purpose Use the Guaranteed Space option to SMS so that you can direct the allocation to the specific volume that you have pre-filled or fragmented. Bob Longabaugh CA Technologies Storage Management QA -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Thomas Conley Sent: Wednesday, September 30, 2015 3:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? On 9/30/2015 4:31 PM, Thomas Conley wrote: > On 9/30/2015 12:25 PM, Farley, Peter x23353 wrote: >> I need some advice from storage gurus. I need to make a tiny >> SMS-managed VSAM KSDS that will NOT extend, neither to secondary >> space on the first volume nor to secondary volumes. I need to test >> some error logic in an application program and I need a "file full" >> or "no more space" condition to test it. >> >> I have these parameters in the define cluster command: >> >> VOLUME(*) CYL (1 0) >> >> But when I try to fill up that file with IDCAMS REPRO so that there >> is no more room for any records by copying from a similar file with >> many records into the tiny one, it automatically extends to new >> volumes, with messages like this: >> >> SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR >> TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME >> XX, NEW VOLUME SMS . VOLUME COUNT IS 2 >> >> I assume this is due to some hidden parameter in the STORCLAS that >> overrides my specification of only one candidate volume. >> >> My question is, how do I override that hidden STORCLAS parameter to >> force a no-more-space error here? I deliberately want the attempt to >> add one more record to force an error. >> >> I do NOT have easy access to a storage admin on this system, so I >> need help from you. ISMF is not available in my TSO menus, so I >> cannot check the STORCLAS for myself. >> >> TIA for any help you can offer. >> > > Peter, > > Add a //ACCIGN DD DUMMY to your allocation and run JCL to bypass > ACC/SRS processing. > > Regards, > Tom Conley > Oops, I saw earlier that these were ACC/SRS messages, but I see now that they're Stop X37 ProSMS messages. In that case, try //PROIGN DD DUMMY or if that doesn't work //NOPLD DD DUMMY. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
Bob, All VSAM IO is handled by Media Manager, not just SMS. You description below is attributing facilities to Media Manager that I have not heard of or observed before. Can you elaborate on " Media Manager consolidates the extents?" Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Longabaugh, Robert E Sent: Thursday, October 1, 2015 7:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] How to limit tiny SMS-managed VSAM KSDS to one volume? SMS VSAM is handled through Media Manager, so even if you bypass or shut down an allocation manager product, Media Manager consolidates the extents, which gets in the way of VSAM running out of space. The easiest way to deal with this is to truly fill the volumes you are allocating to, with dummy data sets that either cause fragmentation or only leave a couple of tracks on the volume. Where I work, we have a set of mini-disks of 15 cylinders to use for this purpose Use the Guaranteed Space option to SMS so that you can direct the allocation to the specific volume that you have pre-filled or fragmented. Bob Longabaugh CA Technologies Storage Management QA -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Thomas Conley Sent: Wednesday, September 30, 2015 3:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? On 9/30/2015 4:31 PM, Thomas Conley wrote: > On 9/30/2015 12:25 PM, Farley, Peter x23353 wrote: >> I need some advice from storage gurus. I need to make a tiny >> SMS-managed VSAM KSDS that will NOT extend, neither to secondary >> space on the first volume nor to secondary volumes. I need to test >> some error logic in an application program and I need a "file full" >> or "no more space" condition to test it. >> >> I have these parameters in the define cluster command: >> >> VOLUME(*) CYL (1 0) >> >> But when I try to fill up that file with IDCAMS REPRO so that there >> is no more room for any records by copying from a similar file with >> many records into the tiny one, it automatically extends to new >> volumes, with messages like this: >> >> SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR >> TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME >> XX, NEW VOLUME SMS . VOLUME COUNT IS 2 >> >> I assume this is due to some hidden parameter in the STORCLAS that >> overrides my specification of only one candidate volume. >> >> My question is, how do I override that hidden STORCLAS parameter to >> force a no-more-space error here? I deliberately want the attempt to >> add one more record to force an error. >> >> I do NOT have easy access to a storage admin on this system, so I >> need help from you. ISMF is not available in my TSO menus, so I >> cannot check the STORCLAS for myself. >> >> TIA for any help you can offer. >> > > Peter, > > Add a //ACCIGN DD DUMMY to your allocation and run JCL to bypass > ACC/SRS processing. > > Regards, > Tom Conley > Oops, I saw earlier that these were ACC/SRS messages, but I see now that they're Stop X37 ProSMS messages. In that case, try //PROIGN DD DUMMY or if that doesn't work //NOPLD DD DUMMY. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
Unfortunately that is not an option for me here. I was informed by my storage admins of a way to bypass the StopX37 processing (and thanks also to Tom Conley for chiming in with that one for the archives) with the appropriate DD DUMMY, so I have managed to create the tiny "full" file that I needed for my application testing. Thanks for your help though. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Longabaugh, Robert E Sent: Thursday, October 01, 2015 10:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? SMS VSAM is handled through Media Manager, so even if you bypass or shut down an allocation manager product, Media Manager consolidates the extents, which gets in the way of VSAM running out of space. The easiest way to deal with this is to truly fill the volumes you are allocating to, with dummy data sets that either cause fragmentation or only leave a couple of tracks on the volume. Where I work, we have a set of mini-disks of 15 cylinders to use for this purpose Use the Guaranteed Space option to SMS so that you can direct the allocation to the specific volume that you have pre-filled or fragmented. Bob Longabaugh CA Technologies Storage Management QA -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Thomas Conley Sent: Wednesday, September 30, 2015 3:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? On 9/30/2015 4:31 PM, Thomas Conley wrote: > On 9/30/2015 12:25 PM, Farley, Peter x23353 wrote: >> I need some advice from storage gurus. I need to make a tiny >> SMS-managed VSAM KSDS that will NOT extend, neither to secondary >> space on the first volume nor to secondary volumes. I need to test >> some error logic in an application program and I need a "file full" >> or "no more space" condition to test it. >> >> I have these parameters in the define cluster command: >> >> VOLUME(*) CYL (1 0) >> >> But when I try to fill up that file with IDCAMS REPRO so that there >> is no more room for any records by copying from a similar file with >> many records into the tiny one, it automatically extends to new >> volumes, with messages like this: >> >> SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR >> TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME >> XX, NEW VOLUME SMS . VOLUME COUNT IS 2 >> >> I assume this is due to some hidden parameter in the STORCLAS that >> overrides my specification of only one candidate volume. >> >> My question is, how do I override that hidden STORCLAS parameter to >> force a no-more-space error here? I deliberately want the attempt to >> add one more record to force an error. >> >> I do NOT have easy access to a storage admin on this system, so I >> need help from you. ISMF is not available in my TSO menus, so I >> cannot check the STORCLAS for myself. >> >> TIA for any help you can offer. >> > > Peter, > > Add a //ACCIGN DD DUMMY to your allocation and run JCL to bypass > ACC/SRS processing. > > Regards, > Tom Conley > Oops, I saw earlier that these were ACC/SRS messages, but I see now that they're Stop X37 ProSMS messages. In that case, try //PROIGN DD DUMMY or if that doesn't work //NOPLD DD DUMMY. Regards, Tom Conley -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
Peter, Space constraint relief is part of the DATACLAS construct, not the Storage Class. These are the collective functions that will cause SPACE requests to be overridden, space reduction, and additional volumes to be added to you dataset. You will need to use a DATACLAS that has Space Constraint Relief and Override Space set to "NO". If ACC/SRS is the cause of the problem I recall there is a JCL statement that can be added to the step that will cause ACC/SRS to leave the datasets alone. However I don't remember what that DD statement is. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Wednesday, September 30, 2015 10:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume? If you do a F DIF,STATUS from the SDSF console you should see if it is active and what components are active. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Farley, Peter x23353 > Sent: Wednesday, September 30, 2015 9:57 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to > one volume? > > I have reached out to that organization, but getting an answer to such > a non- emergency question may take days or more. Hence my attempt to > find a way to do > it a bit sooner from the expertise on this list. > > Peter > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of J O Skip Robinson > Sent: Wednesday, September 30, 2015 12:45 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to > one volume? > > I'm guessing that most shops have some STORCLASS that bypasses at > least some SMS rules. We have NULL. That bypasses volser assignment, but not all rules. In the > absence of ISMF, you really need to get direction from your storage admin. > > -- > > This message and any attachments are intended only for the use of the addressee > and may contain information that is privileged and confidential. If > the reader of the > message is not the intended recipient or an authorized representative > of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you > have received this communication in > error, please notify us immediately by e-mail and delete the message > and any attachments from your system. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
Thanks Ron. Another user emailed me privately about that DD statement (ACCIGN DD DUMMY), which of course was not set to the default value here, but I have actually heard back from my storage admins what the non-default value here really is, so now I can fill the file and keep it from extending. Thank you all for your kind assistance and education of my ignorance. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ron Hawkins Sent: Wednesday, September 30, 2015 2:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume? Peter, Space constraint relief is part of the DATACLAS construct, not the Storage Class. These are the collective functions that will cause SPACE requests to be overridden, space reduction, and additional volumes to be added to you dataset. You will need to use a DATACLAS that has Space Constraint Relief and Override Space set to "NO". If ACC/SRS is the cause of the problem I recall there is a JCL statement that can be added to the step that will cause ACC/SRS to leave the datasets alone. However I don't remember what that DD statement is. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Wednesday, September 30, 2015 10:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume? If you do a F DIF,STATUS from the SDSF console you should see if it is active and what components are active. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Farley, Peter x23353 > Sent: Wednesday, September 30, 2015 9:57 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to > one volume? > > I have reached out to that organization, but getting an answer to such > a non- emergency question may take days or more. Hence my attempt to > find a way to do > it a bit sooner from the expertise on this list. > > Peter > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of J O Skip Robinson > Sent: Wednesday, September 30, 2015 12:45 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to > one volume? > > I'm guessing that most shops have some STORCLASS that bypasses at > least some SMS rules. We have NULL. That bypasses volser assignment, but not all rules. In the > absence of ISMF, you really need to get direction from your storage admin. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
On 9/30/2015 12:25 PM, Farley, Peter x23353 wrote: I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM KSDS that will NOT extend, neither to secondary space on the first volume nor to secondary volumes. I need to test some error logic in an application program and I need a "file full" or "no more space" condition to test it. I have these parameters in the define cluster command: VOLUME(*) CYL (1 0) But when I try to fill up that file with IDCAMS REPRO so that there is no more room for any records by copying from a similar file with many records into the tiny one, it automatically extends to new volumes, with messages like this: SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT IS 2 I assume this is due to some hidden parameter in the STORCLAS that overrides my specification of only one candidate volume. My question is, how do I override that hidden STORCLAS parameter to force a no-more-space error here? I deliberately want the attempt to add one more record to force an error. I do NOT have easy access to a storage admin on this system, so I need help from you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for myself. TIA for any help you can offer. Peter, Add a //ACCIGN DD DUMMY to your allocation and run JCL to bypass ACC/SRS processing. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
On 9/30/2015 4:31 PM, Thomas Conley wrote: On 9/30/2015 12:25 PM, Farley, Peter x23353 wrote: I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM KSDS that will NOT extend, neither to secondary space on the first volume nor to secondary volumes. I need to test some error logic in an application program and I need a "file full" or "no more space" condition to test it. I have these parameters in the define cluster command: VOLUME(*) CYL (1 0) But when I try to fill up that file with IDCAMS REPRO so that there is no more room for any records by copying from a similar file with many records into the tiny one, it automatically extends to new volumes, with messages like this: SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT IS 2 I assume this is due to some hidden parameter in the STORCLAS that overrides my specification of only one candidate volume. My question is, how do I override that hidden STORCLAS parameter to force a no-more-space error here? I deliberately want the attempt to add one more record to force an error. I do NOT have easy access to a storage admin on this system, so I need help from you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for myself. TIA for any help you can offer. Peter, Add a //ACCIGN DD DUMMY to your allocation and run JCL to bypass ACC/SRS processing. Regards, Tom Conley Oops, I saw earlier that these were ACC/SRS messages, but I see now that they're Stop X37 ProSMS messages. In that case, try //PROIGN DD DUMMY or if that doesn't work //NOPLD DD DUMMY. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
How to limit tiny SMS-managed VSAM KSDS to one volume?
I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM KSDS that will NOT extend, neither to secondary space on the first volume nor to secondary volumes. I need to test some error logic in an application program and I need a "file full" or "no more space" condition to test it. I have these parameters in the define cluster command: VOLUME(*) CYL (1 0) But when I try to fill up that file with IDCAMS REPRO so that there is no more room for any records by copying from a similar file with many records into the tiny one, it automatically extends to new volumes, with messages like this: SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT IS 2 I assume this is due to some hidden parameter in the STORCLAS that overrides my specification of only one candidate volume. My question is, how do I override that hidden STORCLAS parameter to force a no-more-space error here? I deliberately want the attempt to add one more record to force an error. I do NOT have easy access to a storage admin on this system, so I need help from you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for myself. TIA for any help you can offer. Peter This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
That looks like DTS Software ACC/SRS product (SMS4400I) not SMS. This product can override SMS constructs. I would check the rules or add a rule for this VSAM file. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Farley, Peter x23353 > Sent: Wednesday, September 30, 2015 9:25 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: How to limit tiny SMS-managed VSAM KSDS to one volume? > > I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM > KSDS that will NOT extend, neither to secondary space on the first volume nor to > secondary volumes. I need to test some error logic in an application program and I > need a "file full" or "no more space" condition to test it. > > I have these parameters in the define cluster command: > > VOLUME(*) CYL (1 0) > > But when I try to fill up that file with IDCAMS REPRO so that there is no more room > for any records by copying from a similar file with many records into the tiny one, it > automatically extends to new volumes, with messages like this: > > SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. > TINY.DATA, XX, 1 > SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME > COUNT IS 2 > > I assume this is due to some hidden parameter in the STORCLAS that overrides my > specification of only one candidate volume. > > My question is, how do I override that hidden STORCLAS parameter to force a no- > more-space error here? I deliberately want the attempt to add one more record to > force an error. > > I do NOT have easy access to a storage admin on this system, so I need help from > you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for > myself. > > TIA for any help you can offer. > > Peter > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
W dniu 2015-09-30 o 18:24, Farley, Peter x23353 pisze: I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM KSDS that will NOT extend, neither to secondary space on the first volume nor to secondary volumes. I need to test some error logic in an application program and I need a "file full" or "no more space" condition to test it. I have these parameters in the define cluster command: VOLUME(*) CYL (1 0) But when I try to fill up that file with IDCAMS REPRO so that there is no more room for any records by copying from a similar file with many records into the tiny one, it automatically extends to new volumes, with messages like this: SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT IS 2 I assume this is due to some hidden parameter in the STORCLAS that overrides my specification of only one candidate volume. My question is, how do I override that hidden STORCLAS parameter to force a no-more-space error here? I deliberately want the attempt to add one more record to force an error. I do NOT have easy access to a storage admin on this system, so I need help from you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for myself. TIA for any help you can offer. Interesting! Please, do the following LISTCAT ENT(your.vsam.ksds) ALL and provide the output check DATACLAS and it's definition from ISMF check STORCLAS and it's definition from ISMF I suspect DVC, but it's only wild guess. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2015 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.840.228 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
Most shops have a STORCLAS(NONSMS) defined which allows sys-progs to bypass all SMS allocations and use vol-ser for placement. If you have that defined then create a KSDS with STORCLAS(NONSMS) VOLUME(xx) trk(1 0). John Clifford On Wed, Sep 30, 2015 at 12:24 PM, Farley, Peter x23353 < peter.far...@broadridge.com> wrote: > I need some advice from storage gurus. I need to make a tiny SMS-managed > VSAM KSDS that will NOT extend, neither to secondary space on the first > volume nor to secondary volumes. I need to test some error logic in an > application program and I need a "file full" or "no more space" condition > to test it. > > I have these parameters in the define cluster command: > > VOLUME(*) CYL (1 0) > > But when I try to fill up that file with IDCAMS REPRO so that there is no > more room for any records by copying from a similar file with many records > into the tiny one, it automatically extends to new volumes, with messages > like this: > > SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. > TINY.DATA, XX, 1 > SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT > IS 2 > > I assume this is due to some hidden parameter in the STORCLAS that > overrides my specification of only one candidate volume. > > My question is, how do I override that hidden STORCLAS parameter to force > a no-more-space error here? I deliberately want the attempt to add one > more record to force an error. > > I do NOT have easy access to a storage admin on this system, so I need > help from you. ISMF is not available in my TSO menus, so I cannot check > the STORCLAS for myself. > > TIA for any help you can offer. > > Peter > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. > If the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please notify us immediately by > e-mail and delete the message and any attachments from your system. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
What problems are you attempting to solve by enforcing this? - -teD - Original Message From: Farley, Peter x23353 Sent: Wednesday, September 30, 2015 12:25 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: How to limit tiny SMS-managed VSAM KSDS to one volume? I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM KSDS that will NOT extend, neither to secondary space on the first volume nor to secondary volumes. I need to test some error logic in an application program and I need a "file full" or "no more space" condition to test it. I have these parameters in the define cluster command: VOLUME(*) CYL (1 0) But when I try to fill up that file with IDCAMS REPRO so that there is no more room for any records by copying from a similar file with many records into the tiny one, it automatically extends to new volumes, with messages like this: SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT IS 2 I assume this is due to some hidden parameter in the STORCLAS that overrides my specification of only one candidate volume. My question is, how do I override that hidden STORCLAS parameter to force a no-more-space error here? I deliberately want the attempt to add one more record to force an error. I do NOT have easy access to a storage admin on this system, so I need help from you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for myself. TIA for any help you can offer. Peter This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
As I said, I need to check some application program error logic designed to do application-specific recovery steps when there is a file-full condition. I need a file that I can fill up and that stays filled and does not extend in order to test that application logic. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ted MacNEIL Sent: Wednesday, September 30, 2015 12:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? What problems are you attempting to solve by enforcing this? - -teD - Original Message From: Farley, Peter x23353 Sent: Wednesday, September 30, 2015 12:25 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: How to limit tiny SMS-managed VSAM KSDS to one volume? I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM KSDS that will NOT extend, neither to secondary space on the first volume nor to secondary volumes. I need to test some error logic in an application program and I need a "file full" or "no more space" condition to test it. I have these parameters in the define cluster command: VOLUME(*) CYL (1 0) But when I try to fill up that file with IDCAMS REPRO so that there is no more room for any records by copying from a similar file with many records into the tiny one, it automatically extends to new volumes, with messages like this: SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT IS 2 I assume this is due to some hidden parameter in the STORCLAS that overrides my specification of only one candidate volume. My question is, how do I override that hidden STORCLAS parameter to force a no-more-space error here? I deliberately want the attempt to add one more record to force an error. I do NOT have easy access to a storage admin on this system, so I need help from you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for myself. TIA for any help you can offer. Peter -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
I'm guessing that most shops have some STORCLASS that bypasses at least some SMS rules. We have NULL. That bypasses volser assignment, but not all rules. In the absence of ISMF, you really need to get direction from your storage admin. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Wednesday, September 30, 2015 9:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume? This is an EXTERNAL email. If the sender is not recognized, do not open attachments or click on any Internet links within the message. As I said, I need to check some application program error logic designed to do application-specific recovery steps when there is a file-full condition. I need a file that I can fill up and that stays filled and does not extend in order to test that application logic. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ted MacNEIL Sent: Wednesday, September 30, 2015 12:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? What problems are you attempting to solve by enforcing this? - -teD - Original Message From: Farley, Peter x23353 Sent: Wednesday, September 30, 2015 12:25 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: How to limit tiny SMS-managed VSAM KSDS to one volume? I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM KSDS that will NOT extend, neither to secondary space on the first volume nor to secondary volumes. I need to test some error logic in an application program and I need a "file full" or "no more space" condition to test it. I have these parameters in the define cluster command: VOLUME(*) CYL (1 0) But when I try to fill up that file with IDCAMS REPRO so that there is no more room for any records by copying from a similar file with many records into the tiny one, it automatically extends to new volumes, with messages like this: SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT IS 2 I assume this is due to some hidden parameter in the STORCLAS that overrides my specification of only one candidate volume. My question is, how do I override that hidden STORCLAS parameter to force a no-more-space error here? I deliberately want the attempt to add one more record to force an error. I do NOT have easy access to a storage admin on this system, so I need help from you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for myself. TIA for any help you can offer. Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
TRACKS-5 HIGH-CCHHX'0071000B' HIGH-RBA--168959 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, September 30, 2015 12:31 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? Interesting! Please, do the following LISTCAT ENT(your.vsam.ksds) ALL and provide the output check DATACLAS and it's definition from ISMF check STORCLAS and it's definition from ISMF I suspect DVC, but it's only wild guess. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
I have reached out to that organization, but getting an answer to such a non-emergency question may take days or more. Hence my attempt to find a way to do it a bit sooner from the expertise on this list. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of J O Skip Robinson Sent: Wednesday, September 30, 2015 12:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume? I'm guessing that most shops have some STORCLASS that bypasses at least some SMS rules. We have NULL. That bypasses volser assignment, but not all rules. In the absence of ISMF, you really need to get direction from your storage admin. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
So you're getting STORAGECLASS SCLARGE MANAGEMENTCLASS--MCLARGE DATACLASS -OTHER These are all installation defined names. (I don't believe that SMS natively provides default names, but I'm not a storage admin.) There is *no way* to guess what name you could use to give you the result you're after. If you're not defined to SAF as having access to the relevant STGADMIN profile in the facility class, I don't think there's any way for you to poke around SMS for alternative class names. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Wednesday, September 30, 2015 9:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume? This is an EXTERNAL email. If the sender is not recognized, do not open attachments or click on any Internet links within the message. I have no way to check the storage or management classes, I have no access to ISMF from ISPF menus. Unless there is a batch JCL I could run to display that information, if so please point me to the right manual. What is DVC please? I'm guessing Dynamic Volume Count? Here is a sanitized LISTCAT, as requested. I also forgot to say that this is a z/OS 2.1 system, in case that matters. CLUSTER --- TSOUSER.VSAM.TINY IN-CAT --- ICF.TEST.CATALOG HISTORY DATASET-OWNER-(NULL) CREATION2015.273 RELEASE2 EXPIRATION--.000 SMSDATA STORAGECLASS SCLARGE MANAGEMENTCLASS--MCLARGE DATACLASS -OTHER LBACKUP ---.000. CA-RECLAIM-(YES) EATTR-(NULL) BWO STATUS-- BWO TIMESTAMP---0 00:00:00.0 BWO---(NULL) RLSDATA LOG (NULL) RECOVERY REQUIRED --(NO) FRLOG (NULL) VSAM QUIESCED ---(NO)RLS IN USE -(NO) LOGREPLICATE-(NO) LOGSTREAMID-(NULL) RECOVERY TIMESTAMP LOCAL-X'' RECOVERY TIMESTAMP GMT---X'' PROTECTION-PSWD-(NULL) RACF(NO) ASSOCIATIONS DATA-TSOUSER.VSAM.TINY.DATA INDEXTSOUSER.VSAM.TINY.INDEX DATA --- TSOUSER.VSAM.TINY.DATA IN-CAT --- ICF.TEST.CATALOG HISTORY DATASET-OWNER-(NULL) CREATION2015.273 RELEASE2 EXPIRATION--.000 ACCOUNT-INFO---(NULL) PROTECTION-PSWD-(NULL) RACF(NO) ASSOCIATIONS CLUSTER--TSOUSER.VSAM.TINY ATTRIBUTES KEYLEN40 AVGLRECL1600 BUFSPACE---37888 CISIZE-18432 RKP0 MAXLRECL1600 EXCPEXIT--(NULL) CI/CA-45 SHROPTNS(2,3) SPEED UNIQUE NOERASE INDEXED NOWRITECHK UNORDERED REUSE NONSPANNED STATISTICS REC-TOTAL495 SPLITS-CI--0 EXCPS--2 REC-DELETED0 SPLITS-CA--0 EXTENTS1 REC-INSERTED---0 FREESPACE-%CI--0 SYSTEM-TIMESTAMP: REC-UPDATED0 FREESPACE-%CA--0 X'CFA093A23D754BAD' REC-RETRIEVED--0 FREESPC0 ALLOCATION SPACE-TYPE--CYLINDER HI-A-RBA--829440 SPACE-PRI--1 HI-U-RBA--829440 SPACE-SEC--0 VOLUME VOLSERXX PHYREC-SIZE18432 HI-A-RBA--829440 EXTENT-NUMBER--1 DEVTYPE--X'3010200F' PHYRECS/TRK3 HI-U-RBA--829440 EXTENT-TYPEX'40' VOLFLAGPRIME TRACKS/CA-15 EXTENTS: LOW-CCHH-X'029D' LOW-RBA0 TRACKS15 HIGH-CCHHX'029D000E' HIGH-RBA--829439 INDEX -- TSOUSER.VSAM.TINY.INDEX IN-CAT --- ICF.TEST.CATALOG HISTORY DATASET-OWNER-(NULL) CREATION2015.273 RELEASE2 EXPIRATION--.000 PROTECTION-PSWD-(NULL) RACF(NO) ASSOCIATIONS CLUSTER--TSOUSER.VSAM.TINY ATTRIBUTES KEYLEN40 AVGLRECL---0 BUFSPACE---0 CISIZE--1024 RKP0 MAXLRECL1017 EXCPEXIT--(NULL) CI/CA-33
Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
Sorry missed that! - -teD - Original Message From: Farley, Peter x23353 Sent: Wednesday, September 30, 2015 12:38 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? As I said, I need to check some application program error logic designed to do application-specific recovery steps when there is a file-full condition. I need a file that I can fill up and that stays filled and does not extend in order to test that application logic. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ted MacNEIL Sent: Wednesday, September 30, 2015 12:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How to limit tiny SMS-managed VSAM KSDS to one volume? What problems are you attempting to solve by enforcing this? - -teD - Original Message From: Farley, Peter x23353 Sent: Wednesday, September 30, 2015 12:25 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: How to limit tiny SMS-managed VSAM KSDS to one volume? I need some advice from storage gurus. I need to make a tiny SMS-managed VSAM KSDS that will NOT extend, neither to secondary space on the first volume nor to secondary volumes. I need to test some error logic in an application program and I need a "file full" or "no more space" condition to test it. I have these parameters in the define cluster command: VOLUME(*) CYL (1 0) But when I try to fill up that file with IDCAMS REPRO so that there is no more room for any records by copying from a similar file with many records into the tiny one, it automatically extends to new volumes, with messages like this: SMS4000I TSOUSERZ, MKTSTFIL, SYS1, ATTEMPTING SPACVOLA FOR TSOUSER. TINY.DATA, XX, 1 SMS4400I VOLUME ADDED - OLD VOLUME XX, NEW VOLUME SMS . VOLUME COUNT IS 2 I assume this is due to some hidden parameter in the STORCLAS that overrides my specification of only one candidate volume. My question is, how do I override that hidden STORCLAS parameter to force a no-more-space error here? I deliberately want the attempt to add one more record to force an error. I do NOT have easy access to a storage admin on this system, so I need help from you. ISMF is not available in my TSO menus, so I cannot check the STORCLAS for myself. TIA for any help you can offer. Peter -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume?
Do you have any way to 'flood' the VSAM file with data? If so, try allocating the VSAM file as small as possible, although SMS may give you more than you want. In any case it won't be infinite. Try writing so much data that the file eventually fills up. Maybe you could prime the file to almost full, then let the application program hit the limit with it's own output. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Wednesday, September 30, 2015 9:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume? I have reached out to that organization, but getting an answer to such a non-emergency question may take days or more. Hence my attempt to find a way to do it a bit sooner from the expertise on this list. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of J O Skip Robinson Sent: Wednesday, September 30, 2015 12:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: (External):Re: How to limit tiny SMS-managed VSAM KSDS to one volume? I'm guessing that most shops have some STORCLASS that bypasses at least some SMS rules. We have NULL. That bypasses volser assignment, but not all rules. In the absence of ISMF, you really need to get direction from your storage admin. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
