ABMG


    Explanation
      The user has requested a basic mapping support (BMS) service that was not specified at system generation, or at initialization.

    

    System action
      The transaction is abnormally terminated with a CICS transaction dump.

    

    User response
      Correlate services requested against options specified in the system generation of BMS.

      Follow this procedure:

      
        
          Scan the trace table for the transaction ID that issued the abend. If this is CSPQ (page cleanup), module DFHTPQ abnormally terminated because a message purge delay of zero has been specified and CSPQ has been entered via a terminal. The message purge delay is specified in the PRGDLAY of the DFHSIT macro, and its value can be found in SITPRGD.

        

        
          Scan the trace table for the last BMS request (code 'FA'). Use the option bytes at the start of the failing module to see if the requested functions have been generated. For example, paging may have been requested, but standard or minimum BMS was specified in the SIT.

        

        
          If the BMS request is compatible with the BMS options in the CICS system generation, some incompatible suffixing amongst BMS modules must have occurred. This can happen if the DFHSIT macro specified individual suffixes for the BMS modules.

        

      

      The following modules differ between standard and full-function BMS:

      
        DFHMCP

        DFHRLR

        DFHPBP

        DFHTPP

      

    

    Module
DFHMCP, DFHTPQ

Applicable releases in Version 6
  
  
    
      beta

      6.3

      6.2

      6.1