Messages U110xx

[U00011000][U00011001][U00011002][U00011003][U00011004][U00011005][U00011006][U00011007][U00011008][U00011009][U00011010][U00011011][U00011012][U00011013][U00011014][U00011015][U00011016][U00011017][U00011018][U00011019][U00011020][U00011021][U00011022][U00011023][U00011024][U00011025][U00011026][U00011027][U00011028][U00011029][U00011030][U00011031][U00011032][U00011033][U00011034][U00011035][U00011036][U00011037][U00011038][U00011039][U00011040][U00011041][U00011042][U00011043][U00011044][U00011045][U00011046][U00011047][U00011048][U00011049][U00011050][U00011051][U00011052][U00011053][U00011054][U00011055][U00011056][U00011057][U00011058][U00011059][U00011060][U00011061][U00011062][U00011063][U00011064][U00011065][U00011066][U00011067][U00011068][U00011069][U00011070][U00011071][U00011072][U00011073][U00011074][U00011075][U00011076][U00011077][U00011078][U00011079][U00011080][U00011081][U00011082][U00011083][U00011084][U00011085][U00011086][U00011087][U00011088][U00011089][U00011090][U00011091][U00011092][U00011093][U00011094][U00011095][U00011096][U00011097][U00011098][U00011099]
U00011000 '&01' (RunID: '&02') could not be started on '&03'. See next message.

Explanation: An error occurred while starting a task. The error will be explained in the next message. Solution: Analyze the next message, remove the error and re-activate the ProcessFlow if required. &01 = Object name &02 = RunID &03 = Agent object
U00011001 Possible program error, please report to development if displayed regularly: Host: '&02' is reporting the status of inactive job '&01'. Msg: '&03'
U00011002 Job '&01' (RunID '&02') on Host '&04' ended normally. &05&06 &07&08
U00011003 Job '&01' (RunID '&02') on Host '&04' aborted (return code='&05'). &06&07 &08&09
U00011004 FileTransfer '&01' (RunID '&02') ended normally.
U00011005 FileTransfer '&01' (RunID '&02') ended abnormally.
U00011006 Job '&01' (RunID '&02' / Workflow-RunID: '&03') on Host '&04' ended normally. &05&06 &07&08
U00011007 Job '&01' (RunID '&02' / Workflow-RunID: '&03') on Host '&04' ended abnormally (return code='&05'). &06&07 &08&09
U00011008 FileTransfer '&01' (RunID: '&02' / RunID: '&03') ended normally.
U00011009 FileTransfer '&01' (RunID: '&02') inside workflow with RunID: '&03' ended abnormally.
U00011010 Cannot find Workflow '&01' for deactivation.
U00011011 Cannot find object with RunID '&01' (for '&02').
U00011012 Runtime modification for runtime monitoring: NEW values: Task: '&01' (RunID: '&02'), method: '&03', maximum: (fixed value: '&04', time: '&05', ERT: '&06') minimum: (fixed value: '&07', ERT: '&08'), execute: '&09'

&03 Method SECONDS Maximum runtime as fixed value TIME Maximum runtime as date and time ESTIMATED_RUNTIME Maximum runtime as ERT CANCEL In the 'else' case occurs, it should be canceled START_OBJECT In the 'else' case the object which is displayed by 'execute' should be started JP_OVERWRITES The modified MRT/SRT settings will be used SHORTEST_RT_SECOND Minimum runtime as fixed value SHORTEST_RT_ESTIMATED_RT Minimum runtime as ERT
U00011013 Job '&01' (RunID '&02' / Workflow RunID '&03') on Host '&04' has disappeared. &05&06 &07&08
U00011014 Job '&01' (RunID '&02') on Host '&04' has disappeared. &05&06 &07&08
U00011015 Processing of Event '&01' (RunID: '&02') was terminated with an error. See following message:

