Even with SYSTEM SNAPS enabled, LOG DATABASE in sysgen and OPT00176 OFF (to get SVC dumps instead of system snaps written to log), message IEC130I CDMSLOGA DD STATEMENT MISSING always appears when an SVC dump is requested in addition to the messages that indicate an SVC dump has been requested.
Example:
IEC130I CDMSLOGA DD STATEMENT MISSING
IEA794I SVC DUMP HAS CAPTURED: 115
DUMPID=014 REQUESTED BY JOB (IDMSCV01)
DUMP TITLE=IDMSSYS# 00075 TASKID# 09621011
Release: All supported releases.
At Routing System Snaps to a Sequential File, the following is documented:
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 set up as described above, an SVC dump will be taken, but the CDMSLOGA file will be opened and the following written to it:
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, the SVC dump will be taken, but the above three lines are written to CDMSLOGA only if multitasking is in use.
In a unitasking CV, the same messages will be written to the LOG DATABASE.
This is a planned design that when multitasking is enabled, dumps are written (if OPT00176 on) to CDMSLOGA and not to the database. In unitasking, if OPT00176 is on, a system snap will be written to the log which is not recommended as the log is a single threaded resource and 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 define the CDMSLOGA DD in startup JCL to suppress it.
The SVC dump is written regardless and is not affected by the fact that the CDMSLOGA DD is not defined.