Are you opening all files before you issue the SORT statement? Have you tried changing the sort storage parameters? The SORT-CORE-SIZE special register is the name of a binary data item that you can use to specify the number of bytes of storage available to the sort utility. It has the implicit definition:
01 SORT-CORE-SIZE GLOBAL PICTURE S9(8) USAGE BINARY VALUE ZERO. So you can MOVE nnnnnnn TO SORT-CORE-SIZE to restrict the amount of storage available to the sort. If all else fails, you can reduce the BUFNO of each of the files from the default of 5. David de Jongh > -----Original Message----- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER- > l...@listserv.uga.edu] On Behalf Of Capon, Diego > Sent: Friday, October 14, 2011 8:15 AM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: storage for vsam ext > > Hi guys > I know this is a well known problem but I don't find the right answer to fix it > so may be you can give me a new idea. > > A very large program (cobol) with internal sort and using so many vsam files > randomly fails when attempts to open a file because resource not available > (status 93) or IEC161I 020-053 or IEC161I 001(8,29)-032 and then messages like > INSUFFICIENT STORAGE WAS AVAILABLE. The file changes in different > runnings. > > I change the HEAP Lenguage storage to 8M or STACK parameters. Sometimes > it works. Also I change the REGION, etc.. TIOT is big enough. Initiators are > recycled everyday.... > > But the most efficient change is to redefine the vsam from vs-e to non > extended. Most of the times it works. > > We have mainview batch optimizer, may be this product is making noise, I > don't know. > I'm not using buf parameter in the jcl. > Any help is welcome. > Thks > Diego > > > > > > POR FAVOR, PIENSE EN EL MEDIO AMBIENTE ANTES DE IMPRIMIR ESTE > MENSAJE.