Attempting to dynamically refresh the DMCL with DCMT VARY DMCL NC results in this abend:
IDMS DC021004 V1 T557 12157AFA TASK:DCMT; LOAD OF IDMSDMCL FAILED--WOULD NEVER FIT IN POOL
The dc-log (OLP) has these messages:
IDMS DC021004 V1 T557 12157AFA TASK:DCMT; LOAD OF IDMSDMCL FAILED--WOULD NEVER FIT IN POOL
IDMS DB347034 V1 T557 Not enough storage to #LOAD module IDMSDMCL
IDMS DB347019 V1 T1 IDMSDMCL module not found - R15 return code X'14'
Release: All supported releases.
The process of varying the DMCL new copy requires that the new DMCL load module be loaded into a program pool for the purpose of comparing it to the existing DMCL. This will be the XA REENT pool or the XA PROG pool depending on whether the new DMCL was linked RENT or NORENT.
The error message means that the new DMCL is too large to fit in the pool.
Increase the size of the relevant pool (see SYSTEM Statement).
Use IDMSLOOK on the DMCL to determine the new size (note, even in CV mode, an IDMSLOOK of the DMCL will load and report on the DMCL from the STEPLIB specified in the JCL, not the one in the currently executing CV):
//LOOK EXEC PGM=IDMSLOOK,REGION=0M
//STEPLIB DD DISP=SHR,DSN=IDMS.CV01.DBA.LOADLIB
// DD DISP=SHR,DSN=IDMS.CV01.CUSTOM.LOADLIB
// DD DISP=SHR,DSN=IDMS.CV01.CAGJLOAD
//SYSCTL DD DISP=SHR,DSN=IDMS.CV01.SYSCTL
//SYSIPT DD *
DMCL
//SYSIDMS DD *
ECHO=ON
LOCAL=OFF
DMCL=IDMSDMCL
//SYSPCH DD SYSOUT=*
//SYSLST DD SYSOUT=*
...IDMSLOOK - OPSYS=z/OS Version 19.00.07
DMCL
DMCL=IDMSDMCL Runtime Size---> 0C4A8 (50,344 Bytes)
This DMCL uses dbtable IDMSDBTB Compiled Size---> 0735C (29,532 Bytes)
...