CMAC - messages and codes display

Use CMAC to display information about CICS® messages and codes.

To use the CMAC transaction:
  • Add the DFHCMAC group on the CICS system definition file (CSD) to your initialization list (DFHLIST).
  • Add the data set name of the CICS messages file to the definition of the DFHCMACD file within the DFHCMAC group.
    Note: The DFHCMACD file is not updated by PTFs that are applied to CICS. For the latest message updates, see the descriptions in CICS messages.
This transaction is not valid for the MVS console and the information is available only in English.
You start the transaction by typing one of the following commands:
  1. CMAC
  2. CMAC abcd where ‘abcd’ is the abend code.
  3. CMAC xxxx where ‘xxxx’ is the message number only.
  4. CMAC yyxxxx where ‘yy’ is the component id and ‘xxxx’ is the message number.
  5. CMAC DFHxxxx where ‘xxxx’ is the message number.
  6. CMAC DFHyyxxxx where ‘yy’ is the component id and ‘xxxx’ is the message number.

If you use method 1, you get the display shown in Figure 1.

Figure 1. CMAC transaction: initial screen
 DFHCMC01              Display On-line Messages and Codes


 Type the required message identifier, then press Enter.



      Component ID ===>  (for example, TC for Terminal Control
                                       FC for File Control, etc.)
                         This field is required for Messages in the
                         form DFHxxyyyy, Where xx is the Component ID.

      Message Number =>  (for example, 1060, 5718, or Abend Code
                         such as ASRA, etc.)









 F3=Exit to CICS

You tell CICS which message you want by typing the component ID and the message number. If the message does not have a component ID, leave that field blank.

The display then gives information under the headings:

Explanation
An explanation of the cause of the message.
System action
The actions the system is taking.
User response
What actions you can or cannot take.
Destination
Where to see the message. This can be the console, the user terminal, or a transient data queue.
Module
The name of the module that is reporting the error.
For example, to display information about message DFH5130, which does not have a component ID, type: 
CMAC 5130

You get the following display:

Figure 2. CMAC transaction: first example screen
   DFH5130   UNABLE TO LOCATE MODULE DFHCICS.  PRIMARY
             CSD NOT INITIALIZED.
   EXPLANATION:  The DFHCICS module is missing from the library.
   SYSTEM ACTION:  Processing of the INITIALIZE command is
   terminated.
   USER RESPONSE:  Ensure that the DFHCICS module is present in
   the library.
   DESTINATION:  SYSPRINT
   MODULE(S):  DFHCSDUP
   F3=CANCEL

To display the message CE3528, type a component ID of CE and a message number of 3528. You get the following display:

Figure 3. CMAC transaction: Second example screen
   DFHCE3528 Signon failed during SECLABEL checking.


   EXPLANATION:   The signon request has failed because the
   external security manager (ESM) detected a critical error.

   SYSTEM ACTION:  The signon transaction terminates.

   USER RESPONSE:  Refer to message DFHSN0108 on the CSCS log
   for the information and actions necessary to resolve this
   problem.

   DESTINATION:  Terminal End User

   MODULE(S):  DFHSNP






   F3=CANCEL

If you use methods 2 - 6, the initial screen is bypassed and you move directly to the message information screen.