Hi, To be able to fix the SPACE problem it would be useful to know what is causing the problem.
Allocating a smaller primary may not work because the space allocation routine may allocate the primary request in up to 5 extents if CONTIG is not specified. This would only leave 11 extents on the first volume to meet the secondary requests. This could lead to an x37 abend rather than the current JCL error. Any request for space in a space parameter, primary or secondary is merely that a request the system will provide it in a single extent if it can, but if not it will try to meet the request in up to 5 extents. If the requested space is valid for the likely number of records, then perhaps the percentage free space rules of the pool, or re-direction to a different storage pool might be a better approach. Terry Sambrooks Director KMS-IT Limited 228 Abbeydale Road South Dore, Sheffield, S17 3LA, UK Tel: +44 (0)114 262 0933 WEB: www.legac-e.co.uk Company Reg: 3767263 at the above address All outgoing E-mail is scanned, but it remains the recipient's responsibility to ensure their system is protected from spy-ware, trojans, viruses, and worms. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
