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 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Farley, Peter x23353 Sent: Wednesday, September 30, 2015 9:36 AM To: [email protected] 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:[email protected]] On Behalf Of Ted MacNEIL Sent: Wednesday, September 30, 2015 12:32 PM To: [email protected] 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: [email protected] 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, 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
