How to resolve a Detector PDT0113 DATASTORE DATASET IS FULL message creating a larger datastore.

Products

• Subsystem Analyzer for DB2 for z/OS
• Detector for DB2 for z/OS

Issue/Introduction

How to resolve a Detector for Db2 for z/OS (PDT) PDT0113 DATASTORE DATASET IS FULL message by
creating a larger datastore.

Resolution

The following steps can be taken to create a larger Detector datastore resolving  a
PDT0113 DATASTORE DATASET IS FULL message:

1. If using the Detector datastore during an active collection, stop the collection
2. Create a new, temporary datastore. Use the PDTDSALC batch job where a sample can be found in <hlq>.CDBAJCL.  You may also
   choose to use the DETECTOR Create Datastore Display. This screen can be accessed by choosing Option 7 (Create/Initialize datastore)
   from the Detector Main Menu
3. In your <hlq>.CDBAJCL, locate member named PDTDSCPY. Use this job to copy your old datastore into your temporary datastore
4. Select option 2 on the Detector Main Menu (SSID historical interval data). Verify that the data on the temporary datastore looks OK.
   If so, delete your old datastore
5. Recreate the old Detector datastore. If possible, allocate it in an Extended Addressability (EA) SMS class.
   This will enable your datastore dataset to span across multiple volumes if the datastore dataset exceeds the 4 Gig VSAM limit
6. Using the PDTDSCPY job, copy your temporary datastore into the datastore that you created in step 5
7. Verify that the data on the new datastore looks OK. If so delete the temporary datastore
8. Restart the Detector collection