|
Abend Code |
Explanation |
|---|---|
|
1000 |
An operation exception was detected. Contact Technical Support at http://ca.com/support immediately. |
|
3000 |
There is a lock on the SCDS. The previous execution of CA SMF Director started to update a series of related records and either was not properly terminated, or another job was running concurrently and had the SCDS lock when the abended job wanted it. To recover, see message CAF0555A. |
|
3001 |
See message CAF2412I. |
|
3002 |
The SMF MANn file was not successfully cleared or the verification was unsuccessful. Rerun CA SMF Director and if it fails again, take the action described in message CAF2101T. |
|
3003 |
A primary history file could not be opened for a configuration with substreams. The dump fails and no index entries are added to the SCDS. Review any preceding error messages and the JOBLOG, and update your configuration accordingly. All primary history files must be opened correctly in order to successfully process a dump for a configuration with substreams. |
|
3010 |
See message CAF2405I. |
|
3020 |
See message CAF2101T. |
|
3030 |
Severe error occurred while reading a history file. See the CA SMF Director Audit Trail for error messages that will explain in detail the error that occurred. |
|
4000 |
Internal error condition. Contact Technical Support at http://ca.com/support immediately. |
|
4001 |
All of the Internal Storage Management area has been used up. No CSA space had been available from a prior GETMAIN, so internal storage was being used. Increase region size and rerun the job. |
|
4002 |
When generating a formatted dump, a recursion error occurred. There should be sufficient information in the dump for CA to diagnose the error. For assistance, contact Technical Support at http://ca.com/support. Have the dump available. |
|
4003-4 |
Internal error conditions. Contact Technical Support at http://ca.com/support immediately. |
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |