S073-08 | DFSORT



Get solution for your ABEND Codes & System Error Messages, SQL Codes, File Status etc...

S073-08 | DFSORT

Postby Aki88 » Mon Sep 19, 2016 3:19 pm

Hello,

A rare and random one S073 RC- 08 abend, a recent abend's details are given below, same occurred in DFSORT processing:


1ICE201I 1 RECORD TYPE IS F - DATA STARTS IN POSITION 1
 ICE751I 0 C5-BASE   C6-BASE   C7-BASE   C8-I29500 E4-BASE   C9-BASE   E5-I29500 E6-BASE   C4-BASE   E7-BASE
 ICE143I 0 BLOCKSET     SORT  TECHNIQUE SELECTED
 ICE250I 0 VISIT http://www.ibm.com/storage/dfsort FOR DFSORT PAPERS, EXAMPLES AND MORE
 ICE000I 1 - CONTROL STATEMENTS FOR 5650-ZOS, Z/OS DFSORT V2R2  - mm:nn ON AAA BBB mm, nnnn -
0           OPTION MOSIZE=10%,HIPRMAX=10%,DYNALLOC=(SYSDA,15),DSPSIZE=300         -
                    EXPMAX=10%,EXPOLD=10%,EXPRES=10%                              
 ICE140I 0 END OF PARAMETERS FROM DFSPARM  - SYSIN OR SORTCNTL/PARAMETER LIST CONTROL STATEMENTS FOLLOW
            SORT FIELDS=(22,23,CH,A)
 ICE193I 0 ICEAM1 INVOCATION ENVIRONMENT IN EFFECT - ICEAM1 ENVIRONMENT SELECTED
 ICE252I 1 PARMLIB OPTIONS WERE MERGED WITH INSTALLATION MODULE DEFAULTS
 ICE088I 1 XXXXXXX.YYYYYYYY.SORTFIL , INPUT LRECL = 2000, BLKSIZE = 18000, TYPE = FB
 ICE093I 0 MAIN STORAGE = (MAX,19440003,19440003)
 ICE156I 0 MAIN STORAGE ABOVE 16MB = (19362163,19362163)
 ICE127I 0 OPTIONS: OVFLO=RC0 ,PAD=RC0 ,TRUNC=RC0 ,SPANINC=RC16,VLSCMP=N,SZERO=Y,RESET=Y,VSAMEMT=Y,DYNSPC=256
 ICE128I 0 OPTIONS: SIZE=19440003,MAXLIM=1048576,MINLIM=450560,EQUALS=N,LIST=Y,ERET=RC16 ,MSGDDN=SYSOUT
 ICE129I 0 OPTIONS: VIO=N,RESDNT=ALL ,SMF=NO   ,WRKSEC=Y,OUTSEC=Y,VERIFY=N,CHALT=N,DYNALOC=(SYSDA   ,015),ABCODE=MSG
 ICE130I 0 OPTIONS: RESALL=4096,RESINV=0,SVC=109 ,CHECK=Y,WRKREL=Y,OUTREL=Y,CKPT=N,COBEXIT=COB2
 ICE131I 0 OPTIONS: TMAXLIM=6291456,ARESALL=0,ARESINV=0,OVERRGN=65536,CINV=Y,CFW=Y,DSA=128
 ICE132I 0 OPTIONS: VLSHRT=N,ZDPRINT=Y,IEXIT=N,TEXIT=N,LISTX=N,EFS=NONE    ,EXITCK=S,PARMDDN=DFSPARM ,FSZEST=N
 ICE133I 0 OPTIONS: HIPRMAX=1200   ,DSPSIZE=300 ,ODMAXBF=0,SOLRF=Y,VLLONG=N,VSAMIO=N,MOSIZE=1200
 ICE235I 0 OPTIONS: NULLOUT=RC0
 ICE236I 0 OPTIONS: DYNAPCT=10 ,MOWRK=Y,TUNE=STOR,EXPMAX=12000  ,EXPOLD=10%    ,EXPRES=10%
 ICE084I 0 BSAM ACCESS METHOD USED FOR SORTOUT
 ICE084I 0 BSAM ACCESS METHOD USED FOR SORTIN
 ICE750I 0 DC 2605227296 TC 0 CS DSVVV KSZ 23 VSZ 23
 ICE752I 0 FSZ=1302613 RC  IGN=0 E  AVG=2000 0  WSP=3383742 C  DYN=53655 53216
 ICE751I 2 DE-BASE   D5-I29741 DA-I29500
