IDMS DB347002 subschema cannot be loaded because of insufficient storage

Products

• IDMS

Issue/Introduction

Received message in the log

DB347002 Vnnn Tnnnn <ssname> subschema cannot be loaded because of insufficient storage

But the message does not indicate which Pool should be increased nor the amount of storage required to load the subschema load module.  

Environment

all IDMS environments 19.0 or later

Resolution

  Subschemas generated into a dictionary load area (DDLDCLOD) are Reentrant, Amode ANY and Rmode ANY, so if that is where it is being loaded from it would go to XA REENT pool.

  If it is being loaded from a loadlib, it depends on how the DBA link edited it, but typically it would be the same (Reentrant, Amode ANY, Rmode ANY).  

 *  If the abending Task Code is defined as LOCATION BELOW  then even if the SS load module is Reentrant and RMODE ANY, IDMS CV will try to load it into the 24-bit Reentrant pool.  There is no reason for a user-defined task to be defined LOCATION BELOW.   They should be LOCATION ANY.

  The Size of the SS load module can easily be determined depending on where it resides.  Opsys Loadlib display commands will show the size of the SS load module and in IDD you can DISPLAY LOAD MODULE ssname  and it will show the size.

DCMT D ALL PRO POOL  will show the pool sizes as well as the amount currently used and the High Water Mark of storage used in the pool

Example

      D ALL PRO POOL                                                           
    Pool      Address     Size     Space      HWM      Prog      Prog     Loads 
                                   Alloc              in pool   in use   to pool
  PROGRAM    00297000      100K        0K        0K        0         0        0 
  REENT      002B0000      848K      433K      433K       38         3       38 
  XA PROG    4073F000     1000K        0K       68K        0         0        3 
  XA REENT   40839000    17604K    12990K    12990K      226        40      226