ibmmainframesyntel
Active User
Joined: 26 Feb 2007
Posts: 126
Location: Chennai
|
|
|
|
Hi Frank,
If xxxx is not 064K:
Ensure that work data sets can be dynamically allocated.
If message ICE118I was received, specify FILSZ=En with a reasonably accurate estimate of the number of records to be sorted. If you cannot specify FILSZ=En, use DYNSPC=n to decrease the primary space allocated.
Where exactly i have to give DYNSPC=n,FILSZ=En in JCL.
In Exec statement with PARM parameter or what.
I didn't get anything.
01I E RECORD TYPE IS F - DATA STARTS IN POSITION 1
83A D RESOURCES WERE UNAVAILABLE FOR DYNAMIC ALLOCATION OF WORK DATA SETS (970C
53I 0 FWK=(0,0) SWK=(0,0) TWK=(0,0) RWK=(0,0) TOTAL=(0,0) BLK=49120
51I 0 C5-K90007 C6-K90007 C7-K90000 C8-K90007 E4-K90007 C9-BASE E5-K10929 E6-
50I 0 DC 12963262455 TC 0 CS DSVVV KSZ 25 VSZ 25
52I 0 FSZ=5113713 RC IGN=0 E AVG=2536 0 WSP=16843691 C DYN=0 49120
52I 3 END OF DFSORT
this is the error am getting now |
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005
Posts: 7129
Location: San Jose, CA
|
|
|
|
| Quote: |
| Where exactly i have to give DYNSPC=n,FILSZ=En in JCL. |
| Code: |
//DFSPARM DD *
OPTION DYNSPC=n,FILSZ=En
/*
|
But it doesn't appear that you received ICE118I so those options won't make any difference.
There appears to be something wrong with the way the dynamically allocated work data sets were set up at your site (e.g. no usable volumes in storage pool, bad device for VIO). Contact your system programmer - they may have to open a problem to have IBM help them figure out what's wrong.
As a bypass, you could try using //SORTWKdd DD statements to avoid dynamic allocation (NOT RECOMMENDED as a permanent thing). |
|