0ICE805I 1 JOBNAME: XXXXXXX , STEPNAME: YYYYYYYY
 ICE802I 0 BLOCKSET     TECHNIQUE IN CONTROL
 ICE906I 0 ST=ABOVE,SR=19440003,RC=0
 ICE907I 0 ST=ABOVE,SA=19439984,NF=1,LF=19439984,SF=19439984
 ICE906I 0 ST=BELOW,SR=1040384,RC=0
 ICE907I 0 ST=BELOW,SA=1040368,NF=1,LF=1040368,SF=1040368
 ICE992I 0 RA 0 WR 0 TR 1
 ICE887I 0 CSES 12500149,14304463,14304463 ES 0,0,0
 ICE886I 0 SYS 76800 TSTG 3072000 FS 638588 INIT 6386 MAX 31930 LEN 0
 ICE915I 0 MOFSZ=2495,MOSZ=0,MOSYS=1200(1),MOSTG=12000,MEML=17592186039803(3)
 ICE916I 0 MOFR=0402,MOVR=VV
 ICE996I 0 ESM=3072000,ESO=180431,ESR=1430446,ESP=7936,ESS=16384,CES=15975680,HSZ=16777216
 ICE997I 0 HWSP=1590104,HMAX=0,MOMAX=307200,ASV=3072000,EQ=I2,HN=1
 ICE898I 0 OMAX=12500149,NMAX=14304463,ENQT=2293504,CMAX=230144,HU=97,BUN=53216,MD=NK,M3,DU=90,DR=0,HN=1
 ICE880I 0 QP=29 QA=107 HI=386 LI=282 MI=388 TZ=230144 N1=230144 N2=230144 SZ=30 HN=1
 ICE889I 0 CT=MAX     , SB=8, L=0, D=0000, CCW=1MAM
 ICE901I 0 W 0EPP17 0CPP17 0APP17 10PP17 05PP17 02PP17 08PP17 04PP17
 ICE901I 0 W 06PP17 0FPP17 0DPP17 0BPP17 03PP17 07PP17 09PP17 01PP13
 ICE902I 0 O PP10  I PP10
 ICE906I 1 ST=ABOVE,SR=19362163,RC=0
 ICE907I 1 ST=ABOVE,SA=19362144,NF=1,LF=19362144,SF=19362144
 ICE906I 1 ST=BELOW,SR=109160,RC=0
 ICE907I 1 ST=BELOW,SA=64088,NF=1,LF=64088,SF=64088
 ICE996I 1 ESM=3072000,ESO=175508,ESR=1386140,ESP=7936,ESS=16384,CES=15975680,HSZ=16777216
 ICE897I 0 AVAL=12106320,BVAL=13861407,ENQT=1658624,ASV=3072000,HSZ=230144,HM=MH,HN=2
 ICE880I 0 QP=29 QA=190 HI=387 LI=199 MI=388 TZ=230144 N1=230144 N2=230144 SZ=30 HN=2
 ICE185A 0 AN S073  ABEND WAS ISSUED BY DFSORT, ANOTHER PROGRAM OR AN EXIT (PHASE S 1)
 


From the z/OS MVS System Codes manual:

073
Explanation: Supervisor control detected an error
while processing a SETLOCK OBTAIN or SETLOCK
RELEASE macro. The hexadecimal reason code in
register 15 explains the error:

