Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Identifying the real cause for ICE046A

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DFSORT/ICETOOL
View previous topic :: :: View next topic  
Author Message
krisprems

Active Member


Joined: 27 Nov 2006
Posts: 649
Location: India

PostPosted: Sat Mar 02, 2013 1:47 am    Post subject: Identifying the real cause for ICE046A
Reply with quote

Hi, I am trying to identify the real cause of why this message was receied - ICE046A (SYSout messages attached).

Situation: The Job ran at the peak time, when the CPU, disk space usage was high and it abended. Hence Job was restarted when the system was in its low, then it ran fine.

Need help with: I do know about the permanent fix for this. But, really trying to understand, did it abend because of the insufficient space in the system at that point of time'?

not everybody is able to see the attachment

Code:
1ICE201I H RECORD TYPE IS F - DATA STARTS IN POSITION 1
 ICE118I 0 UNKNOWN FILE SIZE - FILSZ=EN MAY IMPROVE RESOURCE USAGE AND PERFORMANCE
 ICE751I 0 C5-K76982 C6-K90026 C7-K58148 C8-K67572 E4-K58148 C9-BASE   E5-K76585 E6-K58148 C4-K58148 E7-K79990
 ICE143I 0 BLOCKSET     SORT  TECHNIQUE SELECTED
 ICE250I 0 VISIT http://www.ibm.com/storage/dfsort FOR DFSORT PAPERS, EXAMPLES AND MORE
 ICE000I 0 - CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT V1R12 - 07:04 ON FRI MAR 01, 2013 -
0          SORT FIELDS=(0001,0003,CH,A,0004,0003,CH,A,0007,0001,CH,A,0008,0001,CH,*
                          A,0009,0002,CH,A,0011,0004,CH,A,0015,0002,ZD,A,0106,0008*
                          ,ZD,A,0114,0003,CH,A)
           RECORD TYPE=F,LENGTH=(000400,,)
 ICE201I H RECORD TYPE IS F - DATA STARTS IN POSITION 1
 ICE118I 0 UNKNOWN FILE SIZE - FILSZ=EN MAY IMPROVE RESOURCE USAGE AND PERFORMANCE
 ICE751I 0 C5-K76982 C6-K90026 C7-K58148 C8-K67572 E4-K58148 C9-BASE   E5-K76585 E6-K58148 C4-K58148 E7-K79990
 ICE193I 0 ICEAM2 INVOCATION ENVIRONMENT IN EFFECT - ICEAM2 ENVIRONMENT SELECTED
 ICE089I 1 PTLCM742.STEP0010.PROC0040, INPUT LRECL = 400, TYPE = F
 ICE093I 0 MAIN STORAGE = (MAX,8388608,8388608)
 ICE156I 0 MAIN STORAGE ABOVE 16MB = (8478704,8331248)
 ICE127I 0 OPTIONS: OVFLO=RC0 ,PAD=RC0 ,TRUNC=RC0 ,SPANINC=RC16,VLSCMP=N,SZERO=Y,RESET=Y,VSAMEMT=Y,DYNSPC=2048
 ICE128I 0 OPTIONS: SIZE=8388608,MAXLIM=4194304,MINLIM=450560,EQUALS=N,LIST=Y,ERET=ABEND,MSGDDN=SYSOUT
 ICE129I 0 OPTIONS: VIO=Y,RESDNT=ALL ,SMF=FULL ,WRKSEC=Y,OUTSEC=Y,VERIFY=N,CHALT=N,DYNALOC=(SYSDA   ,006),ABCODE=MSG
 ICE130I 0 OPTIONS: RESALL=8192,RESINV=16384,SVC=109 ,CHECK=Y,WRKREL=Y,OUTREL=Y,CKPT=N,COBEXIT=COB2
 ICE131I 0 OPTIONS: TMAXLIM=8388608,ARESALL=16384,ARESINV=131072,OVERRGN=16384,CINV=Y,CFW=Y,DSA=0
 ICE132I 0 OPTIONS: VLSHRT=N,ZDPRINT=N,IEXIT=N,TEXIT=N,LISTX=N,EFS=NONE    ,EXITCK=S,PARMDDN=DFSPARM ,FSZEST=N
 ICE133I 0 OPTIONS: HIPRMAX=OPTIMAL,DSPSIZE=MAX ,ODMAXBF=0,SOLRF=Y,VLLONG=N,VSAMIO=N,MOSIZE=MAX
 ICE235I 0 OPTIONS: NULLOUT=RC0
 ICE236I 0 OPTIONS: DYNAPCT=10 ,MOWRK=Y
 ICE750I 0 DC 0 TC 0 CS DSVVV KSZ 24 VSZ 24
 ICE752I 0 FSZ=0 RE  IGN=0 C  AVG=408 0  WSP=0 E  DYN=28860 16352
