Even though we have SYSTEM SNAPS enabled, LOG DATABASE in sysgen and OPT00176 OFF (to get SVC dumps instead of System snaps written to log), we always see IEC130I CDMSLOGA DD STATEMENT MISSING when an SVC dump is requested in addition to the messages that indicate an SVC dump has been requested.
IEC130I CDMSLOGA DD STATEMENT MISSING
IEA794I SVC DUMP HAS CAPTURED: 115
DUMPID=014 REQUESTED BY JOB (IDMP75DB)
DUMP TITLE=IDMSSYS# 00075 TASKID# 09621011
In the SYSTEM OPERATIONS GUIDE there is the following:
System snaps are routed to a sequential log file in a multitasking environment. The system snaps are routed even when you have directed the log to the data dictionary DDLDCLOG area in the system definition."
Here is some additional info to clarify:
If the CV is running with multitasking and you are setup as described, we will take the SVC dump, but we also open the CDMSLOGA file and write out
the following 3 message lines:
IDMS-CV/DC VERSION nnn LOG
IDMS DC009001 Vnnn Tnn A SYSTEM SNAP HAS BEEN REQUESTED VIA SVC DUMP SERVICES
IDMS DC009002 Vnnn Tnn DUMP IDENTIFICATION IS:IDMSSYS# nnnnn TASKID# nnnnnnnn
If OPT00176 is OFF, we will take the SVC dump but also put those 3 lines out to CDMSLOGA only if the MT is on.
In unitasking CV, the same messages will be written to the LOG DATABASE.
This is a planned design that when MT is enabled, we write dumps (if OPT00176 on) to CDMSLOGA and not to the database . In unitasking if OPT00176 is on, we will
write to the LOG, which is not recommended as the log is a single threaded resource and also System snaps are very large and would quickly fill the log, as well as not being very useful in problem diagnosis.
The IEC130I CDMSLOGA DD STATEMENT MISSING can be ignored or you can define the CDMSLOGA DD in startup JCL if you do not want to see this.
The SVC dump is written regardless and is not affected by the fact that the CDMSLOGA DD is not defined.
SYSTEM OPERATIONS GUIDE - Extended Addressing and Multitasking