08 The system detected a hierarchy violation.
a. If a SETLOCK OBTAIN macro was being
processed, one of the following occurred:
– The requested lock was lower in the
locking hierarchy than the locks currently
held.
– Another lock of the same type was
already held.
– A CMS lock was requested, but a local
lock was not held.
– A local or CML lock was requested
unconditionally, but the PSASUPER field
was nonzero.
b. If a SETLOCK RELEASE macro was being
processed, one of the following occurred:
– A local lock was specified while a CMS
lock was still held.
– All CMS locks were specified, but not all
CMS locks were held.


A restart of the failed step tends to get the job run clean.

Query: From past experiences with this abend, have come to understand that this is one random customer. It'd be great if someone can kindly help me understand it better. Tried recreating it to get a better understanding, but have failed thus far be it in this case or a different COBOL/or-otherwise program, primarily because I am unable to understand what really went wrong.
Also, in case of this DFSORT failure if someone can kindly point me to an eyecatcher, maybe something to do with MO* or maybe someother storage!?

Any pointers towards what can be done to avoid this abend are really appreciated.

Thank you.
Aki88
 
Posts: 286
Joined: Tue Jan 28, 2014 1:52 pm
Has thanked: 31 times
Been thanked: 23 times

Re: S073-08 | DFSORT

 

Re: S073-08 | DFSORT

Postby BillyBoyo » Mon Sep 19, 2016 9:34 pm

If you are getting transient S073s (ie when you rerun, there is normal and correct completion) I would raise the issue with IBM. I doubt that anyone reading this will be able to help.

If it is happening in other places than DFSORT as well, I don't think it even worth raising with the DFSORT team. It is something beyond their code.

I don't think there's any short-cut here. Raise it with IBM.
BillyBoyo
Global moderator
 
Posts: 3759
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 256 times

Re: S073-08 | DFSORT

Postby Aki88 » Mon Sep 19, 2016 10:37 pm

Hello Billy,

BillyBoyo wrote:If you are getting transient S073s (ie when you rerun, there is normal and correct completion) ....

If it is happening in other places than DFSORT as well .....


You're spot-on with the two points. We did raise it to the IBM support here; aside, after a few follow-ups and mail exchanges I really don't see it getting anywhere; will pursue it further.

Just one last help, it'd be great if someone can help me understand 'S073' a little bit; from what the manual states for this one cookie, am unable to understand it 'right'. My understanding is- one of the call chain commands are failing when a particular MACRO instruction is being executed for a given code instruction (for example assume there is a MOVE statement, it further breaks down into Assembly instructions at its core, and each is executed with system performing MACRO calls, one of these calls failed).

Also, is a S073 possible in DFSORT due to storage (virtual or otherwise/Memory Objects etc) dead-lock/shortage, or something on those lines? Apologies for a vague query, but this is because I am NOT very clear on S073's occurrence.

Thank you.
Aki88
 
Posts: 286
Joined: Tue Jan 28, 2014 1:52 pm
Has thanked: 31 times
Been thanked: 23 times

Re: S073-08 | DFSORT

Postby BillyBoyo » Tue Sep 20, 2016 12:23 am

Well, I've never encountered S073, or even heard of it before. "Supervisor control" indicates that it is from somewhere deep in the operating system. I wouldn't think it actually caused by anything that any program, DFSORT or otherwise, is doing directly, and have zero idea of what it is they've done indirectly to have this happen.

Your tech support needs to raise it with IBM if that has not been done. I'd think it unlikely that someone in your tech support will be able to say "oh, I know what that is" or be certain how to collect diagnosis information about it.

My guess is that it is a symptom. Like a sneeze. You don't cure the sneeze, you cure what is causing the sneeze, which either already or may in the future have further consequences.

Your best bet for insight on S073 is to stick with the issue and see if you can make sense of the resolution. You may never need to know again, however :-)

These users thanked the author BillyBoyo for the post:
Aki88 (Tue Sep 20, 2016 10:17 am)
BillyBoyo
Global moderator
 
Posts: 3759
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 256 times


Return to ABENDS & SQL Codes