Explanation: An event was recognized and the event handling was started. While processing this event an error occurred. The error will be explained in the following message. Possible reasons: * An error was recognized in the script. *The script was aborted with :STOP on purpose.
U00011016 Cannot find Workflow '&01'.
U00011017 Checking all activities for host: '&01'.
U00011018 Host: '&02' is reporting status for inactive FT: '&01'.
U00011019 '&01' is reporting FileTransfer status '&04' for FileTransfer '&02' ('&03').
U00011020 '&01' is reporting job status '&04' for job '&02' (RunID '&03'). Job-status number: '&05' DB: '&06'
U00011021 Host '&01' is not active!

Explanation: The Agent selected for this task is not active. Check its status in the System Overview. You may restart it from the System Manager's dialog program. &01 = Agent object
U00011022 Client '&04': The status of '&01' ('&02') is undefined because host '&03' aborted prematurely or was canceled.
U00011023 Workflow '&01' could not be found at function '&02'.
U00011024 Group '&01' (RunID: '&02') ended normally.
U00011025 Group '&01' (RunID: '&02' / Workflow RunID: '&03') ended normally.
U00011026 '&01' is not in 'noted' status. Cannot delete.
U00011027 Registration '&01' ('&02') was deleted by user '&03'.

Explanation: The task is canceled with ENDED_CANCEL. Get further information from the corresponding statistical record. &01 = Name of the object &02 = RunID &03 = User object
U00011028 It is not possible to deactivate group '&01' because it is not active.
U00011029 Group '&01' ('&02') was canceled by user '&03'.

User: &01 = Group object &02 = RunID &03 = User object
U00011030 Checking group/waiting queue '&01'...
U00011031 '&01' tasks are running in group/waiting queue '&02'. '&03' are allowed.

Explanation: The maximum number of tasks to be processed parallel can be specified in the Group object. If this number is exceeded, a queue is formed in which they are processed one after the other. &01 = Number of the group's currently active tasks &02 = Group object &03 = Maximum number of objects
U00011032 Starting waiting queue '&01'.
U00011033 Group/waiting queue '&01' is currently inactive.
U00011034 Group/waiting queue '&01' is not in the 'ACTIVE' status. EH status = '&02'.
U00011035 No action for client: '&01', object: '&02', RunID: '&03', status: '&04' required.
U00011036 Cannot find task '&02'/'&03'/'&01' at function 'END OF TASK'.
U00011037 Event '&01' (RunID: '&02') ended normally.

Explanation: &01 = Event object &02 = RunID
U00011038 Event '&01' (RunID: '&02' / RunID: '&03') ended normally.
U00011039 Event '&01' (RunID: '&02') ended abnormally.
U00011040 Event '&01' (RunID: '&02' / Workflow-RunID: '&03') ended abnormally.
U00011041 Event '&01' (RunID: '&02') was in status 'active' when the Server's/Host' was started. It will be set to status 'sleeping' and rechecked.

Explanation: An Event that should be checked periodically was active when the UC4 Server or Agent was closed. Hence, the Event was not completely processed. Its status is reset and then the Event is re-checked. It might happen that some activities are processed twice. &01 = Event object &02 = RunID
U00011042 Event '&01' (RunID: '&02') was terminated by user '&03'.

Explanation: &01 = Event object &02 = RunID &03 = User object
U00011043 Activating event '&01' (RunID: '&02' ).

Explanation: &01 = Event object &02 = RunID
U00011044 '$01'
U00011045 Processing of Event '&01' (RunID: '&02') on Host '&03' was terminated with an error. See next message:

Explanation: An Event was recognized and Event handling was started. An error occurred while processing this Event. The error will be explained in the next message. Possible reasons: * An error was recognized in the script. * The script was aborted with :STOP on purpose &01 = Event object &02 = RunID &03 = Agent object
U00011046 Invalid value ('&01') of Variable UC_JOB_CHECKINTERVAL. Value 60 is assumed for this case.

