The system status for this client has been reset to "Start".
Reason: The system status for this client has been set to "Stop".
Explanation: Periodically checked Events have a check time for the next check. If automatic processing is stopped, current Events are not processed. After the activation of automatic processing, check times are re-calculated without an Event being triggered. &01 = Event object &02 = RunID
Start the Agent with the ServiceManager's dialog program if it is not active.
&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 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
Explanation: The attribute GR_MAX_PAR_JOBS defines the maximum number of tasks that my run parallel within a Group. It may be changed with the script element :PUT_ATT or in the group monitor. &01 = User object &02 = Old value &03 = New value
Explanation: The script of this task was being processed when the Server was stopped; it was not finished then. The Server was started in 'cold' mode, hence script processing may not be continued. Solution: Refer to the detail info to see the line where the script was interrupted. Check if the script had already modified UC4 variables and correct them. More detailed information is available in the activation log. Afterwards, you may cancel the task or restart it required. &01 = Name of the object &02 = RunID
Explanation: Send e-mails to users with the script element "SEND_MAIL" or activate the corresponding Notification option.
Make sure that the e-mail connection has been realized correctly: * The Agent must be started with a valid user. Enter the user's name and password in the dialog program of the ServiceManager. * Write a valid mail profile in the INI file of the Agent (Section [MAIL]).
Explanation: At least one wildcard character must be specified in order to select files to be sent. Valid wildcard characters are '*' and '?'. To create a new file name, the target file name also requires the character '*'. The part of the file name that is represented by wildcard characters replaces the asterix in the target-file name. Example: from: C:\temp\test*.txt to: e:\temp\work*.sav selected files: C:\temp\testfile1.txt C:\temp\testfile2.big.txt These files are created: E:\temp\workfile1.sav E:\temp\workfile2.big.sav
Explanation: At least one wildcard character must be specified in order to select files to be sent. Valid wildcard characters are '*' and '?'. To create a new file name from the existing one, the target file name also requires the character '*'. The part of the file name that is represented by wildcard characters replaces the asterix in the target filename. Example: from: C:\temp\test*.txt to: e:\temp\work*.sav selected files: C:\temp\testfile1.txt C:\temp\testfile2.big.txt These files are created: E:\temp\workfile1.sav E:\temp\workfile2.big.sav
Explanation: The connection between Server and Agent was interrupted when the canceling command was sent to the Agent. As the connection could not yet be re-established, it is not clear whether or not the command has reached the Agent and if it could be processed. Solution: Increase the time delay for the restart (Parameter RestartDelay in the Server's INI file) or reduce the Agent's reconnection time interval (Parameter connect= in the Agent's INI file). These measures cause the Agent to be immediately reconnected to the Server after a Server restart.
Explanation: After sending the E-mail command to the Agent, the connection between Server and Agent was interrupted. As the connection could not yet be re-established, it could not be clarified whether or not the command has reached the Agent and if it could be processed. Solution: Increase the time delay for the restart (Parameter RestartDelay in the Server's INI file) or reduce the Agent's reconnection time interval (Parameter connect= in the Agent's INI file). These measures cause the Agent to be immediately reconnected to the Server after a Server restart.
Explanation: &01 = User object &02 = Previous task status &03 = New task status
An internal error occurred. Please contact our support team.
All tasks that are currently active in the client are also set to "Stop".
Stopped tasks can be continued.
An internal error occurred. Please contact our support team.
An internal error occurred. Please contact our support team.
FileTransfer '&01' (RunID:'&02') was not started because source-file name ('&03') contains wildcard characters.
Explanation: There are several possible reasons: * No login object was selected in the task. * The selected login object has been deleted or renamed meanwhile. &01 = Login object &02 = Job object &03 = RunID of the Job
The particular Agent object has been deleted meanwhile. Restore it from the Recycle Bin or select another Agent in the login object.
Possible reasons: * No login object was selected in the task. * The selected login object has been deleted or renamed meanwhile. &01 = Login object &02 = RunID of the FileTransfer &03 = FileTransfer object
Explanation: Check the particular Login object. It contains no Login data for the selected Agent.
Explanation: Enter the adequate Login object for source and destination of the data transfer in the "FileTransfer" tab. &01 = FileTransfer object &02 = RunID
Explanation: A minimum event interval can be set in the UC4 variable UC_SYSTEM_SETTINGS using the entry MIN_EVENT_INTERVAL. It is used when a value below this minimum value has been specified in an Event. &01 = Event object &02 = RunID &03 = Number of minutes for the corrected value
Explanation: The UC4 Server cannot handle this acknowledegment. Perhaps the Agent converted it incorrectly. &01 - Content of acknowledgement &02 - Hexadecimal acknowledgement &03 - Name of the Agent &04 - RunID of the job &05 - Name of the job &06 - End status of the job
Explanation: An internal error occurred. Please contact our support team.
Solution: Select different Agents for the data transfer source and destination. &01 = FileTransfer object &02, &03 = Agent object
Explanation: Execution details are available in the statistical overview. Open the selective statistics and enter the RunID in the "Status/RunID" tab.
Explanation: When a restart point is used, just a part of the task is processed. Therefore, the runtime does not correspond to that one of a regular execution, but will usually be shorter. The minimum runtime is not checked in these cases in order to avoid useless alarms. &01 = Object name &02 = RunID
Explanation: An escalation time was set but the Notification of type 'message' will not escalate. The escalation time was deleted from this task. &01 = Notification object &02 = RunID
Explanation: Processing is canceled because a different work process has modified this RunID in the meantime. No action is required.
Explanation: The user has changed the Job's generated JCL. This is possible in the Activity Window using the command "Open Generated Job". &01 = User object