Steps for reviewing a storage problem

Determine whether a storage problem is related to common, private, or CSM storage.

Perform the following steps:

1. Issue D TCPIP,,STOR and D Net,CSM,Ownerid=All commands to track storage usage.
2. Determine whether a lot of application data is accumulated on the queues for TCP connections. See Steps for reviewing data on the queue if you are using IDS.
3. Look in the system log for messages related to storage.
4. Run the EREP program against the SYS1.LOGREC log and review software records, looking for any storage-related abends.
5. Review the messages and abends you found to determine whether they indicate a common, private, or CSM storage problem.
6. Review your storage settings for any identified problem area (for example common, CSM, or private storage).
7. Compare your current storage usage to your previous usage. If usage has increased, do you know of any situations that would cause increased usage (for example, new applications that use common storage or increased connections)?
8. Review your response to step 6. Can the storage problem be resolved by increasing your storage limits?
9. If you have a dump that was created as a result of the storage problem, proceed to step 11.
10. If no dump was taken, see Collecting documentation to submit to the IBM Support Center before proceeding to step 9. If you are unable to obtain a slip or console dump of the problem, a stand-alone dump may be the only method to gather documentation for the IBM® Support Center. See z/OS MVS Diagnosis: Tools and Service Aids to determine how to take a stand-alone dump.
11. Call the IBM Support Center for assistance in reviewing the documentation.