Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
My user has a job containing the following sort step:
| Code: |
//SORT2 EXEC PGM=SORT,PARM='CORE=MAX'
//SYSOUT DD SYSOUT=*
//STATOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SORTIN DD DSN=xxxxxx,
// DISP=SHR
//SORTOUT DD DSN=xxxxxx.SORTED,
// DISP=(NEW,CATLG,DELETE),
// UNIT=TESTP,
// SPACE=(CYL,(30,10),RLSE),
// DCB=(RECFM=VB,LRECL=4096,BLKSIZE=0,DSORG=PS)
//SYSIN DD *
SORT FIELDS=(5,60,CH,A)
/*
//
|
The step fails CC=16 when contained in the job but works when run in isolation.
The SYSOUT output from the failing job ends with:
ICE084I 0 EXCP ACCESS METHOD USED FOR SORTOUT
ICE084I 0 EXCP ACCESS METHOD USED FOR SORTIN
ICE750I 0 DC 212362484 TC 0 CS DSVRR KSZ 64 VSZ 64
ICE752I 0 FSZ=212362484 BC IGN=0 E AVG=2081 0 WSP=280265 C DYN=0 0
ICE046A 0 SORT CAPACITY EXCEEDED - RECORD COUNT 31858
ICE052I 0 END OF DFSORT
while the successful execution has:
ICE084I 0 EXCP ACCESS METHOD USED FOR SORTOUT
ICE084I 0 EXCP ACCESS METHOD USED FOR SORTIN
ICE750I 0 DC 212362484 TC 0 CS DSVRR KSZ 64 VSZ 64
ICE752I 0 FSZ=212362484 BC IGN=0 E AVG=2081 0 WSP=280265 C DYN=0 0
ICE090I 0 OUTPUT LRECL = 4096, BLKSIZE = 27998, TYPE = VB
ICE055I 0 INSERT 0, DELETE 0
ICE054I 0 RECORDS - IN: 56895, OUT: 56895
ICE134I 0 NUMBER OF BYTES SORTED: 193253350
ICE098I 0 AVERAGE RECORD LENGTH = 3396 BYTES
ICE165I 0 TOTAL WORK DATA SET TRACKS ALLOCATED: 450 , TRACKS USED: 0
ICE180I 0 HIPERSPACE STORAGE USED = 189336K BYTES
ICE188I 0 DATA SPACE STORAGE USED = 0K BYTES
ICE751I 0 C5C6C7C8E9C9E5E7D8D4EAF1E8
ICE052I 0 END OF DFSORT
Other than the jobs having a different number of steps, there is no (apparent) difference. Can you shed any light on this, please? |
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005
Posts: 7129
Location: San Jose, CA
|
|
|
|
Well, I could guess that the other steps are allocating space that prevents the DFSORT step from getting the resources it needs, but it would just be a guess.
More documentation would be needed to analize this situation in depth. Please open a problem report (PMR) with IBM service so they can collect the appropriate doc and help you resolve it. |
|