Explanation: We recommend using a value between 10 and 60 for the periodical check of tasks.
U00011047 Starting task '&01' (RunID: '&02').

Explanation: &01 = Name of the object &02 = RunID
U00011048 Client '&01', Event '&02', RunID '&03', status '&04': Filters of Console Event are re-sent to the Agent. Counters for Windows and OS400 have been reset.
U00011049 Cannot find task with RunID('&01') for CANCEL!

Explanation: The task to be canceled is no longer active. &01 = RunID
U00011050 Cancel/Quit of task '&01' (RunID '&02') not possible because it is not in a cancelable status.
U00011051 User '&03' initiated CANCEL for '&01' (RunID: '&02').
U00011052 Client '&01', Event '&02', RunID '&03', status '&04': Filters of the automatic File Event are re-sent to the Agent. Counters for Windows and OS400 have been reset.
U00011053 Job '&01' (RunID '&02' / Workflow RunID: '&03') on Host '&04' terminated with CANCEL. &05&06 &07&08
U00011054 Job '&01' (RunID '&02') on Host '&04' terminated with CANCEL. &05&06 &07&08
U00011055 FileTransfer '&01' (RunID '&02' / Workflow RunID: '&03') ended with CANCEL
U00011056 FileTransfer '&01' (RunID '&02') ended with CANCEL.
U00011057 Client '&01', Event '&02', RunID '&03' has been set from status: 'CHECKING' to 'SLEEPING'.
U00011058 Invalid message: '&01'

Explanation: Received a message that partly contains incorrect information. Invalid data is neither assumed nor corrected. Inform the UC4 support team.
U00011059 Client '&01', Queue Manager '&02', RunID '&03', status: '&04' is re-sent to the Agent in order to keep running.
U00011060 Combination not supported: Notification = '&01' / Message = '&02'.
U00011061 Notification '&01' (RunID '&02') was already accepted.

Explanation: If several users were specified for receiving messages from a Notification of type "Alarm", the particular person who accepts the alarm is responsible. &01 = Notification object &02 = RunID
U00011062 Notification '&01' (RunID '&02') was acknowledged by a different user: '&03'.
U00011063 Client '&01', Report '&02', RunID '&03', status '&04' is restarted.
U00011064 Notification '&01' (RunID '&02') was rejected by a different user: '&03'.
U00011065 Notification '&01' (RunID '&02') ended normally.

Explanation: &01 = Notification object &02 = RunID of the Notification
U00011066 Notification '&01' (RunID '&02' / Workflow RunID: '&03') ended normally.

Explanation: &01 = Notification object &02 = RunID of the Notification &03 = RunID of the Workflow
U00011067 Notification '&01' (RunID '&02') a b o r t e d .
U00011068 Notification '&01' (RunID '&02' / Workflow RunID: '&03') aborted.
U00011069 Notification '&01' (RunID '&02') was aborted by escalation.

