BTSQ messages are issued by CA Endevor SCM when you use the Build Type Sequence utility. This section details these messages along with possible causes and corrective actions to take in error situations.
Reason:
See previous error messages for actual error.
Action:
Contact CA Technical Support if you cannot resolve the problem.
Action:
Contact CA Technical Support if you cannot resolve the problem.
Reason:
The allocated memory is insufficient.
Action:
Increase the region size of the job and then rerun the job. If problem still occurs, contact CA Technical Support.
Reason:
Memory problem.
Action:
If the error text indicates lack of memory, increase the region size and re-run the job. If it is not a memory problem, call CA Technical Support.
Reason:
An open error occurred against an internal temporary work file.
Action:
Check the job output for any relevant messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
A write error occurred on an internal temporary work file.
Action:
Check the job output for any relevant messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
An error occurred while closing the internal work file.
Action:
Check the job output for any relevant messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
Sort failure occurred on internal work file.
Action:
Check the sort result information and any other output sort related error messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
An error occurred while opening the internal work file.
Action:
Check the job output for any relevant error messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
Memory problem.
Action:
Increase the job's region size and re-run the job. Contact CA Technical Support if the problem continues.
Reason:
An error occurred while opening the type sequence file for output.
Action:
Check the job output for any relevant messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
A read error occurred on the temporary internal work file.
Action:
Check the job output for any relevant messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
A write error occurred on the type sequence file.
Action:
Check the job output for any relevant messages. If the problem cannot be resolved, contact CA Technical Support.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|