Checklist for isolating the problem

Determine whether the error occurred as a result of an ISPF panel or a module. ISPF handles its own error conditions and displays them directly on the panel. If the error message appears in your IPCS output, it is probably issued from a formatted dump module.
If you submit your job using JCL, verify that no JCL errors are issued. If a bad return code is issued, determine whether it is a result of the JCL job or a formatted dump module.
If you receive the message Storage access failed for xxxxxxxx, browse the dump to determine whether the actual location exists in the dump. Storage requests are usually in terms of the length of the control block. For example, if control block BB is X'20' bytes long, the storage service will be trying to retrieve X'20' bytes of data.
View the output to determine whether any error messages were issued during execution.Messages may indicate the cause of the termination.
If the VTAM® formatted dump routine cannot access a field (either in the control block or in the chain of pointers to the control block), an abend will occur and a note of the condition is made on the dump output.
Check whether the required ISPF and IPCS maintenance has been applied as documented in the program directory. Check whether maintenance has been applied to IPCS, ISPF, or VTAM. If any of these are down-level, unpredictable results might occur.
If your ISPF prompt lists or PF keys are not working properly, see z/OS Communications Server: New Function Summary to ensure that everything is installed and concatenated properly.