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