Explanation: None of the users to be informed have acknowledged the Notification. Therefore, it is ended with status ENDED_ESCALATED and a different Notification that has been specified in the "Operator" tab will be started. &01 = Notification &02 = RunID
U00011070 Notification '&01' (RunID '&02' / Workflow RunID: '&03' was aborted by escalation.

Explanation: None of the users to be informed have acknowledged the Notification. Therefore, it is ended with status ENDED_ESCALATED and a different Notification that has been specified in the "Operator" tab will be started. &01 = Notification object &02 = RunID of the Notification &03 = RunID of the Workflow
U00011071 User '&01' is internally informed via the UserInterface.

Explanation: The user is informed via a Notification object. &01 = User object
U00011072 Transmission of message to user '&01' canceled.

Explanation: The Notification is closed for this user because * a different user responded to the request with Yes or No * a different user acknowledged the alarm * the Notification was canceled &01 = User object
U00011073 User '&01' has accepted the Alarm type Notification.

Explanation: The user has accepted the Alarm type Notification. &01 = User object
U00011074 User '&01' has rejected the Notification (Alert: Reject, Request: No).

Explanation: The user has rejected the Alarm type Notification. &01 = User object
U00011075 No user found. Notification '&01 ('&02')' will be escalated.

Explanation: The Notification ended with status ENDED_ESCALATED.
U00011076 User '&01' has accepted the Notification (Alert: Done, Request: Yes, Message: OK).

Explanation: The user accepts the Notification: - Message type with ok - Request type with yes - Alarm type with done &01 = User object
U00011077 ABEND received from user '&01'.

Explanation: The user responded to the request-type Notification with no. &01 = User object
U00011078 Changing Notification status of user '&01'. ('&02' -> '&03')

Explanation: The Notification's status may change in the following cases: * The Notification escalates because none of the users has reacted to it within the period of time specified in the "Operator" tab of the Notification object. * Due to the defined Calendar conditions, none of the users would be informed. Hence, a message is sent to all users. &01 = User object &02, &03 = Status
U00011079 Notification will be escalated because of runtime expiration.

Explanation: The users have not reacted to the Notification within the period of time specified in the "Operator" tab of the Notification object. Hence, the Notification ends with status ENDED_ESCALATED and the escalation Notification is started.
U00011080 Inform user '&01'.

Explanation: The user is informed that the user who originally accepted the alarm now rejects the Notification. &01 = User object
U00011081 Schedule '&01' (RunID '&02') ended normally.

Explanation: &01 = Schedule objectt &02 = RunID
U00011082 Schedule '&01' (RunID '&02' / Workflow-RunID: '&03') ended normally.
U00011083 Schedule '&01' (RunID '&02') aborted.
U00011084 Schedule '&01' (RunID '&02'/Workflow RunID: '&03') aborted.
U00011085 Schedule '&01' (RunID '&02') was terminated by user '&03'.

Explanation: &01 = Schedule object &02 = RunID &03 = User object
U00011086 Schedule '&01' (RunID '&02') starting ...

Explanation: &01 = Schedule object &02 = RunID
U00011087 Task '&01' will not be activated (indicated by active identifier).
U00011088 Task '&01' does not start because the scheduled start time lies before the start time of '&02'.
U00011089 Task '&01' starting ...

Explanation: &01 = Object name
U00011090 Task '&01' is now active (RunID '&02').

Explanation: &01 = Object name &02 = RunID
U00011091 Task '&01' (RunID '&02') ended.

Explanation: &01 = Name of the object &02 = RunID
U00011092 Period turnaround takes place for Schedule '&01' (RunID '&02').

Explanation: The period turnaround defines at what time a new period should start. If required, modifications to the Schedule object may be assumed at period turnaround. Tasks start once within a period. &01 = Schedule object &02 = RunID
U00011093 Cannot start task '&01'. See following message.

Explanation: &01 = Object name
U00011094 Task '&01' is not activated due to the specified Calendar settings.

Explanation: The particular Calendars and their keywords are noted in the tab of the same name. &01 = Name of the object
U00011095 End of task '&01' (RunID '&02') will be ignored. Its status in the Schedule is not active or preparing. Status = '&03' / RunID = '&04'.
U00011096 Start of task '&01' (RunID '&02') will be ignored. Invalid task status in the Schedule. The correct status should be preparing. Status = '&03' / RunID = '&04'.
U00011097 The Automiation Engine was inactive at the planned checking time of Event '&01'(RunID '&02'). A new time will be calculated.

Explanation: Periodically checked Events have a pre-defined time for their next check. When the Automation Engine starts, it verifies if there are active Events whose next check would lie in the past. In such a case, a new check time is calculated.&01 = Event object&02 = RunID
U00011098 Automatic processing has been stopped. The status of '&01' will be changed to 'stopped'.

Reason: The system status for this client has been set to "Stop".
U00011099 Event for RunID '&01' ('&02') is ignored because automatic processing has been stopped.

Reason: The system status for this client has been set to "Stop".