Re: JCL SPACE ALLOCATION ISSUES
From: Joe Zitzelberger (joe_zitzelberger_at_nospam.com)
Date: 02/28/04
- Next message: Richard Heathfield: "Re: Discussion: rmgroup comp.software.year-2000"
- Previous message: berlutte_at_sympatico.ca: "Code as a weapon"
- In reply to: STR: "JCL SPACE ALLOCATION ISSUES"
- Next in thread: John S. Giltner, Jr.: "Re: JCL SPACE ALLOCATION ISSUES"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 Feb 2004 21:38:12 -0500
In article <8623d3bf.0402270713.3cbfe6db@posting.google.com>,
setar@mindspring.com (STR) wrote:
> //OUTPUT1 DD DSN=DATA.SET.NAME,DISP=(,CATLG,DELETE),
> DCB=(LRECL=242,RECFM-FB),
> UNIT=DISK,SPACE=(CYL,(300,30),RLSE)
I know it is counter-intuitive, but try this instead:
//OUTPUT1 DD DISP=(NEW,CATLG),DSN=DATA.SET.NAME,
// DCB=(LRECL=242,RECFM=FB),UNIT=DISK,
// SPACE=(CYL,(5,5),RLSE)
One of the places where MVS shows its very advanced age in in disk
usage. Depending on what software you have installed and how your
machine is configured the request for 300 primary and 30 secondary
cylinders might be what is killing you.
The problem is that the system must have a volume available with 30
contiguous cylinders available or it will kill your task. Some system
software will trap this and reduce the request size, but only if it is
properly installed and configured. Asking for a smaller secondary will
get more candidate volumes on which your dataset might play on.
- Next message: Richard Heathfield: "Re: Discussion: rmgroup comp.software.year-2000"
- Previous message: berlutte_at_sympatico.ca: "Code as a weapon"
- In reply to: STR: "JCL SPACE ALLOCATION ISSUES"
- Next in thread: John S. Giltner, Jr.: "Re: JCL SPACE ALLOCATION ISSUES"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|