0ICE805I 0 JOBNAME: PTLCM742 , STEPNAME: STEP0010
 ICE802I 0 BLOCKSET     TECHNIQUE IN CONTROL
 ICE992I 0 RA 0 WR 0 TR 3
 ICE887I 0 CSES 0,0,0 ES 0,0,0
 ICE886I 0 SYS 0 TSTG 0 FS 0 INIT 0 MAX 0 LEN 0
 ICE915I 0 MOFSZ=16,MOSZ=0,MOSYS=1935(2),MOSTG=9491,MEML=1935(1)
 ICE916I 0 MOFR=0402,MOVR=VV
 ICE996I 0 ESM=3600896,ESO=3600896,ESR=0,ESP=4096,ESS=16384,CES=3600896,HSZ=524288
 ICE997I 0 HWSP=0,HMAX=2429942,HES=2429942,ASV=2429942,EQ=I3,HN=1
 ICE898I 0 OMAX=1729268,NMAX=2429942,ENQT=2429942,CMAX=524288,HU=99,BUN=16352,MD=H2,NK,DU=83,DR=0,HN=1
 ICE880I 0 QP=5 QA=5 HI=594 LI=590 MI=594 TZ=17398 N1=16384 N2=16384 SZ=129 HN=1
 ICE889I 0 CT=MAX     , SB=3, L=0, D=0000, CCW=1MAM
 ICE901I 0 W 01PP15 02PP15 03PP15 04PP15 05PP15 06PP15 07PP11 08PP11
 ICE901I 0 W 09PP11
 ICE897I 0 AVAL=339007,BVAL=1039681,ENQT=0,ASV=1039681,HSZ=0,HM=H1,HN=4
 ICE046A 0 SORT CAPACITY EXCEEDED - RECORD COUNT 15948119
 ICE253I 0 RECORDS SORTED - PROCESSED: 15948119, EXPECTED: 0
 ICE753I 1 FWK=(6,28860) SWK=(0,0) TWK=(0,0) RWK=(3,26271) TOTAL=(9,55131) BLK=16352
 ICE278I 1 6 WORK DATA SETS WERE INSUFFICIENT TO COMPLETE THIS SORT SO 3 ADDITIONAL WERE USED
 ICE751I 1 DE-K61787 D5-K58148 C4-K58148 C4-K58148 E8-K79990
 ICE052I 0 END OF DFSORT



attachment content inlined and code' d , and attachment deleted
Back to top
View user's profile Send private message

Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Sat Mar 02, 2013 2:24 am    Post subject: Re: Identifying the real cause for ICE046A
Reply with quote

krisprems wrote:
But, really trying to understand, did it abend because of the insufficient space in the system at that point of time'?

Might could be. As the entry for ICE046A in the DFSORT Messages, Codes, and Diagnosis Guide states:
Quote:
DFSORT was not able to complete processing with the intermediate storage available (Hiperspace or disk work data sets). [...]
The amount of intermediate storage required can vary depending on many factors including:

•The amount of Hiperspace DFSORT is able to use at the time the sort is run
•The amount of main storage available
•The degree of randomness of the records to be sorted
•The values specified (or defaulted) for options such as DYNALOC, DYNAUTO, DYNSPC, FILSZ/SIZE, AVGRLEN, or DYNALLOC
•The amount of padding required for short records when VLSHRT is in effect.
Back to top
View user's profile Send private message
krisprems

Active Member


Joined: 27 Nov 2006
Posts: 649
Location: India

PostPosted: Sat Mar 02, 2013 2:28 am    Post subject:
Reply with quote

