We has a ADABASE task ADSDBTDT which abended due to S0C3 abend and we observed a SVCDUMP was taken for OPSOSF in a dataset MSDUMP.SYSD.D210615.T134305.OPSOSF.S00001. Could you please review and let us know more about this. Thanks.
15JUN,13:43:06,OPSS0034,IEA794I SVC DUMP HAS CAPTURED:
15JUN,13:43:06,OPSS0034,DUMPID=001 REQUESTED BY JOB (OPSOSF )
15JUN,13:43:06,OPSS0034,DUMP TITLE=COMPON=SSI,COMPID=5752SC1B6,ISSUER=IEFJSARR,MODULE=I
15JUN,13:43:06,OPSS0034, EFJRASP,ABEND=S0D6,REASON=00000027,SNAME=XXXX
15JUN,13:43:06,CONSOLE ,OPS9999T OPAOEV RC= 46 FOR ENVIRONMENTAL VARIABLE MSG.CONID
15JUN,13:43:06,OPSOSF ,OPS1181T OPSOSF OPSS (*Local*) MVS N/A PROBRPT S ADPIR,CANJOB=ADSDBTDT,CANNUM=S30454,SYS=XXXX,ABNSTEP='AD
15JUN,13:43:06,OPSS0034,S ADPIR,CANJOB=ADSDBTDT,CANNUM=S30454,SYS=XXXX,='ADSDBTDT. ',ERR1=S0C3,UNQNUM=A30454,ERR2=U0000
15JUN,13:43:06,OPSS0034,S ADPIR,CANJOB=ADSDBTDT,CANNUM=S30454,SYS=XXXX,ABNSTEP='ADSDBTDT. ',ERR1=S0C3,UNQNUM=A30454,ERR2=U0000
15JUN,13:43:06,OPSOSF ,.PROBRPT05082 ENDING FOR IEF450I ADSDBTDT
15JUN,13:43:06,OPSS0034,OPS3092O READY
15JUN,13:43:06,DUMPSRV ,IEF196I IGD17070I DATA SET OPSDUMP.D210615.T134305.OPSOSF.S00001
15JUN,13:43:06,DUMPSRV ,IEF196I ALLOCATED SUCCESSFULLY WITH 4 STRIPE(S).
15JUN,13:43:06,DUMPSRV ,IEF196I IGD17395I DATA SET OPSDUMP.D210615.T134305.OPSOSF.S00001
15JUN,13:43:06,DUMPSRV ,IEF196I WAS NOT ALLOCATED IN THE SAME STORAGE FACILITY IMAGE
15JUN,13:43:06,DUMPSRV ,IEF196I BECAUSE NO SFI HAD SUFFICIENT PRIMARY VOLS FOR STRIPING
15JUN,13:43:06,DUMPSRV ,IEF196I IGD101I SMS ALLOCATED TO DDNAME (SYS00002)
15JUN,13:43:06,DUMPSRV ,IEF196I DSN (OPSDUMP.D210615.T134305.OPSOSF.S00001 )
15JUN,13:43:06,DUMPSRV ,IEF196I STORCLAS (MSDUMPSC) MGMTCLAS (STANDARD) DATACLAS
15JUN,13:43:06,DUMPSRV ,IEF196I (MSDUMPDC)
15JUN,13:43:06,DUMPSRV ,IEF196I VOL SER NOS= DUMP1F,DUMP1E,DUMP12,DUMP11
Release : 14.0
Component : OPS/MVS
Abend was the result of an issue with third party software in the customer environment. OPS/MVS was not responsible for the dump, which revealed it is executing code in ECSA owned by ADSDBTDU when it incurred the S0D6 abend ADSDBTDU.
The recommendation is to contact the involved 3rd party software company.