PH62802: RECOVERY FROM THE "INSUFFICIENT MEMORY" CONDITION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customers may encounter the "Insufficient Memory", or
  "out-of-storage", condition while working with Optim.
  
  Possible scenarios include, but are not limited to, creating a
  Row List (Point and Shoot) file or Browsing or Editing DB2 data.
  
  The OoS condition may not be properly detected causing random
  errors or Optim termination with the error:
  
  $HASP310 JOBnnnnn TERMINATED AT END OF MEMORY
  

Local fix

• Increase the REGION size or limit the number of rows being
  etched.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Optim users.                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: See Error Description.                  *
  ****************************************************************
  General statements:
  1. There always will be limits on the amount of data Optim can
  process.
  2. Especially, for tables with LOB and XML columns, there is a
  limit on the number of rows Optim can fetch, for PNS processing
  or Edit/Browse, because DB2 limits the number of LOB locators
  which can be active in any given Unit of Work.
  3. Once the "out-of-storage" condition (OoS) occurs, Optim may
  not be able to terminate cleanly and the ISPF session should not
  be used anymore.
  A re-LOGON is required to clean up the environment.
  4. The TRACE output documenting the OoS may not appear, see the
  "Error starting the Error Trace, rc=-1" message, when the lack
  of memory prevents Optim from loading required modules or open
  the TRACE file.
  
  Optim should detect and deal with OoS in a reasonable matter.
  

Problem conclusion

• Optim processing will be improved.
  
  The following scenarios should be handled by Optim as follows:
  
  1. The Edit/Browse and Row List (PNS) processing may be affected
  by shortage of memory. Optim may detect such and issue the
  following message:
  
  FOPK029K: INSUFFICIENT MEMORY TO FETCH DESIRED NUMBER OF ROWS.
  REDUCED FETCH SET SIZE
  with the following associated Help panel FOPT29K:
  +  There is insufficient memory to fetch all the rows in the
     Fetch set.  This is probably due to the fact that the row
     length for this table is large.  Access has fetched a reduced
     number of rows in order to allow them to fit in memory.
     This can be noted by the reduced row count displayed.
     You should be aware that you may be very close to exhausting
     memory, and therefore may encounter problems later in the
     edit or browse session. The REGION size may need to be
     increased.
     This error may be caused by having LE ANYHEAP/HEAP parameters
     enforcing storage being allocated BELOW the line. This
     significantly lowers the amount of storage available for
     processing. Consider changing LE parameters to allow for
     AHYHEAP/HEAP ANYWHERE.
  
  2. The Edit/Browse and Row List (PNS) processing may be affected
  by DB2 limits on the number of active LOB locators. Optim may
  detect such and issue the following message:
  
  FOPK064A: FETCH ROW LIMIT REDUCED TO PREVENT DB2 FAILURE FROM
  EXCESSIVE LOBS HELD
  
  3. A general "out-of-storage" condition, not specific to the
  ones described above, may cause an Optim System Error, producing
  an output similar to the following:
  
  Insufficient Memory on 2024/08/14 14:33
  
  Optim encountered shortage of virtual memory and processing will
  be terminated. The REGION size may need to be increased.
  The minimum recommended REGION size is 64MB in general, or 220MB
  when the ODPP functions are being used during processing.
  The actual storage requirements depend on the complexity of the
  processing scenario and the number of tables and table rows
  being fetched (in Edit or Browse).
  Extended ISPF sessions may cause the DB2 object information to
  accumulate in memory
  This error may be caused by having LE ANYHEAP/HEAP parameters
  enforcing storage being allocated BELOW the line.
  This significantly lowers the amount of storage available for
  processing. Consider changing LE parameters to allow for
  ANYHEAP/HEAP ANYWHERE in such scenarios.
  
  and
  
  An Internal System Error has Occurred on 2024/08/14 14:34
  
  Insufficient memory
  DB2Rel=1215(NFM), Rel=11.7.0
  Code=-2, AuxInfo=
  01  FOPSMCEL 20240813 PH62420  (000472) MemCellAllocEntry
  02  FOPDBLD  20180619 COPYSENT (000278) LDM_BldIns
  ...
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• FOP00003 FOP00103 FOP00203 FOP00303 FOP00B   FOP01B   FOP05B
  FOP07B   FOP08B   FOP09B   FOP0AB   FOP0BB   FOP0ITKA FOP1ODRV
  FOP1OSFN FOP3DTPR FOP4IPMN FOP4PEMN FOP4PMMN FOP4TRCE FOP9APIM
  FOP9GINF FOPAM00  FOPCFPMN FOPCXLIB FOPHSTM  FOPIO    FOPK00
  FOPK09   FOPK12   FOPMADDE FOPMAFCN FOPMAIN  FOPMAMAI FOPMARCN
  FOPMCDRT FOPMCENU FOPMCMAI FOPMCOFN FOPMCOLA FOPMCOLP FOPMDBMN
  FOPMDDDL FOPMDMAI FOPMDPRC FOPMDXTR FOPMECMN FOPMEMAI FOPMIXMM
  FOPMMCMN FOPMMCMR FOPMMJBS FOPMMUNU FOPMMUTL FOPMSELM FOPMTMDB
  FOPMUXIM FOPODPP  FOPOMN   FOPRS10  FOPRS8   FOPTC717 FOPUMCBT
  FOPUUNLD FOPVOU   FOPZFBMN FOPZFMMN FOPZMAIN FOPZSUB
  

Fix information

• Fixed component name

  OPTIM MOVE FOR

• Fixed component ID

  5655V0700

Applicable component levels

• RB70 PSY UI98445

     UP24/09/17 P F409

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.