CMFDMS87 and change to MEMLIMIT

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.




    CMF MONITOR for OS/390


    Recently upgraded from CMF MONITOR v6.0.00 to v6.2.00 and now getting the following message in the CMF Analyzer:

    +CMFDMS87 (IN SODMHIPE) Unable to create a Memory Object - MEMLIMIT 0001610M - requested 0004096M
    IEF450I E411KIPC JS010 - ABEND=S000 U0100 REASON=C8C9D7C5



    In CMF MONITOR v6.1.00 there were Analyzer changes to take advantage of 31 and 64 bit storage.  See below description:

    CMF Analyzer support for 31-bit storage

    In prior releases, CMF Analyzer ran as a 24-bit mode application, which limited the number of reports and the amount of data that could be processed. In version 6.1, the Analyzer runs in 31-bit mode and can handle an increased number of reports and a higher volume of data. It uses a 4G Memory Object for DMSS storage instead of DASD or Hiperspace. If required, you can also specify a larger Memory Object.

    There are new JCL PARM parameters that you can use to manage the storage. The default value for these parameters have already been set. The CTRLSIZE parameter is now obsolete (and ignored without error if specified) and replaced with the STACK and LOWSTACK parameters, with defaults of 16M and 64K respectively, which should eliminate the need to specify them in most cases. You will have to modify these values only when the Analyzer JCL or installation defaults limit the REGION size to less that 32M and the MEMLIMIT to less that 4G.

    The SHIFT Analyzer control statement supports up to 288 time pairs, which allows a full 24 hours to be reported on in 5-minute intervals. The previous limit of 96 would be limited to 15 minute intervals for 24 hours.

    The Analyzer can now create Transaction Dumps (IEATDUMP) in place of the previously formatted SNAP dumps when it encounters certain errors.

    To see the full Release Notes, click here:

     Please update the batch job JCL increasing the MEMLIMIT parameter to “MEMLIMIT=4G” to assist in eliminating the error.  

    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles