IBM CICS Transaction Server for OS/390 SC33-1686-02 - Manual (Page 247)

CMAC—messages and codes display
Chapter 18. CMAC—messages and codes display
Use CMAC to give you individual message information as
provided in the
CICS Messages and Codes manual.
To use the CMAC transaction:
Add the DFHCMAC group on the CICS system definition
(CSD) file 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.
For information about how to carry out these actions, see the
CICS Resource Definition Guide manual.
Notes:
1. This transaction is not valid for the MVS console.
2. The information is available only in English.
You start the transaction by typing one of the following:
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 162.
DFHCMC 1 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, 1 6 , 5718, or Abend Code
such as ASRA, etc.)
F3=Exit to CICS
Figure 162. CMAC transaction: initial screen
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
end-user terminal, or a transient data queue.
Module
The name of the module reporting the error.
For example, to display information about message
DFH5130, which does not have a component ID, type:
CMAC 513
You get the following display:
DFH513 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
Figure 163. CMAC transaction: 1st example screen
To display the message CE3528, type a component ID of CE
and a message number of 3528. You get the following
display:
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 DFHSN 1 8 on the CSCS log
for the information and actions necessary to resolve this
problem.
DESTINATION: Terminal End User
MODULE(S): DFHSNP
F3=CANCEL
Figure 164. CMAC transaction: 2nd example screen
 Copyright IBM Corp. 1982, 1999 229