Troubleshooting the PDX
The following table lists some common problems you may encounter when using the PDX utilities and provides some tips to resolve these problems.
Problem | Tip |
|---|---|
PDX format failed. | Ensure that the primary extent of the space allocation is at least as large as the number of directory tracks the PDX is expecting to format. The entire directory must be contained in the first extent. |
A PDX member is enqueued. | If an active job enqueuing the member cannot be found, run the PDX Dequeue utility (DBUXCLRO, member DBUPDXCL in the sample library). Otherwise, wait until the active job releases the member. |
The PDX is unusable due to corrupted data (abends 990 and 938). | If this happens repeatedly and the PDX is used in a multi-CPU environment, ensure that the PDX is properly registered with the enqueue manager software. |
The PDX is out of space. | Ensure the report set limit option is in force for all products (for POINTER CHECKER PLUS, this is MAXSETS). If it is, a PDX reorganization or reallocation is necessary. |
Messages indicate the PDX is out of space, but the PDX Allocate and Format panel shows space is available. | This indicates a probable directory error. Run the PDX Reorganization utility (DBUPDXRP, member DBUPDXRP in the sample library) with PARM='REORG', and check the reports to see if any bad blocks remain. |
Jobs go into a wait state trying to access the PDX. |
|
The PDX was moved to a different device type and now it is inaccessible ( PDX Open fails). | Use IEBGENER to copy the restored file to a device of the original type. Or use the PDX Unload/Reload utilities (DBUNLOAD and DBURLOAD, member DBUPDSUN in the sample library) to move the file to the new device. |
Related topic