A technique used to diagnose this issue, instead of a temp DSN, Make it a real dsn. Then check the output attributes. Use 3.4 and display the information about allocations. See if the file is as large or small as you think.
With a TEMPDSN, I might create it and pass to a TSO Batch step where REXX is used to list the attributes of the temp DSN. As others had requested, please post the B37 abend message. You can mask company specific details. Now with SMS, there are ways of controlling extents and allocations. Have you talked to your storage administrator for assistance? All indicate dataset out of space. SD37 - no secondary allocation was specified. SB37 - end of vol. and no further volumes specified. SE37 - Max. of 16 extents already allocated. The B37 would be the program looking for another primary extent and it not being available on the volume. "end of volume" By allocating with more primary space, there wouldn't need to be a search for extent. You might get a SB37 when your allocations cannot fit on the volumes. I like to recommend to use a small PRIMAY and huge SECONDARY. The secondary can use more extents than the primary. A Primary allocation can only be gotten in a maximum of 5 extents. The secondary lots more. So if your allocation is 4000,4000 Cylinders than you need to get the first 4000 in no more than 5 extents. Then the secondary can be gotten in the next group of extents. So the dataset may not have fit on the volume and might need more volumes. If you can post the JESMSGLG for this file, that would also be helpful. These messages are IGD prefix. Lizette > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM- > [email protected]] > > On Behalf Of Buckton, T. (Theo) > > Sent: Tuesday, July 07, 2015 12:41 AM > > To: [email protected] > > Subject: Temporary data sets on 3390 model-27 volumes > > > > Hi, > > > > We have only been using 3390 mod 27 volumes over the last year, and > > mainly for the work storage pool. However, we have not managed yet to > > take advantage of the above the 4GB limit allocation for the temporary > > data sets. What SMS settings should be in place to allocate large size > temporary data sets? > > When specifying CYLS 4000,4000, the jobs fails with RC SB37, even > > though there is sufficient space on the mod 27 volumes in the pool. > > It might help if you showed us the accompanying IEC030I message. > > Do you meet one of the following exceptions mentioned in the JCL manual? > "The size of a data set is limited to 65,535 tracks per volume except for the > following types of data sets: > – Hierarchical File System (HFS) > – Extended format sequential > – Partitioned data set extended (PDSE) > – VSAM > – Large format" > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
