PM48900: RECEIVE INSUFFICIENT STORAGE MESSAGE WHEN VIEWING/EDITING A DB2 TABLE MULTIPLE TIMES. AFTER MULTIPLE ITERATIONS, RECEIVE S0C4.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Using FM/DB2, a combination of viewing, editing, and using
  3.4 to edit a DB2 table (without making changes to the
  table) are done when insufficient storage message is
  received. Message is persistent until user logs off TSO and
  back on.  After repeating a similar combination of activities,
  an abend 0C4 is received.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of File Manager DB2 component.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using the FM/DB2 editor multiple   *
  *                      times, receive "insufficient storage"   *
  *                      message.  After multiple iterations     *
  *                      receive ABENDS0C4.                      *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  There are multiple factors that contribute to this problem.
  1.  The minimum recommended TSO region size for FM/DB2 users is
      4 MB.  Storage related problems, particularly in the FM/DB2
      editor and/or object list utility are more likely with TSO
      region sizes of 8MB or less.
  2.  The reported problem scenario includes multiple ISPF split
      screens/logical sessions.  Each additional ISPF logical
      session reduces the amount of below the line storage
      available for FM/DB2 and other applications.
  3.  The FM editor is reserving 1MB of below the line storage for
      emergency use in the event of problems editing large files,
      however this storage is not required for an FM/DB2 editor
      session.  This 1MB of storage is shared between any FM/DB2
      editor sessions (such as occurs with ISPF logical sessions)
      and reduces the available amount of below the line storage,
      making short on storage conditions more likely with small
      TSO region sizes.
  4.  The problem scenario occurs after the "insufficient storage"
      message has been received multiple times.  Analysis suggests
      that the ABEND occurs in ISPF, possible because of memory
      fragmentation.
  

Problem conclusion

• File Manager has been updated to reduce the below the line
  storage usage by 1MB, when using the FM/DB2 editor.  This will
  reduce - but not eliminate - the incidence of storage related
  problems when using small TSO region sizes and multiple ISPF
  logical sessions.
  

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

• FMN0LVL  FMN2LVL
  

Fix information

• Fixed component name

  FILE MANAGER Z/

• Fixed component ID

  5655W4700

Applicable component levels

• RB10 PSY UK74673

     UP11/12/15 P F112

• RB12 PSY UK74677

     UP11/12/15 P F112

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.