How to resolve a Subsystem Analyzer PSA0302 DATASTORE DATASET IS FULL message (by creating a new, bigger Datastore).

Article Id: 17468
Status: Published
Updated On: 14-02-2018 08:05
Legacy Id: TEC617536
Products:
CA RC/Migrator , CA Endevor SCM Interface , DB2 Administration , CA RC Compare for DB2 for z/OS , CA RC Extract for DB2 for z/OS , CA RC/Query , CA RC Secure for DB2 for z/OS , CA RC Update for DB2 for z/OS , CA Bind Analyzer for DB2 for z/OS , CA SQL-Ease for DB2 for z/OS , CA Sysview Performance Management Option for DB2 for z/OS , CA Database Detector for DB2 for z/OS , CA Plan Analyzer for DB2 for z/OS , CA Subsystem Analyzer for DB2 for z/OS , CA Database Analyzer for DB2 for z/OS , CA Fast Unload for DB2 for z/OS , CA Fast Check for DB2 for z/OS , CA Fast Index for DB2 for z/OS , CA Fast Load for DB2 for z/OS , CA Rapid Reorg for DB2 for z/OS
Issue/Introduction:

Description:

This document explains how you can resolve a Subsystem Analyzer PSA0302 DATASTORE DATASET IS FULL message by creating a new, bigger Datastore.

Solution:

The following steps can be taken to create a bigger Datastore and resolve a PSA0302 DATASTORE DATASET IS FULL message:

  1. If you're using the Datastore to run a collection, stop the collection

  2. Create a new, Temporary datastore. You can use the PSADSALC Batch job. A sample of it can be found in <High.Level>.CDBASRC. Or, you may choose to use the SS Analyzer Create Datastore Display. This screen can be accessed by:

    1. Choosing Option 4 (Initialize SSID collection) from the Subsystem Analyzer Main Menu

    2. Setting the Create Datastore ==> prompt to 'Y' on the Initialize SS Analyzer Collection screen

  3. In your <High.Level>.CDBASRC, you'll find a member named PSADSCPY. Use this job to copy your Old Datastore into your Temporary Datastore

  4. Select option 2 on the CA-Subsystem Analyzer Main Menu (SSID historical interval data). Verify that the data on the Temporary Datastore looks OK. If so, delete your Old Datastore

  5. Re-create your old Datastore. If possible, allocate it in an Extended Addressability (EA) SMS class. This will enable your Datastore dataset to span across multiple volumes if your Datastore Dataset exceeds the 4 Gig VSAM limit

  6. Using the PSADSCPY 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 your Temporary Datastore

  8. Restart your collection.

Environment:

Release:
Component: PSA