The following occurs whenever CAS9 is run:
$HASP100 CAS9 ON STCINRDR
IEF695I START CAS9 WITH JOBNAME CAS9 IS ASSIGNED TO USER CAS9
$HASP373 CAS9 STARTED
ACF9CCCD USERID CAS9 IS ASSIGNED TO THIS JOB - CAS9
IEA045I AN SVC DUMP HAS STARTED AT TIME=13.17.50 DATE=01/15/2018 402
FOR ASID (0018)
ERROR ID = SEQ00041 CPU00 ASID003D TIME18.104.22.168
QUIESCE = NO
IEA794I SVC DUMP HAS CAPTURED: 403
DUMPID=002 REQUESTED BY JOB (CAS9 )
DUMP TITLE=SMF ABEND, ERRMOD=IEFU86, RECVMOD=IEEMB830
I have SMF set to NOACTIVE in SMFPRMxx, so I am mystified as to how IEFU86 is involved.
Surprisingly, CAS9 does continue to successful completion. But I of course would like to eliminate
an unnecessary SVC dump.
WHY DO I HAVE A SVC DUMP AT CAS9 STARTUP?
It seems that you didn't apply the support for CA Common Services 14.1 and PTFS for z/OS 2.3 compatibility:
CA Common Services for z/OS 14.1:
Fix Category: CA.TargetSystem-RequiredService.z/OS.V2R3
Resource Initialization Manager (CAS9E10)
RO93293 RO94935 RO95015
CAMASTER/CA-SERV COMMON SERVICE (CEI0E10)
I encourage you to apply all these PTFs to be full compatible with z/OS 2.3 and get rid of this kind of problems.
You can check the compatibility matrix for z/OS 2.3 support at the url: