Joined: 06 Jun 2008 Posts: 8553 Location: Dubuque, Iowa, USA
Why did you not post anything for us to help you -- for example, seeing the actual JCL?
What value did you use for the WORK= parameter of your IEBCOPY EXEC? If you did not specify one, then merely increasing REGION size on the EXEC will do NOTHING to alleviate this issue -- you MUST specify WORK= according to the manual. And if you did not specify SYSUT3 or SYSUT4 in your JCL, they could help resolve the problem -- another reason you should have posted your JCL.
The SIZE and WORK parameters in the PARM=... will not help you unless the REGION parameter specifies a large enough region to allocate these tables. We have no idea what your defaults are.
As for WORK=... the manual explicitly states, "It is best to let IEBCOPY choose buffer sizes by not using this parameter."
The manual does not seem to provide any guideline for SPACE for SYSUT3. I'm pretty certain the space you specify is grossly over allocated. The manual does provide a useful guideline for SYSUT4; I calculated 21 cylinders based on the guideline in the manual. When in doubt, RTFM! However, the manual also seems to state SYSUT4 is only used when copying from more than one INDD, which you are not doing.