This message was issued in an IDMS system migrated from 16 to 18.5 in testing. :
IDMS DC016100 64-bit storage obtain (segments=0x0000000000000002)
failed. R15=0000000C, R0=00002100
What should be checked in IDMS system to determine why it is trying to use extended addressing ?
IDMS all supported releases
This is usually caused when the CV's DMCL specifies the use of MEMORY CACHE for one or more files.
MEMORY CACHE replaced DATASPACE specification as of 16.0.
By default, IDMS will try to allocate the file in a 64-bit Memory Cache.
If this fails we will try to allocate a 31-bit Dataspace. If that fails the file doesn't
get cached.
Either 64-bit memory is not available at all or it is limited by the opsys parameter MEMLIMIT, so that the file(s) accessed by the jobs in
question cannot cache the file in 64-bit memory.
This can be seen in an IDMSLOOK report DMCL ALL.