The most common reason for this is that the pool was actively being changed during the dumping process, producing a "blurred picture" of this part of the dumped system. Storage overlays and storage missing from a dump may also produce indeterminate cells.
Establishing categories of cells is done before processing the cells themselves, and an optional report may be formatted that identifies data areas used to manage the cell and data extracted from those data areas.
RUNCPOOL optionally displays each cell.
RUNCPOOL cpid-general-value
[ ASID(asid) ]
[ DATABLKS | NODATABLKS ]
[ USED | NOUSED ]
[ INDETERMINATE | NOINDETERMINATE ]
[ AVAILABLE | NOAVAILABLE ]
[ EXEC((clist|rexx-exec|subcommand)) ]
[ SUMMARY | NOSUMMARY ]
-------- SETDEF-Defined Parameters -------------------------
Note: You can override the following SETDEF parameters.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]
The RUNCPOOL subcommand generates a return code that consists of its own return code plus the return code from the CLIST, REXX exec, or IPCS subcommand designated on the EXEC parameter. If the CLIST, REXX exec, or IPCS subcommand returns with a serious condition, RUNCPOOL processing ends with the current control block.
The RUNCPOOL subcommand generates a return code that consists of its own return code plus the return code from a CLIST, REXX exec, or IPCS subcommand if designated by the EXEC parameter. If the CLIST, REXX exec, or IPCS subcommand returns with a serious condition, RUNCPOOL processing ends with the current control block.