Akatsukami: So, the next question is, how do you determine, which of these is the cause?
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Sat Mar 02, 2013 2:40 am    Post subject:
Reply with quote

Good question icon_biggrin.gif I'd recruit Sri Kolusu; whilst he might not be able to say himself, if you can provide enough information to the DFSORT development team, they might.
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7223

PostPosted: Sat Mar 02, 2013 3:13 am    Post subject: Reply to: Identifying the real cause for ICE046A
Reply with quote

Looks like a Cobol internal SORT? Have a look at this one.
Back to top
View user's profile Send private message
Skolusu

Senior Member


Joined: 07 Dec 2007
Posts: 2205
Location: San Jose

PostPosted: Sat Mar 02, 2013 4:50 am    Post subject:
Reply with quote

krisprems wrote:
Akatsukami: So, the next question is, how do you determine, which of these is the cause?


You can start with this as your start


Clue #1 by DFSORT wrote:
ICE118I 0 UNKNOWN FILE SIZE - FILSZ=EN MAY IMPROVE RESOURCE USAGE AND PERFORMANCE


Clue #2 by DFSORT wrote:
ICE278I 1 6 WORK DATA SETS WERE INSUFFICIENT TO COMPLETE THIS SORT SO 3 ADDITIONAL WERE USED


Possible Solution # 1
Code:

//DFSPARM  DD *                             
  OPTION DYNALLOC=(,12),FILSZ=E19000000
//*


You can look up the topic that Bill pointed to to understand how I arrived at the numbers for FILSZ.
Back to top
View user's profile Send private message
krisprems

Active Member


Joined: 27 Nov 2006
Posts: 649
Location: India

PostPosted: Mon Mar 04, 2013 9:29 pm    Post subject:
Reply with quote

Hi Skolusu,
I see that you have provided the solution for getting rid of this error message. But, per my original question, I am looking for the reason as to why it failed in the first place, as when I reran the same step with no changes, it did run fine!

I am digging to this depth because, every month end, when there is heavy processing in the system, SORT fails in one or the other job with this error message, then the solution is as simple as , restart the step with no changes and it runs fine.

Per my experience, my guesses are
Quote:

1. Region parameter in the job is playing a role, due to high traffic in the system at that point of time
2. There were no sufficient volumes(space) available in the system at that point of time
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7223

PostPosted: Mon Mar 04, 2013 9:46 pm    Post subject: Reply to: Identifying the real cause for ICE046A
Reply with quote

You have messages in the sysout about disk work datasets. If a Sort is using disk work datasets, there is not enough "memory", in one form or another, to do the sort "in core".

Your disk work datasets are not being allocated effectively, as you are giving Sort no indication from you of the number of records and, due to the involvement of an "exit" (the Cobol program doing the Sort), Sort cannot tell from the dataset(s) as it is not even aware of what they are.

With effective allocation of disk work datasets the message will "go away". I'd think that one of the other reasons must be likely only if no disk work datasets have already been used - but that's just me thinking.

If you look through the linked-to topic, and perhaps this one, you'll find about everything that you can look up to see what affects allocation of disk work space, and other types of work space.

If you get the message again, look for other "unusual" messages in the step. It'll probably get you there.
Back to top
View user's profile Send private message
krisprems

Active Member


Joined: 27 Nov 2006
Posts: 649
Location: India

PostPosted: Tue Mar 05, 2013 12:18 am    Post subject:
Reply with quote

Bill Woodger: I will work based on your suggestions and get back as to what I come up with!
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DFSORT/ICETOOL All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Identifying the emulator used vasanthz All Other Mainframe Topics 8 Thu Sep 29, 2016 2:17 am
No new posts cics & real time monitoring icehat CICS 5 Wed Sep 07, 2016 2:29 am
No new posts REAL TIME DATA MANIPULATION techslam SYNCSORT 3 Mon Dec 01, 2014 6:51 pm
No new posts Identifying programs that invoked my ... Bruno Oliveira COBOL Programming 10 Mon Oct 06, 2014 10:02 pm
No new posts Identifying Caling program name Suresh Uthirapathy CICS 11 Fri Apr 18, 2014 1:25 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us