ISPF messages

This reference section provides detailed information about the error messages that are issued by IMS Network Compression Facility. The technical information in this section can help you troubleshoot and diagnose IMS Network Compression Facility problems.

APPC and IMS address space messages

Messages issued to the MVS syslog from either APPC address spaces or the IMS control region address space are documented in the ISPF interface. Option M on the Primary Options Menu screen (Figure 1) provides access to descriptions of all such error messages.

Using the ISPF message facility

To obtain more information about a message, display a list of the messages and then select the one for which more information is desired.

Enter option M on the Primary Options Menu screen (Figure 1) to obtain a list of product messages. An example of the resulting message display is shown in the following figure:

Figure 1. Message Table screen (List Messages)

---------------- IMS Network Compression Facility Message Ta Row 1 to 17 of 64             
Command ===>                                                    Scroll ===> CSR             
                                                                                            
Select a message to display additional information about that message.                      
                                                                                            
CMD Message ID Message Text                                                                 
--- ---------- --------------------------------------------------------------               
    CFN1001E   ERROR ENCOUNTERED ON xxxxxxxx RC=yyyyyyyy                                    
    CFN1020E   GETMAIN FAILED IN IMS NETWORK COMPRESSION FACILITY APPC PROGRA               
    CFN1021I   FREEMAIN FAILED IN IMS NETWORK COMPRESSION FACILITY APPC PROGR               
    CFN1022E   ERROR ENCOUNTERED ON xxxxxxxx RC=yyyyyyyy                                    
    CFN1042I   IMS NETWORK COMPRESSION FACILITY INITIALIZATION SUCCESSFUL                   
    CFN1043I   IMS CTL RGN U4002 ABEND DUE TO INIT ERROR=ABEND                              
    CFN1044I   IMS NETWORK COMPRESSION FACILITY INITIALIZATION FAILED-RESTART               
    CFN1045I   INVOKING USER SPECIFIED DFSPPUE0 EXIT ROUTINE xxxxxxxx                       
    CFN1046E   IMODULE LOAD FOR USER SPECIFIED DFSPPUE0 EXIT ROUTINE xxxxxxxx               
    CFN1061E   CFNINRTN RECEIVED INVALID DIRECTORY ADDRESS                                  
    CFN1062W   CFNINRTN RECEIVED AN INVALID RPL                                             
    CFN1063W   CFNINRTN RPL REQUEST BYTE OF 00 FOUND                                        
    CFN1064W   OPNDST ERROR: RPL DID NOT HAVE A NIB                                         
    CFN1065W   OPNDST ERROR: RPL HAD AN INVALID NIB                                         
    CFN1066E   CFNINRTN HAD NO IMS CFN SAVE SETS AVAILABLE                                  
    CFN1067W   CFNINRTN RPLREQ xx UNKNOWN                                                   
    CFN1080E   GETMAIN FAILED FOR LU BLOCK

Selecting a specific message number provides additional information about that message. Entering an S in the CMD column selects a message and provides the following example message description:

Figure 2. Messages screen (Sample message description)

------------------ IMS Network Compression Facility Messages ------------------            
 Command ===>                                                                               
                                                                                            
 Message ID: CFN1001E                                                                       
 Message Text: ERROR ENCOUNTERED ON xxxxxxxx RC=yyyyyyyy                                    
                                                                                            
 Explanation: This is an APPC communication error. The "xxxxxxxx" field                     
 identifies the APPC command being processed, and the "yyyyyyyy" field                      
 identifies the return code received from APPC. This error occurred on the                  
 local side (where the TSO user is logged on).                                              
 Module: CFNAPPC0                                                                           
 System Action: The request is aborted.                                                     
                                                                                            
                                                                                            
                                                                                            
 Programmer Response: Determine if APPC is available on both the local MVS                  
 system as well as the remote MVS system (where the target IMSID is brought up).            
 If there are no indications of APPC problems, contact IBM Software
                    Support for           
 assistance.

Message format

Error messages received when using the ISPF interface are designed to be self-documenting. Pressing PF1 (or the help PF key) when an error message occurs provides a description of the error as well as information on what to do to resolve the problem.

ISPF error message identifiers have the format CFNAnnn or CFNBnnn, where nnn is a three-digit message number. ISPF message identifiers are only present in the long version of an ISPF message. To retrieve the long version of an IMS Network Compression Facility message, press the help key (PF1) when a short error message is displayed.

IMS Network Compression Facility runtime messages adhere to the following format:

CFN[A|B]nnn

Where:

CFN[A|B]: Indicates that the message was issued by IMS Network Compression Facility
nnn: Indicates the message identification number

Each message also includes the following information:

Variable text: The variable text appearing next to the message identifier is the short message text.
Explanation:: The Explanation section explains what the message text means, why it occurred, and what its variables represent.
System action:: The System action section explains what the system will do in response to the event that triggered this message.
Programmer response:: The Programmer response section describes whether a response is necessary, what the appropriate response is, and how the response will affect the system or program.