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(xxxxxx) 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, 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 > > 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
