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:[email protected]] On Behalf Of Longabaugh, Robert E Sent: Thursday, October 01, 2015 10:25 AM To: [email protected] 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:[email protected]] On Behalf Of Thomas Conley Sent: Wednesday, September 30, 2015 3:52 PM To: [email protected] 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, SYS00001, ATTEMPTING SPACVOLA FOR >> TSOUSER. TINY.DATA, XXXXXX, 1 SMS4400I VOLUME ADDED - OLD VOLUME >> XXXXXX, 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 [email protected] with the message: INFO IBM-MAIN
