CPU loop with DATASHARING
Article ID: 129968
Updated On: 03-25-2019
Products
IDMS
IDMS - Database
IDMS - ADS
Issue/Introduction
An IDMS CV using datasharing may enter into a CPU loop. The CV has to be cancelled and restarted.
The following messages may also be seen on the IDMS DC log:
DC015007 Pool <pool-number>: SOS condition <condition-number>, SZ=<request-size>, T=<taskcode>, P=<progname>
DC050016 Table-Search was unable to get storage to (re)build an index for an internal table. and DC027007 TASK: <task-code> PROG: <program-name> ABENDED WITH D002
The DC015007 message may reference pools 255 and 0.
The following messages may also be seen on the IDMS DC log:
DC015007 Pool <pool-number>: SOS condition <condition-number>, SZ=<request-size>, T=<taskcode>, P=<progname>
DC050016 Table-Search was unable to get storage to (re)build an index for an internal table. and DC027007 TASK: <task-code> PROG: <program-name> ABENDED WITH D002
The DC015007 message may reference pools 255 and 0.
Environment
CA IDMS, with datasharing, all supported releases.
Cause
Insufficient 31-bit z/OS storage available to satsify a GETMAIN (STORAGE OBTAIN) request when IDMS needs to expand an internal BNVI table index.
Resolution
Test APAR ST07788 is available for this symptom.
If ST07788 is required now, please open a support issue.
If ST07788 is required now, please open a support issue.
Feedback
Yes
No
Powered by
