We recommend switching to the latest versions of Edge, Firefox, Chrome or Safari. Using Internet Explorer will result in a loss of website functionality.

#UOCF014 : The system failed to find any run for cycle cycle_number in the most-recent-run control entity control_entity_name.
#UOCF006 : The system failed to create a cycle because control data instances for the cycle ID {0} already exist.
#ULAY025 : The system failed to open the URL specified_URL.
#ULAY016 : The system failed to delete layout layout_name. There are total_number_of references that refer to this layout list_of_references.
#ULAY007 : The system failed to generate fields because class class_name could not be found.
#ULAY006 : The XML schema has more than one root element.
#ULAY005 : The XML schema has no root element.
#ULAY003 : The system failed to find valid COBOL source code to process
#UOCF014 : The system failed to find any run for cycle cycle_number in the most-recent-run control entity control_entity_name.
#UOCF006 : The system failed to create a cycle because control data instances for the cycle ID {0} already exist.

#UOCF014 : The system failed to find any run for cycle cycle_number in the most-recent-run control entity control_entity_name.

Sathish Ramegowda

February 11, 2020 04:05
Updated

Probable Cause: Your control entity generates a run number based on the most recent run number of another control entity. However, the second control entity does not have any control data for the generated cycle number above, so the system cannot infer a run number.

Resolution: Review the executions of the second control entity to determine why control data does not exist and run control points as necessary. Alternately, rerun this control point with cycle and run overrides.

Comments

0 comments

Please sign in to leave a comment.

Articles in this section

Related articles