DFHME0106 applid Module modname could not be loaded. REGISTER 1 = X'nnnnnnnn' and REGISTER 15 = X'nnnnnnnn'
Explanation
The message language module modname could not be loaded. The reason that it could not be loaded is given by the contents of registers 1 and 15, which are returned by MVS.
System action
If the missing module is not the default language module, CICS uses the default language for messages.
If the default language module is missing, a return code is sent to the domain manager and CICS is terminated.
An exception entry is made in the trace table and a dump is taken, unless you have specifically suppressed dumps in the dump table. As this may not be a critical problem, CICS is not terminated unless the default language module cannot be loaded (even if you have specified terminate in the dump table).
Message DFHME0116, which contains the symptom string for this problem, is produced.
User response
If the default language is in operation and this is acceptable, you need not bring CICS down, or you may do so at some convenient time.
If the default language is in operation and this is not acceptable, or if the default language module itself is missing, consult the MVS messages and codes manual to check the return codes displayed in the message. The return codes indicate why the module could not be loaded.
Module
Destination
Console